Use the following procedure to recover the mailbox database to the point of failure (POF).
Refer to the Microsoft Exchange Shell cmdlets.
Note: |
When restoring after a 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 of failure, you cannot later restore to the point of time. You can only perform one recovery procedure on a mailbox 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 recover the mailbox database to the point of failure
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 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-SourceServer -DeleteExistingFiles [-Confirm:$False]
Use -Confirm to prevent user intervention.