Exchange Disaster recovery whole process

Finally decided to get the mail system again. Because the server often problems, DNS error, SMTP also often problems. Most importantly, because there were only two servers previously, this server acted on several roles (Pdc,isaserver,exchange servers) and later added a server. So the Isa is separated. Because at that time people in Shanghai, can only through remote access to the system operation, the process does not know what is wrong, resulting in the ISA is not completely deleted. It cannot be installed after, and cannot be uninstalled. And after restarting the server, none of the clients can access all the services on the server. (finally found that the restart run ISA installer, which will be an error, after the error, the rollback operation, rollback server or can be accessed) the reason for a long time, has not come to the results.

So this time from Shanghai back, decided for a long time, or to the server to get a good get.

Several recovery scenarios are set:

Environment: Three server PDC mailserver (servers to be maintained) DC DHCPServer member server isaserver, WIN2K3 environment.

First, back up the System state: and Exchange store data. Back up the entire C disk (three separate backups)

Ii. Programme of Rehabilitation:

1, directly reload the system, restore the system state, and then restore Exchange store data. Check to see if two domain controls can communicate properly. can be resolved. No rollback operation can access MailServer (this scenario is the simplest) if the recovery fails, the 2nd recovery scenario is enabled.

2. When the first type of service recovery scheme fails. The original server down state. The server dhcpserver must be forced to capture five FSMO roles. Run as a GC. Whether you can have the client log on normally. Reload the mailserver, join the domain, and do the extra domain control run. Install Exchange in a catastrophic manner and then recover data.

3, after two ways still can not return to normal state. Perform entire C-disk restore (all C-disk backup has been done before)

After you've designed your recovery plan, start doing it (many people will ask why you don't transfer FSMO roles to other DCs first), of course, just because you can't transfer. A connected domain control on the report--RPC service is not available. The reason I think is also the result of the previous Isa.