RedstoneIT
asked on
Exchange, Domain controller and Symantec System Recovery 2011
Good afternoon Experts,
Here's the scenario. I have a 2003 Standard Server box running 2003 Exchange, DNS, DHCP and Print Server. I'm taking snapshots including VSS with Symantec System Restore. The Backup appears to be fine, but when I do a virtual conversion and attempt to load it onto a Hyper-V it takes forever to even get to a login, then it never fully loads and starts.
Is this a result of all the roles the box is trying to provide or is there a software issue that will not allow this to work?
I know that exchange can be run virtual, and I have heard of it being snapshotted and Virtualized.
Any Thoughts or ideas?
Symantec says that it is because of all the roles and if I were to just VM the Exchange it would be fine.
Here's the scenario. I have a 2003 Standard Server box running 2003 Exchange, DNS, DHCP and Print Server. I'm taking snapshots including VSS with Symantec System Restore. The Backup appears to be fine, but when I do a virtual conversion and attempt to load it onto a Hyper-V it takes forever to even get to a login, then it never fully loads and starts.
Is this a result of all the roles the box is trying to provide or is there a software issue that will not allow this to work?
I know that exchange can be run virtual, and I have heard of it being snapshotted and Virtualized.
Any Thoughts or ideas?
Symantec says that it is because of all the roles and if I were to just VM the Exchange it would be fine.
First, for security reasons, Exchange shouldn't be running on a DC. there are quite a few known issues running this scenario, but enough about what should and what shouldn't be.
To accurately assess your scenario, give me your hardware/software configurations for the VM host and the VM Exchange server guest, as well as any other VM guests on the VM host.
To accurately assess your scenario, give me your hardware/software configurations for the VM host and the VM Exchange server guest, as well as any other VM guests on the VM host.
Also is this a full retail version of server 2003 that you are virtualizing? An OEM version or an MS VL version?
As stated above, without knowing what you virtual HOST is and what resources you have allocated we can't say alot.
As stated above, without knowing what you virtual HOST is and what resources you have allocated we can't say alot.
This is normal. As it has new hardware it has lost it's IP address and is tring to get it via DHCP or cannot locate a nic. Since it can't find a nic it will wait somtimes hours until it times out.
1. Wait till it comes online
2. Ensure that you're not in production
3. Install virtual nic and ip
4. If there are other domain controllers in the environment it will still take a while for it to come up as it will be looking to sync with them
1. Wait till it comes online
2. Ensure that you're not in production
3. Install virtual nic and ip
4. If there are other domain controllers in the environment it will still take a while for it to come up as it will be looking to sync with them
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Here is a document on "Virtualizing existing domain controllers" from the VMware site, but it still applies to Hyper-V http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006996
ASKER
I'm looking into your solutions now Everyone. It will be Monday or Tuesday before I have a response.
Regards,
Brian
Regards,
Brian
ASKER
jrhelgeson,
I've managed to get it to start up in safe mode, removed the old drivers, had it find new ones (it did this on its own), the rebooted. It is currently sitting on "Applying Computer Settings" and has been there for 5 hours now.
Could the issue be the Exchange running on this box with so many other roles?
What if it were just Exchange, would it "Snapshot" and run in Hyper-V ?
I've managed to get it to start up in safe mode, removed the old drivers, had it find new ones (it did this on its own), the rebooted. It is currently sitting on "Applying Computer Settings" and has been there for 5 hours now.
Could the issue be the Exchange running on this box with so many other roles?
What if it were just Exchange, would it "Snapshot" and run in Hyper-V ?
Oh, you should shut it down - reboot it in safe mode, shut down/disable the exchange services.
Then boot it up without exchange. Make sure you have all the old hardware removed, of course.
See how that boot time goes.
Sometimes I've had it lock up on that boot screen, and a simple CTRL+ALT+DEL brought me a login prompt. Just a thought.
Then boot it up without exchange. Make sure you have all the old hardware removed, of course.
See how that boot time goes.
Sometimes I've had it lock up on that boot screen, and a simple CTRL+ALT+DEL brought me a login prompt. Just a thought.
ASKER
jrhelgeson,
IT finally started logging in. now its in the process of logging in, but its taking a while.
IT finally started logging in. now its in the process of logging in, but its taking a while.
That would be due to the fact it doesn't have an IP address on the network card.
DNS & AD are having a tough time of it.
DNS & AD are having a tough time of it.
ASKER
jrhelgeson,
Your responses have gotten me furthest along with this situation. I'm awarding the points to you.
Your responses have gotten me furthest along with this situation. I'm awarding the points to you.
Thank you, did the situation actually get resolved?
ASKER
jrhelgeson
No, but you answered the question I asked about. I've been able to get it to come up in safe mode, but when I try to get it up in normal mode it is still horribly slow and never does get to a desktop. I'll probably open a new question tomorrow. I'm trying a few things now to see if I can "break through" this issue.
I really think its a case of this server having too many roles and responsibilities. I think with Exchange 2010 and Windows Server 2008 the problem will go away That is, once I get exchange on its own box.
Regards,
Brian
No, but you answered the question I asked about. I've been able to get it to come up in safe mode, but when I try to get it up in normal mode it is still horribly slow and never does get to a desktop. I'll probably open a new question tomorrow. I'm trying a few things now to see if I can "break through" this issue.
I really think its a case of this server having too many roles and responsibilities. I think with Exchange 2010 and Windows Server 2008 the problem will go away That is, once I get exchange on its own box.
Regards,
Brian
Keep me posted on the new questions - you can get that server up and running. I've had a 100% success rate.
You may want to use MSConfig to disable all services, and boot the computer up just once with just Active Directory so you can configure the network card and get DNS up and running, etc.
Then you can slowly bring other services back online.
You may want to use MSConfig to disable all services, and boot the computer up just once with just Active Directory so you can configure the network card and get DNS up and running, etc.
Then you can slowly bring other services back online.
ASKER