Yeah, I do see that as a best practice. My thinking at the time was that I wanted a DC/DNS up and running before the VMs started. I've since read that the startup order of the VMs can be controlled, so that I could make a VM the DC/DNS and have it start first. I may migrate in that direction in the future. Although, the site where the host server is located doesn't have any DCs. So if that host isn't a DC, it will have to talk to a DC in another site.
There was some reason I chose not to run the backup server in a VM, but now I can't recall it. Performance may have been a factor. At some point I'll run some comparisons with a VM to see if that's so. My host machine doesn't do anything else other than DC/DNS/backup, and I definitely won't be adding any responsibilities on top of that. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 7:07 PM To: NT System Admin Issues Subject: RE: Troubleshooting Server 2008 Reboots I would open a case with Symantec. DPM does this with no problems. (And, just in general, I prefer to leave my hosts ONLY running guests. I think it minimizes the support headaches and simplifies the debugging of same. But that's just me...) Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael Link with me at: http://www.linkedin.com/in/theessentialexchange From: John Hornbuckle [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 7:00 PM To: NT System Admin Issues Subject: RE: Troubleshooting Server 2008 Reboots Yeah, it's Backup Exec 12. I'm not backing up the VM file-I've got a BE Remote Agent installed on the VM, and am connecting to that to backup. From: Bob Fronk [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 6:33 PM To: NT System Admin Issues Subject: RE: Troubleshooting Server 2008 Reboots Are you using Backupexec to copy that VM? I have a Windows 2003 server with MSVS hosting a BES server (has some Exchange parts), and it the entire host server blue screens every time I try to backup with Backup Exec. It has something to do with VSS, but I have not been able to figure it out. The BSOD says something about "VOLSNAP" (not at the office so I don't have the exact error I wrote down). Symantec has a few KBs on backing up Exchange VMs, and if I recall correctly, it says you have to shut the VM down before backing up the VM. Bob Fronk [EMAIL PROTECTED] From: John Hornbuckle [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 5:58 PM To: NT System Admin Issues Subject: Troubleshooting Server 2008 Reboots I've got a 64-bit Server 2008 machine running Hyper-V. It's also a DNS server, a DC, and a Backup Exec server. Its function as a backup server is new-I've only been doing that for about two days. Twice today, while backing up one of the VMs to a NAS system, this server has rebooted. I've backed up the other VMs with no problems, but this one VM (our Exchange VM, incidentally) seems to cause a problem. I'm really not sure how to troubleshoot a spontaneous reboot with Server 2008. The event logs show nothing (other than an entry after the reboot saying that the shutdown was unexpected). The reliability monitor shows nothing-no crash or anything. It's basically like what would happen if I just unplugged a server's power. Power problems are unlikely, though, as this server has dual power supplies, and each is connected to a separate UPS. Any pointers? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
