With the RDB successfully created, you can restore data to it by completing the steps outlined in Renaming Mailbox Databases in Exchange 2010. Amend those steps to including the following steps:
1 |
After you select the Rename to check box in the Rename/Relocate dialog box, enter the name of the RDB in the text box to direct the backup to the RDB. |
2 |
On the Create Selection Set page, click Edit Plugin Options, and select the following options on the Restore and Recovery Options tab: |
3 |
In a DAG, if you created the RDB on an Exchange Mailbox Server that is not the active server and you want to select a specific Exchange Mailbox Server on which to perform the restore, select the applicable NetVault Backup Client from the Target Client list on the Create Restore Job page. |
IMPORTANT: If the plug-in cannot resolve the address of the Exchange Mailbox Server that hosts the RDB, select the applicable NetVault Backup Client from the Target Client list on the Create Restore Job page. |
After you have restored the database to the RDB, use the Exchange Management Shell to extract the data from the RDB to the active mailboxes.
You can find complete instructions for this procedure in the relevant Microsoft Exchange documentation. For more information, see http://technet.microsoft.com/en-us/library/ee332351.aspx.
This topic briefly describes how to recover an Exchange system by using backups performed with the Plug‑in for Exchange. You can use this procedure to rebuild an Exchange Server if the original was destroyed or is otherwise unusable. If you are rebuilding an Exchange Server, the Active Directory service should be available in Disaster Recovery Mode.
• |
Exchange 2010, Recover Exchange Server or Recover a Database Availability Group Member Server: http://technet.microsoft.com/en-us/library/dd876880(v=exchg.141).aspx and http://technet.microsoft.com/en-us/library/dd638206(v=exchg.141).aspx |
• |
Exchange 2013, Recover Exchange Server or Recover a Database Availability Group Member Server: https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and https://technet.microsoft.com/en-us/library/dd638206(v=exchg.150).aspx |
• |
Exchange 2016 and 2019, Recover an Exchange Server or Recover a Database Availability Group Member Server: http://technet.microsoft.com/en-us/library/dd876880.aspx and http://technet.microsoft.com/en-us/library/dd638206.aspx. Pick the applicable version, 2016 or 2019. |
To perform the restore, perform the following steps.
3 |
The Plug‑in for Exchange also lets you take the backup of a Mailbox Database performed on one Exchange Server and restore it to a secondary Exchange Server. This option can be beneficial when you must recover a Mailbox Database to access its contents while leaving the initial Exchange Server untouched and operational. In addition, restoring to a secondary Exchange Server can be a good method for testing the integrity of backed-up data without interfering with a running Exchange Server. This topic offers instructions on restoring Full, Incremental, and Differential Backup types to a secondary Exchange Server.
• |
Clean installation of Exchange has been performed on the new target server: Quest recommends that you complete this step on a newly installed Exchange Server, rather than an existing one. |
• |
Mailbox Databases set up on the target machine: The target Mailbox Database names, database names, database filenames, and the database file path or directory cannot match the original Mailbox Databases; they must be different. |
IMPORTANT: When you use the Exchange Management Console to create the target database in the destination Exchange Server, do not select the Mount Database option. If you select this option, Exchange generates the initial set of database transaction logs. These logs might interfere with the restore job and cause it to fail. By not selecting the Mount Database option, Exchange adds the database to the Exchange Server and creates an empty directory for the database. The restore job populates the directory during completion of the job. |
• |
NetVault Backup and the Plug‑in for Exchange must be installed on both machines: For this operation to work, NetVault Backup and the plug-in must be installed on both the original Exchange Server and the machine set up as the new target. |
• |
Both machines must be added to the NetVault Backup Server as Clients: On the Manage Clients page of the NetVault Backup Server, ensure that both machines have been successfully added as NetVault Backup Clients. For details on adding Clients to the NetVault Backup Server, see the Quest NetVault Backup Administrator’s Guide. |
To perform the restore, complete the following steps.
2 |
For details on restoring Exchange backups, see Restoring data using the plug-in, and note the following exceptions: |
a |
On the Create Selection Set page, click the original database, and select Rename from the context menu. |
b |
In the Rename/Relocate dialog box, enter the name of the new target Mailbox Database in the Rename box, and click Ok. |
• |
On the Restore and Recovery Options tab, select Set ‘This database can be overwritten by a restore’ Flag for Databases. |
• |
If applicable, change the other options on the Restore and Recovery Options tab. |
• |
• |
Exchange Administrator User Name: By default, this field contains the administrator-level account that was used to back up the original target Exchange Server. You can change this value, but the account named must have the proper backup and restore permissions for the machine that is to serve as the target of the restore. |
• |
Password: Enter the password associated with the user name specified in the previous field. |
• |
Windows Domain: This field can be left blank, as it is not requirement for recovering to a different Exchange Server. |
• |
In Job Name, specify a name for the job if you do not want to use the default setting. |
• |
In the Target Client list, select the Exchange Server on which the target database was created. |
• |
3 |
To point to the new database, open the Exchange Management Shell, and run the following command |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center