Steve Malloy
Guest
|
 Posted:
Mon Dec 26, 2005 1:58 am Post subject:
Disaster Recovery |
|
|
I had the good fortune of having 2 disks fail in my RAID 5 exchange 2003
server causing a complete failure.
I purchased a new server and brought the old server up and managed to
replicate for a good 48 hours before she dropped never to be resurrected. Now
I have a lot of issues with client’s outlook, like hanging – unable to cut
and paste and more, that I must attribute to the loss of the replication
partner. I purchased 2 new hard drives for the old server and need to know
the best way to decommission or end the replication.
Do I create the old server with its name and load exchange and re-replicate?
Or, should I find a way to stop replication and forget trying to decommission
properly?
Currently the new server lists the old one in AD as a domain controller;
also, replication is still set up in exchange. I did try to name the old
server its same name but AD won’t allow it to be re-added since it is listed
in AD as a DC.
Any suggestions, ideas or assistance would be greatly appreciated.
Thank you,
Steve
|
|
Andrew Sword [MVP]
Guest
|
| Posted:
Thu Dec 29, 2005 9:59 am Post subject:
RE: Disaster Recovery |
|
|
I'm not sure exactly what's happening at the moment. What exactly are you
replicating? How did you configure replication? If the old server is off the
air what are client connecting to? Is AD still operating on the new server?
"Steve Malloy" wrote:
| Quote: | I had the good fortune of having 2 disks fail in my RAID 5 exchange 2003
server causing a complete failure.
I purchased a new server and brought the old server up and managed to
replicate for a good 48 hours before she dropped never to be resurrected. Now
I have a lot of issues with client’s outlook, like hanging – unable to cut
and paste and more, that I must attribute to the loss of the replication
partner. I purchased 2 new hard drives for the old server and need to know
the best way to decommission or end the replication.
Do I create the old server with its name and load exchange and re-replicate?
Or, should I find a way to stop replication and forget trying to decommission
properly?
Currently the new server lists the old one in AD as a domain controller;
also, replication is still set up in exchange. I did try to name the old
server its same name but AD won’t allow it to be re-added since it is listed
in AD as a DC.
Any suggestions, ideas or assistance would be greatly appreciated.
Thank you,
Steve |
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in