This section describes operation commands for replication management.
NAME
swsrpstartsync - starts synchronous processing
SYNOPSIS
/opt/FJSVswsrp/bin/swsrpstartsync [ [-y [-a | -v]| -k | -i] [-g] [-m] [-Xskip | -Xremain] | -Xgds-softcopy | -Xgds-selectcopy] [-t] [-Xda] [-Xgds-slice-skipchk] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpstartsync [-h Server-Name] [ [-y [-a | -v]| -k | -i] [-g] [-m] [-Xskip | -Xremain] | -Xgds-softcopy | -Xgds-selectcopy] [-t] [-Xda] [-Xgds-slice-skipchk] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpstartsync [-y [-a | -v]| -k | -i] [-g] [-m] [-Xskip | -Xremain] [-t] [-Xda] [-Xgds-slice-skipchk] [-Xreverse] -Xgroup groupName
/opt/FJSVswsrp/bin/swsrpstartsync [-h serverName] [-y [-a | -v]| -k | -i] [-g] [-m] [-Xskip | -Xremain] [-t] [-Xda] [-Xgds-slice-skipchk] [-Xreverse] -Xgroup groupName
DESCRIPTION
Start the synchronous replication processing (copying disks by EC or REC).
It copies all the data from the source volume to the destination volume at the start of the synchronization process, or if run as a restart of the synchronization process it just copies updated data to the destination volume. Use this command at the start of operation or when you want to reflect updated data (differences) from the equivalency maintenance state.
For a PRIMECLUSTER GD transaction volume, synchronous processing using a software copy is also possible.
If the Storage Cluster Continuous Copy function is used, the synchronous replication process is started on both the Primary Storage and Secondary Storage.
OPTIONS
When executing on the Management Server, specify the name of the target Managed Server.
When executing on the target Managed server, it is not necessary to specify this option.
When performing the server-to-server replication, specify the name of the operation server configured with the swsrpsetvol command.
For the server name, accurately specify the same letters, including upper and lower case, as the server name displayed with the stgxfwcmdispsrv command.
Specifies inter-box synchronization in synchronous mode. This option is valid only when total copy is started for inter-box replication.
Specify this option together with the -a option to start the split mode for inter-box synchronization in Automatic Split mode.
Specify this option together with the -v option to start the mode in Manual Split mode.
If both the -a and -v options are omitted, the mode starts in Automatic Split mode.
If the -y, -k, and -i options are omitted, the transfer mode for inter-box synchronization is set to Through mode.
Synchronization in intra-box replication is always handled in synchronous mode.
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.
You cannot use this option when operating SDX objects in units of logical volumes.
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.
You must specify this option when specifying synchronization mode (the -y option) on a box that does not support Automatic Split mode.
You cannot use this option when operating SDX objects in units of logical volumes.
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.
If the -y, -k, and -i options are omitted, the transfer mode for inter-box synchronization is set to Through mode.
You cannot use this option when operating SDX objects in units of logical volumes.
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.
If the -y, -k, and -i options are omitted, the transfer mode for inter-box synchronization is set to Through mode.
You cannot use this option when operating SDX objects in units of logical volumes.
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.
You cannot use this option when operating SDX objects in units of logical volumes.
For server-to-server replication, this option specifies that communication processing with non-operational servers is not performed. When this option is specified, volume status check processing and the pre-processing for the replication destination volume of a non-operational server are not performed.
This option is valid only during server-to-server replication.
Specifies that pre-processing for the replication destination volume is not performed.
Use this option if any of the following conditions apply:
AdvancedCopy Manager does not perform pre-processing or post-processing for the replication destination volume, and independent pre-processes and post-processes are inserted before and after AdvancedCopy Manager commands.(*)
Replication destination pre-processing and post-processing are judged to be unnecessary (for example, for databases constructed on RAW devices).(*)
Synchronous processing (REC) between boxes is restarted after a forcible suspend.
*: If you specify this option to start or resume synchronous processing, specify the -t option also when executing the swsrpmake command.
Specifies the start of synchronous processing of an SDX object and use of the software-copy function instead of the Advanced Copy function.
If you specify this option to start differential copying when the Advanced Copy function is being used, the Advanced Copy processing stops and software-copy processing starts.
You can specify the option when the function is used with PRIMECLUSTER GD Snapshot is being used.
The option is applicable only to SDX objects.
The option cannot be specified together with -y or -Xgds-selectcopy option.
Specifies the start of synchronous processing without a specified copy type, such as copying with the ETERNUS Disk storage system (OPC/EC) or software-copy. PRIMECLUSTER GD selects the type of copying to be started.
You can specify the option when the function in linkage with PRIMECLUSTER GD Snapshot is being used.
The option is applicable only to SDX objects.
The option cannot be specified together with -Xgds-softcopy option.
Specifies that synchronous processing must be started for each group.
Specifies that synchronous processing must be started for each group in the reverse direction (from replica volumes to original volumes).
This option is valid only when the -Xgroup option is specified.
Specifies that synchronous processing must be suspended using the initial copy skip function. This option is valid only when total copy is started for inter-box replication.
This option is not supported when PRIMECLUSTER GD Snapshot linkage is being used.
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 using the -Xskip option and backup data has been copied from the tape media to the copy destination volume.
This option is not supported when PRIMECLUSTER GD Snapshot linkage is being used.
Skips the SDX object status check processing that is usually performed as part of the copy destination pre-processing if SDX objects are operated in slice units.
If this option is specified for a stopped volume, the -t option must also be specified.
Disables update (WRITE) and access (READ) to the replication destination volume from the synchronous processing start until the replication has been completed.
This option is valid only when synchronous processing is started.
If the option is omitted, only update (WRITE) to the replication destination volume is disabled.
You cannot use this option when operating SDX objects in units of logical volumes.
OPERANDS
Specifies a replication source volume name.
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
Specifies a replication destination volume name.
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Starting replication from "/dev/dsk/c1t2d0s3" of a Management Server to "/dev/dsk/c1t2d0s3@TARG-SV" of Managed Server "SRC-SV":
# /opt/FJSVswsrp/bin/swsrpstartsync -h SRC-SV /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3@TARG-SV FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d0s3@TARG-SV swsrpstartsync completed #
Starting replication from "/dev/dsk/c1t2d0s3" of a Management Server to "/dev/dsk/c1t2d0s3@TARG-SV" of a Managed Server "SRC-SV" with replication destination volume access disabled.
# /opt/FJSVswsrp/bin/swsrpstartsync -h SRC-SV -Xda /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3@TARG-SV FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d0s3@TARG-SV swsrpstartsync completed #
Starting replication for group "GRP1":
# /opt/FJSVswsrp/bin/swsrpstartsync -Xgroup GRP1 GROUP=GRP1 swsrpstartsync completed #
NOTES
Replication cannot be started if:
The specified source volume and destination volume have not been set as replication volumes.
A replication source volume is specified as the copy 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, the operation cannot continue for the corresponding volume. Stop the replication operation for the corresponding volume, and then delete and reset the replication volume information.
For server-to-server replication, the Managed 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.
The -g option is specified, except for a remote copy.
When the original volume or replica volume is a logical volume of VxVM, the structure of the logical volume is changed to a structure not supported by AdvancedCopy Manager.
When the original volume or replica volume is a logical volume of VxVM, the logical volume is deleted from VxVM.
The -Xgds-softcopy or -Xgds-selectcopy option is specified when the function in linkage with PRIMECLUSTER GD Snapshot is not being used.
The -a, -v, -k, -i, or -g option is specified when the function in linkage with PRIMECLUSTER GD Snapshot is being used.
The backup management function is executing a process for 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 is terminated immediately if an error occurs.
When the replication to be performed satisfies either of the following two conditions, perform unmount of the copy target volume before executing a command.
When a replication is performed between different OSs
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
In the above mentioned cases, if dismount have been performed, post-processing of the copy target volume at the time of duplicate creation results in 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 |
|---|---|
Dismount status | Start of total copy |
Total or incremental copy status | Informational message (swsrp2401) is output and the command ends normally |
Equivalency maintain status | Informational message (swsrp2401) is output and the command ends normally |
Replication established status (i.e., halt status) | Start of incremental copy |
Before starting the replication, this command executes the replication pre-processing script for the replication destination volume. The contents of this script can be customized. For more information about this, refer to "Appendix C Pre-processing and Post-processing of Replication". If you do not want to implement the pre-processing script, use the -t option.
If replication is started with the -Xgroup option specified, the replication pre-processing script is not executed for the copy destination volume. Therefore, pre-processing must be executed for all copy destination volumes in the group before this command is executed.
Before starting replication that targets a Logical Unit (disk), execute pre-processing and post-processing of the Logical Unit (disk), refer to "Appendix C Pre-processing and Post-processing of Replication" for details.
To protect processing that accesses a replication destination volume, set the replication destination volume before starting replication so that other processes cannot access it. To do so, execute a dismount command. If you cannot execute dismount resulting from any of the conditions described below, this command fails and terminates.
There is a directory in which other volumes are mounted under the mount point.
A file in the volume is being used. In addition, if the replication destination volume is being used on 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 by some other method.
If the replication destination volume exists in a PRIMECLUSTER GFS local file system consisting of multiple devices (multi-partition), replication cannot be performed by using pre-processing and post-processing scripts to execute unmount/mount. In this case, manually unmount the PRIMECLUSTER GFS local file system before starting a replication and re-mount it after the replication has completed.
When the PRIMECLUSTER GFS local file system and AdvancedCopy Manager configurations are as follows:
# sfxinfo /dev/dsk/c1t3d10s1 ID special size mount Type 0 /dev/dsk/c1t3d10s1(800019) 25986 /mnt META 0 /dev/dsk/c1t3d10s1(800019) 105751 /mnt DATA 1 /dev/dsk/c1t3d15s3(800028) 5120 /mnt LOG 2 /dev/dsk/c1t3d16s3(800030) 131736 /mnt DATA Setting AdvancedCopy Manager # /opt/FJSVswsrp/bin/swsrpvolinfo Server Original-Volume Size Replica-Volume Size Copy Op-Server SV1 /dev/dsk/c1t3d10s1@SV1 128.0 Mbyte /dev/dsk/c1t3d20s1@SV1 128.0 Mbyte bi-direction original SV1 /dev/dsk/c1t3d15s3@SV1 5.0 Mbyte /dev/dsk/c1t3d25s3@SV1 5.0 Mbyte bi-direction original SV1 /dev/dsk/c1t3d16s3@SV1 128.0 Mbyte /dev/dsk/c1t3d26s3@SV1 128.0 Mbyte bi-direction original
Backup procedure (replication source volume: PRIMECLUSTER GFS local file system)
# /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d10s1 /dev/dsk/c1t3d20s1 FROM=/dev/dsk/c1t3d10s1@SV1,TO=/dev/dsk/c1t3d20s1 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d15s3 /dev/dsk/c1t3d25s3 FROM=/dev/dsk/c1t3d15s3@SV1,TO=/dev/dsk/c1t3d25s3 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d16s3 /dev/dsk/c1t3d26s3 FROM=/dev/dsk/c1t3d16s3@SV1,TO=/dev/dsk/c1t3d26s3 swsrpstartsync completed : :(Checking equivalence-held state) : # umount /mnt # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d10s1 /dev/dsk/c1t3d20s1 FROM=/dev/dsk/c1t3d10s1@SV1,TO=/dev/dsk/c1t3d20s1 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d15s3 /dev/dsk/c1t3d25s3 FROM=/dev/dsk/c1t3d15s3@SV1,TO=/dev/dsk/c1t3d25s3 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d16s3 /dev/dsk/c1t3d26s3 FROM=/dev/dsk/c1t3d16s3@SV1,TO=/dev/dsk/c1t3d26s3 swsrpmake completed # mount -F sfxfs /dev/dsk/c1t3d10s1 /mnt #
Restore procedure (replication destination volume: PRIMECLUSTER GFS local file system)
# umount /mnt # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d20s1 /dev/dsk/c1t3d10s1 FROM=/dev/dsk/c1t3d20s1@SV1,TO=/dev/dsk/c1t3d10s1 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d25s3 /dev/dsk/c1t3d15s3 FROM=/dev/dsk/c1t3d25s3@SV1,TO=/dev/dsk/c1t3d15s3 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d26s3 /dev/dsk/c1t3d16s3 FROM=/dev/dsk/c1t3d26s3@SV1,TO=/dev/dsk/c1t3d16s3 swsrpstartsync completed: :(Checking equivalence-held state) : # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d20s1 /dev/dsk/c1t3d10s1 FROM=/dev/dsk/c1t3d20s1@SV1,TO=/dev/dsk/c1t3d10s1 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d25s3 /dev/dsk/c1t3d15s3 FROM=/dev/dsk/c1t3d25s3@SV1,TO=/dev/dsk/c1t3d15s3 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d26s3 /dev/dsk/c1t3d16s3 FROM=/dev/dsk/c1t3d26s3@SV1,TO=/dev/dsk/c1t3d16s3 swsrpmake completed # mount -F sfxfs /dev/dsk/c1t3d10s1 /mnt #
When SDX objects of PRIMECLUSTER GD are used: Refer to "Configuration and Conditions of Unsupported SDX Objects" and "10.1.7 Notes on SDX Object Operations (Replication Management)".
Refer to "10.1.1 General Notes" for notes about starting replication.
An error occurs if the synchronous process is restarted with -Xda option. When changing the access permission for replication destination volume, first cancel the current replication processing with the swsrpcancel command and then re-execute this command.
This command terminates abnormally with the following error message if the -Xda option is set for an ETERNUS Disk storage system that does not support the Destination Access Permission function.
swsrp0719 EC cannot be run. Error=17(not support.)
This command cannot be executed while any of the following commands are running:
When the Storage Cluster Continuous Copy function is used:
When the status of the TFO group is "Normal", and synchronous processing cannot start on either the Primary Storage or Secondary Storage, the command may terminate abnormally. Check the cause of the error on both the Primary Storage and Secondary Storage to address the error message in the storage device where the error is occurring.
When the status of the TFO group is "Normal" and its phase is "Maintenance", or when the status of the TFO group is "Halt", the command starts synchronous processing on the storage that has an "Active" TFO status and terminates normally. However, synchronous processing could not be started on the storage that has a "Standby" TFO status. In this case, swsrp2882 message may be output.
If a swsrp2882 message is output, after the status of TFO group has become "Normal" and the phase is not "Maintenance", refer to "7.10 When Recovering Storage Cluster Continuous Copy Function" to take action.
NAME
swsrpmake - creates a replication volume
SYNOPSIS
/opt/FJSVswsrp/bin/swsrpmake [-m] [-f] [-t] ([-j | -Xconcur]) [-Xgds-slice-skipchk] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpmake [-m] [-f] [-t] ([-T | -C | -P]) [-Xgds-slice-skipchk] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpmake [-h serverName] [-m] [-f] [-t] ([-j | -Xconcur]) [-Xgds-slice-skipchk] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpmake [-h serverName] [-m] [-f] [-t] ([-T | -C | -P]) [-Xgds-slice-skipchk] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpmake [-m] [-f] [-t] ([-j | -Xconcur]) [-Xreverse] -Xgroup groupName
/opt/FJSVswsrp/bin/swsrpmake [-m] [-f] [-t] ([-T | -C | -P]) [-Xconcur-opc] [-Xreverse] -Xgroup groupName
/opt/FJSVswsrp/bin/swsrpmake [-h serverName] [-m] [-f] [-t] ([-j | -Xconcur]) [-Xreverse] -Xgroup groupName
/opt/FJSVswsrp/bin/swsrpmake [-h serverName] [-m] [-f] [-t] ([-T | -C | -P]) [-Xconcur-opc] [-Xreverse] -Xgroup groupName
DESCRIPTION
When synchronization processing (EC) is not performed, this command starts snapshot processing (OPC/QuickOPC/SnapOPC/SnapOPC+) to create a replication volume.
When synchronization processing is performed, check whether the status of the processing is in the equivalency maintenance state. If so, 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 destination volume can be accessed.
The behavior of this command could differ depending on the status of the Advanced Copy during progress and the following should be noted:
When synchronous processing is not performed, the command starts snapshot processing and creates replication volumes. This form of replication is called snapshot replication.
When synchronous processing is performed, the command checks the state of synchronous processing and, if the synchronous processing is in the equivalency maintenance state, the command suspends the processing in order to create a replication volume. This form of replication is called synchronous replication. The state in which synchronous processing is suspended is called the copy established state.
In either case, the copy destination volume is made accessible after this command is executed.
This command executes the replication pre-processing and post-processing before a replication is created. For details about these processes, refer to "Appendix C Pre-processing and Post-processing of Replication".
If the Storage Cluster Continuous Copy function is used, replication volumes are created on both the Primary Storage and Secondary Storage.
OPTIONS
When executing on the Management Server, specify the name of the target Managed Server.
When executing on the target Managed server, it is not necessary to specify this option.
When performing the server-to-server replication, specify the name of the operation server configured with the swsrpsetvol command.
For the server name, accurately specify the same letters, including upper and lower case, as the server name displayed with the stgxfwcmdispsrv command.
For server-to-server replication, this specifies that communication processing is not performed with the non-operation server. When this option is specified, volume status check processing and pre-processing and post-processing are not performed for the non-operation server volume.
This option is valid only during server-to-server replication.
Specifies that the pre-processing and post-processing are not performed for a replication source volume.
Use this option only when AdvancedCopy Manager does not execute pre-processing and post-processing of the copy source volume and unique pre-processing and post-processing scripts are inserted before and after (respectively) the AdvancedCopy Manager command, or when you judge that copy pre-processing and post-processing are unnecessary (e.g., for a database constructed on a raw device).
Specifies that the pre-processing and post-processing are not performed for a replication destination volume.
Use this option when applied to either of the following conditions:
Pre-processing and post-processing for copy destination volume is not performed by AdvancedCopy Manager but independent pre-processing and post-processing is added in before and after AdvancedCopy Manager commands.
Pre-processing and post-processing for copy destination volume is determined to be unnecessary (e.g. Database created on RAW device)
If you specify the -t option to execute the swsrpstartsync command, specify the -t option also when executing this command.
Specifies that copy processing is 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 intra-box replication. This option can only be used for intra-box replication; if attempted for intra-box replication, an error occurs.
When this option is specified, the data in the destination volume is not guaranteed.
Additionally, when this option is specified, pre-processing and post-processing for the source and destination volumes are not performed. When restarting synchronous processing (REC) between boxes, execute the swsrpstartsync command with the -t option specified.
Specifies that differential snapshot processing is executed.
This option cannot be specified while synchronous processing is performed.
This option is valid only for a replication within the ETERNUS Disk storage system and when the ETERNUS Disk storage system 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.
Specifies that a replication is created for each group.
Specifies that a replication is created for each group in the reverse direction (i.e., from replica volumes to original volumes).
This option is valid only when the -Xgroup option is specified.
Specifies that a replication is created using the Concurrent Suspend function.
This option is not supported when PRIMECLUSTER GD Snapshot linkage is being used.
Specifies that a replication is created using the Concurrent OPC function.
This option is not supported when linking with PRIMECLUSTER GD Snapshot.
Specifies to start SnapOPC.
This option is only valid for intra-box replications and for ETERNUS Disk storage system that supports the SnapOPC function.
Specifies to start SnapOPC+.
This option is only valid with intra-box replications and for ETERNUS Disk storage system that supports the SnapOPC+ function.
An error occurs in the following cases:
The same SnapOPC+ session exists at the copy source volume and the copy destination volume.
Skips the SDX object status check processing that is usually performed as part of the copy source and copy destination pre-processing if SDX objects are operated in slice units.
If this option is specified for a stopped volume, the -f and -t options must also be specified.
OPERANDS
Specifies a replication source volume.
Specifies the replication source volume or the replication destination volume that was set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
Specifies a replication destination volume.
Specifies the replication source volume or the replication destination volume that was set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
The Management Server instructs Managed Server: SRC-SV to create a copy of /dev/dsk/c1t2d0s3 in /dev/dsk/c1t2d0s3@TARG-SV:
# /opt/FJSVswsrp/bin/swsrpmake -h SRC-SV /dev/dsk/c1t0d2s3 /dev/dsk/c1t2d0s3@TARG-SV FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d0s3@TARG-SV swsrpmake completed #
Creates a copy for the group "GRP1":
# /opt/FJSVswsrp/bin/swsrpmake -Xgroup GRP1 GROUP=GRP1 swsrpmake completed #
Creates a copy for the group "GRP1" by using the Concurrent OPC:
# /opt/FJSVswsrp/bin/swsrpmake -Xgroup GRP1 -Xconcur-opc GROUP=GRP1 swsrpmake completed #
NOTES
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 maintenance 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 reset the replication volume information.
If a replication source volume is an SDX object, the status of the SDX object does not match the following:
The mirror volume is ACTIVE or STOP.
The mirror slice status is ACTIVE or TEMP
When the mirror slice is TEMP, a reproduction former volume is not pre-processed.
The SDX disk status is ENABLE.
For server-to-server replication, the Managed 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.
When the copy source or destination volume constitutes a PRIMECLUSTER GFS local file system consisting of multiple volumes and the file system is mounted. In this case, unmount the PRIMECLUSTER GFS local file system and perform a replication for all the volumes that constitute the PRIMECLUSTER GFS local file system.
When the original volume or replica volume is a logical volume of VxVM and the structure of the logical volume is changed to a structure not supported by AdvancedCopy Manager or deleted from VxVM.
If the -j, -T, or -C option is specified when the function is used with PRIMECLUSTER GD Snapshot.
The backup management function is executing a process for a specified source or destination volume
From the copy destination server, the command was executed with both -Xconcur and -m options specified simultaneously for any of the following ETERNUS Disk storage systems:
ETERNUS DX80 S2 (for earlier than V10L30 firmware)
ETERNUS DX90 S2 (for earlier than V10L30 firmware)
ETERNUS DX400 S2 series (for earlier than V10L30 firmware)
ETERNUS DX8000 S2 series (for earlier than V10L30 firmware)
If the -Xgroup option is specified, processing is 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 is terminated immediately if an error occurs.
Note the following when you specify the -Xconcur-opc option:
Specify this option together with the -Xgroup option.
If an error is detected by the preliminary check for the replication volumes to be processed, processing is terminated without creating a copy.
Refer to the following table for details about the preliminary checks.
Type | Details of Preliminary Checks |
|---|---|
Common | Check if a pair of synchronized replications is not exist in the group. |
When the - T option is specified | Check if a pair of volumes which is in the tracking state and a pair of volumes on which the tracking is not executed are not mixed in the group. |
If this command is executed during the snapshot processing, start or restart the snapshot processing. Refer to the following table for details about copy operation.
Operation Status | Copy Operation |
|---|---|
When the operation status of the replication volume in the group is in one of the following:
|
|
Operation Status | Copy Operation |
|---|---|
When the operation status of the replication volume in the group is in one of the following:
|
|
When the operation status of the replication volume in the group is in one of the following:
| Differential snapshot processing is restarted with the Concurrent OPC specified. |
When the replication to be performed satisfies either of the following conditions, perform dismount of the copy target volume before executing a command.
When a replication is performed between different OSs
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
If dismount is performed in the abovementioned case, post-processing of the copy target volume at the time of duplicate creation produces an error.
Before a replica is created, the pre-processing for the source volume and destination volume are executed (for synchronized replication, only pre-processing is executed). After the replica has been created, the post-processing for the source volume and destination volume is executed. The contents of the script can be customized. For more information about this refer to "Appendix C Pre-processing and Post-processing of Replication". If the -f or -t option is specified, the pre-processing and post-processing are not performed.
If a replica is created with the -Xgroup option specified, the replication, pre-processing and post-processing scripts are not executed for the copy source volume/copy destination volume. Therefore, execute pre-processing for all copy source volumes/copy destination volumes in the group before this command is executed.
(However, for synchronous replication, pre-processing for the copy destination volume is executed when replication starts, so it need not be executed.)
In addition, post-processing must be executed after this command is executed.
If this command is executed while a snapshot process is running, the copy in progress is stopped and a new snapshot process is started. However, if the target copy session is SnapOPC+ and the snap generation is not the oldest, this command terminates with an error before the copy is stopped.
To protect the data, this command sets the replication source volume before creating a replica so that other processes cannot access the volume. The replication source volume is unmounted in order to disable to access it. If you cannot unmount the source volume 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 by using 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 use some other method, refer to "Appendix C Pre-processing and Post-processing of Replication" and note the following:
For replication pre-processing, 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.
When the replication source volume is being used by backup management, dismount may not possible. In this case, "swsrp2613 An error occurred in the pre-processing script for creating a replica. Error Code = 2" is output.
When you are using the original copy source volume in the PRIMECLUSTER GFS local file system, use the following procedures (UNIX commands) to mount the copy source volume.
# sfxadm <list of RAW device names which constitute PRIMECLUSTER GFS local file system> # fsck -F sfxfs [-y] <representation RAW device name of PRIMECLUSTER GFS local file system> # mount -F sfxfs <representation device name of PRIMECLUSTER GFS local file system> Mount point
If the replication source or destination volume exists in a PRIMECLUSTER GFS local file system consisting of multiple devices (multi-partition), replication cannot be performed by using pre-processing and post-processing scripts to execute unmount/mount. In this case, manually unmount the PRIMECLUSTER GFS local file system before starting a replication and re-mount it after the replication has completed.
When the PRIMECLUSTER GFS local file system and AdvancedCopy Manager configurations are as follows:
# sfxinfo /dev/dsk/c1t3d10s1 ID special size mount Type 0 /dev/dsk/c1t3d10s1(800019) 25986 /mnt META 0 /dev/dsk/c1t3d10s1(800019) 105751 /mnt DATA 1 /dev/dsk/c1t3d15s3(800028) 5120 /mnt LOG 2 /dev/dsk/c1t3d16s3(800030) 131736 /mnt DATA Setting AdvancedCopy Manager # /opt/FJSVswsrp/bin/swsrpvolinfo Server Original-Volume Size Replica-Volume Size Copy Op-Server SV1 /dev/dsk/c1t3d10s1@SV1 128.0 Mbyte /dev/dsk/c1t3d20s1@SV1 128.0 Mbyte bi-direction original SV1 /dev/dsk/c1t3d15s3@SV1 5.0 Mbyte /dev/dsk/c1t3d25s3@SV1 5.0 Mbyte bi-direction original SV1 /dev/dsk/c1t3d16s3@SV1 128.0 Mbyte /dev/dsk/c1t3d26s3@SV1 128.0 Mbyte bi-direction original
Backup procedure (replication source volume: PRIMECLUSTER GFS local file system (snapshot type))
# umount /mnt # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d10s1 /dev/dsk/c1t3d20s1 FROM=/dev/dsk/c1t3d10s1@SV1,TO=/dev/dsk/c1t3d20s1 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d15s3 /dev/dsk/c1t3d25s3 FROM=/dev/dsk/c1t3d15s3@SV1,TO=/dev/dsk/c1t3d25s3 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d16s3 /dev/dsk/c1t3d26s3 FROM=/dev/dsk/c1t3d16s3@SV1,TO=/dev/dsk/c1t3d26s3 swsrpmake completed # mount -F sfxfs /dev/dsk/c1t3d10s1 /mnt
Backup procedure (replication source volume: PRIMECLUSTER GFS local file system (synchronous type))
# /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d10s1 /dev/dsk/c1t3d20s1 FROM=/dev/dsk/c1t3d10s1@SV1,TO=/dev/dsk/c1t3d20s1 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d15s3 /dev/dsk/c1t3d25s3 FROM=/dev/dsk/c1t3d15s3@SV1,TO=/dev/dsk/c1t3d25s3 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d16s3 /dev/dsk/c1t3d26s3 FROM=/dev/dsk/c1t3d16s3@SV1,TO=/dev/dsk/c1t3d26s3 swsrpstartsync completed : :(Checking equivalence-held state) : # umount /mnt # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d10s1 /dev/dsk/c1t3d20s1 FROM=/dev/dsk/c1t3d10s1@SV1,TO=/dev/dsk/c1t3d20s1 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d15s3 /dev/dsk/c1t3d25s3 FROM=/dev/dsk/c1t3d15s3@SV1,TO=/dev/dsk/c1t3d25s3 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d16s3 /dev/dsk/c1t3d26s3 FROM=/dev/dsk/c1t3d16s3@SV1,TO=/dev/dsk/c1t3d26s3 swsrpmake completed # mount -F sfxfs /dev/dsk/c1t3d10s1 /mnt #
Restore procedure (replication desitination volume: PRIMECLUSTER GFS local file system (snapshot type))
# umount /mnt # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d20s1 /dev/dsk/c1t3d10s1 FROM=/dev/dsk/c1t3d20s1@SV1,TO=/dev/dsk/c1t3d10s1 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d25s3 /dev/dsk/c1t3d15s3 FROM=/dev/dsk/c1t3d25s3@SV1,TO=/dev/dsk/c1t3d15s3 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d26s3 /dev/dsk/c1t3d16s3 FROM=/dev/dsk/c1t3d26s3@SV1,TO=/dev/dsk/c1t3d16s3 swsrpmake completed # mount -F sfxfs /dev/dsk/c1t3d10s1 /mnt #
Restore procedure (replication destination volume: PRIMECLUSTER GFS local file system (synchronous type))
# umount /mnt # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d20s1 /dev/dsk/c1t3d10s1 FROM=/dev/dsk/c1t3d20s1@SV1,TO=/dev/dsk/c1t3d10s1 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d25s3 /dev/dsk/c1t3d15s3 FROM=/dev/dsk/c1t3d25s3@SV1,TO=/dev/dsk/c1t3d15s3 swsrpstartsync completed # /opt/FJSVswsrp/bin/swsrpstartsync /dev/dsk/c1t3d26s3 /dev/dsk/c1t3d16s3 FROM=/dev/dsk/c1t3d26s3@SV1,TO=/dev/dsk/c1t3d16s3 swsrpstartsync completed : :(Checking equivalence-held state) : # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d20s1 /dev/dsk/c1t3d10s1 FROM=/dev/dsk/c1t3d20s1@SV1,TO=/dev/dsk/c1t3d10s1 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d25s3 /dev/dsk/c1t3d15s3 FROM=/dev/dsk/c1t3d25s3@SV1,TO=/dev/dsk/c1t3d15s3 swsrpmake completed # /opt/FJSVswsrp/bin/swsrpmake /dev/dsk/c1t3d26s3 /dev/dsk/c1t3d16s3FROM=/dev/dsk/c1t3d26s3@SV1,TO=/dev/dsk/c1t3d16s3 swsrpmake completed # mount -F sfxfs /dev/dsk/c1t3d10s1 /mnt #
For Snap Data Volume, only SnapOPC/SnapOPC+ can be executed.
When restoring data from the copy destination volume of SnapOPC/SnapOPC+, note that there must be a copy session between the copy source volume and the copy destination volume. However, for SnapOPC+ sessions whose snap generations are currently being deleted, the data cannot be restored.
If this command is executed during snapshot processing, snapshot processing is restarted.
Refer to the following table for details about 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 and tracking is not executed. | No | Copying that is in progress is terminated and ordinary snapshot processing is restarted. |
Snapshot processing is in progress and tracking is not executed. | Yes | Copying in progress is terminated and differential snapshot processing is restarted. |
Snapshot processing is in progress and tracking is in progress. | No | Copying in progress is terminated and ordinary snapshot processing is restarted. |
Snapshot processing is in progress and tracking is in progress. | Yes | Differential snapshot processing is restarted. |
Tracking is in progress. | No | Tracking processing is terminated and ordinary snapshot processing is restarted. |
Tracking is in progress. | Yes | Differential snapshot processing is restarted. |
When SDX objects of PRIMECLUSTER GD are used: Refer to "Configuration and Conditions of Unsupported SDX Objects", and "10.1.7 Notes on SDX Object Operations (Replication Management)".
Refer to "10.1.1 General Notes" for notes on creating replication.
This command cannot be executed while any of the following commands are running:
When the Storage Cluster Continuous Copy function is used:
If the status of the TFO group is "Normal", and replication volume cannot create on either the Primary Storage or Secondary Storage, the command may terminate abnormally. Check the cause of the error on both the Primary Storage and Secondary Storage to address the error message in the storage device where the error is occurring.
When the status of the TFO group is "Normal" and its phase is "Maintenance", or when the status of the TFO group is "Halt", the command starts synchronous processing on the storage that has an "Active" TFO status and terminates normally. However, synchronous processing could not be started on the storage that has a "Standby" TFO status. In this case, swsrp2882 message may be output.
If a swsrp2882 message is output, after the status of TFO group has become "Normal" and the phase is not "Maintenance", refer to "7.10 When Recovering Storage Cluster Continuous Copy Function" to take action.
NAME
swsrpstat - displays the operation status
SYNOPSIS
/opt/FJSVswsrp/bin/swsrpstat [ [-L] [-Xdate] [-Xda] [-Xstandby-s] | [-Xall] ] [-E] [-H] [-O] [originalVolumeName]/opt/FJSVswsrp/bin/swsrpstat [-h serverName] [ [-L] [-Xdate] [-Xda] [-Xstandby-s] | [-Xall] ] [-E] [-H] [-O] [originalVolumeName]
/opt/FJSVswsrp/bin/swsrpstat [ [-L] [-Xdate] [-Xda] [-Xstandby-s] | [-Xall] ] [-E] [-H] [-O] -Xgroup groupName
/opt/FJSVswsrp/bin/swsrpstat [-h serverName] [ [-L] [-Xdate] [-Xda] [-Xstandby-s] | [-Xall] ] [-E] [-H] [-O] -Xgroup groupName
DESCRIPTION
This command displays the operation status of the specified volume. If a volume is not specified, the operation status of each replication volume is displayed.
The following information is displayed.
Title | Description |
|---|---|
Server | Displays a Managed Server name. |
Original-Volume | Displays a replication source volume name. |
Replica-Volume | Displays a replication destination volume name. |
Direction | Displays the copy direction if a copy session exists.
|
Status | Displays the execution status. If the Storage Cluster Continuous Copy function is used, the execution status of the ETERNUS Disk storage system where the TFO status is "Active" is displayed.
*1: "halt(use-buffer)" and "halt(use-disk-buffer)" are output when the following two conditions are fulfilled:
|
Execute | Displays the copy progress rate as a percentage. "----" is displayed during SnapOPC or when no copying is being performed. If the Storage Cluster Continuous Copy function is used, the replication progress rate of the ETERNUS Disk storage system where the TFO status is "Active" is displayed. |
Trk | Displays whether tracking processing is in progress. If the Storage Cluster Continuous Copy function is used, the presence of the tracking process of the ETERNUS Disk storage system where the TFO status is "Active" is displayed.
Always displays "----" when the PRIMECLUSTER GD Snapshot linkage function is enabled. |
Update | Displays the percentage of data that has been updated since the last copy was created, in the cases shown below. If the Storage Cluster Continuous Copy function is used, the size of the data that has been updated of the ETERNUS Disk storage system where the TFO status is "Active" is displayed. For SnapOPC+, this displays the percentage of data that has been updated since the previous snap generation.
Displays "----" during physical copying or when tracking is not in progress. Always displays "----" when the PRIMECLUSTER GD Snapshot linkage function is enabled. |
Rcv | Indicates the Recovery mode for Inter-ETERNUS synchronization.
|
Split | Indicates the Split mode for Inter-ETERNUS synchronization.
|
Xfer | Indicates the Transfer for Inter-ETERNUS synchronization.
|
Snap-Gen | When SnapOPC+ is performed, displays the snap generation number. |
Copy-DA | Displays the access permission for the replication destination volume. If the Storage Cluster Continuous Copy function is used, the access permission of the ETERNUS Disk storage system where the TFO status is "Active" is displayed.
When an ETERNUS Disk storage system does not support the Destination Access Permission function or the SDX objects is specified with the units of logical volumes, 'off' is displayed. |
Date | If a copy session exists, a timestamp in the [yyyy/mm/dd hh:mm:ss] format is displayed for the last status transition of the copy session as described below. If the Storage Cluster Continuous Copy function is used, the timestamp of the ETERNUS Disk storage system where the TFO status is "Active" is displayed. The timestamp is relative to the time zone settings of the specified storage system. [For the OPC or QuickOPC]
[For the SnapOPC or SnapOPC+]
[For the EC]
[For the REC]
*1: When a forced suspend is performed on a REC session in hardware suspend condition, the timestamp of the last execution is initialized as "----/--/-- --:--:--". When a forced suspend is performed while copy is executing, its timestamp is not updated. "----/--/-- --:--:--" is displayed in the following situations:
|
Standby-Session | If the Storage Cluster Continuous Copy function is used, the Standby-Side Continuous Copy Session status is displayed.
|
OPTIONS
When executing on the Management Server, specify the name of the target Managed Server.
When executing on the target Managed server, it is not necessary to specify this option.
For the server name, accurately specify the same letters, including upper and lower case, as the server name displayed with the stgxfwcmdispsrv command.
Specifies to display in extension format.
For the items displayed by this option, refer to the table in the description above.
An option which when set displays the operational status in the opposite direction only (from the copy destination to the copy source).
If this option is omitted, the operation status is always displayed in the normal direction (from the copy source to the copy destination) when a bi-directional OPC physical copy is taking place.
In case this option is set, the operational status in the normal direction is not displayed. Only the operational status in the opposite direction is displayed.
This option can be used to check the operational status of an OPC session performed in the opposite direction if a QuickOPC/SnapOPC session in the normal direction exists.
Specifies that the operation statuses are displayed by the group.
If this option is set, all the operational statuses relating to the specified group are displayed.
Changes the Status column display method used when a REC enters a hard-suspend (halt) status.
If this option is specified, then "halt (sync)" is displayed when hard-suspend status occurs during a total copy or a differential copy. "halt (equivalent)" is displayed when hard-suspend status occurs during an equivalency maintenance state.
If the transfer mode is Consistency mode and a REC Disk buffer is set, "halt(use-disk-buffer)" is displayed when issue of a hard suspend causes transfer data to be saved to the REC Disk buffer.
If the transfer mode is Consistency mode and a REC buffer is set, "halt(use-buffer)" is displayed when issue of a hard suspend causes transfer data to be saved to the REC buffer.
Note that hard-suspend status is still displayed as "halt" even if this option is specified for PRIMECLUSTER GD snapshot linkage.
Changes the error suspend(failed) status Status column display method.
If this option is specified, the display is as follows:
There is a bad sector: "failed(badsector)"
When there is insufficient Snap Data Volume or Snap Data Pool capacity: "failed(overflow)"
All other cases: "failed(other)"
However, when linked with PRIMECLUSTER GD Snapshot, only "failed" is displayed when an error suspend status occurs even if -O option is specified.
Displays the access permission settings for copy destination volume.
Displays the timestamp of the last copy session status transition.
If the Storage Cluster Continuous Copy function is used, the Standby-Side Continuous Copy Session status is displayed.
Displays the all information.
For the items displayed by this option, refer to the example following.
Note that the items displayed by this option may be subject to change in a future release.
OPERANDS
Specifies a replication source volume name.
For the volume names of other servers, use the format "Volume-Name@Managed-Server-Name".
Specifies the AdvancedCopy Manager device name for the Volume-Name.
Displays all operation statuses for the specified replication source volume.
If this operand is omitted, all the operation statuses of the Managed Server on which this command is executed are displayed.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
Direct that all the replication operation statuses for Managed Server (SRC-SV) be displayed on the Management Server:
# /opt/FJSVswsrp/bin/swsrpstat -h SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d0s3@TARG-SV regular replicated ---- SRC-SV /dev/dsk/c1t2d1s3@SRC-SV /dev/dsk/c1t2d1s3@TARG-SV regular ---- ---- SRC-SV /dev/dsk/c1t2d2s3@SRC-SV /dev/dsk/c1t2d2s3@TARG-SV reverse snap 45% SRC-SV /dev/dsk/c1t1d0s3@SRC-SV /dev/dsk/c1t1d1s3@TARG-SV regular copy-on-write(inactive) ---- SRC-SV /dev/dsk/c1t1d0s3@SRC-SV /dev/dsk/c1t1d2s3@TARG-SV regular copy-on-write(inactive) ---- SRC-SV /dev/dsk/c1t1d0s3@SRC-SV /dev/dsk/c1t1d3s3@TARG-SV regular copy-on-write(active) ---- #
Direct that all the replication operation statuses for Managed Server (SRC-SV) be displayed on the Management Server (with the -L option specified):
# /opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -L Server Original-Volume Replica-Volume Direction Status Execute Trk Update Rcv Split Xfer Snap-Gen SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d0s3@TARG-SV regular replicated ---- ---- ---- auto ---- async ---- SRC-SV /dev/dsk/c1t2d1s3@SRC-SV /dev/dsk/c1t2d1s3@TARG-SV regular ---- ---- on 6% ---- ---- ---- ---- SRC-SV /dev/dsk/c1t2d2s3@SRC-SV /dev/dsk/c1t2d2s3@TARG-SV reverse snap 45% off ---- ---- ---- ---- ---- SRC-SV /dev/dsk/c1t1d0s3@SRC-SV /dev/dsk/c1t1d1s3@TARG-SV regular copy-on-write(inactive) ---- off 0% ---- ---- ---- 1 SRC-SV /dev/dsk/c1t1d0s3@SRC-SV /dev/dsk/c1t1d2s3@TARG-SV regular copy-on-write(inactive) ---- off 5% ---- ---- ---- 2 SRC-SV /dev/dsk/c1t1d0s3@SRC-SV /dev/dsk/c1t1d3s3@TARG-SV regular copy-on-write(active) ---- off 6% ---- ---- ---- 3 #
Direct that all the replication operation statuses for Managed Server (SRC-SV) be displayed on the Management Server (with the -Xall option specified):
# /opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -Xall Server Original-Volume Replica-Volume Direction Status Execute Trk Update Rcv Split Xfer Snap-Gen Copy-DA Date Standby-Session SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d0s3@TARG-SV regular replicated ---- ---- ---- auto ---- async ---- on 2010/10/20 22:00:45 exist SRC-SV /dev/dsk/c1t2d1s3@SRC-SV /dev/dsk/c1t2d1s3@TARG-SV ---- ---- ---- on 6% ---- ---- ---- ---- off 2010/10/20 22:10:39 not-exist SRC-SV /dev/dsk/c1t2d2s3@SRC-SV /dev/dsk/c1t2d2s3@TARG-SV reverse snap 45% off ---- ---- ---- ---- ---- on 2010/10/21 22:00:23 ????? #
Direct that all the replication operation statuses for Managed Server (SRC-SV) be displayed on the Management Server (with the -Xdate option specified):
# /opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -Xdate Server Original-Volume Replica-Volume Direction Status Execute Date SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d0s3@TARG-SV regular replicated ---- 2010/10/20 22:00:45 SRC-SV /dev/dsk/c1t2d1s3@SRC-SV /dev/dsk/c1t2d1s3@TARG-SV ---- ---- ---- 2010/10/20 22:10:39 SRC-SV /dev/dsk/c1t2d2s3@SRC-SV /dev/dsk/c1t2d2s3@TARG-SV reverse snap 45% 2010/10/21 22:00:23 #
Direct that all the replication operation statuses for Managed Server (SRC-SV) be displayed on the Management Server (with the -Xstandby-s option specified):
# /opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -Xstandby-s Server Original-Volume Replica-Volume Direction Status Execute Standby-Session SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d0s3@TARG-SV regular replicated 45% exist SRC-SV /dev/dsk/c1t2d1s3@SRC-SV /dev/dsk/c1t2d1s3@TARG-SV regular replicated 10% not-exist SRC-SV /dev/dsk/c1t2d2s3@SRC-SV /dev/dsk/c1t2d2s3@TARG-SV reverse equivalent 100% ????? #
NOTES
When the execution status (the status displayed in the "Status" column) is "failed", "halt", or "?????", refer to "8.4 Troubleshooting: Hardware or Other Error During Replication" and take action.
If the execution status (displayed in the Status column) is "gds-error":
A PRIMECLUSTER GD error probably occurred. Remove the cause of the PRIMECLUSTER GD error, then use the swsrpcancel command to stop the replication operation.
The operation status cannot be displayed if:
The volumes have not been set as replication volumes.
When the original volume or replica volume is a logical volume of VxVM and the structure of the logical volume is changed to a structure not supported by AdvancedCopy Manager or the logical volume is deleted from VxVM.
This command cannot be executed while the following command is running:
If the Storage Cluster Continuous Copy function is used, some corrective action may be required according to what is displayed in the Standby-Session column.
For "not-exist":
Refer to "7.10 When Recovering Storage Cluster Continuous Copy Function".
Other than those above:
No action is required.
NAME
swsrpcancel - stops snapshot processing and synchronization processing
SYNOPSIS
/opt/FJSVswsrp/bin/swsrpcancel [-c] {([-f] [-t] [-m] [-b])|[-T]|[-Xforce]} [-Xgds-slice-skipchk] fromVolumeName toVolumeName/opt/FJSVswsrp/bin/swsrpcancel [-h serverName] [-c] {([-f] [-t] [-m] [-b])|[-T]|[-Xforce]} [-Xgds-slice-skipchk] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpcancel [-c] {([-f] [-t] [-m] [-b])|[-T]|[-Xforce]} [-Xreverse] -Xgroup groupName/opt/FJSVswsrp/bin/swsrpcancel [-h serverName] [-c] {([-f] [-t] [-m] [-b])|[-T]|[-Xforce]} [-Xreverse] -Xgroup groupName
DESCRIPTION
This command stops snapshot processing (OPC, QuickOPC, SnapOPC, or SnapOPC+) 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.
If the Storage Cluster Continuous Copy function is used, the replication process is stopped on both the Primary Storage and Secondary Storage.
OPTIONS
When executing on the Management Server, specify the name of the target Managed Server.
When executing on the target Managed server, it is not necessary to specify this option.
When performing the server-to-server replication, specify the name of the operation server configured with the swsrpsetvol command.
For the server name, accurately specify the same letters, including upper and lower case, as the server name displayed with the stgxfwcmdispsrv command.
Specifies that the copy processing is forcibly stopped from a non-operation server when the operation server cannot be used because of a system failure. If this option is used, the copy processing is stopped without implementing pre-processing and post-processing.
This option cannot be specified on the operation server.
For server-to-server replication, this option specifies that communication processing is not performed with non-operation servers. When this option is specified, volume status check processing and pre-processing and post-processing are not performed for the replication destination volume of a non-operation server.
This option is valid only during server-to-server replication.
When stopping synchronous processing under the equivalency maintained status, specify that pre-processing and post-processing for the copy source volume is not being executed.
Use this option only when AdvancedCopy Manager does not execute pre-processing and post-processing of the copy source volume and unique pre-processing and post-processing scripts are inserted before and after (respectively) the AdvancedCopy Manager command, or when you judge that copy pre-processing and post-processing are unnecessary (e.g., for a database constructed on a raw device).
When stopping the synchronous processing under the equivalency maintained status, this specifies that post-processing for the copy destination volume is not executed.
Use this option only when AdvancedCopy Manager does not execute pre-processing and post-processing of the copy destination volume and unique pre-processing and post-processing scripts are inserted before and after (respectively) the AdvancedCopy Manager command, or when you judge that copy pre-processing and post-processing are unnecessary (e.g., for a database constructed on a raw device).
Specifies that the inter-box copy operation in the halt status be stopped.
For replication on single server, the copying is cancelled for both boxes.
For server-to-server replication, the copying is cancelled only for the box connected to the server on which this command was executed.
Use the option only for a copy operation in the halt status and whose recovery is not expected to be done successfully.
The option is valid only for a copy operation in the HALT status.
The option can be used on the server that is not specified as the operation server.
This option cannot be used for the logical volume of an SDX object.
If this option is specified together with the -Xgroup option, copy processing is only stopped for sessions in the group whose status is halt.
Specifies that differential snapshot processing is terminated.
This option only terminates tracking processing and does not terminate snapshot processing (OPC physical copying) when it is in progress. This option releases the OPC session if snapshot processing (i.e., OPC physical copying) is complete.
This option can only be used 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.
Specifies that copy processing is stopped for each group.
Specifies that copy processing that is being executed in the reverse direction (from replica volumes to original volumes) is stopped
This option is valid only when the -Xgroup option is specified.
Skips the SDX object status check processing that is usually performed as part of the copy source and copy destination pre-processing. 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 and -t options must also be specified.
Specification of this option forcibly stops a SnapOPC+ session.
Forcibly stopping SnapOPC+ deletes the specified snap generation and all earlier snap generations.
This option can be specified even if there is only one snap generation.
This option is a SnapOPC+ fixed option.
If this option is specified at the same time as the -Xgroup option, the SnapOPC+ sessions in that group are stopped, and all the snap generations and snap generations before it in the group are also deleted.
OPERANDS
Specifies a copy source volume name.
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
Specifies a copy destination volume name.
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
On the Management Server, direct that copying from /dev/dsk/c1t2d0s3 to /dev/dsk/c1t2d0s3@TARG-SV be stopped for Managed Server SRC-SV:
#/opt/FJSVswsrp/bin/swsrpcancel -h SRC-SV /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3@TARG-SV FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d0s3@TARG-SV swsrpcancel completed #
Stops copy processing for group "GRP1":
# /opt/FJSVswsrp/bin/swsrpcancel -Xgroup GRP1 GROUP=GRP1 swsrpcancel completed #
NOTES
Following execution with the -b option specified in replication on single server, the command stops normally when cancellation of the copying succeeds in either of the boxes.
Copy processing cannot be performed if:
The specified replication source volume and replication destination volume have not been 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 Managed 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.
When the original volume or replica volume is a logical volume of VxVM and the structure of the logical volume is changed to a structure not supported by AdvancedCopy Manager or the logical volume is deleted from VxVM.
The backup management function is executing a process for a specified source or destination volume
If the -Xgroup option is specified, processing is performed for each active replication volume, but processing is terminated without cancelling replication in the following case:
If no replication volumes have been copied
When you execute -b option specifying a nonexistent copy in the "halt" state in the group.
When you execute -T option specifying a nonexistent copy in the tracking process of QuickOPC in the group.
When you execute with the -Xforce option specified and there are no sessions of SnapOPC+ with managing the generation in the group
Additionally, if the -Xgroup option is specified, replication volumes are processed in order, but processing is terminated immediately if an error occurs.
SnapOPC+ snap generations are deleted differently depending on whether the target storage device supports deletion of specific snap generation.
When deletion is supported
Specific snap generation can be deleted while past snap generations are retained.
When a snap generation other than the oldest (snap generation number is "2" or later) is deleted, the snap generation may remain for some time after the command is executed with the status of "deleting".
Before reusing the replication destination volume that is being used for the deletion target snap generation as the replication destination volume, confirm that the generation deletion process is completed.
When deletion is not supported
The oldest snap generation (snap generation number is "1") must be deleted first.
To forcibly delete a snap generation other than the oldest, specify the -Xforce option. In this case, the specified snap generation and all snap generations prior to that generation are deleted.
If the -Xforce option and the -Xgroup option are specified at the same time, the SnapOPC+ sessions in the group are stopped and the snap generation and all earlier generations in the group are deleted.
When SnapOPC+ snap generations are deleted, the remaining snap generation numbers are moved up.
When snap generations other than the oldest (snap generation number is "2" or later) are deleted, the snap generation numbers are moved up when the deletion process of the snap generation is completed.
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). The operation is cancelled 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 as a replica. |
Equivalency maintain status | Suspends synchronization processing. The replication destination volume can be used as a replica |
Replication established status | Suspends synchronization processing. The replication destination volume can be used as a replica |
Snapshot processing is being performed | Stops the snapshot processing. The replication destination volume cannot be used as a replica or for any other purposes. To reuse the replication destination volume, the volume must be initialized so that the OS recognizes the volume correctly. |
Pre-processing and post-processing for a replication source and replication destination volumes are performed only when the status of synchronization processing is equivalency maintenance status.
Synchronization processing cannot be stopped in equivalency maintenance status in the following situations:
When a replication source volume is an SDX object and the status of the SDX object is not one of the following:
The mirror volume is ACTIVE or STOP.
The mirror slice status is ACTIVE or TEMP
When the mirror slice is TEMP, a reproduction former volume is not pre-processed.
The SDX disk status is ENABLE.
When the copy source or destination volume constitutes a PRIMECLUSTER GFS local file system consisting of multiple volumes and the file system is mounted. In this case, unmount the PRIMECLUSTER GFS local file system and cancel all the volumes that constitute the PRIMECLUSTER GFS local file system.
When the -T option is omitted
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 as a replica. |
Equivalency maintained 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 as a replica. Tracking processing, if in progress, is also terminated. |
Snapshot processing complete status and tracking processing in progress. | 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 maintained status | Processing is interrupted. |
Replica created status | Processing is interrupted. |
Snapshot processing is in progress and tracking processing is not in progress. | Processing is interrupted. |
Snapshot processing is in progress and tracking processing is progress. | Only tracking processing is terminated. Snapshot processing (ie, physical copying) is continued. The destination volume can be used as a replica. |
Snapshot processing complete status and tracking processing in progress. | Tracking processing is terminated. The destination volume can be used as a replica. |
When SDX objects of PRIMECLUSTER GD are used: Refer to "Configuration and Conditions of Unsupported SDX Objects" and "10.1.7 Notes on SDX Object Operations (Replication Management)".
This command cannot be executed while any of the following commands are running:
When the Storage Cluster Continuous Copy function is used:
When the status of the TFO group is "Normal", and replication processing cannot stop on either the Primary Storage or Secondary Storage, the command may terminate abnormally. Check the cause of the error on both the Primary Storage and Secondary Storage to address the error message in the storage device where the error is occurring.
When the status of TFO group is "Normal" and its phase is "Maintenance", or when the status of the TFO group is "Halt", the command starts synchronous processing on the storage that has an "Active" TFO status and terminates normally. However, synchronous processing could not be started on the storage that has a "Standby" TFO status. In this case, swsrp2882 message may be output.
If a swsrp2882 message is output, after the status of TFO group has become "Normal" and its phase is not "Maintenance", refer to "7.10 When Recovering Storage Cluster Continuous Copy Function" to take action.
NAME
swsrpchsync - changes the operation mode
SYNOPSIS
/opt/FJSVswsrp/bin/swsrpchsync [-F {Sync|Async|Stack|Consist}] [-R {Auto|Manual}] [-S {Auto|Manual}] fromVolumeName toVolumeName/opt/FJSVswsrp/bin/swsrpchsync [-h serverName] [-F {Sync|Async|Stack|Consist}] [-R{Auto|Manual}] [-S {Auto|Manual}] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrpchsync [-F {Sync|Async|Stack|Consist}] [-R {Auto|Manual}] [-S {Auto|Manual}] [-Xreverse] -Xgroup groupName/opt/FJSVswsrp/bin/swsrpchsync [-h serverName] [-F {Sync|Async|Stack|Consist}] [-R {Auto|Manual}] [-S {Auto|Manual}] [-Xreverse] -Xgroup groupName
DESCRIPTION
This command changes the operation mode of inter-box synchronization (transfer mode, recovery mode, or split mode).
OPTIONS
When executing on the Management Server, specify the name of the target Managed Server.
When executing on the target Managed server, it is not necessary to specify this option.
When performing the server-to-server replication, specify the name of the operation server configured with the swsrpsetvol command.
For the server name, accurately specify the same letters, including upper and lower case, as the server name displayed with the stgxfwcmdispsrv command.
Changes the transfer mode for inter-box synchronization.
You can specify one of the following parameters in the operand:
Sync : Changes to Synchronous mode.
Async : Changes to Through 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.
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.
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.
Changes the operation mode of inter-box synchronous processing for each group (transfer mode, recovery mode, or split mode).
Specifies that the operation mode of synchronous processing that is being executed in reverse direction (from replica volumes to original volumes) is changed.
This option is valid only when the -Xgroup option is specified.
OPERANDS
Specifies a copy source volume name.
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
Specifies a copy destination volume name.
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
From Management Server to Managed Server: Instruct SRC-SV to change the transfer mode for inter-box synchronization between /dev/dsk/c1t2d0s3@SRC-SV and /dev/dsk/c1t2d10s3@TARG-SV from Consistency mode to Through mode:
#/opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -L /dev/dsk/c1t2d0s3@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute Trk Rcv Split Xfer Snap-Gen SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d10s3@TARG-SV regular sync 99% ---- auto ---- consist ---- : #/opt/FJSVswsrp/bin/swsrpchsync -h SRC-SV -F Async /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d10s3@TARG-SV FROM=/dev/dsk/c1t2d0s3@SRC-SV, TO=/dev/dsk/c1t2d10s3@TARG-SV swsrpchsync completed : #/opt/FJSVswsrp/bin/swsrpstat -h SRC-SV -L /dev/dsk/c1t2d0s3@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute Trk Rcv Split Xfer Snap-Gen SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d10s3@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 Through mode:
# /opt/FJSVswsrp/bin/swsrpchsync -F Async -Xgroup GRP1 GROUP=GRP1 swsrpchsync completed #
NOTES
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 Managed 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 as the Status column by the swsrpstat command or hard-suspended status (with "halt" indicated as the Status column by the swsrpstat command.
The ETERNUS Disk storage system in which the specified original/replica volume is placed do not support the operation mode change function.
When the original volume or replica volume is a logical volume of VxVM and the structure of the logical volume is changed to a structure not supported by AdvancedCopy Manager or the logical volume is deleted from VxVM.
The specified volume is being used with PRIMECLUSTER GD Snapshot.
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 at least one replication volume that meets the conditions above.
Additionally, if the -Xgroup option is specified, replication volumes are processed in order, but processing is terminated immediately if an error occurs.
This command cannot be executed while any of the following commands are running:
NAME
swsrprevsync - reverses the copying direction of synchronization
SYNOPSIS
/opt/FJSVswsrp/bin/swsrprevsync fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrprevsync [-h serverName] fromVolumeName toVolumeName
/opt/FJSVswsrp/bin/swsrprevsync [-Xreverse] -Xgroup groupName
/opt/FJSVswsrp/bin/swsrprevsync [-h serverName] [-Xreverse] -Xgroup groupName
DESCRIPTION
This command reverses the copying direction of synchronization when in suspended status.
Note that this command cannot be used to handle a logical volume of an SDX object.
If the Storage Cluster Continuous Copy function is used, the replication process is reversed on both the Primary Storage and Secondary Storage.
OPTIONS
When executing on the Management Server, specify the name of the target Managed Server.
When executing on the target Managed server, it is not necessary to specify this option.
When performing the server-to-server replication, specify the name of the operation server configured with the swsrpsetvol command.
For the server name, accurately specify the same letters, including upper and lower case, as the server name displayed with the stgxfwcmdispsrv command.
Changes the direction of synchronous processing for each group.
Specifies that the direction of synchronous processing that is being executed in reverse direction (i.e., from replica volumes to original volumes) is inverted.
This option is valid only when the -Xgroup option is specified.
OPERANDS
Specifies a copy source volume name. (as the destination in the reverse direction)
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
Specifies a copy destination volume name. (as the source in the reverse direction)
Specifies the replication source volume or the replication destination volume set with the swsrpsetvol command.
Specifies the AdvancedCopy Manager device name for the volume name.
EXIT STATUS
=0: Completed successfully
>0: Terminated abnormally
EXAMPLES
From Management Server to Managed Server: Instruct SRC-SV to reverse the copying direction of synchronization between /dev/dsk/c1t2d0s3@SRC-SV and /dev/dsk/c1t2d10s3@TARG-SV:
#/opt/FJSVswsrp/bin/swsrpstat -h SRC-SV /dev/dsk/c1t2d0s3@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d10s3@TARG-SV reverse replicated ---- #/opt/FJSVswsrp/bin/swsrprevsync /dev/dsk/c1t2d10s3@TARG-SV /dev/dsk/c1t2d0s3@SRC-SV FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d10s3@TARG-SV swsrprevsync completed #/opt/FJSVswsrp/bin/swsrpstat /dev/dsk/c1t2d0s3@SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d10s3@TARG-SV regular replicated ---- #
Change the direction of synchronous processing for group "GRP1":
# /opt/FJSVswsrp/bin/swsrprevsync -Xgroup GRP1 GROUP=GRP1 swsrprevsync completed #
NOTES
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 Managed 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 ETERNUS Disk storage system in which the specified original/replica volume is placed do not support the reverse function.
When the original volume or replica volume is a logical volume of VxVM and the structure of the logical volume is changed to a structure not supported by AdvancedCopy Manager or the logical volume is deleted from VxVM.
The specified volume is being used with PRIMECLUSTER GD Snapshot.
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 at least one replication volume that meets the conditions above.
Additionally, if the -Xgroup option is specified, replication volumes are processed in order, but processing is 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 are running:
When the Storage Cluster Continuous Copy function is used:
When the status of the TFO group is "Normal", and synchronous processing cannot reverse on either the Primary Storage or Secondary Storage, the command may terminate abnormally. Check the cause of the error on both the Primary Storage and Secondary Storage to address the error message in the storage device where the error is occurring.
When the status of the TFO group is "Normal" and its phase is "Maintenance", or when the status of TFO group is "Halt", the command reverses the synchronous processing on the storage that has an "Active" TFO status and terminates normally.