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.

Direct Reload system (patch also did not hit), restart press F8 into the directory Recovery mode, start Ntbackup to restore the "system State" process is quickly completed, prompted to reboot the system. Press Yes, reboot. But found that the system can not boot, after the start of the screen, it has been restarted again. I thought it was a problem installing the system, then I installed the system and then resumed. As a result, the boot to the old place is broken and restarted. In my heart, I think it's bad. What's going to go wrong? Let me not think about it, the time problem, decided to adopt the second option.

On the dhcpserver, the seizure of the FSMO role (on the method of capturing, a lot of tutorials on this aspect, the direct start win system help, a check on it), very smooth, in the prompt operation, quickly will the role to capture over. Reboot, after a period of time, immediately test the client login is a problem. Test results, login is normal, there is no slow logon problem. MailServer is soon installed, after joining the domain, upgrade to DC and see that all the information has been synchronized on both DCs. Two DC communications are normal (the previous problem is resolved)

Here's a bit of a special importance: not previously noted, because restoring system state failed, must be installed in a new installation, although named after the same name, but Windows is not considered the original DC, must be before the installation started, the original DC in the domain control, Otherwise, when you install Exchange, you will think that another exchange has already been installed, which will cause the installation to fail!

The next step is the most important one and the most complex process. First, install Exchange2003 in a disaster-recovery installation, very simply by entering the command prompt and then entering X:\setup\i386 (where x is the disk where Exchange is located) type: Setup/disasterrecovery A disaster installation is initiated to install Exchange2003, followed by the installation process. Just follow the guide.

The installation process is also quickly completed (during the installation process, if you have not stopped before, please do not terminate, sometimes very slow, once in the installation to see the fixed, mandatory termination of the installation process.) Result of installation failure) after restarting the server, you are prompted that "at least one or more services will not start" checked logs and found that the "Microsoft Exchange System Attendant" System Attendant could not be started and the log displays:

Event Type:error

Event Source:msexchangesa

Event category:general

Event id:9022

Description:

Microsoft Exchange System Attendant encountered an error while processing to the security data for Exchange server.

For more information, click Http://search.support.microsoft.com/search/?adv=1.

Event Type:error

Event Source:msexchangesa

Event category:general

Event id:9149

Description:

Microsoft Exchange System attendant failed to start Exchange Server '. Error code ' 0x80070005 '.

For more information, click Http://search.support.microsoft.com/search/?adv=1.

Event Type:error

Event Source:msexchangesa

Event category:general

Event id:1005

Description:

Unexpected error Access denied. Facility:ldap Provider ID no:80070005 Microsoft Exchange System attendant occurred.

Check the relevant data, which saw a said is related to GC, because the server log, also shows a row, can not communicate with the GC records, the MAILSERVR as a GC run. After the reboot, the problem remains to be found. After a period of inquiry, finally in Microsoft to see the relevant solutions, as follows:

To resolve this issue, use ADSI edit to grant the server account the correct permissions for the server container in the Exchange organization container and Active Directory. ADSI Edit is located in the Microsoft Windows 2000 support tool. To install the Windows 2000 support tool. Note: There is a Support Tools directory in the WIN2K3 installation tray, where support tools are installed. After installation, you will find the "ADSIEDIT" editing tool in the C:\Program Files\Support Tools directory.