NAME
swsrpvssrestore_exchange - restore of a Storage group or a database
SYNOPSIS
<program-directory>\bin\swsrpvssrestore_exchange [-evs Virtual-Server-Name] (-point|-roll) -sgname Storage-Group-Name [-copygrp Copyset-Group-Name]
<program-directory>\bin\swsrpvssrestore_exchange (-point|-roll) -dbname Database-Name
DESCRIPTION
This command cooperates with VSS to perform the restoration of a Storage group or a database.
Because it cooperates with VSS, the writer metadata document and backup component document which are saved in the backup server are used. One of the following two restoration systems is chosen and restoration is performed.
By restoring all the files (i.e., those with extensions *.edb, *.stm, *.log, *.chk) that constitute a Storage group or a database from the backup volume, a Storage group is restored to the time that the backup was created.
In this case, only database files (i.e., files with extensions *.edb, *.stm) are restored, the log application is performed using the log file which exists on the operating volume, and the database is restored to the newest time.
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 database name containing a space needs to attach double quotation marks (" ")
When cluster is being used, the name of an Exchange virtual server (EVS) is specified.
When cluster usage is omitted, there is no need to specify this option.
A Point-in-Time system is restored.
A roll forward system is restored.
A copy set group name is specified.
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", roll-forward restoration is performed:
C:\>set SWSTGNODE=nodeAGT C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpvssrestore_exchange -evs VSVR -roll -sgname FirstStorageGroup -copygrp GRP1 swsrpvssrestore_exchange successfully completed C:\>
For the storage group "FirstStorageGroup" on the cluster operation (using WSFC) Exchange server "VSVR", roll-forward restoration is performed:
C:\>set SWSTGNODE=nodeAGT C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpvssrestore_exchange -evs VSVR -roll -sgname FirstStorageGroup swsrpvssrestore_exchange successfully completed C:\>
For the database Mailbox1, roll-forward restoration is performed:
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpvssrestore_exchange -roll -dbname Mailbox1 swsrpvssrestore_exchange successfully completed C:\>
NOTES
When the following conditions occur, this command terminates abnormally:
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 acquisition of copy set information produces an error.
When a database volume and a backup volume are not registered as an original volume and a replica volume, respectively.
Volume information (i.e., box identifier, OLU, EXTENT start position, and EXTENT size) is changed after the operation starts. In this case, the operation cannot continue for the corresponding volume. Stop the replication operation for the corresponding volume, and then delete and reset the replication volume information.
When restoration is being performed using EC or REC and the restoration synchronous process is not in the equivalency maintenance state.
When an Exchange server is not the operation server of the replication volume.
When communication with a backup server produces an error.
When the database is in an inconsistent state.
When the store could not be dismounted. (Only applies under Exchange Server 2003)
When the store could not be mounted. (Only applies under Exchange Server 2003)
When the -roll option is specified and the log files exist on the same volume as database files (i.e., files with extensions *. edb, *.stm).
When a transaction log that is required (i.e., when the -roll option is specified) in order to perform a roll-forward does not exist in a log file.
When a volume undergoing the QuickOPC tracking process exists within the specified storage group or database.
When a backup (i.e., the copy source) volume could not be locked.
When the contents of the copy source volume locking specification file are invalid.
When a database volume (the original volume) could not be locked.
When the contents of the copy destination volume locking specification file are invalid.
When a writer metadata document and a backup component document do not exist on a backup server.
When backup data does not exist on the backup volume.
When the correspondence between the drive number and the OLU has collapsed, and editing of information re-collection/device.ini fails. (Applies under Windows Server 2008 or later)
This command cannot be executed during execution of the following commands:
