01-14-2013 07:59 AM
Hi,
Just upgraded to Backupexec 2012. Chose to upgrade because of virtualization capability of the product that I can use specially in DR. Problem is when doing a B2V to a remote Hyper-v server it fails. The job runs for some time and always hangs after processing 20.6 GB of data. Any help is appreciated.
01-14-2013 11:56 AM
...any alerts that are pending?
01-14-2013 12:08 PM
Nope. here is the error I got.
Job server: RC-SVR01
Drive and media mount requested: 1/11/2013 5:01:48 AM
Source Drive and Media
Drive and media information from media mount: 1/11/2013 5:01:49 AM
Performing a verify operation to make sure that media can be read after the backup has completed is recommended.
Destination Set
Backup set #1: ""
01-14-2013 12:20 PM
Does that E:\ drive exist and it isn't an RDM disk is it?
01-14-2013 01:21 PM
E:\ drive is present in the physical server and not RDM disk (I am using Windows 2008R2 Hyper-V server). I tried to convert to VM using the c drive and system state under selections but the result is still the same.
My environment
domain controller/ BE server 2012 (windows 2008 Std R2)
Hyper -V server (windows 2008 Std R2) - installed remote agent for windows
First I was not sure where to get vmguest.iso since it can't be found in BE server. What I did is copied vmware.iso from c:\windows\system32 from remote Hyper V and copied it to c:\windows\system32\ of BE server. Is this ok? Hyper-V server is using basic disks. Not sure what else I am missing.
01-14-2013 07:09 PM
Create a test VM with only a C: drive, back it up and try the B2V to see what happens.
01-17-2013 07:15 AM
result is same. I dont know if backupexec 2012 supports converting windows 2008 backup sets to virtual to remote Hyper -V server. I dont want to install hyper V in my DC/backupexec server locally. please help
01-17-2013 06:29 PM
Conversion to Hyper-V is supported.
I would suggest that you open a support case with Symantec for them to take a look at this problem.