NAME
swsrpvssbackup_exchange - backup of a Storage group or a database
SYNOPSIS
<program-directory>\bin\swsrpvssbackup_exchange [-evs Virtual-Server-Name] [-skipchk] -sgname Storage-Group-Name [-copygrp Copyset-Group-Name]
<program-directory>\bin\swsrpvssbackup_exchange [-skipchk] -dbname Database-Name
DESCRIPTION
This command cooperates with VSS to perform an on-line backup of a Storage group or a database.
The command performs the following processing:
By using VSS and AdvancedCopy, the backup data of a Storage group or a database is created on a backup server.
For snapshot type backups, shadow copies are created by starting an OPC or QuickOPC.
For synchronous type backups, shadow copies are created by suspending an EC or REC in an equivalency maintenance state.
A drive letter is assigned to the backup volume based on a drive letter map file. The backup volume can be accessed as a read-only volume.
ESEUTIL is performed against backup data to verify data integrity. When there is no problem with data integrity, Exchange deletes unnecessary log files.
The metadata documents, which are needed at the time of restoration, are saved in the following locations of the backup server:
File | Output place |
|---|---|
Writer metadata Document |
|
Backup component Document |
|
OPTIONS
A Storage group name is specified.
The storage group name containing a space needs to attach double quotation marks (" ")
A database name is specified.
The storage group name containing a space needs to attach double quotation marks (" ")
When cluster is used, the name of an Exchange virtual server (EVS) is specified.
When cluster employment is omitted, there is no necessity for specification.
This specifies that data consistency verification should not be performed by ESEUTIL.
Specifies the copy set group name.
If this option is omitted, the copy set group name will be the default name "BkupGroup".
This option is not supported in Windows Server 2008 or later.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
For the storage group "FirstStorageGroup" on the cluster operation (using MSCS) Exchange server "VSVR", backup is performed:
C:\>set SWSTGNODE=nodeAGT C:\> C:\Win32App\AdvancedCopyManager\bin\swsrpvssbackup_exchange -evs VSVR -sgname FirstStorageGroup -copygrp BK1 swsrpvssbackup_exchange successfully completed C:\>
For the storage group "FirstStorageGroup" on the cluster operation (using WSFC) Exchange server "VSVR", backup is executed:
C:\>set SWSTGNODE=nodeAGT C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpvssbackup_exchange -evs VSVR -sgname FirstStorageGroup swsrpvssbackup_exchange successfully completed C:\>
Back up database Mailbox1:
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpvssbackup_exchange -dbname Mailbox1 swsrpvssbackup_exchange successfully completed C:\>
NOTES
Backup cannot be executed in the following cases:
When the database information on the specified Storage group or database is not registered by swsrpdbinfo_ex2k3/swsrpdbinfo_exchange (Exchange database information registration command).
When the database composition of the specified Storage group or database is changed.
When acquisition of copy set information results in an error.
When communication with a backup server results in an error.
When the store is being dismounted.
When a copy set with a different copy type exists within the specified storage group or database.
When a copy set which cannot be used for the target Exchange server exists in the specified storage group or database.
When not all of the copy set synchronous processes for the storage group are in an equivalency maintenance state.
When an error occurs with a hardware provider processing.
When an error is caused by a hardware provider command.
When volume (i.e., partition) deletion of Backup LUN is not completed.
When a shadow copy exists in Backup LUN and deletion of a shadow copy is not completed.
When abnormalities are detected by consistency verification of backup data.
When preservation of a writer metadata document and a backup component document results in an error.
When assignment of the drive letter of backup volume results in an error.
When -skipchk option is specified
When verification of data consistency is omitted using -skipchk option, it is recommend strongly to verify data consistency manually after this command ends. For information about the method of verifying data consistency, refer to "support technical know-how" documents in the Microsoft Knowledge Base. In particular, refer to:
"Exchange Server 2003 data backup and Volume Shadow Copy services" (refer to the clause of "How to check snapshot consistency") (*1)
http://support.microsoft.com/kb/822896/en |
(*1) For Exchange Server 2007, Exchange Server 2010 or Exchange Server 2013 verification for "*.stm" file is not required.
When the command is cancelled
An Exchange writer may continue the backup processing when this command is forced to terminate by the task manager, by executing Ctrl-C, etc. In such a case, when you re-execute this command, an error message similar to the following message will be output, and backup cannot be performed.
swsrp4648 An error occurred in VSS processing. Processing Phase=[BACKUP] Creation of Shadow Copy Set, Detected API=StartSnapshotSet, Error=0x80042316 |
In order to recover from this situation, it is necessary to initialize the Exchange writer by restarting the "Microsoft Exchange Information Store" service. Note, however, that if this service is restarted, the client connecting to the Exchange Server may experience an unexpected termination or an unexpected connection shutdown. Therefore, we recommend that you consider the chance to restart this service after consultation with an Exchange administrator.
This command cannot be executed during execution of the following commands:
If an error occurs during the processing for a storage group or a database that is made up of multiple copy sets, processing for this command will be interrupted. If a synchronous-type backup was being performed, suspended synchronous processes must be restarted using swsrpvsssync_exchange (Exchange VSS synchronous processing command).
