Way to be pre-emptive :) On VMWare, if you have the .vmdk, you have the really important stuff. I would be REALLY surprised if the VHD isn't all you need on HyperV.
From: David Lum [mailto:[email protected]] Sent: Friday, December 16, 2011 12:51 AM To: NT System Admin Issues Subject: Hyper-V VM's and backups Hyper-V VM's. By default I have VM's where the config info of each VM is in C:\ProgramData\Microsoft\Windows\Hyper-V but the VHD's are on a separate drive altogether. If I have just the VHD files would it be accurate to say I can probably recover the server by just creating a new VM using the existing VHD's? I'm guessing I'd have to futz with the NIC settings and reinstall the Hyper-V client tools but otherwise I'd be OK? And amazingly no, I haven't blown the server up and have this situation for recovery, I was just askin' :) David Lum Systems Engineer // NWEATM Office 503.548.5229 // Mobile 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
