Restore the mailbox database to the point in time (PIT) that the snapshot set was created or last refreshed and mount the Exchange databases.
Refer to Microsoft Exchange Shell cmdlets for details.
Note: |
When restoring after hardware failure, you must use the command line and make sure to specify the -r option. |
Warning: |
If you choose to restore the mailbox database to the point in time, you cannot later restore it to the point of failure. You can only perform one recovery procedure on a database. |
Warning: |
You must verify that you have correctly assigned the drive letter or mount point to each volume and that you have accounted for all the volumes in the mailbox database. |
To restore the mailbox database to the point in time of the snapshot set
Suspend-MailboxDatabaseCopy -Identity MB1 [-Confirm:$False]
Use -Confirm to prevent user intervention.
set-mailboxdatabase -identity MB1-allowfilerestore:$true
dismount-Database -Identity MB1[-Confirm:$False]
Use -Confirm to prevent user intervention.
For a VCS cluster setup, offline the VCS resource for the database manually if automatic offlining of the resource fails.
Specifying the -a option with the vxsnap restore command dismounts the database automatically. In the case of a VCS cluster setup, it offlines the resource for the database automatically.
vxsnap -x snapdata.xml restore RestoreType=PIT writer="Microsoft Exchange Writer"
For this example, assume that the snapshot of the replica was performed with
vxsnap -x snapdata.xml create writer="Microsoft Exchange writer Replica" component=MB1 backupType=COPY -E -O
mount-Database -Identity MB1
For a VCS cluster setup, online the VCS resource for the database manually if automatic onlining of the resource fails.
Specifying the -a option with the vxsnap restore command utility mounts the database automatically. In the case of a VCS cluster setup, it onlines the resource for the database.
Update-MailboxDatabaseCopy -Identity MB1[-Confirm:$False]
Use -Confirm to prevent user intervention.