Lum [mailto:david@nwea.org]
Sent: Friday, December 16, 2011 1: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 separa
As Ken said, you'd just have to recreate the VM and point it to the disks.
All the crucial stuff is maintained there outside of RAM and NIC
configuration.
* *
*ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of
Technology for the SMB market…
*
On Fri, Dec 16, 2011 at 1:51 AM,
You can create a new VM (assuming there are no snapshots etc.) The NICs will be
new, but that's about it. No need to reinstall the Integration Services
Cheers
Ken
From: David Lum [mailto:david@nwea.org]
Sent: Friday, 16 December 2011 2:51 PM
To: NT System Admin Issues
Subject: Hyper-V
per-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
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 ex
