You can restore an Exchange Server database in the event of data loss or corruption.
To complete a database restore, Tivoli® Storage FlashCopy® Manager must be operating in an account with membership in the Organization Management group.
When you restore a database on Exchange Server, data that exists in the database is overwritten. The data is not available after restore processing is complete. Instant Restore processing overwrites all files on the destination file system.
For database backups in an Exchange Server Database Availability Group (DAG) configuration, because all database copies are backed up by using a single DAG node, you can restore a database regardless of which DAG member the database is backed up from. Local backups must be restored on the node where the backup is completed.
Ensure that you are set up to use the DAG node name (DAGNODE). You can set up the DAG node name in the DAG Node field in the TSM Node Names page of the Tivoli Storage Manager configuration wizard. Alternatively, you can set up the node name in the Back up DAG databases to common node field in the General properties page for your Exchange workload.
In a stand-alone configuration, you cannot back up a database from one DAG member and restore it to a different DAG member. However, backups from the same node are still managed with the same policy, regardless of whether the database was active or passive at the time of the backup.
In a Tivoli Storage Manager configuration, backups of a database from one DAG member to local can be restored only to the system that created the backup. However, backups to Tivoli Storage Manager can be restored on any Exchange server in the DAG.
When you complete the following steps to restore Exchange Server data, one of the terms that is used is restore into. When you use the restore into options, you restore data to another target destination. The data is not restored to the original source destination.
To restore Exchange Server data, complete the following steps: