For proxy object related errors, in one of the following circumstances, take the actions as indicated for the relevant situation.
(1) The Advanced Copy function cannot be used in master-proxy copying.
Explanation
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 ETERNUS Disk storage system, the GDS soft copy function is performing the copy operation.
The following eight possible causes can create a situation where the Advanced Copy function is not used.
The disk array unit's Advanced Copy mechanism was not configured properly.
After GDS Snapshot was installed, the node was not rebooted.
EC or REC sessions exist between the master and another proxy and OPC or QuickOPC function cannot be used.
Multiple proxy volumes are related to a master volume, and the number of proxy volumes with EC or REC session settings has reached the upper limit (16 volumes).
The mirroring configuration of proxy volumes is two-way or more multiplex mirroring.
The group to which master volumes or proxy volumes belong has a lower level group connected.
The disk array unit to which the master or the proxy belongs does not support the Advanced Copy function.
An error occurred in the disk array unit or the Fibre Channel route.
For details, see "A.8 Using Advanced Copy Function in Proxy Configuration."
Resolution
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), set up the disk array unit's Advanced Copy feature.
In the event of (Cause b), reboot all nodes in the cluster system.
In the event of (Cause c) or (Cause d), 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 e) to (Cause g), according to need, select another object, or change the object configuration.
In the event of (Cause h), recover the disk array unit error or the Fibre Channel route error.
(2) Alternative boot environment setup fails resulting in an error numbered 60305. [EFI]
Explanation
In a situation where the master group in the root class includes a volume that is not declared in the /etc/fstab file as a file system or a swap area, if the proxy group is specified and the sdxproxy Root command is executed, the following error message is output and the command fails.
sdxproxy: ERROR: Proxy_Volume_Name: corresponding volume not specified in /etc/fstab
If the current boot is from the proxy group, an event that the "master" and the "proxy" above are exchanged occurs. In this event, exchange the "master" and the "proxy" as shown in [Resolution] below and take action as indicated.
Resolution
In the examples shown below, the following configuration is assumed.
The root class is Class1.
The master group is mg1.
Master volumes in mg1 are mv1, mv2, and mv3.
Among mv1, mv2, and mv3, mv2 is not declared in /etc/fstab.
The proxy group is pg1.
Proxy volumes in pg1 are pv1, pv2, and pv3.
mg1 and pg1, mv1 and pv1, mv2 and pv2, and mv3 and pv3 are related respectively.
The root volume is mv1.
The alternative boot volume is pv1.
With this configuration, the following error occurs.
# sdxproxy Root -c Class1 -p pg1
sdxproxy: ERROR: pv2: corresponding volume not specified in /etc/fstab |
Choose one of the methods shown as (Resolution a) and (Resolution b) to take action.
(Resolution a)
Among proxy volumes in the proxy group, specify only volumes that meet the following conditions and execute the sdxproxy Root command.
The proxy volume of the master volume that is declared in the /etc/fstab file.
The master volume of the proxy volume that is declared in the /etc/fstab file.
A proxy volume related to the master volume of the proxy volume that is declared in the /etc/fstab file.
Example)
# sdxproxy Root -c Class1 -p pv1,pv3 |
(Resolution b)
Following the procedures below, add descriptions of all volumes in the master group to the /etc/fstab file and execute the sdxproxy Root command and then delete unnecessary descriptions from fstab.
1) Among master volumes in the master group, add descriptions of volumes not currently declared in /etc/fstab to this file.
Example) Add mv2 to /etc/fstab.
2) Create an alternative boot environment.
Example)
# sdxproxy Root -c Class1 -p pg1 |
3) Delete the descriptions of volumes added in step 1) from /etc/fstab.
4) Mount the alternative root volume on a temporary mount point (such as /work) and delete a description of the alternative volume of the volume added in step 1) from /work/etc/fstab.
Example) Mount pv1 on /work and delete a description of pv2 from /work/etc/fstab.
5) Unmount the alternative root volume.
Example) Unmount pv1.
