DOCUMENTATION: How to restore an Exchange 2000/2003 database to the same or alternate client

Article:TECH29816  |  Created: 2007-01-19  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH29816
Article Type
Technical Solution

Product(s)

Environment

Issue



DOCUMENTATION: How to restore an Exchange 2000/2003 database to the same or alternate client

Solution



Manuals:
NetBackup 4.5 for Microsoft Exchange Server System Administrator's Guide on Windows NT/2000, p. 64
VERITAS NetBackup 5.0 for Microsoft Exchange Server System Administrator's Guide for Windows, p. 79
VERITAS NetBackup 5.1 for Microsoft Exchange Server System Administrator's Guide for Windows, p. 85
VERITAS NetBackup 6.0 for Microsoft Exchange Server System Administrator's Guide for Windows, p. 81


Modification Type: Supplement

Modification:
Recovery of an Exchange 2000 or 2003 database to an alternate client requires the installation of the operating system and the Exchange server software. Once this software is installed, the database files can be recovered from backup.  

These instructions explain how to restore a database to an alternate client. If restoring to the source server, installation of the operating system and Exchange is not necessary.  
- If restoring to an alternate client, follow all steps outlined below
- If the storage group or individual store is being recovered to the same server, skip to step 11
Note: The following steps are based on the following Microsoft document: mailbox recover_pdf.exe found at:
 http://www.microsoft.com/downloads/details.aspx?displaying=en&FamilyID=9E52BAFC-5C33-46B9-AF14-04E4D989EF6B .
Download and review these instructions as they contain valuable information  


Building a recovery server:
1. Install Windows 2000 Server or Advanced Server. The server does not need the same name as the original server.
2. Run DCPROMO on the recovery server to install Active Directory. The domain does not need to be the same as the original domain. Do not join this server to any other domain or forest
3. Install the primary domain name service (DNS) server on the recovery server; create a forward lookup zone for the root domain of the new forest, and set Allow Dynamic Updates to Yes. Set the recovery server to use this DNS server. Verify that service record (SRV) records are created in DNS for the new forest
4. Install the same service packs on the recovery server as the source server
5. Run forestprep and Domainprep on the recovery server
6. Install Exchange 2000 or 2003 server (whichever was on the source server) on the recovery server
7. Install the same service packs for Exchange on the recovery server as on the source server

IMPORTANT: The recovery server's organization name, administrative group name, and LegacyExchangeDN values must match the configuration objects in the administrative group from which the database is being recovered. These values must be recorded from the source server, and matched on the recovery server. These values are found by following the Microsoft Mailbox Recovery white paper, or by using LEGACYDN.EXE from Exchange Service Pack 1 or Exchange Service Pack 2 (LEGACYDN.EXE comes standard with Exchange 2003). LEGACYDN.EXE will extract all three values from the source server. For more information on LEGACYDN.EXE,  read the readme4legacydn text file

8. Execute LEGACYDN.EXE on the source server. Select the administrative group which contains the database you wish to restore, record the organization name, administrative group, and LegacyDN name. Do not attempt to make any changes on the source server (making changes to the source server renders the databases unable to start). After recording these values, close LEGACYDN.EXE
9. Execute LEGACYDN.EXE on the recovery server. Change the organization name, administrative group, and LegacyDN values on the recovery server using the values recorded from the source server (Figure 1)

Figure 1
 

10. Restart the recovery server (do not create the recovery database before restarting the recovery server)


Creating and Restoring the Databases:
11. Create the storage group and databases with logical names that match the original storage group and databases from the source server to the letter (Figure 2). This is critical for online restores of the database. If the source server is unavailable, open the Backup, Archive and Restore window on the master to view the correct logical names of the storage groups and databases to be recovered.

Figure 2
 


12. Mount the new database store. After mounting each database store you wish to restore, dismount each database store (this will create the .edb and .stm data files required for restore). After each store has been successfully dismounted, right click the store, go to the Properties | Database tab, and select This database can be overwritten by a restore
13. Configure the master server to allow for an alternate client restore from the alternate client
For a UNIX master alternate client recovery, create the following touch file: usr/openv/netbackup/db/altnames/No.Restrictions
For a Windows master, create the following unassociated file: <INSTALL_PATH>\veritas\netbackup\db\altnames\No.Restrictions
14. Install the VERITAS NetBackup (tm) client software on the recovery server
15. Install the Exchange database extension on the recovery server
Note: The Exchange database extension is installed by default if the NetBackup client installed is Feature Pack 3 or later
16. Configure the client to use the same master as the source server
17. Start the restore from the recovery client
18. Select the databases and transaction logs for restore (Figure 3). The administrator must restore the transaction logs with the database for a successful restore.

Figure 3
 

19. After the restore, recover data by using Exmerge or a client application after reconnecting the mailbox which you wish to recover to an Active Directory user account






Legacy ID



264924


Article URL http://www.symantec.com/docs/TECH29816


Terms of use for this information are found in Legal Notices