How to restore Exchange 2000 or 2003 to a recovery server in a different forest

Details:

In order to restore Exchange 2000 or 2003 data to another server, certain prerequisites have to be met:

A new active directory forest has to be created.
The Domain Name Service (DNS) database must be installed and configured.
Exchange has to be installed with the Forest Prep or Domain Prep Options.
The Organization Name, Administrative Group Name, Storage Group Name, Mailbox Store (Server Name), and the LegacyExchangeDN Attribute on the recovery server must match that of the production machine.

·
Please refer to Microsoft Article IDs: KB813337, KB811063, KB322856, KB312371, KB312407, KB280652, KB271882, and KB324606 for further details.

If VERITAS Backup Exec (tm) cannot be installed on the recovery server to run the restore locally, the following steps must be performed :

The VERITAS Backup Exec (tm) Remote Agent has to be installed on the recovery server. The Remote Agent has to be the same revision as the media server.
A trust relationship needs to be established with the recovery forest.
Entries should exist in each forest's DNS database to ensure proper name resolution for the Exchange and Backup Exec servers.
When browsing to the recovery forest's Exchange server, Backup Exec should be able to enumerate both the Exchange Information Store and Exchange Mailboxes for that server (Figure 1).

·
Figure 1

The Backup Exec service account must be a member of the Administrators group local to the Exchange server, or a member of the Administrators or Domain Administrators group if Exchange is running on a domain controller. The Backup Exec service account should also be added to the recovery Exchange server's delegated control list. To delegate control to an account, use the Exchange System manager. Right-click on the Exchange organization, and select Delegate control. Click Next, and then select Add and change the lookup domain to show accounts in the production domain. Grant the account Exchange Full Administrator rights(Figure 2 and 3).

·
Figure 2

Figure 3

Once the pre-requisites have been established, modifications to the recovery server's Exchange Stores will need to be made:

1. Rename the Mailbox Store and Public Folder Store to match the name of the production Exchange server (Figure 4)

Figure 4

2. Set the Mailbox and Public Stores to be overwritten by a restore and then dismount each store (Figure 5)

Figure 5

3. In Backup Exec, select the full backup of the production Exchange Server's Information Store and create a restore job

4. Under the Redirection tab, select Redirect Exchange sets and enter the recovery server's NetBios name (Figure 6)

Figure 6

5. Under the Exchange tab, clear the No loss restore check box and the Mount database after restore check box (Figure 7)

By not selecting to have Backup Exec mount the database after the restore, troubleshooting potential problems with the restore process is simplified. If the restore is successful but the database is subsequently unable to mount, any potential errors are then isolated to the mount operation. Errors specific to mounting the database should then be researched either with the VERITAS or Microsoft Knowledge Base.

·
Figure 7

Figure 8 & 9 shows the Restore Job properties in Backup Exec For Windows Servers 9.x and 10.x

Figure 8

Figure 9

6. Click Run Now

Related Documents:

http://support.veritas.com/docs/239613

http://support.veritas.com/docs/239739

http://support.veritas.com/docs/251829

http://support.veritas.com/docs/252165

Acknowledgements
Microsoft Article KB813337 and KB811063

Products Applied:
Backup Exec for Windows Servers 10.0, 10d (10.1), 8.0, 8.5, 8.5 SBS, 8.6, 8.6 SBS, 9.0 4454, 9.0 4454 SP1, 9.1, 9.1 4691, 9.1 4691 SP1

Last Updated: December 20 2005 09:42 PM GMT
Expires on: 365 days from publish date

Subscribe to receive critical updates about this document

Subjects:
Backup Exec for Windows Servers
   Agent For Exchange: Backup-Restore
   Application: Exchange Module, How To, Restore
   Priority: 06

Languages:
English (US)

Operating Systems:
Windows 2000

Advanced Server, Advanced Server SP1, Advanced Server SP2, Advanced Server Windows Powered, Advanced Server Windows Powered SP1, Advanced Server Windows Powered SP2, Datacenter Server, Datacenter Server SP1, Datacenter Server SP2, Server, Server SP1, Server SP2, Server Windows Powered, Server Windows Powered SP1, Server Windows Powered SP2

Windows Server 2003

DataCenter, DataCenter (IA64), Enterprise (IA64), Enterprise Server, Standard Server

Windows Small Business Server 2003

Premium Edition, Standard Edition

Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.