| ETERNUS SF AdvancedCopy Manager Operator's Guide 13.0 -AIX- |
|
Contents
Index
|
This chapter describes using commands.
This chapter describes operations using backup management commands. It is necessary to execute the command of backup management by the root user.
Only a root user can execute all the commands of backup management. When command execution is carried out by other users, a message "swst0601 This Command cannot be run. This is because the user is not a root user." is outputted and then, an error end.
Operating environment for command execution
The table below lists the requirements for the operating environment in which to execute the respective commands.
Command
Operating environment of AdvancedCopy Manager
swstbackstat
To execute this command on a storage management server with either of the following parameter designations, the daemons and services of the storage management server and target storage server must be operating:
-h option specified, or
No device name specified
swstbackup
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows and is in EC operation, the daemons and services of the storage server must be operating.swstbkpoldel
To execute this command on a storage server, the daemons and services of the storage management server must be operating.
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.swstbkpoldisp
To execute this command on a storage management server with either of the following parameter designations, the daemons and services of the storage management server and target storage server must be operating:
-h option specified, or
No device name specified
swstbkpolset
To execute this command on a storage server, the daemons and services of the storage management server must be operating.
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.swstcancelrest
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swstcancelsync
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows and is in EC operation, the daemons and services of the storage server must be operating.swstcanceltrk
When this command is executed with the -h option specified on the storage management server, the daemons/services of the storage management server and target storage server must be active.
swstdevdisp
To execute this command on a storage management server with either of the following parameter designations, the daemons and services of the storage management server and target storage server must be operating:
-h option specified, or
No device name specified
swstdevinfoset
To execute this command on a storage server, the daemons and services of the storage management server must be operating.
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.swstexecstat
To execute this command on a storage management server with either of the following parameter designations, the daemons and services of the storage management server and target storage server must be operating:
-h option specified, or
No device name specified
swsthistdel
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swsthistdisp
To execute this command on a storage management server with either of the following parameter designations, the daemons and services of the storage management server and target storage server must be operating:
-h option specified, or
No device name specified
swstresback
-
swstresrst
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows, the daemons and services of the storage server must be operating.
To execute this command with the -x option specified, the daemons and services of the storage management server must be operating.swstrestore
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swstreststat
To execute this command on a storage management server with either of the following parameter designations, the daemons and services of the storage management server and target storage server must be operating:
-h option specified, or
No device name specified
swstsrsemtch
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows, the daemons and services of the storage server must be operating.
To execute this command with the -x option specified, the daemons and services of the storage management server must be operating.swststartsync
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows, the daemons and services of the storage server must be operating.swstsvrdisp
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swstsvrset
To execute this command on a storage server, the daemons and services of the storage management server must be operating.
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.swstsyncstat
To execute this command on a storage management server with either of the following parameter designations, the daemons and services of the storage management server and target storage server must be operating:
-h option specified, or
No device name specified
swsttrkstat
When this command is executed in the following format on the storage management server, the daemons/services of the storage management server and target storage server must be active:
-h option is specified, or
No device name is specified.
In cluster operation
In cluster operation, execute a command by taking the following steps:
If necessary, specify the logical node name to the transaction in environment variable SWSTGNODE. For bsh, specify the environment variable as follows:
Execute the command.
The table below lists the commands available in cluster operation, whether environment variables must be configured, and the nodes on which commands are executable. For notes and cautions on command execution, see the Remarks column.
Command
Environment variable
Command execution node
Remarks
swstsvrset
Required
Transaction operation node
swstsvrdisp
Required
Transaction operation node
swstdevinfoset
Required
Transaction operation node
swstdevdisp
Required
Transaction operation node
swstbkpolset
Required
Transaction operation node
swstbkpoldisp
Required
Transaction operation node
swstbkpoldel
Required
Transaction operation node
swstbackup
Required
Transaction operation node
swstbackstat
Required
Transaction operation node
swstrestore
Required
Transaction operation node
swstcancelrest
Required
Transaction operation node
swstreststat
Required
Transaction operation node
swsthistdisp
Required
Transaction operation node
swsthistdel
Required
Transaction operation node
swststartsync
Required
Transaction operation node
swstcancelsync
Required
Transaction operation node
swstsyncstat
Required
Transaction operation node
swstexecstat
Required
Transaction operation node
swstcanceltrk
Required
Transaction operation node
swsttrkstat
Required
Transaction operation node
swstsrsemtch
Required
Transaction operation node
swstresback
Required
Transaction operation node
swstresrst
Required
Transaction operation node
This chapter describes environment definition commands for backup management.
To define a backup management environment, use the following commands:
|
Function |
Command name |
Description |
|---|---|---|
|
swstsvrset |
Sets the configuration information of a storage server. |
|
|
swstsvrdisp |
Displays the configuration information of a storage server. |
|
|
swstdevinfoset |
Sets the use of a device. |
|
|
swstdevdisp |
Displays the information of a device. |
|
|
swstbkpolset |
Sets a backup policy. |
|
|
swstbkpoldisp |
Displays a backup policy that has been set. |
|
|
swstbkpoldel |
Deletes a backup policy that has been set |
This command sets configuration information of a storage server. Execute this command to declare that this storage server is subject to the backup operation.
Specification
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstsvrset [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstsvrset [-h Server] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies the name of a storage server to be subject to the backup operation. This option is valid only on a storage management server. If this option is omitted, the storage server on which the command is entered will be subject to the processing. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Set configuration information of a storage server.
# /opt/FJSVswsts/bin/swstsvrset swstsvrset completed # |
Set configuration information of a storage server (job1) from a storage management server.
# /opt/FJSVswsts/bin/swstsvrset -h job1 swstsvrset completed # |
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command(swstsvrset)
Backup policy setting command (swstbkpolset)
Backup policy deletion command (swstbkpoldel)
Backup execution command (swstbackup)
Restore execution command (swstrestore)
Restore cancellation command (swstcancelrest)
Backup synchronous processing start command (swststartsync)
Backup synchronous processing cancel command (swstcancelsync)
Device information setting command (swstdevinfoset)
History information deletion command (swsthistdel)
Tracking cancel command (swstcanceltrk)
Resource backup command (swstresback)
Resource restore command (swstresrst)
Resource match command (swstsrsemtch)
This command displays configuration information of a storage server, which has been set using the storage server configuration information setting command.
Specification
[To be executed on a storage server] # /opt/FJSVswsts/bin/swstsvrdisp [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstsvrdisp [-h Server] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option is valid only on a storage management server. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Display configuration information of a storage server (job1).
| # /opt/FJSVswsts/bin/swstsvrdisp Storage-Server = job1 # |
The following information will be displayed.
|
Title |
Description |
|---|---|
|
Storage-Server |
Displays a storage server name. |
Set a volume that has been allocated to the disk array unit ETERNUS storage system, as a transaction or backup volume.
A transaction volume refers to a volume that stores work data to be backed up.
A backup volume refers to a volume used to store a backup of this transaction data.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstdevinfoset -t | -b | -o Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstdevinfoset [-h Server] -t | -b | -o Device-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option is valid only on a storage management server. |
|
-t |
Register the specified device as a transaction volume. Cannot be specified at the same time as the -b and -o options. |
|
-b |
Register the specified device as a backup volume. Cannot be specified at the same time as the -t and -o options. |
|
-o |
Deregister the specified device if it has been registered as a work or backup volume. Cannot be specified at the same time as the -t and -b options. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specify a device name. Specify the name of a block device. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Register a device (/dev/vg01) as a transaction volume.
# /opt/FJSVswsts/bin/swstdevinfoset -t /dev/vg01 swstdevinfoset completed # |
Register a device (/dev/vg02) as a backup volume.
# /opt/FJSVswsts/bin/swstdevinfoset -b /dev/vg02 swstdevinfoset completed # |
Deregister a device (/dev/vg04) that has been registered as a transaction volume.
# /opt/FJSVswsts/bin/swstdevinfoset -o /dev/vg04 swstdevinfoset completed # |
No device can be registered as a transaction volume if:
Another device with the same logical volume information has already been registered as a transaction volume.
The space of the device to be registered overlaps the space of an already registered work or backup volume.
No device can be registered as a backup volume if:
Another device with the same logical volume information has already been registered as a backup volume.
The space of the device to be registered overlaps the space of an already registered transaction or backup volume.
The device to be set up is already mounted. However, when setting a volume group as backup volume, the check of whether the logical volume in a volume group is mounted is not carried out. In case you set a volume group as backup volume, make logical volume unmount beforehand.
When the device which it is going to set up is registered as a replication destination volume of replication management.
When the device which it is going to set up is registered as replication source volume of the duplicate volume information in which the bidirectional copy of replication management is possible.
The following is note for using a volume group as transaction volume:
Do not register two or more physical disks into one volume group.
Create a logical disk so that it does not consist of two or more physical disks.
The following is note for using a volume group as backup volume:
Do not register two or more physical disks into one volume group.
Create a logical disk so that it does not consist of two or more physical disks.
It is necessary to be the same physical size as transaction volume. In addition, if in the case of a volume group, it is necessary to also make it into the logical disk whose volume group is different from the transaction volume and is of the same composition as the transaction volume.
You must delete related backup history information before:
Changing a backup volume to a transaction volume
Canceling the setting of a backup volume
You must delete a backup policy specified on a transaction volume before:
Changing a transaction volume to a backup volume
Canceling the setting of a transaction volume
In order to make a configuration change of transaction volume or backup volume, delete a setting of transaction volume or backup volume, and re-register.
The following changes are not possible unless the related synchronous processing (EC session) is cancelled:
Changing a setting of a suspended transaction volume
Changing a setting of a suspended backup volume
To perform the following changes, the related tracking processing (OPC session) must be canceled in advance.
Changing the settings of a transaction volume in tracking processing
Changing the settings of a backup volume in tracking processing
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command(swstdevinfoset)
Backup policy setting command (swstbkpolset)
Backup policy deletion command (swstbkpoldel)
Backup execution command (swstbackup)
Restore execution command (swstrestore)
Restore cancellation command (swstcancelrest)
Backup synchronous processing start command (swststartsync)
Backup synchronous processing cancel command (swstcancelsync)
History information deletion command (swsthistdel)
Tracking cancel command (swstcanceltrk)
Resource match command (swstsrsemtch)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This command displays information of a transaction or backup volume or any other definable device, which has been set using the device information setting command (swstdevinfoset).
Specification method
[To be executed on a storage server] # /opt/FJSVswsts/bin/swstdevdisp [-t] [-b [-u]] [-o] [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstdevdisp [-h Server] [-t] [-b [-u]] [-o] [Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-t |
Displays information on a device that has been set as a transaction volume. Displays device information on all the transaction volumes if the device name in an operand is omitted. |
|
-b |
Displays a device that has been set as a backup volume. Displays device information on all the backup volumes if the device name in an operand is omitted. |
|
-u |
Changes the display format of the Device-Mode field. |
|
-o |
Displays all the devices other than those set as a work or backup volume. Displays all the devices other than those set as a transaction or backup volume if the device name in an operand is omitted. |
Information on a device that has been set as a transaction volume will be displayed if all of the t, b, and o options are omitted.
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specify a device name. Specify the name of a block device. Displays device information on all the transaction volumes if this operand as well as the options are omitted. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Display the usage statuses of the registered devices.
# /opt/FJSVswsts/bin/swstdevdisp -t -b Server Device Size Device-Mode Mount-Point (Method) Backup-Engine job2 /dev/vg00 1.0 Gbyte Transaction ---- (----) AdvancedCopy job2 /dev/vg01 2.0 Gbyte Transaction ---- (----) AdvancedCopy job2 /dev/vg02 1.0 Gbyte Backup (used) ---- (----) AdvancedCopy job2 /dev/vg03 1.0 Gbyte Backup (free) ---- (----) AdvancedCopy job2 /dev/vg04 2.0 Gbyte Backup (free) ---- (----) AdvancedCopy job2 /dev/vg05 1.0 Gbyte Backup (free) ---- (----) AdvancedCopy : # |
The following information will be displayed.
|
Title |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Device |
Displays a AdvancedCopy Manager device name. |
|
Size |
Displays the size of a partition allocated to a device. Also in case a volume group, displays the physical disk size from which a logic disk is constituted. |
|
Device-Mode |
Displays a character string by which a device can be identified.
A backup volume is indicated as "Backup (used)" if it is being used or "Backup (free)" if it is not used. During the backup process with -suspend or -T specified, the backup volume remains in use after history information is deleted. When the -u option is specified, "Backup (used-S)" is displayed for a backup volume in the suspend status for which history information was deleted, or "Backup (used-T)" is displayed for a backup volume in the tracking status for which history information was deleted. |
|
Mount-Point (Method) |
Displays the mount point of a device. The file system type of the mount point is displayed inside the parentheses. However, AIX does not display mount points. Therefore, "---- (----)" is always displayed. |
|
Backup-Engine |
Displays the operation type.
|
This command sets a backup policy (numbers of preservation generations and interval days).
The number of preservation generations means how many generations of backup data should be kept.
The number of interval days means the number of days after execution of backup in which the next backup should be performed.
Even if the number of interval days is specified, AdvancedCopy Manager does not automatically collect backup.
When you specify a backup policy, there must be as many backup volumes required operating according to the specified backup policy. To view information on the number of backup volumes required to perform the backup operation, see "Preparing a backup volume".
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstbkpolset [-i Interval-Days] [-s Save-Number][Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbkpolset [-h Server][-i Interval-Days] [-s Save-Number][Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-i |
Specifies the number of interval days. You can specify a value between 1 and 366. If this option is omitted during initial registration, 30 will be set. If this option is omitted during update, the existing value will be inherited. |
|
-s |
Specifies the number of preservation generations. You can specify a value between 1 and 31. If this option is omitted during initial registration, 2 will be set. If this option is omitted during update, the existing value will be inherited. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specify a AdvancedCopy Manager device name. If the device name is omitted, the backup policy will be set for all the transaction volumes. When a device name is omitted, a backup policy is set up to all operating volumes. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
To set 3 as the save number of a transaction volume (/dev/vg01) as a backup policy:
| # /opt/FJSVswsts/bin/swstbkpolset -s 3 /dev/vg01 /dev/vg01 swstbkpolset completed # |
Change of the number of preservation generations can be performed if there "there is little history information in the time" than "the number of preservation generations to set up."
No backup policy can be set if:
There are not as many backup volumes as the specified number of preservation generations.
An option for more number of preservation generations than can be specified is specified.
An option for more interval days than can be specified is specified.
When the replication control function or tape backup function uses the target transaction volume
This command can be executed only while none of the following commands is executed.
Resource match command (swstsrsemtch)
Device information setting command (swstdevinfoset)
Storage server configuration information setting command (swstsvrset)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This command displays a backup policy that has been set for a transaction volume.
Specification method
[To be executed on a storage server] # /opt/FJSVswsts/bin/swstbkpoldisp [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbkpoldisp [-h Server] [Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specify a AdvancedCopy Manager device name. Specify the name of a block device. If the device name is omitted, a backup policy for a transaction volume with a registered backup policy will be displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
To display the backup policies of a transaction volume (/dev/vg01):
# /opt/FJSVswsts/bin/swstbkpoldisp /dev/vg01 Server Device Interval-Days Save-Number Mount-Point (Method) job2 /dev/vg01 30 3 ---- (----) # |
The following information will be displayed.
|
Title |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Device |
Displays a device name. |
|
Interval-Days |
Displays a number of interval days. |
|
Save-Number |
Displays a number of preservation generations. |
|
Mount-Point (Method) |
Displays the mount point of a device. The file system type of the mount point will be displayed inside the parentheses. However, AIX does not display mount points. Therefore, "---- (----)" is always displayed. |
This command deletes a backup policy that has been set.
If the transaction volume to be deleted has backup history information, delete the backup history information and then execute this command.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstbkpoldel Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbkpoldel [-h Server] Device-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specify a AdvancedCopy Manager device name. Specify the name of a block device. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
To delete the backup policies of a transaction volume (/dev/vg01):
| # /opt/FJSVswsts/bin/swstbkpoldel /dev/vg01 /dev/vg01 swstbkpoldel completed # |
No backup policy can be deleted if:
The transaction volume to be deleted has backup history information.
A transaction volume whose backup policies are to be deleted has already started backup synchronous processing.
When the replication control function or tape backup function uses the target transaction volume
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Resource match command (swstsrsemtch)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This chapter describes operation commands for backup management.
To operate backup management, use the following commands:
|
Function |
Command name |
Description |
|---|---|---|
|
swstbackup |
Performs the synchronous high-speed backup or snapshot-type high-speed backup operation. |
|
|
swstbackstat |
Displays the backup progress status. |
|
|
swstrestore |
Performs restoration. |
|
|
swstcancelrest |
Cancels the execution of restoration. |
|
|
swstreststat |
Displays the execution status of restoration. |
|
|
swsthistdisp |
Displays the history information that has been backed up. |
|
|
swsthistdel |
Deletes the history information that has been backed up. |
|
|
swststartsync |
Starts backup synchronous processing. |
|
|
swstcancelsync |
Aborts backup synchronous processing. |
|
|
swstsyncstat |
Displays the progress of the backup synchronous processing. |
|
|
swstexecstat |
Displays the execution status of a command executed on a transaction volume. |
|
|
swstcanceltrk |
Stops tracking processing. |
|
|
swsttrkstat |
Displays the status of tracking processing. |
As for this command, operation changes with states of the advanced copy under execution.
When synchronous processing (EC) is not performed
Snapshot processing (OPC) is performed and performed information, such as the date and backup volume of a copy place, is registered into backup history information. Backup of such a form is called snapshot type high-speed backup.
When synchronous processing (EC) is performed
The state of synchronous processing is checked and, in the case of an equivalent nature maintenance state, backup synchronous processing is suspended. Information, such as time and backup volume of a copy place, is simultaneously registered into backup history information. Backup of such a form is called synchronous high-speed backup. (It becomes an error end when an equivalent nature maintenance state is not reached)
To use the Suspend/Resume function for synchronous high-speed backup, execute the backup command with -suspend specified, and suspend backup synchronous processing.
In either case, the backup volume is set for the backup operation immediately after execution of this command.
AdvancedCopy Manager executes a backup preprocessing Shell script (OpcBackup.pre) before executing backup and then a backup post processing Shell script (OpcBackup.post) after executing backup. You can customize these Shell script. For more information, see "Preprocessing and Postprocessing of Backup and Restoration".
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstbackup [-suspend|-T] Device-Name [-Xdevmap Device-Map-File] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbackup [-h Server] [-suspend|-T] Device-Name [-Xdevmap Device-Map-File] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-Xdevmap |
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 is described. If this option is not specified, the 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 storage server) using an absolute pathname. A file name specified in Device-Map-File must not include any national character. |
|
-suspend |
This results in synchronous high-speed backup using the Suspend/Resume function. |
|
-T |
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 cabinet when the disk array supports the QuickOPC function. For the snapshot high-speed backup without specifying this option, ordinary snapshot processing (OPC without using the QuickOPC function) is started. This option must be always specified to perform a backup operation using differential snapshots. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify the name of a block device. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Back up a business volume (/dev/vg01)
# /opt/FJSVswsts/bin/swstbackup /dev/vg01 /dev/vg01 swstbackup completed # |
To guarantee data, this command performs backup after inhibiting access to transaction and backup volumes from other processes. Thus, the drive letters of devices are not assigned. This command terminates with an error if a drive letter of a transaction volume is assigned or if:
The mount point has directories to which other volumes are to be mounted.
The volume has a file in use.
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.
When setting the volume group as a transaction volume, and backing up or restoring it, modify the preprocessing and postprocessing script for backup on administrator responsibility such that unmount/mount of all logical devices is carried out.
You cannot perform backup in the following cases. In these cases, do as described in [System Administrator's Response] in a message that will be output.
No backup policy has been specified for the specified transaction volume.
Backup executed one generation earlier was unsuccessful.
A transaction volume on which OPC is in progress has been specified.
Synchronous backup processing is performed in a transaction volume 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.
No unused backup volume to be used as the copying destination could be acquired.
Any of the cabinet information (box identifier, OLU number, EXTENT start position, and EXTENT size) of a transaction volume has been changed.
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
A volume group is in an un-active state in volume group specification.
When the replication control function or tape backup function uses the target transaction volume
When the replication control function or tape backup function uses the target backup volume
When the replication control function or tape backup function uses backup records exceeding the number of preservation generations
When as follows, output place backup volume cannot be specified and backup cannot be performed.
When the backup volume specified by the device map file (or operand of the to option) cannot use it as backup volume of the operating volume used as a pair. Namely, when either of the following conditions is not satisfied.
The specified backup volume is in an intact state.
The partition size of operating volume and backup volume is the same.
When an error is in the description about the object operating volume of a device map file (refer to "Preparing a device map file" of this manual).
When the word character of each country is contained in the device map file name.
At this time, if existing backup history information satisfies the condition of number of saved generations specified by the 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 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.
Please understand "General notes" in this manual as a noted point when you execute the backup.
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Resource match command (swstsrsemtch)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This command displays the completion status of backup that is being performed using the backup execution command.
Please do not use the OPC stop function of GRmgr/ETERNUSmgr while executing the snap shot type high speed backup. When the OPC stop function of GRmgr/ETERNUSmgr is used, it is displayed in this command regardless of the success or failure of an actual backup as succeeded.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstbackstat [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbackstat [-h Server] [Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name corresponding to a transaction volume. Specify the name of a block device. If this operand is omitted, the backup execution statuses of all the transaction volumes will be displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Display the actual copying execution status.
# /opt/FJSVswsts/bin/swstbackstat Server Transaction-Disk Backup-Disk Status Execute job1 /dev/vg00 /dev/vg02 succeeded ---- job1 /dev/vg01 ---- ---- ---- : # |
The following information will be displayed.
|
Keyword |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Transaction-Disk |
Displays the 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.
|
|
Execute |
Displays how much has been copied in percentage if "executing" is displayed in the Status field. Displays "----" unless "executing" is displayed. |
You cannot perform displaying the backup processing status in the following cases
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
If "failed" or "halt" is displayed in the "Status" field, a hardware error may have occurred. Refer to "Troubleshooting for a hardware error, etc. occurring during backup".
The data which exists in backup history information is restored by using OPC.
Restoration of each individual file cannot be performed because copying between devices will be performed.
When the restore execution command is executed, AdvancedCopy Manager performs the restore preprocessing Shell script (OpcRestore.pre) before copying data using OPC and then the restore postprocessing Shell script (OpcRestore.post) after copying data using OPC. You can customize these Shell script. For more information, see "Preprocessing and Postprocessing for Backup and Restoration".
You can restore data to any device other than a transaction volume. When you do so, the device must not be registered as a transaction volume and the device must have the same space size as the specified transaction volume. To restore data on a volume other than a transaction volume, a procedure different from the normal procedure must be followed. For the procedure, see "Notes on restoration."
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstrestore [-g Generation-No | -v Version-No] [-r Restore-Device-Name] Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstrestore [-h Server] [-g Generation-No | -v Version-No] [-r Restore-Device-Name] Device-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-g |
Specifies the relative generation number of data to be restored. Check the relative generation number using the history information display command (swsthistdisp). |
|
-v |
Specifies the absolute generation number of data to be restored. Check the absolute generation number using the history information display command (swsthistdisp). |
|
-r |
Specifies a restore destination device name to restore data to any other device than a transaction volume. |
Note: If neither the -g or -v option is specified, the latest information out of information under history management will be restored.
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name corresponding to a transaction volume. Specify the name of a block device. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Restore data with relative generation number 2 (For information on the relative generation number, see data displayed using the history information display command).
# /opt/FJSVswsts/bin/swstrestore -g 2 /dev/vg01 /dev/vg01 swstrestore completed # |
If the 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, see the data displayed by the backup synchronous processing execution status display command. Execute the backup synchronous processing cancel command to cancel the synchronous processing.
# /opt/FJSVswsts/bin/swstsyncstat /dev/vg01 Server Transaction-Disk Backup-Disk Status Execute job2 /dev/vg01 /dev/vg02 suspend ---- job2 /dev/vg01 /dev/vg03 executing 75% # /opt/FJSVswsts/bin/swstcancelsync -all /dev/vg01 /dev/vg01 swstcancelsync completed # /opt/FJSVswsts/bin/swstsyncstat /dev/vg01 Server Transaction-Disk Backup-Disk Status Execute job2 /dev/vg01 ---- ---- ---- # /opt/FJSVswsts/bin/swstrestore /dev/vg01 /dev/vg01 swstrestore completed # |
On a transaction volume on which a file system has been constructed physically, restore a specific file as follows:
Mount a backup volume. Check the backup volume by executing the Backup History List view/History information display command. For the procedure for mounting the backup volume, see "Notes on restoration."
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.
You cannot perform restoration in the following cases. In these cases, do as described in [System Administrator's Response] in a message that will be output.
Both a relative and absolute generation numbers have been specified.
A device registered as a transaction volume has been specified in a parameter in the -r option.
When a device registered as a backup volume has been specified in a parameter in 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. You are recommended not to specify a backup volume as a restore destination device.
You perform restoration immediately after performing backup (the actual copying using OPC is in progress). In this case, perform restoration 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 Points.
A transaction volume in the process of synchronous backup processing is specified.
Any of the cabinet information (box identifier, OLU number, EXTENT start position, and EXTENT size) of a transaction volume to be restored has been changed.
When changing a mount point specified at transaction volume registration
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
When the replication control function or tape backup function uses the target transaction volume
When the replication control function or tape backup function uses the device specified in the -r option
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 the synchronous processing (during copying by EC, under the equivalency maintain status, in the Suspend state).
If the following error occurs during restore processing, then execute the 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 running.
or
swst0634 OPC cannot be run. (SCSI command busy)
Please understand "General notes" in this manual as a noted point when you execute the backup.
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Resource match command (swstsrsemtch)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This command cancels OPC-based restoration. If you have executed the restore execution command and while data is copied using OPC, an abnormality due to a hardware error is detected. Then, remove the cause of the hardware error and perform restoration again using the restore execution command (swstrestore).
Check whether an abnormality has occurred using the restore execution status display command (swstreststat).
If you cancel OPC-based restoration using this command, the transaction volume will be in an incomplete status and can no longer be used because part of the data has already been copied. Perform restoration again using the restore execution command (swstrestore).
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstcancelrest [-g Generation-No | -v Version-No] [-r Restore-Device-Name] [-emergency] Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstcancelrest [-h Server] [-g Generation-No | -v Version-No] [-r Restore-Device-Name] [-emergency] Device-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-g |
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 the restore execution status display command (swstreststat). |
|
-v |
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 the restore execution status display command (swstreststat). |
|
-r |
Specifies the device name if data is restored to any other device than a transaction volume. Check the device name using the restore execution status display command (swstreststat). |
|
-emergency |
Emergency operation mode is available for operations. In such cases, OPC sessions are neither confirmed nor cancelled. |
Note: The restoration of the latest history information will be canceled if neither the -g or -v option is specified.
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify the name of a block device. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Cancel restore processing of a transaction volume (/dev/vg01).
# /opt/FJSVswsts/bin/swstcancelrest -g 1 /dev/vg01 /dev/vg01 swstcancelrest completed. # |
Restoration of the latest history information on the transaction volume (/dev/vg02) is cancelled in emergency operation mode.
# /opt/FJSVswsts/bin/swstcancelrest -emergency /dev/vg02 /dev/vg02 swstcancelrest completed. # |
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 is a normal end.)
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
When the replication control function or tape backup function uses 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 or halt state, then unmanaged sessions remain. In this event, GRmgr or ETERNUSmgr must be used to cancel these sessions.
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Resource match command (swstsrsemtch)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This command displays the execution status of restoration.
Do not use the OPC stop function of GRmgr/ETERNUSmgr while the snapshot fast backup is in progress. If you use the OPC stop function of GRmgr/ETERNUSmgr, this command displays "succeeded" whether or not the restoration has actually been successful.
Specification method
[To be executed on a storage server] # /opt/FJSVswsts/bin/swstreststat [-g Generation-No | -v Version-No] [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstreststat [-h Server ] [-g Generation-No | -v Version-No] [Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-g |
Specifies the relative generation number of data whose restore execution status should be displayed. |
|
-v |
Specifies the absolute generation number of data whose restore execution status should be displayed. |
Note: The restore execution statuses of all the history will be displayed if both the -g and -v options are omitted.
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify the name of a block device. If this operand is omitted, the restore execution statuses of all the transaction volumes will be displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Display the restore processing status of transaction volumes.
# /opt/FJSVswsts/bin/swstreststat Server Transaction-Disk Generation Version Backup-Disk Restore-Device Status Execute job2 /dev/vg01 1 10 /dev/vg10 /dev/vg20 executing 75% job2 /dev/vg02 ---- ---- ---- ---- ---- ---- job2 /dev/vg03 2 12 /dev/vg11 ---- succeeded ---- job2 /dev/vg04 3 13 /dev/vg12 /dev/vg21 executing 75% : # |
The following information will be displayed.
|
Title |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Transaction-Disk |
Displays the 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 history being restored 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 history being restored 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 restore target device name unless data is copied and restored to a transaction volume. "----" will be displayed if restoration is not in progress or data is restored to a transaction volume. |
|
Status |
Displays an execution status.
|
|
Execute |
Displays how much has been copied in percentage if "executing" is displayed in the Status field. Displays "----" unless "executing" is displayed. |
If "failed" is displayed in the "Status" field, a hardware error may have occurred. Refer to "Troubleshooting for a hardware error, etc. occurring during backup".
If no generation number has been specified in the -v or -g option, the restore execution statuses of all the history will be displayed. If, at this time, restoration is not in progress from any of the history, "----" will be displayed in all the information fields other than "Server" and "Transaction-Disk".
You cannot perform displaying the restore processing status in the following cases
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
This command displays history information that has been backed up.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swsthistdisp [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swsthistdisp [-h Server] [Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name corresponding to a transaction volume. Specify the name of a block device. If this operand is omitted, the backup history information of all the transaction volumes will be displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Display the backup history information of all the transaction volumes.
# /opt/FJSVswsts/bin/swsthistdisp Server=StrgSV01 Device=/dev/vg01 Mount-Point=---- (----) Generation Version Backup-Date Backup-Device Status Execute 1 10 2000/11/12 22:00 /dev/vg02 succeeded ---- 2 9 2000/11/11 22:00 /dev/vg03 succeeded ---- : # |
The following information will be displayed.
|
Keyword |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Device |
Displays a device name. |
|
Mount-Point |
Displays the mount point name of the device and the file system type in parentheses. However, AIX does not display mount points. Therefore, "---- (----)" is always displayed. |
|
Generation |
Displays a relative generation number. This item will not be displayed if no backup history information exists. |
|
Version |
Displays an absolute generation number. This item will not be displayed if no backup history information exists. |
|
Backup-Date |
Displays a date at which backup has been completed. This item will not be displayed if no backup history information exists. |
|
Backup-Device |
Displays the name of a backup volume to which data has been backed up. This item will not be displayed if no backup history information exists. |
|
Status |
Displays an actual copying execution status using one of the following character strings.
This item will not be displayed if no backup history information exists. |
|
Execute |
Displays how much has been copied in percentage if "executing" is displayed in the Status field. Displays "----" unless "executing" is displayed. This item will not be displayed if no backup history information exists. |
You cannot perform processing of displaying history information in the following cases
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
If "failed" or "halt" is displayed in the "Status" field, a hardware error may have occurred. Refer to "Troubleshooting for a hardware error, etc. occurring during backup".
This command deletes backup history information.
The backup volume of the deleted history is released and turns into empty backup volume.
If the history information display command displays "failed" in the "Status" field, a hardware error may have occurred. Refer to "Troubleshooting for a hardware error, etc. occurring during backup".
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swsthistdel -g Generation-No| -v Version-No | -z [-emergency] Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swsthistdel [-h Server] -g Generation-No| -v Version-No | -z [-emergency] Device-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-g |
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. Check the relative generation number using the history information display command (swsthistdisp). |
|
-v |
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. Check the absolute generation number using the history information display command (swsthistdisp). |
|
-z |
Specifies to delete all the backup history information. This option cannot be specified at the same time as the -g or -v. |
|
-emergency |
Emergency operation mode is available for operations. In such cases, OPC sessions are neither confirmed nor cancelled. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name corresponding to a transaction volume. Specify the name of a block device. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Delete the backup history of absolute generation number 10 in a transaction volume (/dev/vg01).
# /opt/FJSVswsts/bin/swsthistdel -v 10 /dev/vg01 /dev/vg01 swsthistdel completed # |
The history information of relative generation number 1 of the transaction volume (/dev/vg02) is deleted in emergency operation mode.
# /opt/FJSVswsts/bin/swsthistdel -g 1 -emergency /dev/vg02 /dev/vg02 swsthistdel completed # |
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 used in restoration.
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
When the replication control function or tape backup function uses the target transaction volume
When the replication control function or tape backup function uses 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 or halt state, then unmanaged sessions remain. In this event, GRmgr or ETERNUSmgr must be used to cancel these sessions.
Deleting the suspended history information does not cancel the synchronous processing (EC session).
Deleteing the tracking history information does not cancel the tracking processing (OPC session).
In synchronous high-speed backup with -suspend specified, the backup volume remains in use even after the history information is deleted.
In differential snapshot high-speed backup with -T specified, the backup volume remains in use even after the 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 (copy stopped halfway). The backup volume is put in the unused state upon deletion of the history information and becomes ready to use at the subsequent 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 to use at the subsequent backup of the relevant transaction volume.
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Resource match command (swstsrsemtch)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This command starts backup synchronous processing (starts disk-to-disk copy using EC).
Specification method
[To be executed on a storage server] # /opt/FJSVswsts/bin/swststartsync Device-Name [-Xdevmap Device-Map-File] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swststartsync [-h Server] Device-Name [-Xdevmap Device-Map-File] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specify the name of a Storage server. This option can be specified only on the Storage management server. |
|
-Xdevmap |
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, the 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 storage server) using an absolute pathname. A file name specified in Device-Map-File must not include any national character. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify the name of a block device |
End status
= 0: Normally terminated
> 0: Abnormally terminated
Execution example
Start synchronous backup processing of a transaction volume (/dev/vg01).
# /opt/FJSVswsts/bin/swststartsync /dev/vg01 /dev/vg01 swststartsync completed. # |
When you execute the backup synchronous processing start command for a transaction volume to which the backup synchronous processing is being executed, the message, "swst0301 Backup synchronous processing is being executed." is output and then the command is terminated normally.
You cannot start backup synchronous processing in the following cases. In any of the cases below, take an action according to the "System administrator response" message.
When specifying a device that does not support the EC function.
When the backup volumes required to start 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.
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
When the replication control function or tape backup function uses 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 (differential copy starts). Otherwise, the synchronous processing (full copy) starts.
Even if already in use, the transaction volume where the synchronous processing started and 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.
When any of the following commands is running, this command cannot be executed:
Resource match command (swstsrsemtch)
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Resource backup command (swstresback)
Resource restore command (swstresrst)
The backup synchronous processing during copying by EC or under the equivalency maintain status may be canceled.
The synchronous processing can be canceled with the backup volume during copying by EC, under the equivalency maintain 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, the copying being performed at that time terminates abnormally. In such a case, use this command to cancel the backup synchronous processing. Use the backup synchronous processing progress display command (swstsyncstat) to check for the error.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstcancelsync [-emergency] [-bd Backup-Device-Name | -all] Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstcancelsync [-h Server] [-emergency] [-bd Backup-Device-Name | -all] Device-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specify the name of a Storage server. This option can be specified only with a Storage management server. |
|
-emergency |
Emergency operation mode is available for operations. In such cases, EC sessions are neither confirmed nor cancelled. |
|
-bd |
The synchronous processing on a specific backup volume can be cancelled. To do so, specify the backup volume name in an operand. The backup volume name and -all option cannot be specified together. |
|
-all |
All of the synchronous processing of the transaction volume can be specified to be cancelled. This specification and the -bd option cannot be specified together. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify the name of a block device. |
|
Backup-Device-Name |
Specify the copy destination backup volume name. Specify the block device name for the specified device. |
End status
= 0: Normally terminated
> 0: Abnormally terminated
Execution example
Cancel synchronous backup processing of a transaction volume (/dev/vg01).
# /opt/FJSVswsts/bin/swstcancelsync /dev/vg01 /dev/vg01 swstcancelsync completed. # |
Backup synchronous processing of transaction volume (/dev/vg02) is cancelled in emergency operation mode.
# /opt/FJSVswsts/bin/swstcancelsync -emergency /dev/vg02 /dev/vg02 swstcancelsync completed. # |
The backup synchronous processing of the backup volume (/dev/vg04) can be specified to be canceled from the transaction volume (/dev/vg06).
# /opt/FJSVswsts/bin/swstsyncstat /dev/vg04 Server Transaction-Disk Backup-Disk Status Execute job2 /dev/vg04 /dev/vg05 suspend ---- job2 /dev/vg04 /dev/vg06 executing 75% # /opt/FJSVswsts/bin/swstcancelsync /dev/vg04 -bd /dev/vg06 /dev/vg04 swstcancelsync completed. # /opt/FJSVswsts/bin/swstsyncstat /dev/vg04 Server Transaction-Disk Backup-Disk Status Execute job2 /dev/vg04 /dev/vg05 suspend ---- # |
All of the backup synchronous processing of the transaction volume (/dev/vg07) can be specified to be cancelled.
# /opt/FJSVswsts/bin/swstsyncstat /dev/vg07 Server Transaction-Disk Backup-Disk Status Execute job2 /dev/vg07 /dev/vg08 suspend ---- job2 /dev/vg07 /dev/vg09 executing 75% # /opt/FJSVswsts/bin/swstcancelsync /dev/vg07 -all /dev/vg07 swstcancelsync completed. # /opt/FJSVswsts/bin/swstsyncstat /dev/vg07 Server Transaction-Disk Backup-Disk Status Execute job2 /dev/vg07 ---- ---- ---- # |
You cannot perform cancel processing of synchronous backup processing in the following cases
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
When the replication control function or tape backup function uses the target transaction volume
However, EC sessions are neither confirmed nor cancelled by execution in emergency operation mode. If an EC session is in the error suspended state or halt state, then unmanaged sessions remain. In this event, GRmgr or ETERNUSmgr must be used to cancel these sessions.
This command cannot be executed when any of the following commands is running:
Resource match command (swstsrsemtch)
Device information setting command (swstdevinfoset)
Storage server configuration information setting command (swstsvrset)
Resource backup command (swstresback)
Resource restore command (swstresrst)
The execution status of the backup synchronous processing is displayed (during copying, under the equivalency maintain status, in the suspended status).
If one transaction volume has multiple EC sessions, then the statuses of all of these EC sessions are displayed.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstsyncstat [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstsyncstat [-h Server] [Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specify the name of a Storage server. This option can be specified only with the Storage management server. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify the name of a block device. When you omit the device name, the system displays the status of backup synchronous processing for all of the transaction volumes. |
End status
= 0: Normally terminated
> 0: Abnormally terminated
Execution example
Display the synchronous backup processing status of a transaction volume (/dev/vg01).
# /opt/FJSVswsts/bin/swstsyncstat /dev/vg01 Server Transaction-Disk Backup-Disk Status Execute job1 /dev/vg01 /dev/vg02 suspend ---- job1 /dev/vg01 /dev/vg03 executing 75% # |
Display the synchronous backup processing status of all business volumes.
# /opt/FJSVswsts/bin/swstsyncstat Server Transaction-Disk Backup-Disk Status Execute job1 /dev/vg01 /dev/vg05 suspend ---- job1 /dev/vg01 /dev/vg06 executing 75% job1 /dev/vg01 /dev/vg07 suspend ---- job1 /dev/vg02 /dev/vg08 equivalent 100% job1 /dev/vg03 /dev/vg09 failed ---- job1 /dev/vg04 ---- ---- ---- # |
The table below lists the meaning of each title.
|
Title |
Description |
|---|---|
|
Server |
Indicates the name of the Storage server. |
|
Transaction-Disk |
Indicates the name of the transaction volume. |
|
Backup-Disk |
Indicates the name of the backup volume. When backup synchronous processing is not being executed, the system displays "----". |
|
Status |
Indicates the status of backup synchronous processing:
|
|
Execute |
Indicates the progress of the backup synchronous processing as a percentage (0 to 100%). "----" is displayed when the status is Suspend and at times not during the backup synchronous processing. |
You cannot perform processing of displaying status of the synchronous processing in the following cases
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
If "failed" or "halt" is indicated as the status of the backup synchronous processing (in the Status field), a hardware failure is considered. Refer to "Troubleshooting for a hardware error, etc. occurring during backup".
If "nosession" is indicated as the status of the backup synchronous processing (in the Status field)," resource information having inconsistency is considered. Use the resource match command (swstsrsemtch) to remove the inconsistency from the resource information.
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.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstexecstat [-j] [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstexecstat [-h Server] [-j] [Device-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-j |
Specifies to display information in another format. |
Description of operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name corresponding to a transaction volume. Specify the name of a block device. If this operand is omitted, the execution statuses of all the transaction volumes will be displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Display the execution statuses of transaction volumes.
# /opt/FJSVswsts/bin/swstexecstat Server Device Last-Backup-Date Interval Status Mount-Point (Method) Execute job1 /dev/vg01 2000/12/11 12:20 OK IDLE ---- (----) ---- job1 /dev/vg02 2000/12/10 12:20 DELAY=1 IDLE ---- (----) sync(22%) job1 /dev/vg03 2000/12/09 12:20 DELAY=2 IDLE ---- (----) snapshot(45%) : # |
The following information will be displayed.
|
Keyword |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Device |
Displays a AdvancedCopy Manager device name. |
|
Last-Backup-Date |
Displays the last backup date. * Displays the time when the 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 name of a transaction volume and FStype in parentheses. However, AIX does not display mount points. Therefore, "---- (----)" is always displayed. |
|
Execute |
Displays the name of a command being executed or the copying progress ratio.
|
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 snap shot backup is being handled), the display in the Execute field conforms to the following rule:
The display of a command name takes priority if both copying and command execution are in progress.
When a disk copy of the snap shot 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 snap shot backup or backup synchronous processing due to a restriction of the ETERNUS storage system.)
The execution example of using the "-j" option is as follows:
# /opt/FJSVswsts/bin/swstexecstat -j Server Device Execute-Date Status Mount-Point (Method) Execute job1 /dev/vg01 2000/12/11 12:20 IDLE ---- (----) ---- job1 /dev/vg02 2000/12/10 12:20 IDLE ---- (----) sync(22%) job1 /dev/vg03 2000/12/09 12:20 IDLE ---- (----) snapshot(45%) : # |
The following information will be displayed.
|
Keyword |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Device |
Specifies a AdvancedCopy Manager device name. |
|
Execute-Date |
Displays the command execution time. |
|
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 name of a transaction volume and FStype in parentheses. However, AIX does not display mount points. Therefore, "---- (----)" is always displayed. |
| Execute |
Displays the name of a command being executed or the copying progress ratio.
|
During synchronous high-speed backup with -suspend specified, no operation ("----") is indicated in the Execute field.
You cannot perform processing of displaying the execution status in the following cases
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
If "sync (failed),", "snapshot(failed)", or "restore(failed)", "sync (halt)", "snapshot(halt)" or "restore(halt)" is displayed in the "Execute" field, a hardware error may have occurred. After removing the cause of the hardware error, do as follows:
For "sync (failed)"
Execute the backup synchronous processing cancel command (swstcancelsync) to cancel the backup synchronous processing.
If "snapshot(failed)" is displayed
Delete backup history information using the history information deletion command (swsthistdel).
If "restore(failed)" is displayed
Cancel restoration using the restore cancellation command (swstcancelrest).
This command stops tracking processing.
Specification method
|
[To execute on the storage server] [To execute on the storage management server] |
Options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on the storage management server. |
|
-copy |
Specifies that physical copying, if active, should also be stopped (the OPC session should be canceled). This option cannot be specified for a backup volume that has already been a backup history. For a volume whose copy destination volume has been a backup history, delete the history information in advance using the history deletion command (swsthistdel). |
|
-emergency |
Specifies that the command should operate in emergency operation mode. The command does not check tracking processing and does not stop tracking processing and the OPC session. |
|
-bd |
Stops tracking processing for the specified backup volume. Specify the target backup volume name as an operand. This option cannot be specified together with the -all option. |
|
-all |
Stops the entire tracking processing specified for the transaction volumes. This option cannot be specified together with the -bd option. |
Operand
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify a block device name. |
End status
= 0: Normal end
> 0: Abnormal end
Example
The following example stops the tracking processing that was specified for the backup volume (/dev/vg8) from the transaction volume (/dev/vg3)
# /opt/FJSVswsts/bin/swstcanceltrk /dev/vg03 -bd /dev/vg08 /dev/vg03 swstcanceltrk completed. # |
The following example stops tracking processing and physical copying that were specified for the transaction volume (/dev/vg3).
# /opt/FJSVswsts/bin/swsttrkstat /dev/vg03 Server Transaction-Disk Backup-Disk Status Execute Update job2 /dev/vg03 /dev/vg03 executing 33% ----- # /opt/FJSVswsts/bin/swstcanceltrk -copy /dev/vg03 -bd /dev/vg08 /dev/vg03 swstcanceltrk completed. # |
If the command is executed in emergency operation mode, no OPC session is canceled. A session that is not managed remains if the command is entered during tracking. The session must be canceled using GRmgr, ETERNUSmgr, or GDS.
Tracking processing cannot be stopped under the following conditions. In this case, take action according to "System administrator response" provided for the message output.
- Tracking processing is not performed for the specified copy source and destination volumes.
This command cannot be executed while the following command is executed:
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Resource matching command (swstsrsemtch)
Resource backup command (swstresback)
Resource restore command (swstresrst)
This command displays the status of tracking processing.
When multiple types of synchronous processing exist for one transaction volume, the command displays the statuses of all types of tracking processing.
Specification method
|
[To execute on the storage server] [To execute on the storage management server] |
Options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on the storage management server. |
Operands
|
Operand |
Description |
|---|---|
|
Device-Name |
Specifies a device name. Specify a block device name. If this operand is omitted, the command displays the statuses of tracking processing for all transaction volumes. |
End status
= 0: Normal end
> 0: Abnormal end
Example
The following example displays the status of tracking processing of a transaction volume (/dev/vg3):
# /opt/FJSVswsts/bin/swsttrkstat /dev/vg03 Server Transaction-Disk Backup-Disk Status Execute Update job1 /dev/vg03 /dev/vg08 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/vg03 /dev/vg08 nosession ---- ---- job1 /dev/vg04 /dev/vg09 executing 75% ---- job1 /dev/vg05 /dev/vg10 failed ---- ---- job1 /dev/vg06 /dev/vg11 tracking ---- 12% job1 /dev/vg07 ---- ---- ---- ---- : # |
The displayed data is explained below.
|
Title |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Transaction-Disk |
Displays a transaction volume name. |
|
Backup-Disk |
Displays a backup volume name. Displays "----" when the volume is not in the tracking status. |
|
Status |
Displays the execution status. "----": Not in progress of tracking "executing": In progress of physical copying and tracking "tracking": In progress of tracking "failed": Physical copying or tracking terminated abnormally. "nosession": No session exists. (Resource information is inconsistent.) |
|
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. |
When the execution status (status displayed in the "Status" column) is "failed," a hardware problem is assumed. Remove the problem cause and then reexecute the differential snapshot backup.
When the execution status (status displayed in the "Status" column) is "nosession," the resource information is probably inconsistent. Use the resource matching command (swstsrsemtch) to remove any inconsistencies from the resource information.
The execution status of tracking processing cannot be displayed under the following conditions:
When the transaction volume or backup volume is a logical volume, the volume configuration of the logical volume has been changed to one that is not supported by AdvancedCopy Manager.
When the transaction volume or backup volume is a volume group, the volume group is not active.
This chapter describes maintenance commands for backup management.
To operate backup management, use the following maintenance commands:
|
Function |
Command name |
Description |
|---|---|---|
|
swstsrsemtch |
Recovers the consistency of information in a backup management files. |
|
|
swstresback |
Backs up a backup management files. |
|
|
swstresrst |
Restores a backup management files. |
This command makes recovery to make resource information consistent if a system failure, etc. has made the resource information inconsistent.
Specification method
| [To be executed on a storage server] # /opt/FJSVswsts/bin/swstsrsemtch [-x] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstsrsemtch [-x] [-h Server] |
Description of operands
|
Operand |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-x |
Gets consistency with a repository. Specify this option if the consistency between a backup management files and a repository comes to be inconsistent. |
Execution example
# /opt/FJSVswsts/bin/swstsrsemtch swstsrsemtch completed # |
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Backup policy setting command (swstbkpolset)
Backup policy deletion command (swstbkpoldel)
Backup execution command (swstbackup)
Restore execution command (swstrestore)
Restore cancellation command (swstcancelrest)
Backup synchronous processing start command (swststartsync)
Backup synchronous processing cancel command (swstcancelsync)
History information deletion command (swsthistdel)
Tracking cancel command (swstcanceltrk)
Resource match command(swstsrsemtch)
Resource backup command(swstresback)
Resource restore command(swstresrst)
This command backs up a backup management files to a specified directory.
Specification method
# /opt/FJSVswsts/bin/swstresback Backup-Directory |
Description of operand
|
Operand |
Description |
|---|---|
|
Backup-Directory |
Specifies the name of a directory to which a backup management files should be saved. |
Execution example
Create backup copy of the backup management files in /home/backup.
# /opt/FJSVswsts/bin/swstresback /home/backup swstresback completed # |
You cannot perform backup if:
The specified directory does not exist.
Copying of data to the specified directory failed because of insufficient free space, etc.
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Backup policy setting command (swstbkpolset)
Backup policy deletion command (swstbkpoldel)
Backup execution command (swstbackup)
Restore execution command (swstrestore)
Restore cancellation command (swstcancelrest)
Backup synchronous processing start command (swststartsync)
Backup synchronous processing cancel command (swstcancelsync)
History information deletion command (swsthistdel)
Tracking cancel command (swstcanceltrk)
Resource match command(swstsrsemtch)
Resource backup command(swstresback)
Resource restore command(swstresrst)
The backup management files are restored from the specified directory.
Specification method
# /opt/FJSVswsts/bin/swstresrst Backup-Directory |
Description of operand
|
Operand |
Description |
|---|---|
|
Backup-Directory |
Specify the name of the directory to which to save the backup management files. |
Execution example
Create backup copy of the backup management files in /home/backup.
# /opt/FJSVswsts/bin/swstresrst /home/backup swstresrst completed # |
Before the backup management files can be restored by this command, the storage server configuration information setting command (swstsvrset) must be executed.
You cannot perform restoration if:
The specified directory does not exist.
No backup management files exist in the specified directory.
Copying of data from the specified directory for restoration failed because of insufficient free space, etc.
This command can be executed only while none of the following commands are running.
Storage server configuration information setting command (swstsvrset)
Device information setting command (swstdevinfoset)
Backup policy setting command (swstbkpolset)
Backup policy deletion command (swstbkpoldel)
Backup execution command (swstbackup)
Restore execution command (swstrestore)
Restore cancellation command (swstcancelrest)
Backup synchronous processing start command (swststartsync)
Backup synchronous processing cancel command (swstcancelsync)
History information deletion command (swsthistdel)
Tracking cancel command (swstcanceltrk)
Resource match command(swstsrsemtch)
Resource backup command(swstresback)
Resource restore command(swstresrst)
This chapter is explaining operation by the command of the composition management which manages the information on a device used as the server which performs backup employment and replication employment, or the candidate for employment.
Operating environment for command execution
The table below lists the requirements for the operating environment in which to execute the respective commands.
Command
Operating environment of AdvancedCopy Manager
stgcmmodnode
To execute this command on a storage management server (storage management server transaction), the storage management server (storage management server transaction) must be operating.
stgenvdisp
This command is executable when both storage management server (storage management server transaction) and storage server (storage server transaction) are not operating.
Note that when the cluster service (named differently in respective cluster systems) is not operating in cluster operation, this command cannot display certain information.stgmgrinfoset
The package-backup-of-the-management-information execution server must be operating.
stgmgrinfobkup
The storage management server (storage management server transaction), package-backup-of-the-management-information execution server, and package-backup-of-the-management-information target servers must be operating.
stgmgrinfodisp
The package-backup-of-the-management-information execution server must be operating.
In cluster operation
In cluster operation, execute a command by taking the following steps:
If necessary, specify the logical node name to the transaction in environment variable SWSTGNODE. For bsh, specify the environment variable as follows:
Execute the command.
The table below lists the commands available in cluster operation, whether environment variables must be configured, and the nodes on which commands are executable. For notes and cautions on command execution, see the Remarks column.
Command
Environment variable
Command execution node
Remarks
stgcmmodnode
Required
Transaction operating node
stgenvdisp
Not required
Transaction operating node
stgmgrinfobkup
Required
Transaction operating node
stgmgrinfodisp
Required
Transaction operating node
stgmgrinfoset
Required
Transaction operating node
This command changes the server change information of the Storage management server. Concretely, execute this command for the following purposes:
To change the IP address of the Storage management server or the PORT number (stgxfws) used by the communication daemon
Follow the procedure below:
Change server information by executing this command on the Storage management server.
Change server information of the Storage management server by executing this command on every Storage server. This command must be executed on all Storage servers managed by the Storage management server.
To change the server name of the Storage management server
Follow the procedure below:
Change the server name from the initial window of the Storage management server.
Change the server name of the Storage management server by executing this command on every Storage server. This command must be executed on all Storage servers managed by the Storage management server.
This command has the following two functions:
Displays storage management server information specified on the storage server on which this command is currently executed
Changes storage management server information.
Specification method
|
# /opt/FJSVswstf/bin/stgcmmodnode [-i IP-address] [-p PORT number] [-n server name] |
Description of options
|
Option |
Description |
|---|---|
|
None |
Displays the server information currently managed. |
|
-i |
Specifies the IP address of a storage management server to change the IP address of the storage management server. |
|
-p |
Specifies the port number of a storage management server to change the port number of the storage management server. |
|
-n |
Specifies the server name of a storage management server to change the server name of the storage management server. This option cannot be specified if this command is executed on a storage management server. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Display server information.
# /opt/FJSVswstf/bin/stgcmmodnode swstf2413 IP Address = 10.10.10.10 swstf2413 PORT Number = 1226 swstf2413 Storage Management Server's Name = fujitsu-storage-management-server # |
Change the IP address of a storage management server to 10.12.13.14.
# /opt/FJSVswstf/bin/stgcmmodnode -i 10.12.13.14 swstf2401 AdvancedCopy Manager registry updated. |
The following lists notes on this command.
This command can be executed only by root users.
As the PORT number of a storage management server, you can specify a value between 1024 and 65535.
In this command, specify the same value as the one specified on a storage management server. A error will occur in the operation if an invalid value is specified.
If this command is executed, restart the AdvancedCopy Manager daemons.
Repository access user change command (stguserset) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
GUI connection information setting command (stgguiipset) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Server information addition command (stgxfwcmaddsrv) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Server information change command (stgxfwcmmodsrv) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Server information deletion command (stgxfwcmdelsrv) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Device information collection/reflection command (stgxfwcmsetdev) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Device information deletion (stgxfwcmdeldev) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Server information display command (stgxfwcmdispsrv) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Device information display command (stgxfwcmdispdev) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
Partition information display command (stgxfwcmdisppat) is executed by the Storage management server.
Please refer to the Operator's guide to OS of a Storage management server.
This command displays values of environment settings in AdvancedCopy Manager.
To output cluster operation information, execute the command from an active node. Executing the command from a standby node displays only partial information. To output cluster operation information while a transaction is stopped, set the shared disk containing the AdvancedCopy Manager shared data of the transaction to the online state or mount the shared disk, and then execute the command.
When this command is executed in a cluster environment, the environment variable (SWSTGNODE) need not be set.
Only users with root authority can execute this command.
Specification method
# /opt/FJSVswstf/bin/stgenvdisp [-n transaction-logical-node-name] |
Description of options
|
Option |
Description |
|---|---|
|
-n |
Specifies the logical node name (logical node name specified in the cluster setup command) of the transaction.
If this option is specified, information on only the specified transactions is output. Otherwise, information on all transactions is output.
This option cannot be specified. If the option is specified, then message swstf6001 is output and processing ends. Otherwise, information is output. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Information in a non-cluster environment is displayed.
# /opt/FJSVswstf/bin/stgenvdisp Server type : Server Manager IP address : 10.10.10.10 Communication : 1226 # |
Information on all transactions in a cluster environment (VERITAS Cluster Server) is displayed.
# /opt/FJSVswstf/bin/stgenvdisp Server type : Server Cluster system : VERITAS Cluster Server Node type : Primary Node name : nodeagt1 Service name : agent_service1 Mount point : /acmagt1disk Manager IP address : 10.10.10.10 Communication : 11000 ------------------------------------------------------------------------- Server type : Server Cluster system : VERITAS Cluster Server Node type : Secondary Node name : nodeagt2 Service name : agent_service2 Mount point : /acmagt2disk Manager IP address : 10.10.10.10 Communication : 12000 ------------------------------------------------------------------------- Server type : Server Node name : Local-Service Manager IP address : 10.10.10.10 Communication : 1226 # |
The contents of displayed information are described below.
|
Title |
Description |
|---|---|
|
Server type |
The server type is displayed as follows: |
|
Cluster system |
The type of cluster system is displayed as follows: |
|
Node type |
The node type is displayed as follows: |
|
Node name |
The logical node name is displayed. |
|
Service name |
The transaction name is displayed. |
|
Cluster name |
The cluster name is displayed. |
|
Mount point |
The mount point for AdvancedCopy Manager shared data is displayed. |
|
Disk resource |
The name of the shared disk resource used for AdvancedCopy Manager shared data is displayed. |
|
Drive |
The drive letter used for AdvancedCopy Manager shared data is displayed. |
|
Volume group |
The volume group name is displayed. |
|
Network name |
The name of the network for AdvancedCopy Manager is displayed. |
|
External connection |
The external connection network name is displayed. |
|
Subnet mask |
The subnet mask is displayed. |
|
IP address resource |
IP address resource information is displayed. |
|
IP by cluster setup |
The logical IP address specified in the cluster setting command is displayed. |
|
Manager IP address |
The IP address of the storage management server is displayed. |
|
Repository user |
The name of the user accessing the repository is displayed. |
|
DB log file |
[Windows Edition only] |
|
DB dictionary file |
[Windows Edition only] |
|
Repository database |
[Windows Edition only] |
|
DB file |
[Solaris Edition] [Linux Edition] |
|
RDB dictionary |
[Solaris Edition] [Linux Edition] |
|
RDB log file |
[Solaris Edition] [Linux OE Edition] |
|
Database space |
[Solaris Edition] [Linux Edition] |
|
Database size |
[Windows Edition and Linux Edition only] |
|
IP address for GUI |
The GUI connection IP address is displayed. |
|
Communication |
The communication service/daemon port number (service name in the services file: stgxfws) is displayed. |
|
Remote access |
The remote access service/daemon port number (service name in the services file: rmiswstf) is displayed. |
|
Exclusive control |
The exclusive control service/daemon port number (service name in the services file: semswstf) is displayed. |
|
Authentication feature |
The authentication feature service/daemon port number (service name in the services file: smaclmgr) is displayed. |
|
Repository |
The repository service/daemon port number (service name in the services file: rdaswstf) is displayed. |
"????" is displayed for any information that cannot be displayed because of an error.
Some items may not be output depending on the cluster type.
The command registers the management information package backup execution server (the server on which the management information package backup command is executed).
The command deletes the management information package backup execution server.
The command displays information about the management information package backup execution server.
Specification method
program-directory/bin/stgmgrinfoset [-del | -d directory-name -c storage-management-server-encoding] |
Description of options
|
Option |
Description |
|---|---|
|
None |
Displays information about the management information package backup execution server. |
|
-del |
Deletes the management information package backup execution server. |
|
-d |
Specify the full path to the directory where the backup data is to be stored. Only alphanumeric characters and underscores can be used in the directory name. |
|
-c |
Specify the encoding designated when the storage management server was installed. Specify either of the following: ASCII : ASCII |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Register the management information package backup execution server (the path to the directory where backup data is to be stored is D:\stgbkupdata, and the encoding used on the storage management server is ASCII):
# /opt/FJSVswstf/bin/stgmgrinfoset -d /stgbkupdata -c ASCIIswstf3000 The server which performs package backup of the management information on AdvancedCopy Manager was registered. # |
Delete the management information package backup execution server:
# /opt/FJSVswstf/bin/stgmgrinfoset -del swstf3001 The server which performs package backup of the management information on AdvancedCopy Manager was deleted. Delete a directory. Directory=/stgbkupdata # |
Display information about the management information package backup execution server:
# /opt/FJSVswstf/bin/stgmgrinfoset Directory : /stgbkupdata Manager code : ASCII # |
The following notes apply to this command:
Only a root user or an account which belongs to the administrators group can execute this command.
To change the backup data storage directory, first use the -del option to delete the current directory, then register a new backup data storage directory.
Register only one storage server as the management information package backup execution server.
Set the name of the logical node in the SWSTGNODE environment variable when the storage server registered as the management information package backup execution server is in a cluster system.
Create the directory specified in the -d option in advance.
This command makes backups of the management information stored on the storage servers and storage management server.
Specification method
program-directory/bin/stgmgrinfobkup [-n server-name] [-t backup-type] |
Description of options
|
Option |
Description |
|---|---|
|
-n |
Makes backups of the management information stored on the specified server. If this option is not specified, the management information on all storage servers (including the storage management server) is backed up. |
|
-t |
Specifies the types of data that is to be backed up. Specify one of the values listed below. Do not specify more than one value in the -t option: DBData: Database RegiData: Registry MgrInfoData: Policy file for management information package backup AuthData: Authentication management list BkupData: Backup management ReplData: Replication management TapeData: Tape backup management backup If this option is not specified, backups are made as defined in the policy file. For details on the policy file, refer to the "Preliminaries" in this manual. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Make backups of the management information on all the storage servers as defined in the policy file:
# /opt/FJSVswstf/bin/stgmgrinfobkup swstf3014 Backup of management information is started. Start time=04/07/02 11:00:00, Server name=acm01 swstf3020 Backup of management information was ended normally. End time=04/07/02 11:02:00, Server name=acm01 swstf3014 Backup of management information is started. Start time=04/07/02 11:02:00, Server name=acm02 swstf3020 Backup of management information was ended normally. End time=04/07/02 11:05:00, Server name=acm02 swstf3021 The normal end of the backup of management information was carried out by all servers. # |
Make backups of the management information on storage server acm01 as defined in the policy file:
# /opt/FJSVswstf/bin/stgmgrinfobkup -n acm01 swstf3014 Backup of management information is started. Start time=04/07/02 11:00:00, Server name=acm01 swstf3020 Backup of management information was ended normally. End time=04/07/02 11:02:00, Server name=acm01 swstf3021 The normal end of the backup of management information was carried out by all servers. # |
Makes backups of the registries on all of the storage servers.
# /opt/FJSVswstf/bin/stgmgrinfobkup -t RegiData swstf3014 Backup of management information is started. Start time=04/07/02 11:00:00, Server name=acm01 swstf3020 Backup of management information was ended normally. End time=04/07/02 11:02:00, Server name=acm01 swstf3014 Backup of management information is started. Start time=04/07/02 11:02:00, Server name=acm02 swstf3020 Backup of management information was ended normally. End time=04/07/02 11:05:00, Server name=acm02 swstf3021 The normal end of the backup of management information was carried out by all servers. # |
Make a backup of backup management located on storage server acm01:
# /opt/FJSVswstf/bin/stgmgrinfobkup -n acm01 -t BkupData swstf3014 Backup of management information is started. Start time=04/07/02 11:00:00, Server name=acm01 swstf3020 Backup of management information was ended normally. End time=04/07/02 11:02:00, Server name=acm01 swstf3021 The normal end of the backup of management information was carried out by all servers. # |
The following notes apply to this command:
Only a root user or an account which belongs to the administrators group can execute this command.
Be sure to check the information (a message indicating completion or an error) output by this command.
This command can be executed only on the management information package backup execution server.
Set the name of the logical node in the SWSTGNODE environment variable when the management information package backup execution server is in a cluster system.
Do not execute other AdvancedCopy Manager commands or GUI commands while this command is running. Conversely, do not execute this command while another AdvancedCopy Manager command or a GUI command is running.
Do not execute this command again if it is already running.
To save backup data to a tape or similar medium, save all files and directories under the backup data storage directory.
Registry backups are made only when RegiData is specified in the -t option. A registry backup will not be made if the -t option is not specified.
A backup of the policy file for management information package backup is made only when MgrInfoData is specified in the -t option. No backup is made when the -t option is not specified. Additionally, specify the name of the management information package backup execution server in the -n option.
Backup is not possible for any management information on storage servers with Softek AdvancedCopy Manager 10.3 (V10.0L40) or earlier.
This command displays the status of execution of the management information package backup command.
Specification method
program-directory/bin/stgmgrinfodisp [-n server-name] |
Description of options
|
Option |
Description |
|---|---|
|
-n |
Specifies the name of the server where the backup status is to be output. If this option is not specified, the status of backups on the storage server for which the management information package backup command was executed is displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Output information
The types of information listed below are output. If no backups are made when the management information package backup command is executed or if the management information package backup command ends in error, no data is output.
|
Item |
Description |
|---|---|
|
Server |
Server name |
|
RegiData |
Date and time at which the management information package backup command created a backup of a registry (date and time that the management information package backup command was executed) yy/mm/dd hh:mm:ss |
|
DBData |
Date and time at which the management information package backup command created a backup of the database (date and time that the management information package backup command was executed) yy/mm/dd hh:mm:ss |
|
AuthData |
Date and time at which the management information package backup command created a backup of the authentication management list (date and time that the management information package backup command was executed) yy/mm/dd hh:mm:ss |
|
BkupData |
Date and time at which the management information package backup command created a backup of the backup management (date and time that the management information package backup command was executed) yy/mm/dd hh:mm:ss |
|
ReplData |
Date and time at which the management information package backup command created a backup of replication management (date and time that the management information package backup command was executed) yy/mm/dd hh:mm:ss |
|
MgrInfoData |
Date and time at which the management information package backup command created a backup of the policy file for management information package backup (date and time that the management information package backup command was executed) yy/mm/dd hh:mm:ss |
|
TapeData |
Date when a backup of tape backup management was made by package backup using the management information command (with package backup of the management information command executed) yy/mm/dd hh:mm:ss |
Execution example
Output information about all storage servers:
# /opt/FJSVswstf/bin/stgmgrinfodisp Server: acm01 DBData: 04/08/02 16:11:26 AuthData: 04/08/02 16:32:00 RegiData: 04/08/01 09:00:00 ReplData: 04/08/02 16:32:22 Server: acm02 RegiData: 04/08/01 09:00:00 BkupData: 04/08/03 16:00:00 Server: tape RegiData: 05/08/01 09:00:00 TapeData: 05/08/03 16:00:00 # |
Output information about storage server acm01:
# /opt/FJSVswstf/bin/stgmgrinfodisp -n acm01 Server: acm01 DBData: 04/08/02 16:11:26 AuthData: 04/08/02 16:32:00 RegiData: 04/08/01 09:00:00 ReplData: 04/08/02 16:32:22 # |
The following notes apply to this command:
Only a root user or an account which belongs to the administrators group can execute this command.
This command can be executed only on the management information package backup execution server.
Set the name of the logical node in the SWSTGNODE environment variable when the management information package backup execution server is in a cluster system.
This chapter describes operations using Replication Management Commands. It is necessary to execute the command of replication management by the root user.
Only a root user can execute all the commands of replication management. When command execution is carried out by other users, a message "swsrp0601 This Command cannot be run. This is because the user is not a root user." is outputted and then, an error end.
Operating environment for command execution
The table below lists the requirements for the operating environment in which to execute the respective commands.
Command
Operating environment of AdvancedCopy Manager
swsrpcancel
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows and is in EC operation, the daemons and services of the copy destination storage server must be operating (except when the -m option or -t option is specified).
For inter-server replication in EC equivalency status, the associated server must be operating (except when the -m option is specified).swsrpchsync
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swsrpdelvol
To execute this command on a storage server, the daemons and services of the storage management server must be operating.
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
For inter-server replication, the daemons and services of the storage server in communication must be operating (except when the -d option is specified).swsrprecbuffstat
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swsrprecbuffset
To execute this command on a storage server, the daemons and services of the storage management server must be operating.
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operatingswsrpmake
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows and is engaged in intra-server replication and EC operation, the daemons and services of the storage server must be operating.
For inter-server replication, the daemons and services of the storage server in communication must be operating (except when the -m option or -t option is specified).swsrprecoverres
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows, the daemons and services of the storage server must be operating.
To specify the -r option, the daemons and services of the storage management server must be operating.swsrprevsync
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swsrpsetvol
To execute this command on a storage server, the daemons and services of the storage management server must be operating.
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
For inter-server replication, the daemons and services of the storage server in communication must be operating.swsrpstartsync
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
When the storage server runs on Windows, the daemons and services of the storage server must be operating.
For inter-server replication, the associated server must be operating (except a case where the -m option is specified).swsrpstat
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
swsrpvolinfo
To execute this command on a storage management server with the -h option specified, the daemons and services of the storage management server and target storage server must be operating.
In cluster operation
In cluster operation, execute a command by taking the following steps:
If necessary, specify the logical node name to the transaction in environment variable SWSTGNODE. For bsh, specify the environment variable as follows:
Execute the command.
The table below lists the commands available in cluster operation, whether environment variables must be configured, and the nodes on which commands are executable. For notes and cautions on command execution, see the Remarks column.
Command
Environment variable
Command execution node
Remarks
swsrpsetvol
Required
Transaction operation node
swsrpvolinfo
Required
Transaction operation node
swsrpdelvol
Required
Transaction operation node
swsrprecbuffstat
Required
Transaction operation node
swsrprecbuffset
Required
Transaction operation node
swsrpstartsync
Required
Transaction operation node
swsrpmake
Required
Transaction operation node
swsrpstat
Required
Transaction operation node
swsrpcancel
Required
Transaction operation node
swsrpchsync
Required
Transaction operation node
swsrprevsync
Required
Transaction operation node
swsrprecoverres
Required
Transaction operation node
This chapter describes environment definition commands for replication management. To define a replication management environment, use the following commands:
|
Function |
Command name |
Description |
|---|---|---|
|
swsrpsetvol |
Sets the information about a replication volume. |
|
|
swsrpvolinfo |
Displays the information about a replication volume. |
|
|
swsrpdelvol |
Deletes replication volume information that has been set. |
|
|
swsrprecbuffstat |
Displays information for the REC transfer buffer. |
|
|
swsrprecbuffset |
Changes the settings for the REC transfer buffer. |
This command sets the replication source and replication destination volumes that will be used in a replication operation. Execute this command to declare that the replication operation will performed using the specified replication volumes.
Specification method
|
[To be executed on a storage server] For replication on a server /opt/FJSVswsrp/bin/swsrpsetvol [-n] [-u] [-Xgroup Group-Name] Original-Volume-Name Replica-Volume-Name For replication between servers /opt/FJSVswsrp/bin/swsrpsetvol [-n] [-u] -o (ORG|REP|BOTH) [-Xgroup Group-Name] Original-Volume-Name Replica-Volume-Name [To be executed on a storage management server] For replication on a server /opt/FJSVswsrp/bin/swsrpsetvol -h Server-Name [-n] [-u] [-Xgroup Group-Name] Original-Volume-Name Replica-Volume-Name For replication between servers /opt/FJSVswsrp/bin/swsrpsetvol -h Server-Name [-n] [-u] -o (ORG|REP|BOTH) [-Xgroup Group-Name] Original-Volume-Name Replica-Volume-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies the name of a storage server subject to the replication operation. This option is valid only on a storage management server. If this option is omitted, the storage server on which the command is entered will be the target to the processing. |
|
-u |
Specifies the direction of copying. If this option is specified, copying from a replication source volume to a replication destination volume is performed only in this direction. Copying from a replication destination volume to a replication source volume is prohibited. If this option is omitted, copying between the replication source and replication destination volumes interactively is bidirectional. |
|
-o |
Specifies the operation server. Specify one of the following for this operand: ORG: Sets the replication source server as the operation server. REP: Sets the replication destination server as the operation server. BOTH: Sets both the copy-source server and copy-destination server as operation servers. On the server that is not specified as the operation server, only the following commands can be executed for a replication volume:
Specifying BOTH in the operand enables the execution of all commands on both the copy-source server and copy-destination server. Note that the BOTH option is usable when the versions of both servers are 11.0/V11.0L10 or later. This option is valid only for replication between servers. |
|
-n |
If this option is omitted, replication volume information cannot be set when the sizes of the replication source volume and replication destination volume are different. When this option is specified, the sizes of the replication source volume and replication destination volume are not checked. Use this option when volume sizes are different (for example, for replication between different OSs). When the volume sizes of the replication source volume and replication destination volume are different, copying is performed as follows: The address at which copying starts is the first sector of the replication destination volume. The copy data size is the size of the smaller volume. |
|
-Xgroup |
Specifies that the copy source and copy destination volumes be registered in a group. If the specified group does not exist, a new group is created. Otherwise, the specified copy source and copy destination volumes are added to an existing group. Specifies a group name. The characters that can be used for the group name are single-byte alphanumeric characters, the minus sign (-), underscore (_), number sign (#) and period (.). The first character must be a single-byte alphanumeric character. Up to 64 characters can be used. |
Description of operands
|
Operand |
Description |
|---|---|
|
Original-Volume-Name |
Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." |
|
Replica-Volume-Name |
Specifies a replication destination volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Set replication volume information by specifying volume/dev/vg01 of storage server SRC-SV as the replication source volume and volume /dev/vg02 of storage server TARG-SV as the replication destination volume. In addition, specify one-way copying for the copy direction and specify the replication source server (SRC-SV) as the operation server. The example below shows the command executed on SRC-SV.
|
# /opt/FJSVswsrp/bin/swsrpsetvol -u -o ORG /dev/vg01 /dev/vg02@TARG-SV |
When the same settings are made from TARG-SV, the example is as follows (be careful with the volume name):
|
# /opt/FJSVswsrp/bin/swsrpsetvol -u -o ORG /dev/vg01@SRC-SV /dev/vg02 |
Replication volume information cannot be set if:
Replication volume information has already been set.
The specified replication source volume and replication destination volume are set as the replication destination volume and the replication source volume.
The n option is not specified when the sizes of the replication source volume and the replication destination volume are different.
Two volumes that have the same cabinet information (box identifier, OLU number, EXTENT start position, and EXTENT size) as the cabinet information of the specified two volumes have already been set as replication volumes.
The replication destination volume has been registered as a backup volume of the backup management function.
The replication source volume has been registered as a backup volume of the backup management function and bi-directional copying is specified as a replication volume attribute.
The specified replication destination volume and replication source volume are volumes belonging to other servers (at least one volume must be a volume on the local server).
If the replication source volume and the replication destination volume are located on another disk array device, the remote copy function of the disk array device is not correctly set.
Communication with the storage management server fails.
Communication with a destination server fails for replication between servers.
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
Note the following points when using a volume group as an original volume or replica volume:
Be sure to specify the pairs of a volume group as an original volume and replica volume. However, excluding between other platforms.
The same volume group cannot be registered as an original volume and replica volume.
When registering a volume group as an original volume and replica volume, make those logical disk compositions the same.
Note the following points about creating copy source volumes and copy destination volumes on Solaris system:
When creating multiple volumes (slices) on the same disk, volume areas must not overlap.
When using a physical disk on Solaris, create volumes (slices) so that VTOC is not contained in them.
Specify each volume defined in units of slices as a copy source volume or a copy destination volume. Do not specify any volume defined as an entire disk.
When you change physical information on volumes (partition size, drive letter, and cabinet information on a disk array device) using such functions as an OS management tool (for example, Disk Administrator) or GRmgr/ETERNUSmgr provided by the disk array device, you need to reset the registered replication volume information associated with the changed volumes, according to the following procedures:
Delete the replication volume information by the replication volume information deletion command (swsrpdelvol).
In an initial screen, "information acquisition / reflection" of all devices are performed. Or device information acquisition / reflection command (stgxfwcmsetdev) is executed in a Storage management server.
Reset the replication volume information by the replication volume informatin setting command (swsrpsetvol).
When you use a replication destination volume by mounting or by allocating a drive letter after creating a replication, the size of the replication destination volume must exactly match the size of the replication destination volume to the byte. If you do not use a replication destination volume (for example, when you need copy data, you restore it to the replication source volume and then use it), the size of the replication destination volume can be larger than the size of the replication source volume.
Group settings cannot be made in the following cases:
When the group configuration conditions are not met
When both servers involved in inter-server replication are not running version 13.0 or later
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Synchronous processing start command (swsrpstartsync)
Replication creation command (swsrpmake)
Replication cancellation command (swsrpcancel)
Syncronization mode change command (swsrpchsync)
Syncronisation reverse command (swsrprevsync)
Resource adjustment command (swsrprecoverres)
This command displays the replication volume information registered by the replication volume setting command.
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrpvolinfo [-L] [Original-Volumue-Name] [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrpvolinfo -h Server-Name [-L] [Original-Volume-Name] |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option is valid only on a storage management server. |
|
-L |
Specifies that information be displayed using the extended format. Refer to the table in the execution example for information about the items that are displayed when this option is specified. The items that are displayed when this option is specified may be expanded to support new functions provided by future versions. |
Description of operands
|
Operand |
Description |
|---|---|
|
Original-Volume-Name |
Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Displays all the replication volume information for the specified replication source volume. If this operand is omitted, all the replication volume information existing on the storage server on which this command is executed is displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Direct that all the replication volume information on a storage management server be displayed on storage server SRC-SV.
# /opt/FJSVswsrp/bin/swsrpvolinfo -h SRC-SV Server Original-Volume Size Replica-Volume Size Copy Op-Server SRC-SV /dev/vg01@SRC-SV 4.0Gbyte /dev/vg01@TARG-SV 4.0Gbyte uni-direction original SRC-SV /dev/vg02@SRC-SV 4.0Gbyte /dev/vg02@TARG-SV 5.0Gbyte bi-direction original SRC-SV /dev/vg03@SRC-SV 9.1Gbyte /dev/vg03@TARG-SV 9.1Gbyte bi-direction replica SRC-SV /dev/vg04@SRC-SV 7.5Gbyte /dev/vg04@TARG-SV 7.5Gbyte bi-direction both # |
The following information will be displayed.
|
Title |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Original-Volume |
Displays a replication source volume name. |
|
Size |
Displays the volume size. Also in case a volume group, displays the physical disk size from which a logic disk is constituted. |
|
Replica-Volume |
Displays a replication destination volume name. |
|
Copy |
Displays the copying direction. uni-direction: One-way copying from a replication source volume to a replication destination volume is allowed. bi-direction: Bidirectional copying is allowed. |
|
Op-Server |
Displays the operation server of a pair of replication volumes. original: The replication source server is the operation server. replica: The replication destination server is the operation server. both: Sets both the copy-source server and copy-destination server as operation servers. |
|
Group [only if the -L option has been specified] |
Displays the group name. "----"is displayed if the copy source and destination volumes are not registered in a group. |
Replication volume information cannot be displayed if:
The specified volume is not set as a replication source volume
This command cannot be executed while the following command is running:
Resource adjustment command (swsrprecoverres)
Delete the replication volume information that has been set.
If copy processing is being performed on a replication volume that is to be deleted, execute the command after the copy processing has stopped.
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrpdelvol [-e] Original-Volume-Name Replica-Volume-Name [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrpdelvol -h Server-Name [-e] Original-Volume-Name Replica-Volume-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option is valid only on a storage management server. |
|
-e |
Emergency operation mode is available for operations. Specifies deleting replica volume information, without checking the execution state of an advanced copy. Use this option, only when it is clear that the advanced copy is not executed. |
|
-d |
Specifies that no communication take place between the linked servers in replication between servers. When this option is specified, replication volume information is deleted without communication taking place between the linked servers. Use the option only when recovery of one of the linked servers cannot be expected. The option is valid only for replication between servers. The option can be used on the server not specified as the operation server. |
Description of Operand
|
Operand |
Description |
|---|---|
|
Original-Volume-Name |
Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." |
|
Replica-Volume-Name |
Specifies a replication destination volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Delete replication volume information on storage server SRC-SV.
# /opt/FJSVswsrp/bin/swsrpdelvol /dev/vg01 /dev/vg01@TARG-SV swsrpdelvol completed # |
Replication volume information cannot be deleted if:
The specified replication source volume and the replication destination volume are not set as replication volumes.
The copy processing (synchronization processing and snapshot processing) is performed between replication volumes.
For server-to-server replication, the storage server that executed the command is not the operation server of the replication volume.
Communication with a storage management server fails.
For server-to-server replication, communication with a destination server fails.
Changing into the logic disk composition which cannot be supported by AdvancedCopy Manager.
When logical volume is deleted, or when logical volume composition is changed into the composition which cannot be supported by AdvancedCopy Manager, replica volume information cannot be deleted. In this case, perform processing of (A) or (B) shown below.
(A):Specify -e option and execute this command, after checking that the advanced copy is not carried out in the replica volume to delete (when the advanced copy is carried out, stop an advanced copy with disk array equipment, or cope with (B)).
(B):Execute this command after re-creating logical volume in the composition which AdvancedCopy Manager can support or making logical volume composition the original state.
However, OPC sessions are neither confirmed nor cancelled by execution in emergency operation mode. If an OPC session is in the error suspended state or halt state, then unmanaged sessions remain. In this event, GRmgr or ETERNUSmgr must be used to cancel these sessions.
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Synchronous processing start command (swsrpstartsync)
Replication creation command (swsrpmake)
Replication cancellation command (swsrpcancel)
Syncronization mode change command (swsrpchsync)
Syncronisation reverse command (swsrprevsync)
Resource adjustment command (swsrprecoverres)
Displays information for the transfer buffer used by ETERNUS when REC is performed in Consistency mode.
Specification method
|
[To be executed on a storage server] swsrprecbuffstat [-Xaltpath] Volume-Name [To be executed on a storage management server] swsrprecbuffstat -h Server [-Xaltpath] Volume-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies the name of a storage server. |
|
-Xaltpath |
When replication volume is applying per logic volume by the SDX object, an /dev/sfdsk/(class name)/dsk/(volume name):( DEVNAM value for sdxinfo) |
Description of operands
|
Operand |
Description |
|---|---|
|
Volume-Name |
Specifies the name of a volume that has been registered as a replication volume. You can only specify volumes that are connected to the Storage server where the command is executed. Specify the AdvancedCopy Manager device name as the volume name. |
End status
=0:Normal end
>0:Abnormal end
Execution example
Display information for the transfer buffer used by the REC, where the copy source volume is /dev/hdisk10@Server1 and the copy destination volume is /dev/hdisk11@Server1, and replication is performed within the storage server "Server1":
# /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk10@Server1 BoxID = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ID Use Rate RemoteBoxID 1 SEND 12% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk11@Server1 BoxID = BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB ID Use Rate RemoteBoxID 1 RECV 0% AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA # |
Display information for the transfer buffer used by the REC in an environment where replication is being performed between storage server "Server1" and storage server "Server2". Additionally, the copy source volume is /dev/hdisk10@Server1 and the copy destination volume is /dev/hdisk20@Server2:
[Command executed on storage server "Server1"] # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk10@Server1 BoxID = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ID Use Rate RemoteBoxID 1 SEND 12% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB 2 RECV 0% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB # # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk20@Server2 BoxID = BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB ID Use Rate RemoteBoxID 1 RECV 0% AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 2 SEND 5% AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA # |
Display information for the transfer buffer used by the REC if a cabinet where the copy source volume /dev/hdisk10@Server1 resides has been set up to make remote copies to multiple cabinets, and replication is being performed between storage server "Server1" and storage server "Server2":
[Command executed on storage server "Server1"] # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk10@Server1 BoxID = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ID Use Rate RemoteBoxID 1 SEND 12% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB 2 RECV 0% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB 3 SEND 4% CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC 4 RECV 0% CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC 5 SEND 10% DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD 6 RECV 0% EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE 7 SEND 3% FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 8 SEND 5% GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG # |
The following information will be displayed.
|
Title |
Description |
|---|---|
|
BoxID |
The box identifier for the cabinet connected to the server where the command was executed. |
|
ID |
The ID for the transfer buffer. |
|
Use |
The attribute (usage) for the transfer buffer. SEND : Transfer buffer for sending data RECV : Transfer buffer for receiving data |
|
Rate |
The usage rate of the transfer buffer as a percentage. If the usage is SEND: Displays the usage rate of the transfer buffer as a percentage.This will never be 0%, even if REC is not being performed in asynchronous Consistency mode. "----" will be displayed if the transfer buffer cannot be used. |
|
RemoteBoxID |
The box identifier for the cabinet performing a remote copy. |
The device name on a cabinet to display information can be specified as -Xaltpath.
Information is displayed only for cabinets that contain replication volumes for the server where the command was executed.
If intercabinet replication is being performed between servers, then the command must be executed on both servers involved in the replication in order to check information for the transfer buffers in both cabinets.
It will take a short period for changes to REC transfer buffer settings to take effect, during which time the buffer may become unusable (the "Rate" field will be displayed as "----"). In this case, wait about one minute and then execute the command again.
This command cannot be executed while the following command is running:Resource adjustment command (swsrprecoverres)
Changes the settings for the transfer buffer used by ETERNUS when REC is performed in Consistency mode.
Refer to "ETERNUSmgr User's Guide Setup / Maintenance" about the setting method of REC transfer buffer.
Specification method
|
[To be executed on a storage server] swsrprecbuffset -Xbuffid buffer-id -Xbuffuse {SEND|RECV} [-Xaltpath] Volume-Name [To be executed on a storage management server] swsrprecbuffset -h Server -Xbuffid buffer-id -Xbuffuse {SEND|RECV} [-Xaltpath] Volume-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies the name of a storage server. |
|
-Xbuffid |
Specifies the ID for the transfer buffer. |
|
-Xbuffuse |
Specifies the usage for the transfer buffer. SEND : Transfer buffer for sending data |
|
-Xaltpath |
When replication volume is applying per logic volume by the SDX object, an /dev/sfdsk/(class name)/dsk/(volume name):(DEVNAM value for sdxinfo) |
Description of operands
|
Operand |
Description |
|---|---|
|
Volume-Name |
Specifies the name of a volume that has been registered as a replication volume. You can only specify volumes that are connected to the Storage server where the command is executed. When replication volume is applying per logic volume by the SDX object, it is necessary to use the -Xaltpath option and to specify an alternative path. |
End status
=0:Normal end
>0:Abnormal end
Execution example
Change the attributes for the transfer buffer used by the REC where the copy source volume is /dev/hdisk10@Server1 and the copy destination volume is /dev/hdisk11@Server1, and replication is being performed within the storage server "Server1":
# /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk10@Server1 BoxID = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ID Use Rate RemoteBoxID 1 SEND 12% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB # /opt/FJSVswsrp/bin/swsrpbuffset -Xbuffid 1 -Xbuffuse RECV /dev/hdisk10@Server1 swsrpbuffset completed # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk10@Server1 BoxID = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ID Use Rate RemoteBoxID 1 RECV 0% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk11@Server1 BoxID = BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB ID Use Rate RemoteBoxID 1 RECV 0% AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA # /opt/FJSVswsrp/bin/swsrpbuffset -Xbuffid 1 -Xbuffuse SEND /dev/hdisk11@Server1 swsrpbuffset completed # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk11@Server1 BoxID = BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB ID Use Rate RemoteBoxID 1 SEND 3% AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA # |
Change the attribute for the transfer buffer where the copy source volume is /dev/hdisk10@Server1, and replication is being performed between storage server "Server1" and storage server "Server2".
[Command executed on storage server "Server1"] # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk10@Server1 BoxID = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ID Use Rate RemoteBoxID 1 SEND 12% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB 2 RECV 0% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB # /opt/FJSVswsrp/bin/swsrpbuffset -Xbuffid 1 -Xbuffuse SEND /dev/hdisk11@Server1 swsrpbuffset completed # /opt/FJSVswsrp/bin/swsrpbuffset -Xbuffid 2 -Xbuffuse RECV /dev/hdisk11@Server1 swsrpbuffset completed # /opt/FJSVswsrp/bin/swsrprecbuffstat /dev/hdisk11@Server1 BoxID = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ID Use Rate RemoteBoxID 1 SEND 4% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB 2 RECV 0% BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB # |
The device name on a cabinet to display information can be specified as -Xaltpath.
Settings for dedicated REC buffers must be made in advance.
Change settings while there are no asynchronous Consistency mode sessions in either the ACTIVE or ERROR SUSPEND state.
It will take a short period for changes to buffer settings to take effect, during which time the transfer buffer will become unusable. Do not perform REC operations during this time.
This command cannot be executed while any of the following commands are running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Synchronous processing start command (swsrpstartsync)
Replication creation command (swsrpmake)
Operation status display command (swsrpstat)
Replication cancellation command (swsrpcancel)
Synchronization mode change command (swsrpchsync)
Synchronization reverse command (swsrprevsync)
Resource adjustment command (swsrprecoverres)
This chapter describes operation commands for replication management.
To operate replication management, use the following commands:
|
Function |
Command name |
Description |
|---|---|---|
|
swsrpstartsync |
Starts replication while the synchronous type replication function is performed. |
|
|
swsrpmake |
Creates replication while the snapshot type and the synchronous type replication functions are performed. |
|
|
swsrpstat |
Displays the status of replication operation |
|
|
swsrpcancel |
Cancels the replication processing while the snapshot type and the synchronous type replication functions are performed. |
Start the synchronous type replication processing (copying between disks by EC and REC).
Copy all the specified replication destination and replication source volumes (start of the synchronization processing), or copy (restart of the synchronization processing) updated data (difference). Use this command at the start of operation or when you want to reflect updated data (difference) from the equivalency holding state.
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrpstartsync [ -y [ -a | -v ] | -k | -i ] [-g] [-m] [ -Xskip | -Xremain ] [-t] From-Volume-Name To-Volume-Name [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrpstartsync -h Server-Name [ -y [ -a | -v ] | -k | -i ] [-g] [-m] [ -Xskip | -Xremain ] [-t] From-Volume-Name To-Volume-Name [if executed on a storage server: group specification] /opt/FJSVswsrp/bin/swsrpstartsync [ -y [ -a | -v ] | -k | -i ] [-g] [-m] [ -Xskip | -Xremain ] [-t] Group-Name [if executed on a storage management server: group specification] /opt/FJSVswsrp/bin/swsrpstartsync -h Server-Name [ -y [ -a | -v ] | -k | -i ] [-g] [-m] [ -Xskip | -Xremain ] [-t] Group-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
This option is valid only on a storage management server. This option can be specified only on a storage management server. |
|
-y |
Specifies synchronization in synchronous write mode. This option is valid only when total copy is started for inter-box replication. Not specifying the -y, -k, and -i option sets asynchronous write mode. Synchronization in intra-box replication is always handled in synchronous write mode. |
|
-a |
Specifies the start of split mode for inter-box synchronization in Automatic Split mode. This option is valid only when total copy is started for inter-box replication. Specify this option together with the -y option. Specifying the -y option without the -a option or -v option sets Automatic Split mode. |
|
-v |
Specifies the start of split mode for inter-box synchronization in Manual Split mode. This option is valid only when total copy is started for inter-box replication. Specify this option together with the -y option. Specifying the -y option without the -a option or -v option sets Automatic Split mode. You must specify this option when specifying synchronization mode (-y option) on a box that does not support Automatic Split mode. |
|
-k |
Specifies the setting of transfer mode for inter-box synchronization in Stack mode. This option is valid only when total copy is started for inter-box replication. Not specifying the -y, -k, or -i option sets asynchronous write mode. You cannot use this option when operating SDX objects in units of logical volumes. |
|
-i |
Specifies the setting of transfer mode for inter-box synchronization in Consistency mode. This option is valid only when total copy is started for inter-box replication. Not specifying the -y, -k, or -i option sets asynchronous write mode. |
|
-g |
Specifies the setting of recovery mode for inter-box synchronization in Manual Recovery mode. This option is valid only when total copy is started for inter-box replication. Not specifying this option sets Automatic Recovery mode. |
|
-m |
For server-to-server replication, specifies that communication processing with non-operation servers is not performed. When this option is specified, volume status check processing and the preprocessing for the replication destination volume of a non-operation server are not performed. This option is valid only during server-to-server replication. |
|
-t |
Specifies that preprocessing for the replication destination volume is not performed. Use this option only when AdvancedCopy Manager does not execute preprocessing and postprocessing of the copy destination volume and unique preprocessing and postprocessing scripts are inserted before and after, respectively, the AdvancedCopy Manager command, or when you judge that copy preprocessing and postprocessing are unnecessary (e.g., for a database constructed on a raw device). |
|
-Xreverse |
Specifies that synchronous processing be started for each group in the reverse direction (from replica volumes to original volumes). |
|
-Xskip |
Specifies that synchronous processing be suspended using the initial copy skip function. This option is valid only when total copy is started for inter-box replication. |
|
-Xremain |
Enables data that has been updated to the copy destination during replication established status when synchronous processing is restarted. This option is valid only when inter-box replication is restarted. This option is used to reflect to the copy destination volume only those parts of the copy source volume that have been updated, after synchronous processing has been started by specifying the -Xskip option and backup data has been copied from the tape medium to the copy destination volume. |
Description of operands
|
Operand |
Description |
|---|---|
|
From-Volume-Name |
Specifies a replication source volume name. Specifies the replication source volume or the replication destination volume set with the replication volume information setting command. |
|
To-Volume-Name |
Specifies a replication destination volume name. Specifies the replication source volume or the replication destination volume set with the copy volume information setting command. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Start replication from /dev/vg01 of a storage management server to /dev/vg01 @TARG-SV of storage server SRC-SV.
# /opt/FJSVswsrp/bin/swsrpstartsync -h SRC-SV /dev/vg01 /dev/vg01@TARG-SV FROM=/dev/vg01@SRC-SV,TO=/dev/vg01@TARG-SV swsrpstartsync completed # |
Start replication for group "GRP1".
# swsrpstartsync -Xgroup GRP1 GROUP=GRP1 swsrpstartsync completed # |
Replication cannot be started if:
The specified replication source volume and replication destination volume are not set as replication volumes.
A replication source volume is specified as the copy place volume and a replication destination volume is specified as the copied material volume, and one-way copy is set as the copy attribute of the replication volume.
Volume information (box identifier, OLU, EXTENT start position, and EXTENT size) is changed after operation starts. In this case, operation cannot continue for the corresponding volume. Stop the replication operation for the corresponding volume, and then delete and set the replication volume information.
For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume.
For server-to-server replication, communication with a destination server fails.
Replication cannot be started as a result of the preceding advanced copy function.
Changing into the logic disk composition which cannot be supported AdvancedCopy Manager.
When the backup management function or tape backup function uses a specified source/destination volume
Either the copy source volume or the copy destination volume is a Snap Data Volume.
If the -Xgroup option is specified, replication volumes are processed in order, but processing will be terminated immediately if an error occurs.
When the replication to perform corresponds to either of the following conditions, please perform drive character release or unmount of copy place volume before executing a command.
When a replication is performed between different OS's
When the sizes of replication source volume and replication destination volume differ
When the file systems of replication source volume and replication destination volume differ
When performing neither drive character release nor unmount in the above-mentioned case, post-processing of the copy place volume at the time of duplicate creation serves as an error.
You cannot change synchronization mode when synchronization is resumed.
When synchronization is resumed, you must specify the -y, -a, -v, -k, -i, and -g options as follows:
Specify only the options that match the mode of synchronization to be resumed, or
Do not specify any of the options.
The processing of this command varies according to the status of the synchronization processing of the specified replication source and replication destination volumes.
Status of synchronization processing
Processing
Unmount status
Start of total copy
Total or incremental copy status
Informational message (swsrp2401) is output and normally end
Equivalency maintain status
Informational message (swsrp2401) is output and normally end
Replication established status (halt status)
Start of incremental copy
Before starting the replication, run the replication preprocessing script for the replication destination volume. The contents of this script can be customized. For more information, see "Preprocessing and Postprocessing of Replication". If you do not want to implement the preprocessing script, use the -t option.
To protect processing that accesses a replication destination volume, set the copied material volume before starting replication so that other processes cannot access it. To do so, cancel the drive letter of the replication destination volume or execute unmount. If you cannot cancel the drive letter of the replication destination volume or execute unmount because of the situations described below, this command fails and terminates.
There is a directory in which other volumes are mounted under the mount point.
A file on the volume is being used. In addition, if the replication destination volume is being used from a server other than the server on which this command is entered, the replication-operation administrator must disable access to the replication destination volume by cancellation of the share setting, unmounting, or some other method.
When setting the volume group which consists of two or more logical disks as a original volume, and replicating it, make all logical devices unmount/mount on administrator responsibility.
Please understand "General notes" in this manual as a noted point when you start Synchronous processing start.
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Resource adjustment command (swsrprecoverres)
When synchronization processing (EC) is not performed, start snapshot processing (OPC) to create a replication volume.
When synchronization processing is performed, check whether the status of the processing is equivalency holding state. If the status is equivalency holding state, suspend the synchronization processing and create a replication volume. The status in which synchronization processing is suspended is referred to as the replication established status. After this command is executed, the replication volume (replication destination volume) can be accessed.
This command executes the replication preprocessing and postprocessing scripts before a replication is created. For details of these scripts, see "Preprocessing and Postprocessing of Replication".
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrpmake [-f] [-t] [-m] [-j|-T|-Xconcur|-C] [-Xgds-slice-skipchk] From-Volume-Name To-Volume-Name [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrpmake -h Server-Name [-f] [-t] [-m] [-j|-T|-Xconcur|-C] [-Xgds-slice-skipchk] From-Volume-Name To-Volume-Name [if executed on a storage server: group specification] /opt/FJSVswsrp/bin/swsrpmake [-f] [-t] [-m] [-j|-T|-Xconcur|-C] [-Xreverse] -Xgroup Group-Name [if executed on a storage management server: group specification] /opt/FJSVswsrp/bin/swsrpmake -h Server-Name [-f] [-t] [-m] [-j|-T|-Xconcur|-C] [-Xreverse] -Xgroup Group-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-m |
For server-to-server replication, specifies that communication processing with the non-operation server is not performed. When this option is specified, volume status check processing and preprocessing and post processing are not performed for the non-operation server volume. This option is valid only during server-to-server replication. |
|
-f |
Specifies that the preprocessing and post processing for a replication source volume are not performed. Use this option only when AdvancedCopy Manager does not execute preprocessing and postprocessing of the copy source volume and unique preprocessing and postprocessing scripts are inserted before and after, respectively, the AdvancedCopy Manager command, or when you judge that copy preprocessing and postprocessing are unnecessary (e.g., for a database constructed on a raw device). |
|
-t |
Specifies that the preprocessing and post processing for a replication destination volume are not performed. Use this option only when AdvancedCopy Manager does not execute preprocessing and postprocessing of the copy destination volume and unique preprocessing and postprocessing scripts are inserted before and after, respectively, the AdvancedCopy Manager command, or when you judge that copy preprocessing and postprocessing are unnecessary (e.g., for a database constructed on a raw device). |
|
-j |
Specifies that copy processing be forcibly suspended even if the execution status of copying is "sync: Total copy or incremental copy is being performed" or "halt: Hard suspend status" in synchronization processing of intercabinet replication. This option can be used only for intercabinet replication. If used for intracabinet replication, an error occurs. When this option is specified, the data in the destination volume is not guaranteed. Also, when this option is specified, preprocessing and postprocessing for the source and destination volumes are not performed. |
|
-T |
Specifies that differential snapshot processing be executed. This option cannot be specified while synchronous processing is performed. This option is valid only for a replication within a cabinet and when the disk array supports the QuickOPC function. For a snapshot replication without specifying this option, ordinary snapshot processing (OPC without using the QuickOPC function) is started. This option must be specified to perform the replication operation using differential snapshots. |
|
-Xgroup |
Specifies that operation statuses are displayed by the group. |
|
-Xreverse |
Specifies that a replication be created for each group in the reverse direction (from replica volumes to original volumes). |
|
-Xconcur |
Specifies that a replication be created using the concurrent suspension function. This option is not supported when GDS Snapshot linkage is being used. |
|
-C |
Specifies that a SnapOPC start. This option is only valid with intra-cabinet replications and for disk array devices that support the SnapOPC function. In order to execute a SnapOPC, the copy destination volume must be a Snap Data Volume. |
|
-Xgds-slice-skipchk |
Skips the SDX object status check processing that is usually performed as part of the copy source and copy destination preprocessing if SDX objects are operated in slice units. If this option is specified for a stopped volume, the -f option and the -t option must also be specified. |
Description of operands
|
Operand |
Description |
|---|---|
|
From-Volume-Name |
Specifies a replication source volume. Specifies the replication source volume or the replication destination volume that was set with the replication volume information setting command. |
|
To-Volume-Name |
Specifies a replication destination volume. Specifies the replication source volume or the replication destination volume that was set with the replication volume information setting command. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
The Storage management server instructs Storage server: SRC-SV to create a copy of /dev/vg01 in /dev/vg01@TARG-SV.
|
# /opt/FJSVswsrp/bin/swsrpmake -h SRC-SV /dev/vg01 /dev/vg01@TARG-SV |
Creates a copy for the group "GRP1".
|
# swsrpmake -Xgroup GRP1 |
Replication cannot be created if:
The specified replication source and replication destination volumes are not set as replication volumes.
The synchronization processing from the specified replication source volume to the replication destination volume is not in the equivalency maintain status.
After operation starts, physical volume information (box identifier, OLU, EXTENT start position, and EXTENT size) is changed. In this case, operation for the corresponding volume cannot continue. Stop the replication operation for the volume, and then delete and set the replication volume information.
A replication source volume or a replication destination volume has multiple mount points.
For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume.
For server-to-server replication, communication with a destination server fails.
Changing into the logic disk composition which cannot be supported AdvancedCopy Manager.
A volume group is in an un-active state in volume group specification.
When the backup management function or tape backup function uses a specified source/destination volume
If the -Xgroup option is specified, processing will be terminated without creating a copy if the operation statuses of the replication volumes being processed include both snapshot-type replication and synchronous-type replication.
Additionally, if the -Xgroup option is specified, replication volumes are processed in order, but processing will be terminated immediately if an error occurs.
When the replication to perform corresponds to either of the following conditions, please perform drive character release or unmount of copy place volume before executing a command.
When a replication is performed between different OS's
When the sizes of replication source volume and replication destination volume differ
When the file systems of replication source volume and replication destination volume differ
When performing neither drive character release nor unmount in the above-mentioned case, post-processing of the copy place volume at the time of duplicate creation serves as an error.
In the operation mode involving activation of the replica volume group, the post-processing script for the replica volume may take longer for command processing because the LVM management information is rewritten (recreatevg).
Before a replication is created, the replication preprocessing and postprocessing scripts for the replication source volume are executed (for synchronized replication, only preprocessing script is executed). After the replication has been created, the replication postprocessing script for the replication source volume and replication destination volume is executed. The contents of the script can be customized. For more information, see "Preprocessing and Postprocessing of Replication" If you do not want to implement the preprocessing and postprocessing scripts, use the -f option and the -t option.
If this command is executed during execution of snapshot processing, stop the copy processing in progress and start the snapshot processing again.
To protect the data, set the replication source volume before creating a replication so that other processes cannot access the volume. To do so, cancel the drive letter of the replication source volume or execute unmount. If you cannot cancel the drive letter of the replication source volume or execute unmount because of the situations described below, this command fails and terminates.
There is a directory in which other volumes are mounted under the mount point.
A file on the volume is being used. In addition, if the replication source volume is being used from a server other than the server on which this command is entered, the backup-operation administrator must disable access to the replication source volume by cancellation of the share setting, unmounting, or some other method. If for whatever reason you do not want to remove the share setting of the replication source volume or execute unmount or some other method, see "Preprocessing and Postprocessing of Replication" and note the following.
When setting the volume group which consists of two or more logical disks as a original volume, and replicating it, make all logical devices unmount/mount on administrator responsibility.
When the replication source volume is being used by backup management, unmount may not possible. If so, "swsrp2613 An error occurred on the preprocessing script at replication creation. Error code = 2" is output.
For replication preprocessing, execute the UNIX sync command to synchronize volumes and the file system.
In replication post-processing, execute the fsck command to check the file system at the copy destination.
For Snap Data Volumes, only SnapOPCs can be executed and OPCs and QuickOPCs cannot be executed.
Additionally, when data is restored from a Snap Data Volume, there must be a SnapOPC session between the copy source volume and the copy destination volume (the Snap Data Volume).
Please understand "General notes" in this manual as a noted point when you do to Replication creation.
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Resource adjustment command (swsrprecoverres)
If this command is executed during snapshot processing, snapshot processing is newly started. See the following table for details of copy operation:
|
Operation status |
-T option specification |
Copy operation |
|---|---|---|
|
Copy is not executed. |
No |
Ordinary snapshot processing is started. |
|
Copy is not executed. |
Yes |
Differential snapshot processing is started. |
|
Snapshot processing is in progress |
No |
Copying in progress is terminated and ordinary snapshot processing is newly started. |
|
Snapshot processing is in progress |
Yes |
Copying in progress is terminated and differential snapshot processing is newly started. |
|
Snapshot processing is in progress |
No |
Copying in progress is terminated and ordinary snapshot processing is newly started. |
|
Snapshot processing is in progress |
Yes |
Differential snapshot processing is restarted. |
|
Tracking is in progress. |
No |
Tracking processing is terminated and ordinary snapshot processing is newly started. |
|
Tracking is in progress. |
Yes |
Differential snapshot processing is restarted. |
This command displays the operation status of the specified volume. If a volume is not specified, the operation status of each replication volumes is displayed.
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrpstat [-L] [-E] [-H] [Original-Volume-Name] [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrpstat -h Server-Name [-L] [-E] [-H] [Original-Volume-Name] [if executed on a storage server: group specification] /opt/FJSVswsrp/bin/swsrpstat [-L] [-E] -Xgroup Group-Name [if executed on a storage management server: group specification] /opt/FJSVswsrp/bin/swsrpstat -h Server-Name [-L] [-E] -Xgroup Group-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-L |
Specifies display in extension format. For the items displayed by this option, see the table of the execution example. Note that the items displayed by this option may be subject to change in a future release. |
|
-E |
An option which when set will display the operational status in the opposite direction only(from the copy destination to the copy source). In case this option is not set, the operation status in the normal direction (from the copy source to the copy destination) will always be displayed when a bi-directional OPC physical copy is taking place. In case this option is set, the operational status in the normal direction will not be displayed. Only the operational status in the opposite direction will be displayed. This option can be used to check the operational status of an OPC session performed in an opposite direction in case a QuickOPC session in the normal direction exists. |
|
-Xgroup |
Specifies that operation statuses are displayed by the group. In case this option is set, all the operational statuses about the specified group will be displayed. |
|
-H |
Changes the Status field display method used when a REC enters a hard suspend (HALT) status. If this option is specified, then "halt(sync)" will be displayed when hard-suspend status occurs during a total copy or a differential copy. "halt(equivalent)" will be displayed when hard-suspend status occurs during an equivalency maintenance state. Note that hard-suspend status will still be displayed as "halt" even if this option is specified for ROPC. |
Description of operands
|
Operand |
Description |
|---|---|
|
Original-Volume-Name |
Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Displays all operation statuses for the specified replication source volume. If this operand is omitted, all the operation statuses of the storage server on which this command is executed are displayed. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Direct that all the replication operation statuses for storage server SRC-SV be displayed on the storage management server.
#swsrpstat -h SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV /dev/vg01@SRC-SV /dev/vg01@TARG-SV regular replicated ---- SRC-SV /dev/vg02@SRC-SV /dev/vg02@TARG-SV ---- ---- ---- SRC-SV /dev/vg02@SRC-SV /dev/vg03@TARG-SV reverse snap 45% # |
From storage management server to storage server: Instruct SRC-SV to display the status of all replication operations (with the -L option specified).
#swsrpstat -h SRC-SV -L Server Original-Volume Replica-Volume Direction Status Execute Trk Update Rcv Split Xfer SRC-SV /dev/vg01@SRC-SV /dev/vg01@TARG-SV regular replicated ---- ---- ---- auto ---- async SRC-SV /dev/vg02@SRC-SV /dev/vg02@TARG-SV ---- ---- ---- on 6% ---- ---- ---- SRC-SV /dev/vg02@SRC-SV /dev/vg03@TARG-SV reverse snap 45% off ---- ---- ---- ---- # |
The following information will be displayed.
|
Title |
Description |
|---|---|
|
Server |
Displays a storage server name. |
|
Original-Volume |
Displays a replication source volume name. |
|
Replica-Volume |
Displays a replication destination volume name. |
|
Direction |
Displays the copy direction.
|
|
Status |
Displays the progress.
|
|
Execute |
Displays the copy progress rate as a percentage. "----" is displayed during SnapOPC or when no copying is being performed. |
|
Trk |
Displays whether tracking processing is in progress. on : Tracking processing is in progress. off : Tracking processing is in progress. ----: Snapshot processing is not performed. Always displays "----" when the GDS Snapshot linkage function is enabled. |
|
Update |
Displays the percentage of data that has been updated since the last copy was created, in the following cases:
In all other cases, "----" is displayed. |
|
Rcv |
Indicates recovery mode for inter-box synchronization. auto: Automatic Recovery mode. manual: Manual Recovery mode. ----: Synchronous duplication (REC) is not performed between boxes. |
|
Split |
Indicates split mode for inter-box synchronization. auto: Automatic Split mode. manual: Manual Split mode. ----: Synchronous duplication (REC) is not performed between boxes. |
|
Xfer |
Indicates transfer mode in inter-box synchronization. sync: Synchronous mode. async: Asynchronous mode. stack: Stack mode. consist: Consistency mode. ----: Synchronous duplication (REC) is not performed between boxes. |
When the execution status (status displayed in the Status field) is one of the following, take appropriate action.
Status display
Corrective action
failed
A hardware error may have occurred. Correct the hardware error, and then use the replication cancellation command to stop operation.
halt
A hardware error during replication operation between cabinets may occur. Correct the hardware error, and then use the replication cancellation command to stop the copy operation.
?????
Copy situation cannot be acquired. A hardware error may have occurred if the result is the same after reexecution. Correct the hardware error, and then reexecute the command.
The operation status cannot be displayed if:
The volumes are not set as replication volumes.
Changing into the logic disk composition which cannot be supported AdvancedCopy Manager.
This command cannot be executed while the following command is running:
Resource adjustment command (swsrprecoverres)
This command stops snapshot processing (OPC) and synchronization processing (EC) of the specified replication volume. Use this command when an error is detected during the replication operation and when you want to stop replication processing.
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrpcancel [-c] ([-f] [-t] [-m] [-b])|[-T] [-Xgds-slice-skipchk] From-Volume-Name To-Volume-Name [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrpcancel -h Server-Name [-c] ([-f] [-t] [-Xgds-slice-skipchk] [-m] [-b])|[-T] From-Volume-Name To-Volume-Name [if executed on a storage management server: group specification] /opt/FJSVswsrp/bin/swsrpcancel -h Server-Name [-c] ([-f] [-t] [-m] [-b])|[-T] [-Xreverse] -Xgroup Group-Name [if executed on a storage management server: group specification] /opt/FJSVswsrp/bin/swsrpcancel -h Server-Name [-c] ([-f] [-t] [-m] [-b])|[-T] [-Xreverse] -Xgroup Group-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be specified only on a storage management server. |
|
-c |
Specifies that copy processing be canceled from servers other than the operation server if the operation server becomes unavailable (due to system failure, etc). If this option is used, copy processing is stopped without executing preprocessing and postprocessing. This option cannot be specified on the operation server. |
|
-m |
For server-to-server replication, specifies that communication processing with non-operation servers is not performed. When this option is specified, volume status check processing and preprocessing and postprocessing for the replication destination volume of a non-operation server are not performed. This option is valid only during server-to-server replication. |
|
-f |
When stopping the synchronous processing under the equivalency maintain status, specify that preprocessing and postprocessing for the copy source volume not be executed. Use this option only when AdvancedCopy Manager does not execute preprocessing and postprocessing of the copy source volume and unique preprocessing and postprocessing scripts are inserted before and after, respectively, the AdvancedCopy Manager command, or when you judge that copy preprocessing and postprocessing are unnecessary (e.g., for a database constructed on a raw device). |
|
-t |
When stopping the synchronous processing under the equivalency maintain status, specify that postprocessing for the copy destination volume not be executed. Use this option only when AdvancedCopy Manager does not execute preprocessing and postprocessing of the copy destination volume and unique preprocessing and postprocessing scripts are inserted before and after, respectively, the AdvancedCopy Manager command, or when you judge that copy preprocessing and postprocessing are unnecessary (e.g., for a database constructed on a raw device). |
|
-b |
It is specified to stop the copy processing between cases in the state of HALT. The copy termination processing between cases is done to both cases for the replication in the server. The copy termination processing is done only to the case connected with the server which executes this command for the replication between servers. The copy processing must use it only when you cannot expect the restoration in the state of HALT. When the copy processing is only HALT, this option can be used. This option can be used also with non-operation server. If this option is specified together with the -Xgroup option, copy processing is only stopped for sessions in the group whose status is HALT. |
|
-T |
Specifies that differential snapshot processing be terminated. This option terminates only tracking processing but does not terminate snapshot processing (OPC physical copying) in progress. This option releases the OPC session if snapshot processing (OPC physical copying) is complete. This option can be used only while physical copying or tracking is in progress. This option cannot be used for the logical volume of an SDX object. If this option is specified together with the -Xgroup option, only tracking processing within the group is stopped. |
|
-Xgroup |
Specifies that copy processing be stopped for each group. |
|
-Xreverse |
Specifies that copy processing that is being executed in the reverse direction (from replica volumes to original volumes) be stopped. |
|
-Xgds-slice-skipchk |
Skips the SDX object status check processing that is usually performed as part of the copy source and copy destination preprocessing. This takes place if SDX objects are operated in slice units and the synchronization processing for equivalency maintenance state is stopped. If this option is specified for a stopped volume, the -f option and the -t option must also be specified. |
Description of operands
|
Operand |
Description |
|---|---|
|
From-Volume-Name |
Specifies a copysource volume name. Specifies the replication source volume or the replication destination volume set with the replication volume information setting command. |
|
To-Volume-Name |
Specifies a copydestination volume name. Specifies the replication source volume or the replication destination volume set with the copy volume information set command. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
On the storage management server, direct that copying from /dev/vg01 to /dev/vg01@TARG-SV is stopped for storage server SRC-SV.
#/opt/FJSVswsrp/bin/swsrpcancel -h SRC-SV /dev/vg01 /dev/vg01@TARG-SV FROM=/dev/vg01@SRC-SV,TO=/dev/vg01@TARG-SV swsrpcancel completed # |
Stops copy processing for group "GRP1".
# swsrpcancel -Xgroup GRP1 GROUP=GRP1 swsrpcancel completed # |
This command ends normally if succeeding in the copy termination processing of the case either specification or the execution of b option by the replication in the server.
Copy processing cannot be performed if:
The specified replication source volume and replication destination volume are not set as replication volumes.
The copy processing is not performed for the specified replication source and replication destination volumes.
For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume.
For server-to-server replication, communication with a destination server fails.
Changing into the logic disk composition which cannot be supported AdvancedCopy Manager.
When the backup management function or tape backup function uses a specified source/destination volume
If the -Xgroup option is specified, processing will be performed for each active replication volume, but processing will be terminated without canceling replication in the following case:
If no replication volumes have been copied
When you execute -b option specifying it to no existence of the copy processing in the state of HALT in the group.
When you execute -T option specifying it to no existence of the tracking processing of QuickOPC in the group.
Additionally, if the -Xgroup option is specified, replication volumes are processed in order, but processing will be terminated immediately if an error occurs.
In the operation mode involving activation of the replica volume group, the post-processing script for the replica volume may take longer for command processing because the LVM management information is rewritten (recreatevg).
The volume information for the specified volume is not checked (check for matching of the volume information in the management list and the actual physical information). Operation is canceled unconditionally using the volume information in the management list.
The following processing is performed depending on the operation status of the specified replication source volume and replication destination volume.
Operation status
Processing
Reverse copy direction
Suspends the processing.
Not operating yet
Suspends the processing.
Total or incremental copy is performed
Suspends synchronization processing. The replication destination volume cannot be used.
Equivalency maintain status
Suspends synchronization processing. The replication destination volume can be used as a copy
Replication established status
Suspends synchronization processing. The replication destination volume can be used as a copy
Snapshot processing is being performed
Stops the snapshot processing. The replication destination volume cannot be used.
Preprocessing and postprocessing for a replication source and replication destination volumes are performed only when the status of synchronization processing is equivalency maintain.
If replication is canceled before the equivalency maintain status is achieved, the replica volume is placed in the incomplete state and, in the case of a file system, the replica volume cannot be mounted.
If the processing target is a volume group, the operation may be customized so that the pre-processing and post-processing scripts for the replica volume are used to mount and unmount the volume. If replication is canceled before the equivalency maintain state is achieved under these conditions, take action as follows:
To start synchronous processing
Execute the replication command (swsrpstartsync) with the -t option specified.
To execute replication
Execute the replication command (swsrpmake) with the -t option specified. After replication is completed, mount the replica volume.
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Resource adjustment command (swsrprecoverres)
When the -T option is not specified, command processing varies depending on the operation status of the source and destination volumes.
|
Operation status |
Processing |
|---|---|
|
Reverse copy |
Processing is interrupted. |
|
Not in operation |
Processing is interrupted. |
|
Total or difference copying is in progress. |
Synchronous processing is terminated. The destination volume cannot be used. |
|
Equivalency maintain status |
Synchronous processing is terminated. The destination volume can be used as a replica. |
|
Replica created status |
Synchronous processing is terminated. The destination volume can be used as a replica. |
|
Snapshot processing is in progress. |
Synchronous processing is terminated. The destination volume cannot be used. Tracking processing, if in progress, is also terminated. |
|
Snapshot processing complete status |
Tracking processing is terminated. The destination volume can be used as a replica. |
When the -T option is specified, command processing varies depending on the operation status of the source and destination volumes.
|
Operation status |
Processing |
|---|---|
|
Reverse copy |
Processing is interrupted. |
|
Not in operation |
Processing is interrupted. |
|
Total or difference copying is in progress. |
Processing is interrupted. |
|
Equivalency maintain status |
Processing is interrupted. |
|
Replica created status |
Processing is interrupted. |
|
Snapshot processing is in progress |
Processing is interrupted. |
|
Snapshot processing is in progress |
Only tracking processing is terminated. Snapshot processing (physical copying) is continued. The destination volume can be used as a replica. |
|
Snapshot processing complete status |
Tracking processing is terminated. The destination volume can be used as a replica. |
This command changes the operation mode of inter-box synchronization (transfer mode, recovery mode, or split mode).
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrpchsync [-F (Sync|Async|Stack|Consist)] [-R (Auto|Manual)] [-S (Auto|Manual)] From-Volume-Name To-Volume-Name [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrpchsync -h Server-Name [-F (Sync|Async|Stack|Consist)] [-R (Auto|Manual)] [-S (Auto|Manual)] From-Volume-Name To-Volume-Name [if executed on a storage server: group specification] /opt/FJSVswsrp/bin/swsrpchsync [-F (Sync|Async|Stack|Consist)] [-R (Auto|Manual)] [-S (Auto|Manual)] [-Xreverse] -Xgroup Group-Name [if executed on a storage management server: group specification] /opt/FJSVswsrp/bin/swsrpchsync -h Server-Name [-F (Sync|Async|Stack|Consist)] [-R (Auto|Manual)] [-S (Auto|Manual)] [-Xreverse] -Xgroup Group-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies the name of a storage server. You can use this option only for a storage management server. |
|
-F |
Changes the transfer mode. You can specify one of the following parameters in the operand: Sync: Changes to Synchronous mode. Async: Changes to Asynchronous (sequential transfer) mode. Stack: Changes to Stack mode. Consist: Changes to Consistency mode. Changing the transfer mode requires this option. You can only specify the -S option together with the -F Sync option. Specifying the -F Sync option to change the transfer mode from a non-synchronous mode to the synchronous mode without specifying the -S option sets the automatic split mode. |
|
-R |
Changes the recovery mode. You can specify either of the following parameters in the operand: Auto: Changes to Automatic Recovery mode. Manual: Changes to Manual Recovery mode. Changing the recovery mode requires this option. |
|
-S |
Changes the split mode. You can specify either of the following parameters in the operand: Auto: Changes to Automatic Split mode. Manual: Changes to Manual Split mode. Changing the split mode requires this option. To specify this option, you must also specify -F Sync or the transfer mode of the current synchronization must be synchronous mode. |
|
-Xgroup |
Changes the operation mode of inter-box synchronous processing for each group (transfer mode, recovery mode, or split mode). |
|
-Xreverse |
Specifies that the operation mode of synchronous processing that is being executed in reverse direction (from replica volumes to original volumes) be changed. |
Description of operands
|
Operand |
Description |
|---|---|
|
From-Volume-Name |
Specifies the name of a source volume. Specify the original volume or replica volume configured by the replication volume information set command. |
|
To-Volume-Name |
Specifies the name of a destination volume. Specify the original volume or replica volume configured by the replication volume information set command. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
From storage management server to storage server: Instruct SRC-SV to change the transfer mode for inter-box synchronization between /dev/vg03@SRC-SV and /dev/vg03@TARG-SV from Consistency mode to Asynchronous mode.
#/opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -L /dev/vg03@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute Trk Rcv Split Xfer SRC-SV /dev/vg03@SRC-SV /dev/vg03@TARG-SV regular sync 99% ---- auto ---- consist : #/opt/FJSVswsrp/bin/swsrpchsync -h SRC-SV -F Async /dev/vg03@SRC-SV /dev/vg03@TARG-SV FROM=/dev/vg03@SRC-SV, TO=/dev/vg03@TARG-SV swsrpchsync completed : #/opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -L /dev/vg03@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute Trk Rcv Split Xfer SRC-SV /dev/vg03@SRC-SV /dev/vg03@TARG-SV regular equivalent 100% ---- auto ---- async # |
Specify that the transfer mode of inter-box synchronous processing for group "GRP1" be changed from consistency mode to asynchronous mode.
# swsrpchsync -F Async -Xgroup GRP1 GROUP=GRP1 swsrpchsync completed # |
In any of the following cases, you cannot change the operation mode of inter-box synchronization:
The specified original/replica volume has not been configured as a replica volume.
None of the -F, -R, and -S options are specified.
In inter-server replication, the storage server on which you execute the command is not the operation server for the replica volume.
Synchronization from the specified source volume to the destination volume is not secured.
Synchronization from the specified source volume to the destination volume is in error-suspended status (with "failed" indicated for Status by the operating status display command) or hard-suspended status (with "halt" indicated for Status by the operating status display command).
The disk array in which the specified original/replica volume is placed does not support the operation mode change function.
A change is made to a logical disk configuration that AdvancedCopy Manager does not support.
The specified volume group is inactive.
If the -Xgroup option is specified, the synchronous processing for all replication volumes being processed is changed to the same operation mode. However, the operation mode cannot be changed if there is even one replication volume that meets the conditions above.
Additionally, if the -Xgroup option is specified, replication volumes are processed in order, but processing will be terminated immediately if an error occurs.
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Resource adjustment command (swsrprecoverres)
This command reverses the copying direction of inter-box synchronization (REC) in suspended status.
This command is unusable to handle an intra-box synchronization or a logical volume of an SDX object.
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrprevsync From-Volume-Name To-Volume-Name [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrprevsync -h Server-Name From-Volume-Name To-Volume-Name [if executed on a storage server: group specification] /opt/FJSVswsrp/bin/swsrprevsync [-Xreverse] -Xgroup Group-Name [if executed on a storage management server: group specification] /opt/FJSVswsrp/bin/swsrprevsync -h Server-Name [-Xreverse] -Xgroup Group-Name |
Description of options
|
Option |
Description |
|---|---|
|
-h |
Specifies the name of a storage server. You can only use this option for a storage management server. |
|
-Xgroup |
Changes the direction of inter-box synchronous processing for each group. |
|
-Xreverse |
Specifies that the direction of synchronous processing that is being executed in reverse direction (from replica volumes to original volumes) be inverted. |
Description of operands
|
Operand |
Description |
|
From-Volume-Name |
Specifies the name of a source volume (as the destination in the reverse direction). Specify the original volume or replica volume configured by the replication volume information set command. |
|
To-Volume-Name |
Specifies the name of a destination volume (as the source in the reverse direction). Specify the original volume or replica volume configured by the replication volume information set command. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
From storage management server to storage server: Instruct SRC-SV to reverse the copying direction of inter-box synchronization between /dev/vg03@SRC-SV and /dev/vg03@TARG-SV.
#/opt/FJSVswsrp/bin/swsrpstat -h SRC-SV /dev/vg03@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV /dev/vg03@SRC-SV /dev/vg03@TARG-SV reverse replicated ---- #/opt/FJSVswsrp/bin/swsrprevsync /dev/vg03@TARG-SV /dev/vg03@SRC-SV FROM=/dev/vg03@SRC-SV,TO=/dev/vg03@TARG-SV swsrprevsync completed #/opt/FJSVswsrp/bin/swsrpstat /dev/vg03@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV /dev/vg03@SRC-SV /dev/vg03@TARG-SV regular replicated ---- # |
Change the direction of inter-box synchronous processing for group "GRP1".
# swsrprevsync -Xgroup GRP1 GROUP=GRP1 swsrprevsync completed # |
In any of the following cases, you cannot reverse the direction of synchronization:
The specified original/replica volume has not been configured as a replica volume.
Unidirectional copying has been specified in the copying attribute for the replica volume.
In inter-server replication, the storage server on which you execute the command is not the operation server for the replica volume.
Replication has not been established in synchronization from the specified source volume to the destination volume.
The disk array in which the specified original/replica volume is placed does not support the REC reverse function.
A change is made to a logical disk configuration that AdvancedCopy Manager does not support.
The specified volume group is inactive.
If the -Xgroup option is specified, the direction of synchronous processing for all replication volumes being processed is changed. However, the direction of synchronous processing cannot be changed if there is even one replication volume that meets the conditions above.
Additionally, if the -Xgroup option is specified, replication volumes are processed in order, but processing will be terminated immediately if an error occurs.
If the -Xgroup option is specified, processing is not performed for those sessions in the group where the direction has already been changed.
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information deletion command (swsrpdelvol)
Resource adjustment command (swsrprecoverres)
This chapter describes the maintenance commands for replication management.
Use the following maintenance commands for replication management.
|
Function |
Command name |
Description |
|---|---|---|
|
swsrprecoverres |
Restores the consistency of information in a replication management files. |
This command executes recovery to make replication management information consistent if a system failure or other problem has made the replication management information inconsistent.
Specification method
|
[To be executed on a storage server] /opt/FJSVswsrp/bin/swsrprecoverres [-r] [-p] [To be executed on a storage management server] /opt/FJSVswsrp/bin/swsrprecoverres -h Server-Name [-r] [-p] |
Description of operands
|
Operand |
Description |
|---|---|
|
-h |
Specifies a storage server name. This option can be used only on a storage management server. |
|
-r |
Specify this option when an incorrect status exists in the replication management files (for example, the replication volume information setting command or the replication volume information deletion command that update the replication management files terminate suddenly because of a forced stop or a system failure, or the replication management files has been deleted by mistake). When this option is specified, the following processing to re-create the replication management files is performed. Replication management information in the storage management server repository is downloaded to the storage server, and the replication volume information is restored. The disk array device is queried, and the execution information for the synchronization processing is restored. |
|
-p |
Specifies not to perform any postprocessing that has not been performed. This option can be used when the replication creation command processing terminates suddenly because of a forced stop or system failure. |
End status
= 0: Normal end
> 0: Abnormal end
Execution example
Perform resource adjustment.
#/opt/FJSVswsrp/bin/swsrprecoverres swsrprecoverres completed # |
The resource adjustment processing cannot be performed if:
Communication with a storage management server fails and the -r option is specified.
The -r option is not specified when this command is executed after processing by the replication volume information setting command and the replication volume information deletion command has been forcibly terminated.
When specifying -r option, and corresponding to the following conditions, this command terminates with an error.
Changing into the logic disk composition which cannot be supported AdvancedCopy Manager.
The consistency of resource information is restored only for the storage server on which this command is executed. When a resource inconsistency occurs during processing related to replication between servers, this command must be executed both on the storage server on which the processing was performed and on the storage server with which communication is being made.
This command cannot be executed while any of the following commands is running:
Replication volume information setting command (swsrpsetvol)
Replication volume information display command (swsrpvolinfo)
Replication volume information deletion command (swsrpdelvol)
Synchronous processing start command (swsrpstartsync)
Replication creation command (swsrpmake)
Replication status display command (swsrpstat)
Replication cancellation command (swsrpcancel)
Syncronization mode change command (swsrpchsync)
Syncronisation reverse command (swsrprevsync)
Resource adjustment command (swsrprecoverres)
AdvancedCopy Manager daemons can be started in the ways explained in this chapter.
A note on this command is as follows:
Please confirm environment variable SWSTGNODE is not set.
Execute this command using the same LANG environment variable that of the code system used by the system.
Only a root user can execute this command.
For cluster operation, refer to "Starting and Stopping Daemons"
Starting the communication daemon
Enter the following command to stop the communication daemon:
|
# /opt/FJSVswstf/bin/stgfwcom start |
Stopping the communication daemon
Enter the following command to stop the communication daemon:
|
# /opt/FJSVswstf/bin/stgfwcom stop |
The daemons listed below are started and stopped together:
|
Server type |
Storage server |
|
Daemon name |
Communication daemon |
* For details on how to start a daemon of a storage management server, see the operator's guide of the storage management server intended for the target OS.
Starting a AdvancedCopy Manager daemon
Enter the following command to start a AdvancedCopy Manager daemon:
|
# /opt/swstorage/bin/startacm |
Stopping a AdvancedCopy Manager daemon
Enter the following command to stop a AdvancedCopy Manager daemon:
|
# /opt/swstorage/bin/stopacm |
This section explains the commands that execute SnapOPC.
Operating environment for command execution
The table below lists the requirements for the operating environment in which to execute the respective commands.
Command
Operating environment of AdvancedCopy Manager
swstestupdate
-
In cluster operation
In cluster operation, execute a command by taking the following steps:
If necessary, specify the logical node name to the transaction in environment variable SWSTGNODE. For bsh, specify the environment variable as follows:
Execute the command.
The table below lists the commands available in cluster operation, whether environment variables must be configured, and the nodes on which commands are executable. For notes and cautions on command execution, see the Remarks column.
Command
Environment variable
Command execution node
Remarks
swstestupdate
Required
Transaction operation node
-
This command measures the physical capacity of Snap Data Disks using the pseudo SnapOPC session setup function.
Specification method
|
[When starting update volume measurements (setting up a pseudo SnapOPC session)] /opt/FJSVswsrp/bin/swstestupdate start Volume-Name [When looking up the update volume (displaying the status of the pseudo SnapOPC session)] /opt/FJSVswsrp/bin/swstestupdate status Volume-Name [When finishing update volume measurements (canceling the pseudo SnapOPC session)] /opt/FJSVswsrp/bin/swstestupdate stop Volume-Name |
Description of operands
|
Operand |
Description |
|
Volume-Name |
Specifies the volume name. Specify a copy source volume that is used with SnapOPC operations. GDS logical volumes cannot be specified. |
End status
= 0 : Normal end
> 0 : Abnormal end
Execution example
Measure the update volume for /dev/hdisk10:
(Start taking measurements by starting a pseudo SnapOPC) #/opt/FJSVswsts/bin/swstestupdate start /dev/hdisk10 /dev/hdisk10 swstestupdate completed (First measurement) #/opt/FJSVswsts/bin/swstestupdate status /dev/hdisk10 Volume-Name Update /dev/hdisk10 644333 (Second measurement) #/opt/FJSVswsts/bin/swstestupdate status /dev/hdisk10 Volume-Name Update /dev/hdisk10 1045000 (Stop taking measurements by canceling the pseudo SnapOPC) # /opt/FJSVswsts/bin/swstestupdate stop /dev/hdisk10 /dev/hdisk10 swstestupdate completed # |
The following information will be displayed:
|
Title |
Description |
|---|---|
|
Volume-Name |
Displays the volume name. |
|
Update |
Displays the amount of data (the number of blocks) that has been updated since measurements started (1 block = 512 bytes). Displays "----" if there is no pseudo SnapOPC session. Displays "failed" if the pseudo SnapOPC session is error-suspended. |
The amount of data updated cannot be measured in the following cases:
When the specified volume does not exist.
When the disk array device does not support the SnapOPC function.
When the pseudo session has already been set up (when the "start" option is specified).
When the pseudo session does not exist (when the "stop" option is specified).
|
Contents
Index
|