Search <book_title>...

Storage Foundation 8.0 Quick Recovery Solutions Guide for Microsoft Exchange - Windows

Last Published: 2021-12-21

Product(s): InfoScale & Storage Foundation (8.0)

Platform: Windows

Recovery for Exchange 2010 using the vxsnap utility

Using the vxsnap utility, you can do the following:

Restore an Exchange 2010 database to the point in time (PIT) of the snapshot set
Perform a roll-forward recovery of an Exchange 2010 database to the point of failure (POF)

Before you begin, review the prerequisites.

See Prerequisites for recovery.

You use the vxsnap restore command. The complete syntax of the vxsnap restore command is:

vxsnap -x <filename>[-f][-b][-r] [-a] restore
restoreType=<PIT|POF>writer=<writername>[subComponent=<subCompo
nentName>][RSG=<Yes|No>]

Note:

The Subcomponent and RSG=YES|NO options are not valid for Exchange 2010.

To restore a database to the point in time of the snapshot set using the vxsnap restore command

If replication is enabled for a cluster setup, then use the Suspend-MailboxDatabaseCopy cmdlet to block replication and replay activities (log copying and replay).
```
Suspend-MailboxDatabaseCopy -Identity MB1[-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 -allowfilerestore:$true
```
Use the dismount-Database cmdlet to dismount the database.
```
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.
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
```
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.
If you have suspended replication as shown in step 1, then use the Update-MailboxDatabaseCopy cmdlet.
```
Update-MailboxDatabaseCopy -Identity MB1[-Confirm:$False]
```
Use -Confirm to prevent user intervention.

To perform a roll-forward recovery of a database to the point of failure using the vxsnap restore command

If replication is enabled for a cluster setup, then use the Suspend-MailboxDatabaseCopy cmdlet to block replication and replay activities (log copying and replay).
```
Suspend-MailboxDatabaseCopy -Identity MB1[-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 -allowfilerestore:$true
```
Use the dismount-Database cmdlet to dismount the database.
```
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.
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
```
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.
If you have suspended replication as shown in step 1, then use the Update-MailboxDatabaseCopy cmdlet.
```
Update-MailboxDatabaseCopy -Identity MB1[-Confirm:$False]
```
Use -Confirm to prevent user intervention.