Note Following Points about Operation with SDX Object in Units of Logical Volumes
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.
Note Following Points about Operation with SDX Object in Units of Logical Volumes
Backup synchronous processing of a PRIMECLUSTER GD 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 Corrective 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 PRIMECLUSTER GD is available. To use the software-copy function of PRIMECLUSTER GD, 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 PRIMECLUSTER GD.
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).
Note Following Points about Use with SDX Object in Units of Logical Volumes
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 automatically clears the data invalid state.
To use an alternative method to restore the state, refer to "Errors Related to Volume States" in the PRIMECLUSTER Global Disk Services User's Guide (Solaris(TM) Operating System), and perform appropriate action.
Note Following Points about Use with SDX Object in Units of Logical Volumes
Backup of a PRIMECLUSTER GD 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 Corrective 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 PRIMECLUSTER GD.
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 PRIMECLUSTER GD logical volume as the backup volume.
A PRIMECLUSTER GD logical volume is specified as the transaction volume and an ordinary volume as the backup volume.
Note Following Points about Operation with SDX Object in Units of Slices
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 Corrective Action] 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.
Note Following Points about Operation with SDX Object in Units of Logical Volumes
A PRIMECLUSTER GD 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 Corrective Action] 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 PRIMECLUSTER GD transaction volume in the following circumstances:
In these cases, only software-copy is available. To use the software-copy function of PRIMECLUSTER GD, specify the -Xgds-softcopy option.
A PRIMECLUSTER GD 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 the swstrestore command using the software-copy function of PRIMECLUSTER GD 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 the swstsrsemtch command.
Note Following Points about Operation with SDX Object in Units of Slices
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 or swsthistdisp command.
For restoration, use the "dd" command to copy data to the volume.
