PRIMECLUSTER GDS (hereinafter referred to as GDS) is software whose main function is mirroring disk units.
AdvancedCopy Manager can backup and replicate the SDX objects of GDS.
SDX objects are virtual resources managed by GDS, and they include classes, groups, disks, volumes, and slices.
AdvancedCopy Manager can backup and replicate SDX objects in units of logical volumes or slices.
The format used to specify a device name in AdvancedCopy Manager is different depending on whether units of logical volumes or units of slices are to be used. Specify a device name as follows:
/dev/sfdsk/<class name>/dsk/<volume name>
/dev/sfdsk/<class name>/dsk/<volume name>:<device name used for volume configuration>
Either of the following is used as the device name for volume configuration:
Example:
sda |
Example:
/dev/disk/by-id/xxxxxxxx (xxxxxxxx is the information generated from the identification information set in the disk) /dev/disk/by-path/yyyyyyyy (yyyyyyyy is the information generated from the disk location information.) |
The udev device name takes priority and is used in environments that have udev device names. The by-id name and by-path name can be used in udev device names, but the by-id name takes priority and is used in environments that have both by-id names and by-path names.
If the environment contains udev device names but you want to use the sdxinfo DEVNAM value for operations, then before the device information collection and reflection processing is performed, you must change the information collection mode so that udev device names are not used.
Refer to "stgxfwcmsetmode (Information collection mode configuration command)" for details.
When the class name is 'class1', the volume name is 'volume1', the sdxinfo DEVNAM value is 'sda', and the udev device name indicated by sda is /dev/disk/by-id/SFUJITSU_MAP3367NC_UPP4P4307J95
/dev/sfdsk/class1/dsk/volume1
/dev/sfdsk/class1/dsk/volume1:sda
/dev/sfdsk/class1/dsk/volume1:/dev/disk/by-id/SFUJITSU_MAP3367NC_UPP4P4307J95
Note
To use the udev device name in an environment in which the ETERNUS multi-path driver is installed, enable use of the by-id name.
If the by-id name has not been generated, modify the settings so that it is generated.
Note
Note the following points when using the udev device name in an environment in which the ETERNUS multi-path driver is not installed.
The udev device name may change if by-id is used and disks are exchanged, or if by-path is used and the connection configuration is changed. If the udev device name has been changed, perform the steps described in "7.5.5 Changing the device configuration".
Note
PRIMECLUSTER GDS 4.1A30 or later and PRIMECLUSTER GDS Snapshot 4.1A30 or later are required to perform separate operations for each logical volume.
Operation in units of logical volumes and operation in units of slices at the same time on a single Managed Server is not possible. Note that for cluster operations, operating in units of logical volumes or in units of slices is possible in separate Managed Server transactions.
For details on backup of SDX objects, refer to "3.8 SDX Object Operations". For details on replication of SDX objects, refer to "6.8 SDX Object Replication".
Note that the software versions and levels vary in accordance with the environment at the installation destination system. Refer to the relevant software manuals for details.
