Veritas InfoScale 7.3.1 What's New Guide - Windows
- What's new in this release of Veritas InfoScale
- About this document
- New features and changes in this release
- Change in upgrade path
- 256-bit encryption for enhanced security
- The NIC and the IP agents can monitor network adapters based on GUID
- Updated auto-import functionality of dynamic disk groups
- VxVM support for hardware cloning
- Added support for DMP DSMs
- Support for Veritas InfoScale Storage deployments on Amazon Web Services (AWS) cloud
- Support for setting up replication across clouds
- Support for configuring applications for HA in Azure cloud using InfoScale Enterprise
- New High Availability agents for Azure environment
- Support for configuring applications for HA in AWS cloud using InfoScale Enterprise
- New High Availability agent for Amazon Web Services (AWS)
VxVM support for hardware cloning
Advanced disk arrays provide methods to create clones or copies of physical volumes (disks or LUNs) from the hardware-side. Using the hardware cloning technology, you can create a hardware snapshot (such as an EMC BCV™ or Hitachi ShadowImage™), a hardware mirror, or a hardware clone.
If a disk that you plan to clone is under SFW control, the data that is stored in the private region of the disk is also copied. As a result, the disk id in the private region of the original disk and the cloned disk remains same. Also, the VxVM disk group becomes a duplicate of the original disk group.
In order to identify a cloned disk, a unique and persistent attribute called the Veritas Device Identifier (VDID) is added to the private region of every disk. For a disk in which the original VDID differs from the one in the private region, a vdid_mismatch flag or a "shadow" flag is added to the private region. Such a disk is considered as a cloned disk.
Now, if standard (non-cloned) disks in a disk group are already imported, you cannot simultaneously import the cloned disks in the same disk group. VxVM does not support a disk group with both clone and non-clone disks. If you want to import the cloned disks, you must specify a new disk group name for the disk group containing the cloned disks. During the import process, the vdid_mismatch flag and the shadow flag are cleared from the disks in the new disk group. The new disk group becomes a standard disk group, and the disks become the standard disks.
Notes:
The functionality to import a cloned disk group is disabled by default. To enable the functionality, you must set the SupportVDIDTOC registry key value to 1, and then restart the vxsvc service.
The SupportVDIDTOC registry key is located under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vxboot\VDID.
Currently, you cannot import a cloned disk group if your disk groups contains volume layout type Mirrored with Stripped.
If the process to import a cloned disk group fails or if you intend to import a cloned disk group on a new host, you must first update the VDID in the private region and then import the disk group.
For more details about importing a cloned disk group and updating the VDID, see Storage Foundation 7.3.1 Administrator's Guide-Windows.