An example of a PIT recovery procedure from a snapshot of a passive replica copy of an Exchange mailbox database MB1 on an active mailbox database TestServer1 and replica copy on TestServer2 would be as follows:

• Take a snapshot of the replica copy of the mailbox database on TestServer2.

• Use the Move-ActiveMailboxDatabase cmdlet to perform the active mailbox database MB1 switchover from TestServer1 to TestServer1.

  Move-ActiveMailboxDatabase MB1 -ActivateOnServer TestServer2

  Now TestServer1 has the active mailbox database and TestServer1 has the replica copy.

• Use the Suspend-MailboxDatabaseCopy cmdlet to block replication and replay activities (log copying and replay).

  Suspend-MailboxDatabaseCopy -Identity MB1\TestServer1 
  [-Confirm:$False]

  Use -Confirm to prevent user intervention.

• Use the Set-MailboxDatabaseCopy cmdlet to configure the properties of a database copy and set the checkbox for "This database can be overwritten by Restore".

  set-mailboxdatabase -identity MB1\TestServer2 
  -allowfilerestore:$true

• Use the dismount-Database cmdlet to dismount the database

  dismount-Database -Identity MB1\TestServer2 [-Confirm:$False]

  Use -Confirm to prevent user intervention.

  For a VCS cluster setup, offline the VCS resource for the Exchange 2010 database manually if automatic offlining fails.

  Specifying the -a option with the vxsnap restore utility dismounts the database automatically. For a cluster setup, it offlines the resource automatically.

• Now perform the VSS restore operation using either the VEA wizard or the vxsnap CLI utility with the active writer (Microsoft Exchange Writer) to restore the passive copy snapshot.

  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

• Use the mount-Database cmdlet to mount the database.

  mount-Database -Identity MB1\TestServer2

  For a VCS cluster setup, online the VCS resource for the Exchange 2010 database manually if automatic onlining of the resource fails.

  Specifying the -a option with the vxsnap restore utility mounts the database automatically. For a cluster setup, it onlines the resource automatically.

• Use the Update-MailboxDatabaseCopy cmdlet.

  Update-MailboxDatabaseCopy -Identity MB1\TestServer2 
  -SourceServer TestServer1 -DeleteExistingFiles [-Confirm:$False]

  Use -Confirm to prevent user intervention.