PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System) |
Contents |
Appendix F Troubleshooting | > F.1 Resolving Problems |
For proxy object related errors, in one of the following circumstances, take action as indicated for the relevant situation.
The method handling copying from a master to a proxy can be checked in the CPTYPE field that is displayed with the sdxinfo command. When the CPTYPE field displays soft, instead of the Advanced Copy function of Fujitsu Storage Systems ETERNUS, the GDS soft copy function is performing the copy operation.
# sdxinfo -S -e long -o pv1 OBJ NAME CLASS GROUP DISK VOLUME JRM MODE STATUS COPY CURBLKS COPYBLKS DLY CPTYPE CPSOURCE ------ ------------ ------- ------- ------- ------- --- ---- -------- ---- -------- -------- --- ------ -------- slice * Class1 Group1 Disk1 pv1 * * COPY run 93952 10027008 0 soft * |
The following ten possible causes can create a situation where the Advanced Copy function is not used.
For details, see "Using the Advanced Copy Function in a Proxy Configuration "
Check the disk array settings and the GDS object configuration and identify the cause, and take the following actions according to the cause.
In the event of (Cause a), follow the procedures below.
Configure the disk array unit's Advance Copy mechanism.
Back up master and proxy volume data if necessary.
Delete the disks constituting the master and the proxy from their classes.
Register the disks deleted from the classes in step 3) back to the classes.
Create master and proxy volumes and restore the data backed up in step 2) as needed.
In the event of (Cause b) or (Cause c), follow the procedures below.
Back up master and proxy volume data if necessary.
Among the disks constituting the master and the proxy, delete disks registered with classes before configuring the Advance Copy mechanism or installing GDS Snapshot from their classes.
Register the disks deleted from the classes in step 4) back to the classes.
Create master and proxy volumes and restore the data backed up in step 1) as needed.
In the event of (Cause d), follow the procedures below.
Reboot the node.
Back up master and proxy volume data if necessary.
Delete the disks constituting the master and the proxy from their classes.
Register the disks deleted from the classes in step 3) back to the classes.
Create master and proxy volumes and restore the data backed up in step 2) as needed.
In the event of (Cause e) or (Cause f), take the following action (Resolution 1) or (Resolution 2).
(Resolution 1)
Part a proxy with EC or REC session settings from the target master.
Cancel EC or REC sessions of step 1) using the sdxproxy Cancel command.
(Resolution 2)
Cancel the relationship between the target master and a proxy with EC or REC session settings.
In the event of (Cause g) to (Cause i), select another object, or change the object configuration.
In the event of (Cause j), recover the disk array unit error or the Fibre Channel route error.
Contents |