NAME
swsrprestore_symfoware(Symfoware recovery execution command)
SYNOPSIS
<program-directory>\bin\swsrprestore_symfoware [-a | -e EndPoint] [-l ArchiveLogFileList-FileName] [-w Work-Directory] [-Xnolog Work-RecCtrlFile-Directory] -Xgroup Group-Name [-Xdev Device-Name | -Xdevlist DeviceListFile] Log-Group-Name[/RDB-Name]
DESCRIPTION
This command performs database space recovery cooperating with Symfoware.
This command is run on the Symfoware server.
During recovery of database spaces, access to the relevant database spaces must not be permitted. In order to prohibit access, execute the "rdbinh" command provided by Symfoware. For details on these commands, refer to the Symfoware Server RDB Operations Guide.
If recovery of a database space fails due to insufficient space in the working directory, you can use the -w option to retry recoverytemporarily specifying a different directory.
OPTIONS
Specify so that the entire database resource managed by the recovery control file is recovered to the point in time when backup was collected.
This option cannot be specified at the same time with the -e option.
Specify so that the entire database resource managed by the recovery control file is recovered to a specific point in time specified for end point.
For recovery end point, refer to the Symfoware Server manual.
This option cannot be specified at the same time with the -a option.
This option cannot be specified at the same time with the -Xnolog option, either.
Specify with the absolute path a file in which archive log backup destination names required for Symforware recovery are listed.
The file in which archive log backup names are listed and the archive backup destinations written on the file should be stored in the Managed Server in which a transaction volume performing revocrey exists.
This option cannot be specified at the same time with the -Xnolog option.
Specify a temporary working directory with the absolute path.
The directory name should be on the Managed Server in which a transactiom volume performing recovery exists.
When running the command on the Management Server, the directory should be on the Managed Server in which the transaction volume performing recovery exists.
An archive log is not applied at Symfoware recovery time.
Specify the directory that outputs the recovery control file required to apply the log and specify this directory when applying the log by the Symfoware command (rdbmrrcv).
If this option is specified to do recovery, database cannot be used till the log is applied by the Symfoware command (rdbmrrcv).
Specify a device name corresponding to the database space to be recovered.
Specify this option in either of the following cases:
Recover the database space contained in a log group.
Recover the database space that is not defined in a log group.
In this case, specify "system" for Log-Group-Name.
Specify a device list file in which device names corresponding to database space to be recovered at one time are listed.
The device list file is allocated on the Symfoware server.
For the device list file description method, refer to "How to describe device list file".
OPERANDS
Specify log group name.
Specify "system" for the database space that is not defined in a log group.
Specify RDB system name after log group name with slash "/" as a separator character.
If there is no RDB system name, it is omitted.
EXIT STATUS
=0 : Completed successfully
>0 : Terminated abnormally
EXAMPLES
Recover log group (LOG1/RDB1) by replication management function group (grp1).
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrprestore_symfoware -Xgroup grp1 LOG1/RDB1 LOG1/RDB1 swsrprestore_symfoware completed C:\>
Recover database space (DB1.DBS1(g1d1p1)) contained in log group (LOG1/RDB1) by replication management function group (grp1).
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrprestore_symfoware -Xgroup grp1 -Xdev g1d1p1 LOG1/RDB1 LOG1/RDB1 swsrprestore_symfoware completed C:\>
Recpver multiple database space contained in log group (LOG1/RDB1) by replication management function group (grp1). Multiple database space contained in the log group is specified in a device list file.
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrprestore_symfoware -Xgroup grp1 -Xdevlist c:\devlist.txt LOG1/RDB1 LOG1/RDB1 swsrprestore_symfoware completed C:\>
NOTES
swsrpmake (Replication creation command) is executed in this command. Please confirm notes of swsrpmake (Replication creation command) beforehand.
Restoration or recovery cannot be executed in the following situations:
An error was detected when during recovery of Symfoware.
When the file stating the names of the archive log backup files contains an archive log backup file that is backed up on an MT (tape device).
When the archive log files are stored on a different device at the time of recovering database spaces, the file which states the names of the backup locations for the archive logs and is required for recovery, must be stored beforehand on the Managed Server that contains the transaction volumes to be recovered. Refer to the Symfoware Server RDB Operations Guide for information on how to describe this file.
Recovery cannot be performed if the specified "file that includes the name of the archive log's backup location" contains an archive log backup file that is backed up on an MT (tape device). For recovery using an archive log that is backed up on an MT, use one of the following methods:
Deploy all backed up archive logs from the MT to the working directory.
Perform recovery without applying the log by specifying the -nolog option, and apply the archive log afterwards.
In order to apply the archive log after recovery without the log, execute the Symfoware's "rdbmrrcv" command. Refer to the Symfoware Server RDB Operations Guide for details on applying archive logs.
If you perform "recovery of a specific point in time by specifying the end point of recovery" or "recovery of the point in time of backup" during recovery of database spaces, processing to restore Symfoware's management information will also be implemented. Since this processing is implemented as a portion of recovery processing, it takes time for commands to be processed.
For recovering the database space, simultaneously issuing this command two or more times will result in some of the commands terminating abnormally when they meet the following requirements. The order of command execution is dependent on the OS. Which command(s) will terminate abnormally is not predictable. For instance, the command executed first might terminate abnormally.
When multiple commands specify a transaction volume:
Command(s) will terminate abnormally when multiple commands specify the same transaction volume or the specified transaction volumes use the same DSI. Details:
When multiple commands specify the same transaction volume.
When multiple commands specify different transaction volumes, but the transaction volumes use the same DSI.
(A DSI contains information for two or more transaction volumes.)
When DSI of the table relates to DSI of INDEX even if the different transaction volumes (transaction volume where DSI of the table is stored and transaction volume where DSI of INDEX is stored) are specified by each command.
When multiple commands specify two or more transaction volumes:
Command(s) will terminate abnormally when multiple commands specify transaction volumes that use the same log group. Details:
When the transaction volumes specified by different commands contain at least one of the same transaction volumes.
When the transaction volumes specified by different commands use the same log group, even though the transaction volumes do not contain any of the same transaction volumes.
When multiple commands specify a log group:
When multiple commands specify the same log group.
When a command specifies a transaction volume and another command specifies two or more transaction volumes:
When both commands specify a transaction volume that is included the same log group.
When a command specifies a log group and another command specifies other than log group:
Command(s) will terminate abnormally when multiple commands specify resources in the same log group. Details:
When the log group specified by a command and the log group that includes transaction volume(s) specified by another command is the same log group.
