Actually that was part of my script - shut down Exchange services first - a few PSSERVICE STOP commands, followed 2 minutes later with a PSSHUTDOWN command for the VM, then 5 minutes later PSSHUTDOWN the guest OS.
I'm not sure what I did wrong (if aything), because even if the timing was tight I have it configured to have the host shut down the guest VM gracefully. I've learned a lot about manaully merging AVHD's into VHD's. Sucks that it takes so dan long, and creating copies before merging just adds more time. When the Host came up, looking at Hyper-V console it had the guest mode as "reconnecting", but after 15 minutes I rebooted the host OS as it appeared to be hung, but now I'm wondering if it was doing some merge -which it shouldn't have because I have the guest set to start at host startup, so I say only 50% my fault. Not sure how to bill the client, but I'll certainly be eating much of this bill (except the $515 Microsoft off-hours call...). Dave ________________________________________ From: Carl Houseman [[email protected]] Sent: Monday, April 26, 2010 10:08 AM To: NT System Admin Issues Subject: RE: One of those days....(Hyper-V love) Hyper-V does not have to save a snapshot on OS power down - you can change the shutdown option to shut down the client OS, assuming HV integration services are installed. And you want your SBS to use a shutdown script that stops Exchange services or the shutdown takes a very long time. Carl -----Original Message----- From: David Lum [mailto:[email protected]] Sent: Monday, April 26, 2010 11:36 AM To: NT System Admin Issues Subject: One of those days....(Hyper-V love) Yesterday I went to a client to do some DR testig - namely to make sure when the UPS lost AC power that a script would run and gracfully power off the servers. It worked, almost. The servers did power off, but while the Hyper-V host (2008 non-R2) started fine, the SBS 2003 VM did not. talking to Microsoft snapshots of SBS servers are not supported (I had exactly one). Also apparently hyper-V will take a snapshot if the host OS is told to power down - or something, as there was a snaphot of the 3 logical drives taken at the time the VM was attempting to start. 24 hours laster I'm probably 3-4 hours from knowing if all this merging even works.... Dave ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
