It explains the each following operating system.
For Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6 and SUSE Linux Enterprise Server 11
The following devices are supported in backup and replication management.
sd driver resources
Multi-path resources (MPLB resources and Device Mapper Multipath resources)
Moreover, the unit of management is a disk partition unit or a Logical Unit (disk) unit.
AdvancedCopy Manager uses the following device names for ordinary devices:
Example:
/dev/sda1 (for disk partition units) /dev/sda (for Logical Unit units) |
Example:
/dev/mapper/*p1 (for disk partition units on RHEL5 or RHEL6) /dev/mapper/*_part1 (for disk partition units on SUSE Linux Enterprise Server 11) /dev/mapper/* (for Logical Unit units)
Example:
/dev/disk/by-id/xxxxxxxx-part1 (for disk partition units) /dev/disk/by-id/xxxxxxxx (for Logical Unit units) (xxxxxxxx is the information generated from the identification information set in the disk.) /dev/disk/by-path/yyyyyyyy-part1 (for disk partition units) /dev/disk/by-path/yyyyyyyy (for Logical Unit units) (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 compatible device names 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.
Note
Refer to "9.1.1.10 Notes on executing Logical Unit (disk) unit copy" if operation is in Logical Unit (disk) units.
The information collection mode can be set for each Managed Server. For the information collection mode, the udev device name and compatible device name cannot be the same in the same Managed Server.
If Device Mapper Multipath device names are used in an environment in which Device Mapper Multipath is installed, configure them so that Device Mapper Multipath device names are used.
Please don't use the compatible device name or udev device name that indicates each path for the multi-path.
If operation is in the Logical Unit (disk) units, the Device Mapper Multipath device cannot be configured.
If using the EC (Equivalent Copy) in the backup management, the Device Mapper Multipath device cannot be defined as the transaction volume and the backup volume.
If using the EC (Equivalent Copy) or REC (Remote Equivalent Copy) in the replication management, the Device Mapper Multipath device cannot be defined as the copy source volume and the copy destination volume.
If udev device names are used in an environment in which ETERNUS multi-path drivers are installed, configure them so that by-id names are used.
If by-id names are not generated, change the settings so that by-id names are generated.
Note the following if udev device names are used in an environment in which ETERNUS multi-path drivers are 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, the steps described in "7.5.5 Changing the device configuration" are required.
For Red Hat Enterprise Linux AS v.4 and Red Hat Enterprise Linux ES v.4
The following devices are supported in backup and replication management.
sd driver resources
Multi-path resources (MPLB resources)
Moreover, the unit of management is a disk partition unit or a Logical Unit (disk) unit.
AdvancedCopy Manager uses the following device names for ordinary devices:
Example:
/dev/sda1 (for disk partition units) /dev/sda (for Logical Unit units) |
Example:
/dev/disk/by-id/xxxxxxxx-part1 (for disk partition units) /dev/disk/by-id/xxxxxxxx (for Logical Unit units) (xxxxxxxx is the information generated from the identification information set in the disk.) /dev/disk/by-path/yyyyyyyy-part1 (for disk partition units) /dev/disk/by-path/yyyyyyyy (for Logical Unit units) (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 compatible device names 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.
Note
Refer to "9.1.1.10 Notes on executing Logical Unit (disk) unit copy" if operation is in Logical Unit (disk) units.
The information collection mode can be set for each Managed Server. For the information collection mode, the udev device name and compatible device name cannot be the same in the same Managed Server.
If udev device names are used in an environment in which ETERNUS multi-path drivers are installed, configure them so that by-id names are used.
If by-id names are not generated, change the settings so that by-id names are generated.
Note the following if udev device names are used in an environment in which ETERNUS multi-path drivers are 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, the steps described in "7.5.5 Changing the device configuration" are required.
