Note Following Points about Operation with SDX Object in Units of Logical Volumes
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.
Note Following Points about Operation with SDX Object in Units of Logical Volumes
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.
Note Following Points about Operation with SDX Object in Units of Logical Volumes
If any of the following is true, the swsrpstartsync 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 the swsrpcancel command to cancel the replication operation.
Note Following Points about Operation with SDX Object in Units of Slices
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.
Note Following Points about Operation with SDX Object in Units of Logical Volumes
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 the swsrpcancel command to cancel the replication operation.
Note Following Points about Operation with SDX Object in Units of Slices
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.
Note Following Points about Operation with SDX Object in Units of Logical Volumes
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 enters the stop state (STOP), which automatically clears the data invalid state.
To restore the state using an alternative method, refer to "Errors Related to Volume Statuses" in the PRIMECLUSTER Global Disk Services User's Guide (Solaris(TM) Operating Environment), and perform appropriate action.
Note Following Points about Operation with SDX Object in Units of Slices
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 PRIMECLUSTER GFS local file system is mounted in an environment where the copy source volume or copy destination volume makes up the PRIMECLUSTER GFS local file system of a multi-volume structure. In such cases, unmount the PRIMECLUSTER GFS local file system, and process all of the volumes that make up the PRIMECLUSTER GFS local file system.
