B2V Restore Issue
Hello Guys, I am having a problem trying to restore a Full backup set from a VM with an agent onto an EXSI host. Below are the steps that I have done and I will also be including the screen shots of the job selection, backup options, and error message that I am getting below. Any help would be greatly appreciated. Things I have done so far. 1. Inventory and Catalog the tape. 2. Made sure what I want to restore is on those tape. 3. Select Convert to Virtual from a Point in Time 4. Select the appropriate backup options and attempt to run the job.
BackupExec2010R3 can't restore virtual machine(Vmware)
Hi: We are using Symantec BackupExec 2010 R3 backup virtual machine(Vmware), We can successfully backup the vmware server. but can't restore it, I'm using Vmware redirection when restore the server, and input Vcenter and ESX server name, then click "Browse vCenter and ESX servers for destination button", Backup software jump out a error message, Could not connect to the Vmware virtual center or ESX server, please verify the credential supplied for login. BTW, All servers are joinin same domain. Could you please someone can give some advice? thanks
After converting to VMWare MS SQL won't start
Hello, maybe someone can help me. After full backup of Windows 2008 R2 server (with MS SQL) we duplicated (I mean P2V convert) it to VMWare. But then we started converted server the MSSQL instances didn't start (we have two). In log file I have found that there was problems with permissions. 2014-04-25 08:36:54.17 spid7s Starting up database 'master'. 2014-04-25 08:36:54.18 spid7s Error: 17204, Severity: 16, State: 1. 2014-04-25 08:36:54.18 spid7s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLLAIKINAS\MSSQL\DATA\master.mdf for file number 1. OS error: 5(failed to retrieve text for this error. Reason: 15100). 2014-04-25 08:36:54.18 spid7s Error: 5120, Severity: 16, State: 101. 2014-04-25 08:36:54.18 spid7s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLLAIKINAS\MSSQL\DATA\master.mdf". Operating system error 5: "5(failed to retrieve text for this error. Reason: 15105)". 2014-04-25 08:36:54.18 spid7s Error: 17204, Severity: 16, State: 1. 2014-04-25 08:36:54.18 spid7s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLLAIKINAS\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(failed to retrieve text for this error. Reason: 15105). 2014-04-25 08:36:54.18 spid7s Error: 5120, Severity: 16, State: 101. 2014-04-25 08:36:54.18 spid7s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLLAIKINAS\MSSQL\DATA\mastlog.ldf". Operating system error 5: "5(failed to retrieve text for this error. Reason: 15105)". Same error on both instances. It looks like after convert all files in DATA directory looses its initial permissions. DATA directory has Full control permission for SQLServerMSSQLUser$... group but all files in it don't. Maybe someone has solution. Here is info about servers: For backup we use Sym BE 2012 SP4 SQL Server: Windows 2008 R2, MS SQL 2008 R2 Standart joined to AD Thanks in advance.
CASO Optimised Deduplication Convert to Virtual failure if connection to MMS is lost
WE have a Optimised Deduplication setup CAS - Jobs are setup and run from this server to local storage MMS - Local storage CAS manages all jobs, Backups run on MMS server to local dedup storage, then duplicates to CAS deduplication storage. SDR files are located on both servers When attempting to convert to Virtual we are requested to restore from CAS or MMS, CAS is selected. When the communication between the CAS and MMS is established, all convert jobs run successfully. When communication is dropped, these converts fail.Inside the job setup, the Conversion settings options dissapear (ie, CPU, mem etc....) Strange though this never worked in SP1,SP2. Worked fine in SP3, but after upgrade to SP4 this stopped working again.SP4 was required as SP3 was unable to restore GPT drives. The reason we doing this and have this setup is for DR purposes, so if the client premises were to burn down wee have all the backed up data sitting at a DR site. In this scenario, the MMS sserver would no longer be available. Appreciate any assistance.Convert to virtual from Point-In-Time failed 0xe000846a
Dear All, I need help. Our environment: Source server - physical server Windows 2003 SP2, Basic disk (not dynamic) - partitioned to C: E:, SQLExpress. Media server - Windows 2008 R2, Hyper-V role,BackupExec 2012 SP3, NAS connected via iSCSI Destination- Virtual Machine on Media server We are trying to migrate physical server to Hyper-V Virtual Machine using BackupExec 2012. First i made full backup to disk of Source machine - SDR on - successfull. Then convert to virtual machine from Point-In-Time. Selected Point-In-Time: C:,E:, System State, SQLExpress Convert to Virtual - Options - Conversion settings: In Virtual machine options field on Disk Configuration tab we have only one drive (Disk 0 Boot, System, Dynamically Expanding) - is it correct - Source machine has C and E? Job Completion status: Job ended: Tuesday, January 28, 2014 at 10:47:36 PM Completed status: Failed Final error: 0xe000846a - The resource could not be restored because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-33898 Errors: Duplicate- 02s012.san.com Unable to attach to \\02s012.san.com\E:. V-79-57344-33898 - The resource could not be restored because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer. On Media Server in Hyper-V manager - new Virtual machine is created. On disk we have Virtual machine configurations files and one *.VHD file. Virtual machine is starting but only with System drive C: I'm thinking about restore drive E: from full backup to virtal disk connected to destination virtal machine. ButI am not sure if this convertion (only system) will be working fine. I would like to resolve this issue with your help. Many thanks for your help. Szymon
Successful Full Backup Failure to Convert to Virtual VM (Error: 0xe000a400)
HI, I am trying to convert a Successful Full SDR backup of a Windows 2003 server to a VMware virtual machine but I am receiving the below error: Completed status: Failed Final error: 0xe000a400 - Failed to create the standby virtual machine required for warm conversion. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-41984 I have clicked the the link and searched on google for answers but the all answers refer to Hyper-V and I cannot see them being relevant to VMware. I know the VM host username and password credentials are correct as it can find the host when I am pointing the conversion to it. Any help would be very much appreciated. Thanks Dan
Error Converting to Virtual Machine
Hi everyone, When i try to convert a backup to a virtual machine, i get this error, "Failed to create the standby virtual machine required for warm conversion", in some forums, they says "This canoccur when the System Logon Account on the media server doesn't have permissionson the Hyper-V server. If for instance the Media Server and Hyper-V server being converted are on different domains." but the user 's logon belongs to Domain Admins and backupoperator groups. Im using Backup Excec 2012 Running on Windows 2008 server R2. I hope you can help me.
Installing BE on Hyper-V
I was wondering if someone can point me to a good document on how to go about installing BE on a Microsoft 2008 R2 Hyper-V host. The host server has of course the Hyper-V host, as well as four other virtual machines (Exchange, Terminal Server, SQL, as well as just a file server). I would like to find a document that talks about actual installation and best practices. Thank you for your help.