spooky-mulder
asked on
Hyper-V guest systems has disappeared from the Host's VM Console
I have a win2008 Std 64bit server with the Hyper-v Role Installed and two guest systems in the VM Console (a win03r2 Std running as a member server and a win08 Std running as a pdc both 32bit)
TrendMicro WFBS is installed and controlled on the PDC and pushed to the member server and the host system.
Everything has been running smoothly and then suddenly after a controlled shutdown of the host (the guests werent shutdown manually first) the VM console had lost the guest systems.
My technician panicked and created new vms and pointed them to the virtual hard disks from the former machines. Problem is they seem to be obsolete version as if the had returned to former snapshots which by the way are also missing of course.
Questions
1) Any clues as to what might have happened?
2) Whats the best practice for reclaiming my guests?
THX in advance
TrendMicro WFBS is installed and controlled on the PDC and pushed to the member server and the host system.
Everything has been running smoothly and then suddenly after a controlled shutdown of the host (the guests werent shutdown manually first) the VM console had lost the guest systems.
My technician panicked and created new vms and pointed them to the virtual hard disks from the former machines. Problem is they seem to be obsolete version as if the had returned to former snapshots which by the way are also missing of course.
Questions
1) Any clues as to what might have happened?
2) Whats the best practice for reclaiming my guests?
THX in advance
ASKER
Hi bjinfo,
That's indeed excellent info. We suspected the TM install did something like this so while recovering from the crash we avoided installing TM on the host and so far we havent experienced any problems like before. Combined with your feedback it looks like weve got the answer to our first concern. As for the second question, do you have any experience with best practice on how to reclaim the guests? In our case the .vhd, and snapshot files were available but couldnt get associated to the VMM.
Cheers,
Kenny
That's indeed excellent info. We suspected the TM install did something like this so while recovering from the crash we avoided installing TM on the host and so far we havent experienced any problems like before. Combined with your feedback it looks like weve got the answer to our first concern. As for the second question, do you have any experience with best practice on how to reclaim the guests? In our case the .vhd, and snapshot files were available but couldnt get associated to the VMM.
Cheers,
Kenny
Hello Kenny,
so far, in our case we had to reinstall our guests from scratch, because it happened, before we could do any backup of the virtual files, so i cannot answer your second question precisely. But the question is why you could not associate your vhf and snapshot file to the vmm. Any error code shown? If I understand you, your PDC is installed in a virtual guest, i heard somewhere that install a dc alone on an hyperV should be avoided, should always be a second one installed on another physical machine (virtually or not does not matter) for replication and recovery purpose. Next week i will try to do a recovery test of one virtual server, and i will post my results here.
Best regard
Pascal
so far, in our case we had to reinstall our guests from scratch, because it happened, before we could do any backup of the virtual files, so i cannot answer your second question precisely. But the question is why you could not associate your vhf and snapshot file to the vmm. Any error code shown? If I understand you, your PDC is installed in a virtual guest, i heard somewhere that install a dc alone on an hyperV should be avoided, should always be a second one installed on another physical machine (virtually or not does not matter) for replication and recovery purpose. Next week i will try to do a recovery test of one virtual server, and i will post my results here.
Best regard
Pascal
ASKER
Hi Pascal,
I concur that they should indeed have a second DC. Unfortunately in a few setups like SBS 08 Prem and small office / small budget installations demanding two separate server e.g. for sql that option is not available.
Ill be anticipating the result of your recovery test.
THX in advance.
Cheers,
Kenny
I concur that they should indeed have a second DC. Unfortunately in a few setups like SBS 08 Prem and small office / small budget installations demanding two separate server e.g. for sql that option is not available.
Ill be anticipating the result of your recovery test.
THX in advance.
Cheers,
Kenny
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Pascal,
The guide to manually merge the snapshots did the trick. It might not be elegant, but it was definitely efficient.
Thanks allot for your answers, Ill shut down the question and assign you all the points.
Best regards,
Kenny
The guide to manually merge the snapshots did the trick. It might not be elegant, but it was definitely efficient.
Thanks allot for your answers, Ill shut down the question and assign you all the points.
Best regards,
Kenny
we had the same problem here, it's a known problem with Trendmicro products. You need to add the directory where you will put your virtual servers in every exclusion list in the Trendmicro configuration (real scan, manual scan, etc..) before you configure your virtual server in Hyper-V, otherwise Trendmicro deletes them and you have the phenomenon you describe.
Hope this helps.