Restoring Images to Hyper-V

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 7

Hello Folks

Sorry for the long post but hopefully it will be worth it.

Is there anyone else out there trying to restore images created with Backup & recovery 10 to a Windows 2008 Server with Hyper-V role installed and configured?

I have had my head in this for the last two weeks and to be honest havent made much progress. I have been speaking to a 2nd line support guy at Acronis, to be fair he has been very good but I get the impression from him I am at the cutting edge and I am the only person that has tried to do this which surely cant be the case.

Anyway, here is what I am doing:

I am imaging 4 physical servers with Backup & Recovery 10. These images are then spooled to a USB drive. My plan is to load these images into the recovery server (running Windows Server 2008 with the Hyper-v role installed) as virtual machines in the event of a DR scenario.

Here are the issues I have encountered:

Now I know that we can convert the images to VHD files (more about that later) however I simply want to create a blank virual machine, boot it with the Acronis Universal Restore ISO file and then run through the recovery process. This all works to the point where I start the recovery and the issue is that I get no progress indicator or success (of failure) notification. The thing is, it does actually work, if I cancel the task (after leaving it for ages) and then reboot the virtual machine the recovered server does actually boot.

My guess as to why this happening is that in order to get the Acronis Universal Restore enviroment to recognise the USB drive you need to first put it "offline" in Windows disk management so that you can then effectively add the drive to the virtual machine settings. I think this is called "pass-through" in virtualisation language.

Acronis said they tested a similar scenario to mine above in which they got the progress indicator and succesful task completion - the difference with their test though was that they loaded the image from a network share.

So the question is has anyone else attempted the scenario I have described above and if so what were your results?

Alternatively the only other way I assume this could work is to convert the tib file into a VHD file and import it into Hyper-V. I am going to try this over the weekend. For anyone who has done this what kind of timescale did it take to convert the image to VHD? Obviously it will depend on the size of the image so some examples would be good (again obviously platform power CPU/RAM will also probably make a difference in conversion time).

Lastly if anyone else out there can suggest a better way of doing please feel free to suggest however I do want to use Hyper-V!

Thanks

Fri, 10/16/2009 - 19:22
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 3

What version of Backup and Restore 10 are you using (eg. Advanced, Advanced Virtual etc.). I was considering a similar scenario by restoring a Windows Server 2008 to Hyper-V standalone but True Image didn't like converting a 64bit tib to vhd. So we upgraded to B&R10 for Windows Server as part of our maintenance and still don't have 64bit support from what I have found.

Thu, 10/29/2009 - 20:41
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 4
Comments: 15

Does anyone have an update on this? I am trying to do exactly what Issproking was trying to do, and I am not having any luck. I created the VMC + VHD using Acronis conversion, and assumed that I could just boot a new VM to the VHD. However, I get "BOOTMGR is missing" on startup.

Reading KB and the forums, everyone seems to be referring to starting the VM from Acronis Bootable CD first. I don't understand why I woudl need to create VHD file and then use Acronis bootable media on the recovery server. If I boot to the media, I could just restore the TIB file and not worry about VHD.

Or is it the case that if I don't have Universal Restore option, I need to create VHD, while with UR option, I could boot from TIB?

I am sure I am missing something in the process, but I can't find anything that would help. Please advise if you can.

Thank you,

Pavla

Sat, 11/13/2010 - 00:35
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 4
Comments: 15

Does anyone have an update on this? I have been working with technical support on this for months without making any progress. We are running ABR Advanced 12497.
Our IT consultant is telling me that this will not work for disks over 127 GB, but when I read Release Notes for the build, they seem to be clearly stating that the limitation has been resolved.
I am now looking at other ways of converting P2V for DR purposes, but it would be so convenient to be able to use Acronis since we already have it...
Thank you for any update.
Pavla

Thu, 01/06/2011 - 17:16
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 6
Comments: 70

I have worked in this senario and resolved it for many customer as well. 127GB drive size use to be limitation, not sure about the current situation didnt tried that

here is the way i resolved the issue

Solution 1
===========
1. First "no progress bar" issue i have seen, but it resolved, when i connect the bootable media as "remote machine", by using connecting the remote machine option and giving the IP assigned to bootable media. This i saw in 11639, not sure with current version

2. While restoring, dont restore as complete Drive, restore partitions with MBR...

3. Specify the Universal restore option but dont specify the driver, let them be default.

4. After restore, first boot machine in Safe mode to load windows safely. Infact it is suggest always when using safe mode

Note: I suggest to make image with bootable media (cold image) if facing such issue, though it doesnt matter. It matters only when its exchange server or Oracle, or you can stop the service before taking snapshot.

Solution 2
========
while converting directly to virtual machine, their is an option to recover as new virtual machine or exiting. The difference is one option gives you only the VHD file, other gives VHD with configuration file. The time it takes is usually 1GB per minute on standard server.

Please note that image size will be 50% approx of data size, however, VHD will be exactly the same size of HDD, hence i suggest to follow steps 1-4. If getting issue with driver, using second way to restore.

Feedbacks/Comments are most welcome :)

Fri, 01/07/2011 - 17:02
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 7

An update on this.

Instead of creating a blank virtual machine I now just convert the tib files into Virtual PC (which obviously creates the vhd files) and then create a new Virtual Machine in Hyper-V and attach the VHD file that was created during the conversion process.

Works a treat for 2003 server backups but as someone has already pointed out the universal restore embedded process will not work for 2008 x64 servers.

The answer is to use the Virtual Edition of Acronis, this will convert 2003 and 2008 32 and 64 bit images and load them straight into Hyper-V

Wed, 01/12/2011 - 16:24