Restoring Microsoft Exchange Server Nodes or Components

Take the following steps to restore the Microsoft Exchange Server nodes or components on the Java-based DPX Management Interface:

1. Click the Restore tab, and click Block in the task pane to open the Restore page. In the Restore page, there are the SOURCE pane and the DESTINATION pane.

2. In the SOURCES pane, expand the virtual node to display backup instances under the Exchange application. You can select an Exchange application, database, database file, or transaction log for a single restore. In the following example, the Exchange database file (EDB file) is part of the File component and the transaction logs are part of the Logs component.

See also. To recover individual mailbox items, as well as copy, search, and analyze email and email attachments, must be installed on the node. See Chapter 49: Using EMBR for Rapid Recovery of Exchange Mailbox Items in the Reference Guide.

Selecting an EDB file will not automatically select its corresponding logs.

1. Click the selection box to select components to restore.

Note. For DAGs, the physical nodes can also be browsed for backup instances, but Microsoft Exchange Server components are not available for restore. Microsoft Exchange Server components are only displayed under the virtual node.

1. From the expanded virtual node, select single or multiple components to restore. You can select the entire Exchange backup instance for restore, or drill down to Exchange components.

2. In the DESTINATIONS pane on the right, select a location to restore to.

   To restore to the same database, overwriting the active database where it is currently hosted, select Original Location, which is indicated by an arrow on the DESTINATIONS tree. In the event of failover, Original Location is the location of the active database copy.

Tip. If you select multiple sources for restore, such as several Microsoft Exchange Server databases, and you select Original Location as the restore destination, the databases will each be restored to their original location. There is no need to run multiple restore jobs to restore multiple databases to their original locations.

The following three optional steps are done from the Task Panel. You can change source options, destination options, and email notification settings.

1. Change source options by clicking Set Source Options on the Task Panel, or accept the defaults. For a description of Block source options, see Setting Block Restore Source Options.

2. Change destination options by clicking Set Destination Option on the Task Panel, or accept the defaults. For a description of Block restore destination options see Selecting Block Restore Destinations.

   The destination options specific to Exchange:

Use Exchange Point-in-Time Recovery to control whether Restore will delete Exchange logs to restore Exchange to a point-in-time.

Yes	Catalogic DPX will delete existing transaction logs before restore and then perform a point-in-time restore, which brings the database back to the state when it was backed up. This option is commonly used when you are restoring a backup instance that is not the latest. This option is strongly recommended whenever a restore is needed to nullify an incorrect or maliciously altered transaction.
No	This is the default. Catalogic DPX will not delete existing transaction logs before restore. performs an up-to-the-minute restore by retaining the existing transaction logs and rolling forward all new transaction from the existing logs. This option is commonly used when you lose a database without losing its transaction logs and you choose to restore from the latest backup instance.

Use Exchange Handling to select how Exchange databases are handled after restore completes.

Commit Restore and Mount Database	This is the default. After the restore completes, commit the changes (transaction logs) to the database and mount the Exchange database. The Exchange administrator does not have to manually intervene before the database is available for clients.
Commit Restore Only	After the restore completes, commit the changes (transaction logs) to the database but do not mount the Exchange database. The Exchange administrator will need to manually mount the database to make it available to clients.
Do Not Commit Restore	After the restore completes, neither commit the changes to the database nor mount the exchange database. The Exchange administrator will need to either commit or rollback the changes (transaction logs) and mount the database for use.