This section describes operation commands for backup management.
NAME
swstbackup - backup
SYNOPSIS
/opt/FJSVswsts/bin/swstbackup [-suspend|-T] [-k] Device-Name [-Xdevmap Device-Map-File]
/opt/FJSVswsts/bin/swstbackup [-h Server-Name] [-suspend|-T] [-k] Device-Name [-Xdevmap Device-Map-File]
/opt/FJSVswsts/bin/swstbackup -n [-suspend|-T] [-k] Log-Group-Name[/RDB-Name] [-Xdevmap Device-Map-File]
/opt/FJSVswsts/bin/swstbackup -n [-h Server-Name] [-k] [-suspend|-T] Log-Group-Name[/RDB-Name] [-Xdevmap Device-Map-File]
DESCRIPTION
When using this command, the operation changes according to different states of the Advanced Copy that is being executed.
When synchronous processing (EC) is not performed
Snapshot processing (OPC) is performed and the processing of information, such as the TimeStamp and backup volume of a copy target, is registered into backup history information.
When synchronous processing (EC) is performed
The state of synchronous processing is checked and, in the case of an equivalent maintenance state, backup synchronous processing is suspended. Information such as time and backup volume of a copy target is simultaneously registered into backup history information. A backup of this form is called synchronous high-speed backup. Note that it aborts when an equivalent maintenance state is not reached. To use the "Chapter 5 Backup Operation using Suspend/Resume Function" for synchronous high-speed backup, execute the backup command with -suspend option specified, and suspend backup synchronous processing.
In the above cases, a backup is established, and access to the backup volume is available immediately after the execution command.
AdvancedCopy Manager executes backup pre-processing and post-processing scripts before and after backup.
For information on customizing these scripts, refer to "Appendix A Pre-processing and Post-processing of Backup and Restoration".
OPTIONS
Specifies a Managed Server name.
This option can be specified only on a Management Server.
Specifies implementation of backup with reference dump.
If you omit this option, backup will be implemented with normal dump.
When you back up with reference dump, you have to execute Symfoware's "rdbrtr" command in order to set inhibition of updates (disable writing of data) for all DSI (function that expresses the storage structures for tables) on the transaction volumes to be backed up.
It cannot specify this option for the transaction volumes other than Symfoware.
Specifies that the item being backed up is a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
Specifies a target backup volume to perform the snapshot fast backup. In the operand, specify a "device map file" in which a combination of a transaction volume and a target backup volume are described. If this option is not specified, the target backup volume will be automatically selected by the backup function. To execute this command on a remote basis using the -h option, specify a device map file (of a Managed Server) using an absolute pathname. A file name specified in Device-Map-File must not include any national character.
This results in synchronous high-speed backup using the "Chapter 5 Backup Operation using Suspend/Resume Function".
Specifies that the differential snapshot high-speed backup be executed.
This option cannot be specified during synchronous processing.
This option is valid only for copying within a box when the ETERNUS Disk storage system supports the QuickOPC function.
If this option is not specified, ordinary snapshot processing (ie, OPC without using the QuickOPC function) is started. This option must always be specified to perform a backup operation using differential snapshots.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Back up a transaction volume:
# /opt/FJSVswsts/bin/swstbackup /dev/sdg3 /dev/sdg3 swstbackup completed #
Back up log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swstbackup -n LOG01/RDB1 LOG01/RDB1 swstbackup completed #
NOTES
To preserve data integrity, this command performs the backup only after inhibiting access to both transaction and backup volumes from all other processes. Thus, drive letters, logical volume names or device labels of devices are unassigned. This command terminates with an error if a drive letter, logical volume name or device label of a transaction volume is assigned or if:
The mount point has directories to which other volumes are also mounted.
The volume has a file in use.
When the -bind option in the mount command is specified to mount part of the file hierarchy of the transaction volume at another mount point, use backup manager's authority to unmount the transaction volume.
Do not execute the backup execution command in a state where another volume is mounted at the mount point of the target volume.
For such a state, unmount the other volume before executing the backup execution command.
To mount a transaction volume from a server other than the server on which this command is entered, unmount the transaction volume, using the authority of the backup administrator. If the transaction volume must not be unmounted, create backup copies with the following procedure:
Execute the sync command to synchronize the transaction volume and file system.
Execute this command.
Execute the fsck command for the backup volume, and check the file system.
Backup cannot be executed in the following situations:
No backup policy has been specified for the specified transaction volume.
The backup that was executed one generation earlier was unsuccessful.
Restore is being performed to the transaction volume that is to be backed up.
Synchronous backup processing is performed in a transaction volume or a log group to be processed, but the state of equivalence is not reached;
Restoration is being executed using backup history information that will cause a generation overflow (this may occur when restoration is performed using the backup volume of the oldest history).
Any of the box information (box identifier, OLU number, EXTENT start position, and EXTENT size) of a transaction volume has been changed.
No unused backup volume was available for use as the copying destination.
The replication management function is executing a process for the target transaction volume.
The replication management function is executing a process for the target backup volume.
The replication management function is executing a process for backup records exceeding the number of preservation generations.
The mount point of a transaction volume set at registration has been changed.
A backup volume defined as the copy destination is mounted.
An error was detected during backup of Symfoware database spaces.
When during backup of transaction volumes with Symfoware's reference dump specified, multi-database spaces are being used.
When the -T option is specified during the operation in which SDX objects are backed up in units of logical volumes
When the -n option was specified for a log group in which GDS and non-GDS volumes are mixed.
You cannot perform backup if:
The backup volume specified by the device map file cannot be paired with the transaction volume. This occurs if:
The specified backup volume is in use.
The transaction volume and the backup volume are not the same partition size.
The device map file contains an error (refer to "3.4.9.1 Describing a device map file").
The device map file name includes a national character.
When an ordinary volume is specified as the transaction volume and a GDS logical volume as the backup volume.
When a GDS logical volume is specified as the transaction volume and an ordinary volume as the backup volume.
At this time, if existing backup history information satisfies the condition of the number of saved generations specified by swstbkpolset (Backup policy setting command), then information on the oldest generation is automatically deleted from the backup history information during the backup process, and the backup volume is cleared. However, if -suspend or -T option is specified for the backup history information, then the backup volume with the Suspend or tracking state is not cleared and the backup volume remains in use.
The transaction volume on which the backup command is executed, one other transaction volume, and the suspended or tracking backup volume cannot be specified as backup destinations in the device map file.
For details on how to use SDX objects of GDS, refer to "Configuration and conditions of unsupported SDX objects" and "10.1.5.1 Notes on SDX object operations (backup management)".
The pre-processing and post-processing scripts are not executed when the mirror partition of the SDX object is TEMP.
This command can be executed only while none of the following commands are running:
NAME
swstbackstat - displays the completion status of a backup
SYNOPSIS
/opt/FJSVswsts/bin/swstbackstat [Device-Name]/opt/FJSVswsts/bin/swstbackstat [-h Server-Name] [Device-Name]
/opt/FJSVswsts/bin/swstbackstat -n Log-Group-Name[/RDB-Name]
/opt/FJSVswsts/bin/swstbackstat -n [-h Server-Name] Log-Group-Name[/RDB-Name]
DESCRIPTION
This command displays the completion status of a backup that is being performed using swstbackup (Backup execution command).
The following information will be displayed:
Title | Description |
|---|---|
Server | Displays a Managed Server name. |
Transaction-Disk | Displays the AdvancedCopy Manager device name of a transaction volume. |
Backup-Disk | Displays a backup volume name. If no backup has been collected, "----" will be displayed. |
Status | Displays a backup completion status using one of the following character strings: "----" : No backup has been collected (ie, no history exists). |
Execute | Displays how much has been copied in percentage terms if "executing" is displayed in the Status column. Displays "----" unless "executing" is displayed. |
OPTIONS
Specifies a Managed Server name.
This option can be specified only on a Management Server.
Specifies that the item being displayed is a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
OPERANDS
Specifies the "1.5 Managing a Device on AdvancedCopy Manager" corresponding to a transaction volume.
If this operand is omitted, the backup execution statuses of all the transaction volumes will be displayed.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Display the actual copying execution status:
# /opt/FJSVswsts/bin/swstbackstat Server Transaction-Disk Backup-Disk Status Execute Work1 /dev/sdb3 /dev/sdd3 succeeded ---- Work1 /dev/sdb4 /dev/sdd4 executing 70% Work1 /dev/sdb5 /dev/sdd5 executing 30% : #
NOTES
Do not use the OPC stop function of ETERNUS Web GUI while the snapshot fast backup is in progress. If you do use the OPC stop function of ETERNUS Web GUI, it will display "succeeded" whether or not the backup has actually been successful.
If "failed", "halt", or "?????" is displayed in the Status column, a hardware error, etc. may have occurred. Refer to "8.3 Troubleshooting: Hardware error during backup" for information about this.
If "gds-error" is displayed in the Status column, a problem with GDS is assumed.
Remedy the cause of the GDS problem, and take one of the following steps:
If backup synchronous processing is in progress, execute swstcancelsync (Backup synchronous processing cancel command) to cancel the backup synchronous processing.
If snapshot backup is in progress, execute swsthistdel (History information deletion command) to delete the backup history information.
If restoration is in progress, execute swstsrsemtch (Resource match command), and perform restoration again.
NAME
swstrestore - restore
SYNOPSIS
/opt/FJSVswsts/bin/swstrestore [-g Generation-No | -v Version-No] [-r Restore-Device-Name] [-Xgds-softcopy] Device-Name
/opt/FJSVswsts/bin/swstrestore [-h Server-Name] [-g Generation-No | -v Version-No] [-r Restore-Device-Name] [-Xgds-softcopy] Device-Name
/opt/FJSVswsts/bin/swstrestore [-g Generation-No | -v Version-No] [-l ArchiveLogFileList-FileName] [-w Work-Directory] [-nolog Work-RecCtrlFile-Directory] [-Xgds-softcopy] Device-Name
/opt/FJSVswsts/bin/swstrestore [-h Server-Name] [-g Generation-No | -v Version-No] [-l ArchiveLogFileList-FileName] [-w Work-Directory] [-nolog Work-RecCtrlFile-Directory] [-Xgds-softcopy] Device-Name
/opt/FJSVswsts/bin/swstrestore -bundle [-g Generation-No | -v Version-No] [-a | -e EndPoint] [-l ArchiveLogFileList-FileName] [-w Work-Directory] [-nolog Work-RecCtrlFile-Directory] [-Xgds-softcopy] DeviceListFile
/opt/FJSVswsts/bin/swstrestore -bundle [-h Server-Name] [-g Generation-No | -v Version-No] [-a | -e EndPoint] [-l ArchiveLogFileList-FileName] [-w Work-Directory] [-nolog Work-RecCtrlFile-Directory] [-Xgds-softcopy] DeviceListFile
/opt/FJSVswsts/bin/swstrestore -n [-g Generation-No | -v Version-No] [-a | -e EndPoint] [-l ArchiveLogFileList-FileName] [-w Work-Directory] [-nolog Work-RecCtrlFile-Directory] [-Xgds-softcopy] Log-Group-Name[/RDB-Name]
/opt/FJSVswsts/bin/swstrestore -n [-h Server-Name] [-g Generation-No | -v Version-No] [-a | -e EndPoint] [-l ArchiveLogFileList-FileName] [-w Work-Directory] [-nolog Work-RecCtrlFile-Directory] [-Xgds-softcopy] Log-Group-Name[/RDB-Name]
DESCRIPTION
The data that exists in backup history information is restored using OPC.
When this command is executed, AdvancedCopy Manager performs the restoration pre-processing and post-processing scripts before and after copying data using OPC. For more information on customizing these scripts, refer to "Appendix A Pre-processing and Post-processing of Backup and Restoration".
You can restore data to a device that is not a transaction volume. When you do so, the device must not be registered as a transaction volume and the device must have the same amount of space available as the specified transaction volume.
For transaction volumes of Symfoware and logical volumes of GDS, restoring to devices other than the original transaction volumes is not available.
During recovery of database spaces, access to the relevant database spaces must not be permitted. In order to prohibit access, execute the "rdbinh" or the "rdbexspc" 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 recovery temporarily specifying a different directory.
OPTIONS
Specifies a Managed Server name.
This option can be specified only on a Management Server.
Specifies the relative generation number of data to be restored.
Check the relative generation number using swsthistdisp (History information display command).
Specifies the absolute generation number of data to be restored.
Check the absolute generation number using swsthistdisp (History information display command).
Specifies a restore destination device name to restore data to any device other than a transaction volume.
Cannot be specified for a Symfoware transaction volume.
Specifies that the entire database resources managed by a recovery control file shall be recovered up to the point in time of backup collection.
Cannot be specified at the same time as the -e option.
Cannot be specified when recovering individual transaction volumes in a log group.
Cannot be specified for the transaction volumes other than Symfoware.
Specifies that the entire database resources managed by a recovery control file shall be recovered up to a specific recovery point. For details on recovery points, refer to the Symfoware Server manuals.
Cannot be specified at the same time as the -a option.
Cannot be specified at the same time as the -nolog option.
Cannot be specified when recovering individual transaction volumes in a log group.
Cannot be specified for the transaction volumes other than Symfoware.
Specifies the absolute path of the file stating the names of the backup locations for the archive logs that are required for recovery of Symfoware.
The file stating the name of the backup locations for the archive logs must be stored on the Managed Server that contains the transaction volumes to be restored.
If you execute this command on a Management Server, the file must be stored on the Managed Server that contains the transaction volumes to be restored.
Cannot be specified at the same time as the -nolog option.
Cannot be specified for the transaction volumes other than Symfoware.
Specifies the absolute path to the name of a temporary working directory.
The directory must be located on the Managed Server that contains the transaction volumes to be restored.
If you execute this command on a Management Server, the directory must be located on the Managed Server that contains the transaction volumes to be recovered.
If this option is omitted, the working directory specified in swstsvrset (Managed Server configuration information setting command) will be used.
Cannot be specified for the transaction volumes other than Symfoware.
Specifies that the item being restored is a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
Specifies bundle recovery of multiple database spaces.
In the operand, specify the file (DeviceListFile) stating the device names corresponding with the database spaces to be recovered in a batch.
During recovery of Symfoware, archive logs are not applied.
If you want to specify an output directory for the recovery control files that are required when applying the log, and then apply the log by Symfoware's "rdbmrrcv" command, you can specify this directory.
If you perform recovery with this option specified, the database will not be available for use until you apply the log with Symfoware's "rdbmrrcv" command.
Performs restoration by software-copy for restoration in linkage with GDS Snapshot. If this option is not specified, restoration is performed with OPC.
Note: If neither the -g or -v option is specified, the latest information from the information history management will be restored.
OPERANDS
Specifies the AdvancedCopy Manager device name corresponding to a transaction volume.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
Specify the device list file that states the device names corresponding with the database spaces to be recovered in a batch.
If you execute this command on a Management Server, this file must be stored on the Managed Server that contains the transaction volumes to be recovered.
For information on how to describe device list files, refer to "4.1.5.3.1 Describing a device list file".
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Restore data with relative generation number 2. For information on the relative generation number, refer to data displayed using swsthistdisp (History information display command):
# /opt/FJSVswsts/bin/swstrestore -g 2 /dev/sdb6 /dev/sdb6 swstrestore completed #
Restore data with relative generation number 2 for log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swstrestore -n -g 2 LOG01/RDB1 LOG01/RDB1 swstrestore completed #
If the "Chapter 5 Backup Operation using Suspend/Resume Function" is used for the backup operation on the transaction volume, the suspended synchronous processing is deleted and the restore command is executed. For information on the suspended synchronous processing, refer to the data displayed by swstsyncstat (Backup synchronous processing progress display command). Execute swstcancelsync (Backup synchronous processing cancel command) to cancel the synchronous processing:
# /opt/FJSVswsts/bin/swstsyncstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Work2 /dev/sdb6 /dev/sdd6 suspend ---- Work2 /dev/sdb6 /dev/sde5 executing 75% # /opt/FJSVswsts/bin/swstcancelsync -all /dev/sdb6 /dev/sdb6 swstcancelsync completed # /opt/FJSVswsts/bin/swstsyncstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Work2 /dev/sdb6 ---- ---- ---- # /opt/FJSVswsts/bin/swstrestore /dev/sdb6 /dev/dsk/sdb6 swstrestore completed #
NOTES
On a transaction volume on which a file system has been constructed, restore a specific file as follows:
Mount a backup volume. Check the backup volume by executing the Backup History List view/swsthistdisp (History information display command).
Copy the file to be restored by executing, for example, the cp command.
Unmount the backup volume.
If a transaction volume is mounted from a server other than the server on which this command is entered, execute this command after unmounting the transaction volume, using the authority of the backup administrator.
When the -bind option in the mount command is specified to mount part of the file hierarchy of the transaction volume at another mount point, use the backup administrator's authority to unmount the transaction volume.
Do not execute the restore execution command in a state where another volume is mounted at the mount point of the target volume.
In this case, unmount the other volume before executing the restore execution command.
Restoration or recovery cannot be executed in the following situations:
When both relative and absolute generation numbers have been specified.
When a device registered as a transaction volume has been specified in a parameter with the -r option.
When a device registered as a backup volume has been specified in a parameter with the -r option, the device has been registered in the backup registration information of a certain transaction volume. If you restore data to a backup volume without registered backup data, and the backup volume is used to back up a certain transaction volume, then data will be overwritten. It is recommended that a backup volume should NEVER be specified as a restore destination device.
When you perform restoration immediately after starting backup where the actual copying using OPC is still in progress, (except when the combination of transaction volume and backup volume is the same for backup and restoration). A restoration should always be performed after the actual copying using OPC is completed. Alternatively, on a transaction volume on which a file system has been constructed, perform restoration according to the method described in the Point "In a transaction volume on which a file system has been constructed, restore a specific file" above.
A transaction volume currently in use with synchronous backup processing is specified.
When any of the box information (box identifier, OLU number, EXTENT start position, and EXTENT size) of a transaction volume to be restored has been changed.
The replication management function is executing a process for the target transaction volume.
The replication management function is executing a process for the device specified in the -r option.
The mount point set at registration of a transaction volume has been changed.
The -Xgds-softcopy option is specified for a device that is not a GDS logical volume.
A GDS logical volume is specified as the restoration destination volume of an ordinary transaction volume.
The -n or -bundle option was specified when GDS volumes and non-GDS volumes are mixed in a log group.
Different backup methods (normal dump or reference dump) to recover data exist in the same log group, when you specify a log group or you perform recovery of multiple volumes in a batch,
The -r option was specified when you perform recovery of the transaction volumes of Symfoware.
When an SDX object has been specified in a parameter with the -r option.
When the -a, -e, -l, -w, -bundle, or -nolog option was specified for setting transaction volumes other than Symfoware.
When a directory name specified in the -w, -l, -bundle, or -nolog option contains double-byte characters (as used in Asian languages).
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).
The suspended or tracking backup volume cannot be used as the restore destination volume.
The restore command cannot be executed on a transaction volume during synchronous processing (eg, during copying by EC, under the equivalency maintained status, in the Suspend state).
If the following errors occur during restore processing, then execute swstcancelsync (Backup synchronous processing cancel command) (with the -all option specified) to cancel all of the synchronous processing of the transaction volume, and execute the restore command:
"swst0639 This Command cannot be run. This is because a copy is currently running"
"swst0634 OPC cannot be run. Error code=26 (SCSI command busy)"
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. For information on how to describe this file, refer to the Symfoware Server RDB Operations Guide.
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. For details on applying archive logs, refer to the Symfoware Server RDB Operations Guide.
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 details on how to use SDX objects of GDS, refer to "Configuration and conditions of unsupported SDX objects" and "10.1.5.1 Notes on SDX object operations (backup management)".
This command can only be executed while none of the following commands are running:
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.
NAME
swstcancelrest - cancels OPC-based restoration
SYNOPSIS
/opt/FJSVswsts/bin/swstcancelrest [-g Generation-No | -v Version-No] [-r Restore-Device-Name] [-emergency] Device-Name
/opt/FJSVswsts/bin/swstcancelrest [-h Server-Name][-g Generation-No | -v Version-No][-r Restore-Device-Name] [-emergency] Device-Name
/opt/FJSVswsts/bin/swstcancelrest -n [-g Generation-No | -v Version-No ] [-emergency] Log-Group-Name[/RDB-Name]
/opt/FJSVswsts/bin/swstcancelrest -n [-h Server-Name] [-g Generation-No | -v Version-No ] [-emergency] Log-Group-Name[/RDB-Name]
DESCRIPTION
This command cancels OPC-based restoration.
A hardware error will be displayed when swstrestore (Restore execution command) is executed while data is being copied using OPC. Fix the cause of the hardware error and repeat restoration using swstrestore (Restore execution command).
Check whether a fault occurred using swstreststat (Restore execution status display command).
OPTIONS
Specifies a Managed Server name.
This option can be specified only on a Management Server.
Specifies the relative generation number of data being restored.
This option cannot be specified at the same time as the -v option.
Check the relative generation number using swstreststat (Restore execution status display command).
Specifies the absolute generation number of data being restored.
This option cannot be specified at the same time as the -g option.
Check the absolute generation number using swstreststat (Restore execution status display command).
Specifies the device name if data is restored to any other device than a transaction volume.
Check the device name using swstreststat (Restore execution status display command).
It cannot specify this option for the transaction volumes of Symfoware.
Emergency operation mode is available for operations.
In such cases, OPC sessions are neither confirmed nor cancelled.
Specifies that the restore is being cancelled for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
Note: The restoration of the latest history information will be cancelled if neither the -g or -v option is specified.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Cancel restoration of the transaction volume:
# /opt/FJSVswsts/bin/swstcancelrest -g 1 /dev/sdb6 /dev/sdb6 swstcancelrest completed. #
Restoration of the latest history information on the transaction volume is cancelled in emergency operation mode:
# /opt/FJSVswsts/bin/swstcancelrest -emergency /dev/sdb6 /dev/sdb6 swstcancelrest completed. #
Cancel restoration of log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swstcancelrest -n -g 1 LOG01/RDB1 LOG01/RDB1 swstcancelrest completed. #
NOTES
If you cancel OPC-based restoration using this command, the transaction volume will be in an incomplete state and can no longer be used because part of the data has already been overwritten by the copy process. Perform restoration again using swstrestore (Restore execution command).
If the transaction volume is a GDS logical volume and restoration is cancelled, the state of the transaction volume becomes INVALID. In such cases, refer to the PRIMECLUSTER(TM) Global Disk Services User's Guide (Linux), and restore the logical volume.
You cannot cancel restoration if:
The history specified in the -g or -v option does not exist.
Restoration is not performed on the device specified in the -r option.
Restoration is not performed from the specified history. In this case, processing is terminated with an information message "swst0303 Restoration for specified restoration device is not performed". The end status after this message is a normal end.
The -n option was specified when GDS volumes and non-GDS volumes are mixed in a log group.
The replication management function is executing a process for the target transaction volume
However, OPC sessions are neither confirmed nor cancelled by execution in emergency operation mode. If an OPC session is in the error suspended state, then unmanaged sessions remain. In this case, ETERNUS Web GUI must be used to cancel these sessions.
This command can only be executed while none of the following commands are running:
NAME
swstreststat - displays the execution status of restoration
SYNOPSIS
/opt/FJSVswsts/bin/swstreststat [-g Generation-No | -v Version-No] [-Xgds-softcopy] [Device-Name]
/opt/FJSVswsts/bin/swstreststat [-h Server-Name] [-g Generation-No | -v Version-No] [-Xgds-softcopy] [Device-Name]
/opt/FJSVswsts/bin/swstreststat -n [-g Generation-No | -v Version-No] [-Xgds-softcopy] Log-Group-Name[/RDB-Name]
/opt/FJSVswsts/bin/swstreststat -n [-h Server-Name] [-g Generation-No | -v Version-No] [-Xgds-softcopy] Log-Group-Name[/RDB-Name]
DESCRIPTION
This command displays the execution status of restoration.
The following information will be displayed:
Title | Description |
|---|---|
Server | Displays a Managed Server name. |
Transaction-Disk | Displays the AdvancedCopy Manager device name of a transaction volume. |
Generation | Displays the relative generation number of restored backup data. "----" will be displayed if no generation number is specified in the -g or -v option and no backup history exists. |
Version | Displays the absolute generation number of restored backup data. "----" will be displayed if no generation number is specified in the -g or -v option and no backup history exists. |
Backup-Disk | Displays the name of a backup volume from which data should be copied and restored. "----" will be displayed if restoration is not in progress. |
Restore-Device | Displays a restoration target device name unless data is copied and restored to a transaction volume. "----" will be displayed if restoration is not in progress, or if data is restored to a transaction volume. |
Status | Displays the execution status: "----" : No copying using OPC or software-copy by GDS is in progress. |
Execute | Displays how much has been copied in percentage terms if "executing" is displayed in the Status column. Displays "----" unless "executing" is displayed. |
OPTIONS
Specifies a Managed Server name.
This option can be specified only on a Management Server.
Specifies the relative generation number of data whose restore execution status is to be displayed.
Specifies the absolute generation number of data whose restore execution status is to be displayed.
Specifies that the execution status of restoration being displayed is for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
Displays the restore execution status of a GDS logical volume.
Use this option to check the copy status when restoration using the software-copy function of GDS is in progress.
When the option is specified, the Status column display when copying is completed is "----", which is the same as before copying started.
Note: The restore execution statuses of all the histories will be displayed if both the -g and -v options are omitted.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
If this operand is omitted, the restore execution statuses of all the transaction volumes will be displayed.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Display the restore execution statuses of transaction volumes:
# /opt/FJSVswsts/bin/swstreststat Server Transaction-Disk Generation Version Backup-Disk Restore-Device Status Execute Work2 /dev/sdb3 1 10 /dev/sdd3 /dev/sdc3 executing 75% Work2 /dev/sdb4 ---- ---- ---- ---- ---- ---- Work2 /dev/sdb5 2 12 /dev/sdd5 ---- succeeded ---- Work2 /dev/sdb6 3 13 /dev/sdd6 /dev/sdc6 executing 75% : #
NOTES
Do not use the OPC stop function of ETERNUS Web GUI while the snapshot fast backup is in progress. If you use the OPC stop function of ETERNUS Web GUI, this command displays "succeeded" whether or not the restoration has actually been successful.
If "failed", "halt", or "?????" is displayed in the Status column, a hardware error, etc. may have occurred. Refer to "8.3 Troubleshooting: Hardware error during backup" for information about this.
If no generation number has been specified in the -v or -g option, the restore execution statuses of all the histories will be displayed. If, at this time, restoration is not in progress from any of the histories, "----" will be displayed in all the information columns other than "Server" and "Transaction-Disk".
If "gds-error" is the status displayed in the Status column, a problem with GDS is assumed. Correct the cause of the GDS problem, and take action as follows:
If backup synchronous processing is in progress, execute swstcancelsync (Backup synchronous processing cancel command) to cancel the backup synchronous processing.
If snapshot backup is in progress, execute swsthistdel (History information deletion command).
If restoration is in progress, execute swstsrsemtch (Resource match command), and perform restoration again.
NAME
swsthistdisp - displays the backup history information
SYNOPSIS
/opt/FJSVswsts/bin/swsthistdisp [Device-Name]/opt/FJSVswsts/bin/swsthistdisp [-h Server-Name] [Device-Name]
/opt/FJSVswsts/bin/swsthistdisp -n Log-Group-Name[/RDB-Name]
/opt/FJSVswsts/bin/swsthistdisp -n [-h Server-Name] Log-Group-Name[/RDB-Name]
DESCRIPTION
This command displays history information in relation to data that has been backed up.
The following information will be displayed:
Title | Description |
|---|---|
Server | Displays a Managed Server name. |
Device | Displays the AdvancedCopy Manager device name. |
Mount-Point | Displays the mount point of a device. The file system type of the mount point is displayed inside the parentheses. If the "Device" is a transaction volume used for Symfoware, the names of Symfoware database spaces and log groups as well as the RDB system names are displayed, followed by "SymfoWARE" in parentheses. |
Generation | Displays a relative generation number. |
Version | Displays an absolute generation number. |
Backup-Date | Displays a TimeStamp reflecting when backup has been completed. |
Backup-Disk | Displays the name of a backup volume to which data has been backed up. |
Status | Displays an actual copying execution status using one of the following character strings: "succeeded" : Copying using OPC has been completed. This item will not be displayed if no backup history information exists. |
Execute | Displays how much has been copied in percentage terms if "executing" is displayed in the Status column. Displays "----" unless "executing" is displayed. |
ArcSerial | Displays the serial number of the archive log. |
OPTIONS
Specifies a Managed Server name.
This option can be specified only on a Management Server.
Specifies that the backup history information being displayed is for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
If this operand is omitted, the backup history information of all the transaction volumes will be displayed.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Display the backup history information of all the transaction volumes:
# /opt/FJSVswsts/bin/swsthistdisp Server=StrgSV01 Device=/dev/sdb6 Mount-Point=/mnt/Tran1 (ext2) Generation Version Backup-Date Backup-Disk Status Execute 1 10 2000/11/12 22:00 /dev/sdd6 succeeded ---- 2 9 2000/11/11 22:00 /dev/sdf6 succeeded ---- : #
NOTES
If "failed", "halt", or "?????" is displayed in the Status column, a hardware error, etc. may have occurred. Refer to "8.3 Troubleshooting: Hardware error during backup" for information about this.
If "gds-error" is the status displayed in the Status column, a problem with GDS is assumed. Correct the cause of the GDS problem, and take action as follows:
If backup synchronous processing is in progress, execute swstcancelsync (Backup synchronous processing cancel command) to cancel the backup synchronous processing.
If snapshot backup is in progress, execute swsthistdel (History information deletion command).
If restoration is in progress, execute swstsrsemtch (Resource match command), and perform restoration again.
NAME
swsthistdel - deletes backup history information
SYNOPSIS
/opt/FJSVswsts/bin/swsthistdel -g Generation-No | -v Version-No | -z [-emergency] Device-Name
/opt/FJSVswsts/bin/swsthistdel [-h Server-Name] -g Generation-No | -v Version-No | -z [-emergency] Device-Name
/opt/FJSVswsts/bin/swsthistdel -n -g Generation-No | -v Version-No | -z [-emergency] Log-Group-Name[/RDB-NAME]
/opt/FJSVswsts/bin/swsthistdel -n [-h Server-Name] -g Generation-No | -v Version-No | -z [-emergency] Log-Group-Name[/RDB-NAME]
DESCRIPTION
This command deletes backup history information.
The backup volume of the deleted history is released and becomes an empty backup volume.
When you delete the history information for Symfoware transaction volumes, the recovery control files will also be deleted.
OPTIONS
Specifies a Managed Server name.
This option can only be specified on a Management Server.
Specifies the relative generation number of backup history information to be deleted.
This option cannot be specified at the same time as the -v or -z option.
Check the relative generation number using swsthistdisp (History information display command).
Specifies the absolute generation number of backup history information to be deleted.
This option cannot be specified at the same time as the -g or -z option.
Check the absolute generation number using swsthistdisp (History information display command).
Specifies that all the backup history information is to be deleted.
This option cannot be specified at the same time as the -g or -v option.
Emergency operation mode is available for operations.
In such cases, OPC sessions are neither confirmed nor cancelled.
Specifies that the backup history being deleted is for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Delete a history with absolute generation number 10 of a transaction volume:
# /opt/FJSVswsts/bin/swsthistdel -v 10 /dev/sdb6 /dev/sdb6 swsthistdel completed #
The history information of relative generation number 1 of the transaction volume is deleted in the emergency operation mode:
# /opt/FJSVswsts/bin/swsthistdel -g 1 -emergency /dev/sdb6 /dev/sdb6 swsthistdel completed #
Delete the backup history of absolute generation number 10 for log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swsthistdel -n -v 10 LOG01/RDB1 /dev/sdd1 swsthistdel completed /dev/sdd2 swsthistdel completed : LOG01/RDB1 swsthistdel completed #
NOTES
You cannot delete backup history information if:
The backup history information specified in the -g or -v option does not exist.
The specified backup history information is currently being used in a restoration.
The replication management function is executing a process for the target transaction volume.
The replication management function is executing a process for the target backup volume.
However, OPC sessions are neither confirmed nor cancelled by execution in emergency operation mode. If an OPC session is in the error suspended state, then unmanaged sessions remain. In this case, ETERNUS Web GUI must be used to cancel these sessions.
Deleting the suspended history information does not cancel the synchronous processing (in an EC session).
Deleting the tracking history information does not cancel the tracking processing (in an OPC session).
In synchronous high-speed backup with -suspend option specified, the backup volume remains in use even after the history information is deleted.
In differential snapshot high-speed backup with -T option specified, the backup volume remains in use even after the history information is deleted.
If the history information is deleted while the OPC physical copy has not been completed in a backup operation mode other than the differential snapshot high-speed backup, physical copying of the deleted history is interrupted. In this case, the data in the backup volume is incomplete (ie, copy has stopped part way through). The backup volume is put in the unused state upon deletion of the history information and becomes ready for use in the next backup.
In the differential snapshot high-speed backup mode, the physical copying of the deleted history is continued even after the history information on the incomplete OPC physical copy is deleted. Even after deletion of the history information, the backup volume is in the busy state and becomes ready for use in the next backup of the relevant transaction volume.
For details on how to use SDX objects of GDS, refer to "Configuration and conditions of unsupported SDX objects" and "10.1.5.1 Notes on SDX object operations (backup management)".
This command can be executed only while none of the following commands are running:
NAME
swststartsync - starts backup synchronous processing
SYNOPSIS
/opt/FJSVswsts/bin/swststartsync [-Xgds-softcopy | -Xgds-selectcopy] Device-Name [-Xdevmap Device-Map-File]
/opt/FJSVswsts/bin/swststartsync [-h Server-Name] [-Xgds-softcopy | -Xgds-selectcopy] Device-Name [-Xdevmap Device-Map-File]
/opt/FJSVswsts/bin/swststartsync [-Xgds-softcopy | -Xgds-selectcopy] -n Log-Group-Name[/RDB-NAME] [-Xdevmap Device-Map-File]
/opt/FJSVswsts/bin/swststartsync -n [-h Server-Name] [-Xgds-softcopy | -Xgds-selectcopy] Log-Group-Name[/RDB-NAME] [-Xdevmap Device-Map-File]
DESCRIPTION
This command starts backup synchronous processing (ie, it starts disk-to-disk copy using EC).
Even if it is already in use, the transaction volume where the synchronous processing started s well as the suspended backup volume can be used as backup destinations.
Except for the transaction volume where the synchronous processing started and the suspended backup volume, transaction volumes cannot be specified as backup destinations in the device map file.
If you execute this command with specifying a log group name, backup synchronous processing will be executed for all transaction volumes that are included in the specified log group. If execution of this command terminates with an error, backup synchronous processing that was performed so far will be cancelled. However, if the status was "suspend" before command execution, even after terminating with an error, synchronous processing will not be cancelled.
Also, you can run this command specifying individual transaction volumes that are included in a log group.
For a GDS transaction volume, synchronous processing by software-copy is also possible.
OPTIONS
Specify the name of a Managed Server.
This option can be specified only on the Management Server.
Specifies a target backup volume to perform the backup synchronous processing. In the operand, specify a device map file in which a combination of a transaction volume and a target backup volume is described. If this option is not specified, a target backup volume will be automatically selected. To execute this command on a remote basis using the -h option, specify a device map file of a Managed Server using an absolute pathname. A file name specified in Device-Map-File must not include any national characters.
Specifies that backup synchronous processing is being started for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
Specifies the start of backup synchronous processing of an SDX object and use of the software-copy function instead of the Advanced Copy function.
If you specify this option to start differential copying when the Advanced Copy function is being used, Advanced Copy processing stops and software-copy processing starts.
You can specify the option when the function in linkage with GDS Snapshot is being used.
Specifies that GDS select the copy processing method of an SDX object.
You can specify the option when the function in linkage with GDS Snapshot is being used.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
To start the backup synchronous processing for a transaction volume:
# /opt/FJSVswsts/bin/swststartsync /dev/sdb6 /dev/sdb6 swststartsync completed. #
To start backup synchronous processing for log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swststartsync -n LOG01/RDB1 LOG01/RDB1 swststartsync completed. #
Backup synchronous processing of a logical volume (/dev/sfdsk/CLS01/dsk/VOL01) of an SDX object is started. The copy processing method is software-copy:
# /opt/FJSVswsts/bin/swststartsync -Xgds-softcopy /dev/sfdsk/CLS01/dsk/VOL01 /dev/sfdsk/CLS01/dsk/VOL01 swststartsync completed. #
NOTES
When you execute the backup synchronous processing start command for a transaction volume or log group to which the backup synchronous processing is already being executed, the message "swst0301 Backup synchronous processing is already in progress." is output. (When you specify a log group, the message id is "swst0302".)
And then the command is terminated normally.
You cannot start backup synchronous processing in the following cases. In any of the cases below, perform the action according to the [System administrator response] message.
When specifying a device that does not support the EC function.
When the backup volumes required for starting the backup synchronous processing cannot be obtained.
When specifying a device that is being restored by OPC.
When mounting the backup volume to which data is copied.
The -Xgds-softcopy option is specified for a device that is not a GDS logical volume. Alternatively, the -Xgds-selectcopy option is specified for a device that is not a GDS logical volume.
The -n option was specified when GDS volumes and non-GDS volumes are mixed in a log group.
The replication management function is executing a process for the target transaction volume.
If a suspended backup volume is the transaction volume at the start of the synchronous processing, then the suspended backup volume is selected as the backup destination with the highest priority, and the synchronous processing restarts (ie, differential copy) starts. Otherwise, the synchronous processing (ie, full copy) starts.
Backup synchronous processing with the output destination backup volume specified cannot be started in the following circumstances:
The backup volume specified in the device map file cannot be used as the backup volume to be paired with the transaction volume. This means that either of the following conditions is not satisfied:
The specified backup volume is in the unused state.
The transaction volume and backup volume have the same partition size.
The target transaction volume is incorrectly described in the device map file (Refer to "3.4.9.1 Describing a device map file").
Any special or foreign characters, operators or reserved words are used in the in the device map file names.
An ordinary volume is specified as the transaction volume and a GDS logical volume as the backup volume.
A GDS logical volume is specified as the transaction volume and an ordinary volume as the backup volume.
For details on how to use SDX objects of GDS, refer to "Configuration and conditions of unsupported SDX objects" and "10.1.5.1 Notes on SDX object operations (backup management)".
This command cannot be executed when any of the following commands are running:
NAME
swstcancelsync - cancels the backup synchronous processing
SYNOPSIS
/opt/FJSVswsts/bin/swstcancelsync [-emergency] [-bd Backup-Device-Name | -all] Device-Name
/opt/FJSVswsts/bin/swstcancelsync [-h Server-Name] [-emergency] [-bd Backup-Device-Name | -all] Device-Name
/opt/FJSVswsts/bin/swstcancelsync [-emergency] -n Log-Group-Name[/RDB-NAME] [-all]
/opt/FJSVswsts/bin/swstcancelsync [-h Server-Name] [-emergency] -n Log-Group-Name[/RDB-NAME] [-all]
DESCRIPTION
The backup synchronous processing can be cancelled during copying by EC or under the equivalency maintained status.
The synchronous processing can be cancelled with the backup volume during copying by EC, under the equivalency maintained status, or while the Suspend state is set. Specifying cancellation of all of the synchronous processing cancels all of the backup synchronous processing including those in the Suspended state.
If the system detects an error while backup synchronous processing is being executed, copying in progress at that time terminates abnormally. In this case, use this command to cancel the backup synchronous processing. Use swstsyncstat (Backup synchronous processing progress display command) to check for the error.
You can execute this command specifying individual transaction volumes that are included in a log group for which to cancel backup synchronous processing.
OPTIONS
Specify the name of a Managed Server.
This option can be specified only with a Management Server.
Emergency operation mode is available for operations.
In such cases, EC sessions are neither confirmed nor cancelled.
The synchronous processing on a specific backup volume can be cancelled.
Specify the copy destination backup volume name. In the operand, specify the AdvancedCopy Manager device name for the specified device.
Note that the backup volume name and the -all option cannot be specified together.
All of the synchronous processing of the transaction volume can be specified to be cancelled. Note that this specification and the -bd option cannot be used together.
Specifies that backup synchronous processing is being cancelled for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Cancelling backup synchronous processing to a transaction volume:
# /opt/FJSVswsts/bin/swstcancelsync /dev/sdb6 /dev/sdb6 swstcancelsync completed. #
Cancelling backup synchronous processing of transaction volume in the emergency operation mode:
# /opt/FJSVswsts/bin/swstcancelsync -emergency /dev/sdb6 /dev/sdb6 swstcancelsync completed. #
To cancel backup synchronous processing for log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swstcancelsync -n LOG01/RDB1 LOG01/RDB1 swstcancelsync completed. #
Cancelling backup synchronous processing of the backup volume from the transaction volume:
# /opt/FJSVswsts/bin/swstsyncstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Work2 /dev/sdb6 /dev/sdc6 suspend ---- Work2 /dev/sdb6 /dev/sdd6 executing 75% # /opt/FJSVswsts/bin/swstcancelsync /dev/sdb6 -bd /dev/sdd6 /dev/sdb6 swstcancelsync completed. # /opt/FJSVswsts/bin/swstsyncstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Work2 /dev/sdb6 /dev/sdc6 suspend ---- #
Cancelling all of the backup synchronous processing of the transaction volume:
# /opt/FJSVswsts/bin/swstsyncstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Work2 /dev/sdb6 /dev/sdc6 suspend ---- Work2 /dev/sdb6 /dev/sdd6 executing 75% # /opt/FJSVswsts/bin/swstcancelsync /dev/sdb6 -all /dev/sdb6 swstcancelsync completed. # /opt/FJSVswsts/bin/swstsyncstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Work2 /dev/sdb6 ---- ---- ---- #
NOTES
However, EC sessions are neither confirmed nor cancelled by execution in the emergency operation mode. If an EC session is in the error suspended state or the halt state, then unmanaged sessions remain. In this event, ETERNUS Web GUI must be used to cancel these sessions.
You cannot cancel synchronous backup processing in the following case:
The -n option was specified when GDS volumes and non-GDS volumes are mixed in a log group.
The replication management function is executing a process for the target transaction volume.
For details on how to use SDX objects of GDS, refer to "Configuration and conditions of unsupported SDX objects" and "10.1.5.1 Notes on SDX object operations (backup management)".
This command cannot be executed when any of the following commands are running:
NAME
swstsyncstat - displays the execution status of the backup synchronous processing
SYNOPSIS
/opt/FJSVswsts/bin/swstsyncstat [Device-Name]/opt/FJSVswsts/bin/swstsyncstat [-h Server-Name] [Device-Name]
/opt/FJSVswsts/bin/swstsyncstat -n Log-Group-Name[/RDB-Name]
/opt/FJSVswsts/bin/swstsyncstat -n [-h Server-Name] Log-Group-Name[/RDB-Name]
DESCRIPTION
The execution status of the backup synchronous processing is displayed (during copying, under the equivalency maintained status, or in the suspended status).
If one transaction volume has multiple EC sessions, then the statuses of all of these EC sessions are displayed.
The table below lists the meaning of each title.
Title | Description |
|---|---|
Server | Displays the name of the Managed Server. |
Transaction-Disk | Displays the AdvancedCopy Manager device name of a transaction volume. |
Backup-Disk | Displays the name of the backup volume. |
Status | Displays the status of backup synchronous processing: "----" : Backup synchronous processing is not being executed. |
Execute | Displays the progress of the backup synchronous processing as a percentage (0 to 100%). |
OPTIONS
Specify the name of a Managed Server.
This option can be specified only with the Management Server.
Specifies that the execution status of backup synchronous processing being displayed is for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
When you omit the device name, the system displays the status of backup synchronous processing for all of the transaction volumes.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
To display the status of backup synchronous processing to a transaction volume:
# /opt/FJSVswsts/bin/swstsyncstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Work1 /dev/sdb6 /dev/sdd5 suspend ---- Work1 /dev/sdb6 /dev/sdd6 executing 75% #
To display the status of backup synchronous processing for all of the transaction volumes:
# /opt/FJSVswsts/bin/swstsyncstat Server Transaction-Disk Backup-Disk Status Execute Work1 /dev/sdb3 /dev/sdd1 suspend ---- Work1 /dev/sdb3 /dev/sdd3 executing 75% Work1 /dev/sdb3 /dev/sdd4 suspend ---- Work1 /dev/sdb5 /dev/sdd5 equivalent 100% Work1 /dev/sdb6 /dev/sdd6 failed ---- Work1 /dev/sdb4 ---- ---- ---- #
To display information on the execution status of backup synchronous processing for log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swstsyncstat -n LOG01/RDB1 Server Transaction-Disk Backup-Disk Status Execute job2 /dev/sdd1 /dev/sdz1 executing 75% job2 /dev/sdd2 /dev/sdz2 executing 10% : #
NOTES
If "failed", "halt", or "?????" is indicated as the status of the backup synchronous processing (in the Status column), a hardware failure, etc. has possibly occurred. Refer to "8.3 Troubleshooting: Hardware error during backup" for more information about this.
If "nosession" is indicated as the status of the backup synchronous processing (in the Status column), resource information having inconsistency is a possible cause. Use swstsrsemtch (Resource match command) to remove the inconsistency from the resource information.
If "gds-error" is the status displayed in the Status column, a problem with GDS is assumed. Correct the cause of the GDS problem, and take action as follows:
If backup synchronous processing is in progress, execute swstcancelsync (Backup synchronous processing cancel command) to cancel the backup synchronous processing.
If snapshot backup is in progress, execute swsthistdel (History information deletion command).
If restoration is in progress, execute swstsrsemtch (Resource match command), and perform restoration again.
NAME
swstexecstat - displays the execution status of other commands executed
SYNOPSIS
/opt/FJSVswsts/bin/swstexecstat [-j] [Device-Name]/opt/FJSVswsts/bin/swstexecstat [-j] [-h Server-Name] [Device-Name]
/opt/FJSVswsts/bin/swstexecstat -n [-j] Log-Group-Name[/RDB-NAME]
/opt/FJSVswsts/bin/swstexecstat -n [-h Server-Name] [-j] Log-Group-Name[/RDB-NAME]
DESCRIPTION
This command displays the execution status of other commands executed on a transaction volume. The execution status of OPC/EC will be displayed if OPC/EC is being executed.
The following information will be displayed:
Title | Description |
|---|---|
Server | Displays a Managed Server name. |
Device | Displays the AdvancedCopy Manager device name. |
Last-Backup-Date | Displays the time when the last backup execution command was accepted. |
Interval | Displays how many days have passed after the specified number of interval days since the last backup date has been exceeded. This item will be displayed as "DELAY=number-of-days-passing". "OK" will be displayed if the number of interval days has not been exceeded. |
Status | Displays whether any of the following commands is being executed on a transaction volume. If so, "EXEC" will be displayed. Otherwise, "IDLE" will be displayed. |
Mount-Point (Method) | Displays the mount point of a device. The file system type of the mount point is displayed inside the parentheses. If the "Device" is a transaction volume used for Symfoware, the names of Symfoware database spaces and log groups as well as the RDB system names are displayed, followed by "SymfoWARE" in parentheses. |
Execute | Displays the name of the command being executed or the progress of copying. "----" : Neither a command nor OPC/EC is being executed. During synchronous high-speed backup with -suspend specified, no operation ("----") is indicated in the Execute column. |
If multiple processes are performed on transaction volumes (for example, when the backup synchronous processing start command is issued while a real copy of the snapshot backup is being handled), the display in the Execute column conforms to the following rules:
The display of a command name takes priority if both copying and command executions are in progress.
When a disk copy of the snapshot backup and a disk copy of the backup synchronous processing are being handled simultaneously, the progress of the disk copy of the backup synchronous processing is displayed. A disk copy for restoration is not performed during disk copy of the snapshot backup or backup synchronous processing due to a restriction of ETERNUS Disk storage system.
The following information will be displayed when -j option is specified:
Title | Description |
|---|---|
Server | Displays a Managed Server name. |
Device | Displays the AdvancedCopy Manager device name. |
Execute-Date | Displays the command execution date and time (TimeStamp). |
Status | Displays whether any of the following commands are being executed on a transaction volume. If so, "EXEC" will be displayed. Otherwise, "IDLE" will be displayed. |
Mount-Point (Method) | Displays the mount point of a device. The file system type of the mount point is displayed inside the parentheses. If the "Device" is a transaction volume used for Symfoware, the names of Symfoware database spaces and log groups as well as the RDB system names are displayed, followed by "SymfoWARE" in parentheses. |
Execute | Displays the name of the command being executed or the progress of copying. "----" : Neither a command nor OPC/EC is being executed. During synchronous high-speed backup with -suspend specified, no operation ("----") is indicated in the Execute column. |
OPTIONS
Specifies a Managed Server name.
This option can be specified only on a Management Server.
Specifies to display information in another format.
Specifies that the command execution status being displayed is for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
OPERANDS
Specifies the AdvancedCopy Manager device name corresponding to a transaction volume.
If this operand is omitted, the execution statuses of all the transaction volumes will be displayed.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Display the execution statuses of transaction volumes:
# /opt/FJSVswsts/bin/swstexecstat Server Device Last-Backup-Date Interval Status Mount-Point (Method) Execute Work1 /dev/sdb3 2000/12/11 12:20 OK IDLE /usr1 (ext2) ---- Work1 /dev/sdb4 2000/12/10 12:20 DELAY=1 IDLE /usr2 (ext2) sync(22%) Work1 /dev/sdb5 2000/12/09 12:20 DELAY=2 IDLE /usr3 (ext2) snapshot(45%) : #
An example of using the -j option is as follows:
# /opt/FJSVswsts/bin/swstexecstat -j Server Device Execute-Date Status Mount-Point (Method) Execute Work1 /dev/sdb3 2000/12/11 12:20 IDLE /usr1 (ext2) ---- Work1 /dev/sdb4 2000/12/10 12:20 IDLE /usr2 (ext2) sync(22%) Work1 /dev/sdb5 2000/12/09 12:20 IDLE /usr3 (ext2) snapshot(45%) : #
NOTES
If "sync (failed)", "snapshot(failed)", "restore(failed)", "restore(halt)", or "?????" is displayed in the Execute column, a hardware error may have occurred. Refer to "8.3 Troubleshooting: Hardware error during backup" for more information about this.
If "gds-error" is the status displayed in the Status column, a problem with GDS is assumed. Correct the cause of the GDS problem, and take action as follows:
If backup synchronous processing is in progress, execute swstcancelsync (Backup synchronous processing cancel command) to cancel the backup synchronous processing.
If snapshot backup is in progress, execute swsthistdel (History information deletion command).
If restoration is in progress, execute swstsrsemtch (Resource match command), and perform restoration again.
NAME
swstcanceltrk - stops tracking processing
SYNOPSIS
/opt/FJSVswsts/bin/swstcanceltrk [-copy | -emergency] Device-Name (-bd Backup-Device-Name | -all)
/opt/FJSVswsts/bin/swstcanceltrk -h Server-Name [-copy | -emergency] Device-Name (-bd Backup-Device-Name | -all)
DESCRIPTION
This command stops tracking processing.
OPTIONS
Specifies a Managed Server name.
This option can be specified only on the Management Server.
Specifies that physical copying, if active, should also be stopped (the OPC session should be cancelled).
This option cannot be specified for a backup volume that has already contained a backup history. For a volume whose copy destination volume has contained a backup history, delete the history information in advance using swsthistdel (History information deletion command).
Specifies that the command should operate in the emergency operation mode.
The command does not check tracking processing and does not stop tracking processing or the OPC session.
Stops tracking processing for the specified backup volume. Specify the target backup volume name as an operand. This option cannot be specified at the same time as the -all option.
Stops the entire tracking processing specified for the transaction volumes. This option cannot be specified at the same time as the -bd option.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
The following example stops the tracking processing that was specified for the backup volume from the transaction volume:
# /opt/FJSVswsts/bin/swstcanceltrk /dev/sdb6 -bd /dev/sdd6 /dev/sdb6 swstcanceltrk completed. #
The following example stops tracking processing and physical copying that were specified for the transaction volume:
# /opt/FJSVswsts/bin/swsttrkstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Update job2 /dev/sdb6 /dev/sdd6 executing 33% ----- # /opt/FJSVswsts/bin/swstcanceltrk -copy /dev/sdb6 -bd /dev/sdd6 /dev/sdb6 swstcanceltrk completed. #
NOTES
If the command is executed in emergency operation mode, no OPC session is cancelled. A session that is not managed remains in operation if the command is entered during tracking. The session must be cancelled using ETERNUS Web GUI or GDS.
Tracking processing cannot be stopped under the following condition. In this case, take action according to "System administrator response" provided for the message output.
When tracking processing is not performed for the specified copy source and destination volumes.
This command cannot be executed while one of the following commands is being executed:
NAME
swsttrkstat - displays the status of tracking processing
SYNOPSIS
/opt/FJSVswsts/bin/swsttrkstat [Device-Name]/opt/FJSVswsts/bin/swsttrkstat [-h Server-Name] [Device-Name]
/opt/FJSVswsts/bin/swsttrkstat -n Log-Group-Name[/RDB-Name]
/opt/FJSVswsts/bin/swsttrkstat -n [-h Server-Name] Log-Group-Name[/RDB-Name]
DESCRIPTION
This command displays the status of tracking processing.
When multiple types of synchronous processing are running on one transaction volume, the command displays the statuses of all types of tracking processing.
The displayed data is explained below.
Title | Description |
|---|---|
Server | Displays a Managed Server name. |
Transaction-Disk | Displays the AdvancedCopy Manager device name of a transaction volume. |
Backup-Disk | Displays a backup volume name. Displays "----" when the volume is not in the tracking status. |
Status | Displays the execution status. "----" : Not in the process of tracking |
Execute | Displays the progress of copying as a percentage when "executing" is displayed in the Status column. "----" is displayed when "tracking" is displayed in the Status column. |
Update | Displays the amount of updated data after logical copying as a percentage when "tracking" is displayed in the Status column. "----" is displayed when "executing" is displayed in the Status column. |
OPTIONS
Specifies a Managed Server name.
This option can be specified only on the Management Server.
Specifies that the execution status of tracking being displayed is for a log group.
In the operand, specify the log group name and the RDB system name. If there is no RDB system name, you can omit it.
OPERANDS
Specify an AdvancedCopy Manager device name.
Refer to "1.5 Managing a Device on AdvancedCopy Manager" for the devices to be specified.
If this operand is omitted, the command displays the statuses of tracking processing for all transaction volumes.
Specify the name of the log group.
Specify the RDB system name after the log group name, delimited by a slash ("/").
If there is no RDB system name, you can omit it.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
The following example displays the status of tracking processing of a transaction volume:
# /opt/FJSVswsts/bin/swsttrkstat /dev/sdb6 Server Transaction-Disk Backup-Disk Status Execute Update job1 /dev/sdb6 /dev/sdd6 tracking ---- 12% #
The following example displays the status of tracking processing of all transaction volumes:
# /opt/FJSVswsts/bin/swsttrkstat Server Transaction-Disk Backup-Disk Status Execute Update job1 /dev/sdb3 /dev/sdd3 nosession ---- ---- job1 /dev/sdb4 /dev/sdd4 executing 75% ---- job1 /dev/sdb5 /dev/sdd5 failed ---- ---- job1 /dev/sdb6 /dev/sdd6 ????? ---- ---- job1 /dev/sdb7 /dev/sdd7 tracking ---- 12% job1 /dev/sdc1 ---- ---- ---- ---- : #
To display the execution status of tracking for log group (LOG01/RDB1):
# /opt/FJSVswsts/bin/swsttrkstat -n LOG01/RDB1 Server Transaction-Disk Backup-Disk Status Execute Update job2 /dev/sdc4 /dev/sde4 tracking ---- 12% job2 /dev/sdc5 /dev/sde5 tracking ---- 15% : #
NOTES
When the execution status (ie, the value displayed in the "Status" column) is "failed" or "?????", a hardware problem, etc. has occurred. Refer to "8.3 Troubleshooting: Hardware error during backup" for more information about this.
When the execution status (ie, the value displayed in the "Status" column) is "nosession," the resource information is probably inconsistent. Use swstsrsemtch (Resource match command) to remove any inconsistencies from the resource information.