Note the following about the backup operation of SDX objects.
swstdevinfoset (Device information setting command)
An SDX object cannot be set as a transaction volume for operation of an SP-series product.
A volume in a disk group to which the transaction volume belongs cannot be registered as a backup volume.
A volume in a single disk to which the transaction volume belongs cannot be registered as a backup volume.
A volume in a disk group to which an associated backup volume belongs cannot be registered as the transaction volume.
A volume in a single disk to which an associated backup volume belongs cannot be registered as the transaction volume.
swststartsync (Backup synchronous processing start command)
Backup synchronous processing of a GDS transaction volume cannot be started in the following circumstances:
In the case of any of the above, you should take appropriate action according to the [System administrator's action] for the error message as displayed.
The volume structure of the transaction volume is changed.
The transaction volume is set as a proxy object.
A backup volume cannot be stopped.
The slices that make up the transaction volume include a temporarily separated slice or a slice being copied.
Backup synchronous processing with EC cannot be started in the following circumstances:
In these cases, only software-copy with GDS is available. To use the software-copy function of GDS, specify the -Xgds-softcopy option.
An SDX object that does not support the EC function is specified.
All available backup volumes are in a mirroring structure.
The transaction volume belongs to a mirror group connected to any subordinate group.
An SDX object is in the root class.
If a backup volume satisfies any of the following conditions, it is not selected as the backup destination because it cannot be used as a proxy object of the transaction volume. Even if it is specified as the backup destination, it cannot be used.
The backup volume is not the same class as the transaction volume.
The slices that make up the backup volume include a temporarily separated slice or a slice that is being copied.
The backup volume is set as the master object associated with another proxy of GDS.
The backup volume is mounted.
The backup volume is a logical volume whose size is different from that of the transaction volume.
The backup volume is in a mirroring structure (excluding cases where -Xgds-softcopy or -Xgds-selectcopy option is specified).
No disk is connected directly to the backup volume (excluding cases where -Xgds-softcopy or -Xgds-selectcopy option is specified).
swstcancelsync (Backup synchronous processing cancel command)
The backup volume enters the invalid data state (INVALID) if synchronous processing is cancelled in the following circumstances during the backup of an SDX object:
When the synchronous processing is not in the equivalency maintenance state or copy established state
Restart synchronous processing or snapshot processing again, and the volume should enter the stop state (STOP), which will automatically clear the data invalid state.
To use an alternative method to restore the state, refer to Section F.1.3, "Errors Related to Volume States," in the "PRIMECLUSTER(TM) Global Disk Services User's Guide (Solaris(TM) Operating System)," and perform appropriate action.
swstbackup (Backup execution command)
Backup of a GDS transaction volume cannot be performed in the following circumstances:
In the case of any of the above, you should take appropriate action according to the [System administrator's action] for the error message as displayed.
The volume structure of the transaction volume is changed.
The transaction volume is set as a proxy object.
A backup volume cannot be stopped.
The slices that make up the transaction volume include a temporarily separated slice or a slice being copied.
An SDX object that does not support the OPC function is specified.
All available backup volumes are in a mirroring structure.
The transaction volume belongs to a mirror group connected to any subordinate group.
An SDX object is in the root class.
If a backup volume satisfies any of the following conditions, it is not selected as the backup destination because it cannot be used as a proxy object of the transaction volume even if it is specified as the backup destination.
The backup volume is not the same class as the transaction volume.
The slices that make up the backup volume include a temporarily separated slice or a slice being copied.
The backup volume is set as the master object associated with another proxy of GDS.
The backup volume is mounted.
The backup volume is a logical volume whose size is different from that of the transaction volume.
The backup volume is in a mirroring structure.
No disk is connected directly to the backup volume.
Backup with the output destination backup volume specified cannot be performed in the following circumstances:
An ordinary volume is specified as the transaction volume and a GDS logical volume as the backup volume.
A GDS logical volume is specified as the transaction volume and an ordinary volume as the backup volume.
Backup cannot be performed in the following circumstances:
In the case of any of the above, you should perform appropriate action according to the [System administrator response] for the error message as displayed.
An SDX object does not satisfy the following conditions:
The state of the mirror volume is ACTIVE.
The state of the SDX disk is ENABLE.
The state of the mirror slice is ACTIVE or TEMP.
Pre-processing and post-processing scripts cannot be executed in the following circumstances
The state of the SDX object slice is TEMP.
swstrestore (Restore execution command)
A GDS transaction volume cannot be restored in the following circumstances:
In the case of any of the above, you should take appropriate action according to the [System administrator response] for the error message as displayed.
In restoration to a transaction volume, the backup volume is not the proxy object of the transaction volume.
In restoration to a transaction volume, the transaction volume cannot be stopped.
In restoration to a transaction volume, the target backup volume cannot be stopped.
Restoration with OPC cannot be performed for a GDS transaction volume in the following circumstances:
In these cases, only software-copy is available. To use the software-copy function of GDS, specify the -Xgds-softcopy option.
A GDS logical volume that does not support the OPC function is specified.
The backup volume belongs to a mirror group connected to any subordinate group.
An SDX object is in the root class.
If swstrestore (Restore execution command) using the software-copy function of GDS is suspended, such as for a forced termination, the started software-copy processing continues. In this case, wait for the software-copy processing to finish, and then execute swstsrsemtch (Resource match command).
If the transaction volume is a slice of an SDX object and it is not a single volume, restoration using this command cannot be performed. This is because advanced copy cannot be performed on a mirror volume.
For restoration to the transaction volume of an SDX object, follow the procedure below.
Confirm the backup volume by using the backup history list view swsthistdisp (History information display command).
For restoration, use the "dd" command to copy data to the volume.
Note the following about the replication operation of SDX objects.
swsrpsetvol (Replication volume information setting command)
Replication volume information for the replication operation of an SDX object cannot be set in the following circumstances:
An SDX object and slice, or an SDX object and a volume of another OS are specified.
A logical volume and the n option are specified.
The original volume and replica volume belong to different classes.
The original volume and replica volume belong to the same group; alternatively, in operation of single volumes, they belong to the same single disk.
swsrpdelvol (Replication volume information deletion command)
If the original volume and replica volume are bound, or if they are separated when a copy session exists, the replication volume information cannot be deleted.
swsrpstartsync (Synchronous processing start command)
If any of the following is true, swsrpstartsync (Synchronous processing start command) in the replication operation of an SDX object cannot be executed:
The copy source volume and copy destination volume are in the master-proxy relationship when synchronous processing is started.
The copy source volume and copy destination volume have not been separated from their master-proxy relationship when synchronous processing is resumed.
The copy source volume and copy destination volume belong to different classes when synchronous processing is started.
The copy source volume and copy destination volume belong to the same disk group or single disk.
The copy source volume satisfies any of the following conditions:
The volume contains any temporarily separated slice or slice that is being copied.
The copy source volume is a proxy object when synchronous processing is started.
Copy processing with another volume is in progress.
The copy destination volume satisfies any of the following conditions:
The volume is in a mirroring structure and the -Xgds-softcopy or -Xgds-selectcopy option is not specified when synchronous processing is started. The volume cannot be stopped.
The volume is a master volume when synchronous processing is started.
The volume contains any temporarily separated slice or slice that is being copied.
The volume is a proxy of another master.
The hardware copy function is not available (excluding cases when the -Xgds-softcopy or -Xgds-selectcopy option is specified). The typical causes are:
EC/REC of the ETERNUS Disk storage system is not properly set.
The copy source volume belongs to a mirror group connected to any subordinate group.
The copy destination volume is in a mirroring structure.
The volume is in the root class.
In the replication operation of an SDX object registered with the replication function, do not use the "sdxproxy" command directly to change the state of the SDX object. Otherwise, the "sdxproxy" command may create an inconsistency between the management information of the replication function and the actual object state. In this case, use swsrpcancel (Replication cancellation command) to cancel the replication operation.
Note the following for the replication operation of an SDX object:
Replication cannot be started in the following cases:
The copy destination volume is an SDX object and the status of the SDX object is not as follows:
Mirror volume is either ACTIVE or STOP
Mirror slice status is either ACTIVE or STOP
If the copy destination volume is an SDX object that is not a single volume, replication using this command cannot be performed. Therefore, if either the original volume or replica volume is an SDX object that is not a single volume, you can perform replication only from an SDX object to a non-SDX object.
To copy data to a volume that is an SDX object but not a single volume, use the dd command.
swsrpmake (Replication creation command)
If any of the following is true, replication in the replication operation of an SDX object cannot be created:
The copy source volume and copy destination volume are in the master-proxy relationship in snapshot replication.
The copy source volume and copy destination volume belong to different classes in snapshot replication.
The copy source volume and copy destination volume belong to the same disk group or a single disk in snapshot replication.
The copy source volume satisfies any of the following conditions:
The volume contains any temporarily separated slice or slice that is being copied, in snapshot replication.
The copy source volume is a proxy object in snapshot replication.
Copy processing with another volume is in progress.
The copy destination volume satisfies any of the following conditions:
The volume is in a mirroring structure in snapshot replication.
The volume could not be stopped in snapshot replication.
The volume is a master volume in snapshot replication.
The volume contains any temporarily separated slice or slice that is being copied, in snapshot replication.
The volume is a proxy of another master in snapshot replication.
The OPC function is not available for snapshot replication. The typical causes are:
OPC of the disk array unit is not properly set.
EC/REC in the equivalency maintenance state or suspended state is between the specified copy source volume and another proxy. However, advanced copy can be set in units of mirror slices, which makes it possible to set advanced copy for as many copy destination volumes as the number of mirror slices of the copy source volume at the same time. Therefore, this error occurs as the result of an attempt to set advanced copy for a greater number of copy source volumes than the number of mirror slices.
The copy source volume belongs to a mirror group connected only to some subordinate groups but not directly to a disk. The copy source volume belongs to a mirror group connected to any subordinate group.
The copy destination volume is in a mirroring structure.
The volume is in the root class.
In the replication operation of an SDX object registered with the replication function, do not use the "sdxproxy" command directly to change the state of the SDX object. Otherwise, the "sdxproxy" command may create an inconsistency between the management information of the replication function and the actual object state. In this case, use swsrpcancel (Replication cancellation command) to cancel the replication operation.
Replication cannot be performed in the following circumstances:
The copy source volume is an SDX object for replication of an SDX object, and the SDX object is not in the following states:
The state of the mirror volume is either ACTIVE or STOP.
The state of the mirror slice is either ACTIVE or TEMP.
The state of the SDX disk is ENABLE
The copy destination volume is an SDX object, and the SDX object is not in the following states:
The state of the mirror volume is either ACTIVE or STOP.
The state of the mirror slice is either ACTIVE or STOP.
If the copy destination volume is an SDX object that is not a single volume for the replication operation for an SDX object, replication using this command cannot be performed. Therefore, if either the original volume or replica volume is an SDX object that is not a single volume, you can perform replication only from an SDX object to a non-SDX object.
To copy data to a volume that is an SDX object but not a single volume, use the dd command.
Preprocessing of the copy source volume is not performed in the following circumstances.
The state of the slice of the SDX object is TEMP.
swsrpcancel (Replication cancellation command)
If any of the following is true, replication in the replication operation of an SDX object cannot be cancelled:
The pair of the target replication volume used for replication cancellation is in the equivalency maintenance state, and copy processing between the copy source volume and another volume is in progress.
If replication cancellation is executed at either of the following times during the replication operation of an SDX object, the copy destination volume enters the invalid data state (INVALID):
When snapshot replication is neither in the equivalency maintenance state nor copy established state
When data copy processing of snapshot processing is in progress
Restart synchronous processing or snapshot processing, and the volume will enter the stop state (STOP), which will automatically clear the data invalid state.
To restore the state using an alternative method, refer to Section F.1.3, "Errors Related to Volume Statuses", in the "PRIMECLUSTER(TM) Global Disk Services User's Guide (Solaris(TM) Operating Environment)", and perform appropriate action.
Synchronous processing in the equivalency maintenance state cannot be stopped in the following circumstances:
The copy source volume is an SDX object, and the SDX object is in any of the following states:
The state of the mirror volume is either ACTIVE or STOP.
The state of the mirror slice is either ACTIVE or TEMP.
The state of the SDX disk is ENABLE.
Note: If the mirror slice is in the TEMP state, pre-processing of the original volume is not performed.
The file system is mounted in an environment where the copy source volume or copy destination volume makes up a SynfinityFILE of a multi-volume structure. In such cases, unmount the file system, and process all of the volumes that make up the SynfinityFILE.
