Backup of the Exchange server databases can be stopped by performing the following steps:
Delete the shadow copy
Stop the copy process that is currently being executed
Delete the shadow copy by executing swsrpshadowadm_exchange (Exchange VSS shadow copy management command) on the Exchange server.
Example:
For Exchange Server 2007
C:\>set SWSTGNODE=nodeAGT C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpshadowadm_exchange delete -evs VSVR -sgname FirstStorageGroup swsrpshadowadm_exchange delete successfully completed C:\> |
For Exchange Server 2010 or Exchange Server 2013
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpshadowadm_exchange delete -dbname Mailbox1 swsrpshadowadm_exchange successfully completed C:\> |
Executing this command:
Deletes any shadow copy that exists on the backup server.
Deletes the backup server "writer metadata" documents and the "backup component" documents.
Note
OPC/QuickOPC physical copying and tracking are not stopped even if the shadow copy is deleted.
If all shadow copies are deleted from a disk, the disk status might change to "offline". Since AdvancedCopy Manager cannot execute copy for a disk that is offline, change the disk status to online if you want to continue to use the disk as a backup disk after the shadow copies are deleted. Refer to "1.7.2 Notes about the online/offline status of disks" for information about the online and offline status of disks under Windows Server 2008 or later.
To perform differential snapshot type backups, tracking processing must first be stopped.
Stop tracking processing by executing swsrpshadowadm_exchange (Exchange VSS shadow copy management command) on the Exchange server.
Example:
For Exchange Server 2007
C:\>set SWSTGNODE=nodeAGT C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpshadowadm_exchange stopqopc -evs VSVR -sgname FirstStorageGroup swsrpshadowadm_exchange successfully completed C:\> |
For Exchange Server 2010 or Exchange Server 2013
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpshadowadm_exchange stopqopc -dbname Mailbox1 swsrpshadowadm_exchange successfully completed C:\> |
It is also possible to stop tracking processing by executing the copy stop command (stxvcopy<source-disk>stop).
Stop the restoration copy process by executing swsrpcancel (Replication cancellation command) on the Exchange server.
Example:
For Exchange Server 2007
C:\>set SWSTGNODE=nodeAGT C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpcancel g1d11p1@BKUP-SVR g1d1p1@EXCHG-SVR FROM=g1d3p1@BKUP-SVR, TO=g1d1p1@EXCHG-SVR swsrpcancel completed C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpcancel g1d12p1@BKUP-SVR g1d2p1@EXCHG-SVR FROM=g1d4p1@BKUP-SVR, TO=g1d2p1@EXCHG-SVR swsrpcancel completed C:\> |
For Exchange Server 2010 or Exchange Server 2013
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpcancel g1d11p1@BKUP-SVR g1d1p1@EXCHG-SVR FROM=g1d3p1@BKUP-SVR, TO=g1d1p1@EXCHG-SVR swsrpcancel completed C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpcancel g1d12p1@BKUP-SVR g1d2p1@EXCHG-SVR FROM=g1d4p1@BKUP-SVR, TO=g1d2p1@EXCHG-SVR swsrpcancel completed C:\> |
When this command is executed, any restoration copy process in progress will be stopped.
It is generally not possible to use a transaction volume as a normal file system after restoration copy process has been stopped;
The transaction volumes must be reformatted so that they can be used again.
