NAME
swsrpvssrestore_exchange - restore of a Storage group or a database
SYNOPSIS
<program-directory>\bin\swsrpvssrestore_exchange (-point|-roll) -dbname databaseName
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.
When using WSFC for cluster operation in a Windows environment, this command performs automatic configuration of the maintenance mode of the physical disk resources to which the volume belongs with pre- and post-processing. For more information, refer to "15.1.8.1 When Using WSFC for Cluster Operation".
OPTIONS
A database name is specified.
If the database name contains a space, enclose it with double quotes.
A Point-in-Time system is restored.
A roll forward system is restored.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
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 the swsrpdbinfo_exchange 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 a business 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 -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.
This command cannot be executed during execution of the following commands:
This command terminates abnormally if it cannot turn the maintenance mode of the physical disk resource ON.
