Snapshot Configuration Properties for the Hitachi Vantara Storage Array

COW pool ID

The copy-on-write (COW) pool that is used for COW snapshot creation.

You can specify the COW pool ID using the Storage Device Group, but precedence is given to the specification in COW Pool ID. If this property is empty, then 0 is used.

Storage device group

The name of the device group created on the array that you want to use for snapshot operations.

The name must be either COW_pool_ID-label or label-COW_ pool ID.

Notes:

• The COW pool ID and the label must be separated by hyphen.

• The COW pool ID must be a number.

• The label must not contain any special characters and must not start with a number.

• Use the COW pool ID only for COW jobs. Use the label for ShadowImage (SI) jobs.

• If COW pool ID is blank, use 0.

Use devices only from this group

If you select this option, then devices whose label matches for SI jobs are used. IntelliSnap operations select ShadowImage volume (S-VOL) with label match. If no label match is found against S-VOL, then the SI job fails.

Enable incremental resync of ShadowImage pairs using aged clones

Select this option to incrementally resynchronize SI pairs that are created and aged by Hitachi Vantara IntelliSnap, instead of incrementally resynchronizing the existing SI pairs.

Always select DP volumes as S-VOL

Select this option to enable Dynamic Provisioned (DP) volume for SI operation.

If you select this option, but no DP volume is available, then snapshot operations fail.

Enable XML message tracing

Select this option to send XML request and response to all Hitachi Vantara snapshot operations.

HORCM installation home directory path (Windows only)

If Hitachi Open Remote Copy Manager (HORCM) is not installed in the default location (C:/HORCM/etc), then enter the installation path in this property.

Name of HDvM client as visible in HDvM server, if it differs from the client name

If the host name of the Hitachi Device Manager (HDvM) client is different from the name that is available on the HDvM server, then enter the host name of the HDvM client in this property.

Enable quick resync capability (if applicable)

If you select this option, then Hitachi Vantara IntelliSnap does not wait until the pair copy reaches 100%. Instead, the S-VOL can be used almost immediately to mount and perform a backup operation.

This property reduces the time to complete a Hitachi Vantara IntelliSnap backup job.

Do not use HDvM agent for Mount/Unmount

When selected, new devices on the host computer or on the proxy computer are detected or cleaned up with the CCI method, bypassing the HDvM agent.

S-VOL LDEV nickname (max 20 characters) (CCI engines)

The S-VOL nickname. TI and SI jobs select S-VOLs that match this nickname.

Note: The nickname can have up to 20 characters, including alphanumeric, _ (underscore), or - (hyphen) characters. The nickname should not start with “IS_SVOL_”.

CU range to be used to pick S-VOLs (CCI engines)

The range within which Thin Image (TI) jobs and SI jobs select an S-VOL with ldev_id.

The Control Unit (CU) range is a hexadecimal comma-separated value, such as 2-5 and 8-C.

You can use this property in conjunction with the S-VOL logical device (LDEV) nickname.

If your environment involves VSMs from multiple physical arrays, then you must set different CU range on the VSM array entries to avoid LDEV ID conflict during V-VOL\S-VOL creation.

The S-VOLs are created within the specified CU range during the instant clone operation.

Create VVols for Thin Image (CCI TI engine)

Select this option to enable the automatic creation of TI snapshot virtual volumes (VVoLs).

You can use this property in conjunction with the CU range and the TI pool name.

TI pool to be used for VVoLs (CCI TI engine)

The name of the pool in which TI snapshot data is created.

If you don't specify a TI pool name, then TI snapshot jobs fail.

DP pool to be used for S-VOLs (CCI engines)

The DP pool from which S-VOLs are selected.

If no DP volume that matches other filter criteria is found in this pool, then the job fails.

If TI snapshot backups are run in cascade mode, the DP pool will be used for the creation of the S-VOL needed during the TI snapshot backup.

The DP pool will also be used to create S-VOL during instant clone operation.

Always select DP volumes as S-VOL (CCI SI engine)

If you select this option, then only DP volumes are selected as S-VOLs.

Use preexisting clones (CCI SI engine)

If you select this option, then the job selects SI pairs that are created by the user.

This option ignores all the other selection criteria that are described on this page.

Pairs are automatically used for incremental resynchronization after aging.

To select a specific mirror, use this option in combination with S-VOL LDEV nickname.

Enable incremental resync using aged clones (CCI SI engine)

Select this option to enable the incremental resynchronization of SI pairs that are created and aged by Hitachi Vantara IntelliSnap.

Enable quick resync capability (CCI SI engine)

Select this option to enable quick resynchronization capabilities.

You can manage SI pairs by using the Hitachi Vantara quick resynchronization command with the -quick option.

Enable quick restore capability (CCI SI engine)

Select this option to enable quick restore capabilities.

You can use the Hitachi Vantara quick restore command with the -quick option to perform hardware restore operations for SI pairs.

HostGroup to which S-VOLs will be presented (CCI engines)*

A list of host groups to which S-VOLS are presented, which overrides the default setting of S-VOLs that are mapped to the host group where the command device is mapped.

If a proxy host exists, specifies the proxy host’s host group.

If you run the mount operation from the GUI, then the specified host group is not used by the operation. For more information on GUI mount, refer to Advanced.

Notes:

• The host group name has the format port-name.

• The HostGroup list items must be separated by commas.

Enable command logging for troubleshooting (CCI engines)

Select this option to save the command control interface (CCI) command output in the <base>/temp folder for troubleshooting.

HORCM installation home directory path (CCI engines)

The full path where CCI commands are installed (for example, C:\mydir\HORCM\etc).

If you change this path, then restart CVMA services.

HORCM instance number to be used for Raidcom commands (CCI engines)

A user-created HORCM instance number to be used by Raidcom commands. If multiple arrays are configured in your environment, you must use a separate HORCM instance number and create respective HORCM file for each array.

The engine does not create a HORCM file for the Raidcom command. The HORCM instance is started before Raidcom commands are issued.

Remote Snap MA (CCI engines)

The client name of the MediaAgent that you want to designate as the Remote Snap MediaAgent.

Perform snap of an existing clone (CCI TI engine)

Select this option to perform a TI snapshot operation on an SI S-VOL instead of on a P-VOL.

Use Consistency Group (CCI engine)*

If you select this option, then either a TI pair or an SI pair is created with a consistency group.

Remote replication copy group (CCI engines)

The replication name to use for both the primary copy and the remote copy.

Physical array serial ID (CCI engines)**

The serial ID of the physical array where the Virtual Storage Machine (VSM) array runs.

For physical arrays, the Physical array serial id (CCI engines) property must be empty.

VSM arrays must contain the specification of the serial ID of the physical array to form a global-active device (GAD) pair.

After you add the array in Array Management, you cannot edit the Physical array serial id (CCI engines) property.

Disable GAD operation for the devices (CCI engines)

If you select this option, then only one array of the GAD pair is backed up.

If you don't select this option, then both arrays of the GAD pair are backed up.

By default, this option is selected.

Port for Pre-Snap HostGroup, to which S-VOLs will be presented (CCI engines)

Specifies the pre-snap hostgroup port in which the dummy hostgroup is created.

When specified, the Pre-Snap HostGroup is created on the specified port and snapshots are mapped to it.

When not specified, the dummy hostgroup is created on the same port that the source device is mapped to.

To specify a port, follow these rules:

• Specify only one port.

• To avoid exceeding the maximum limit on a port, specify the port at subclient level.

• The port cannot be part of any resource group or VSM.

• The port must be part of a meta_resource group.

Create primary snap at the replication target site (CCI engines)

The secondary or remote site ID where the primary snapshot is created.

Enable cascade mode for Instant Clone support

When selected, the TI snapshot is created using cascade mode on. This is required to create instant clones for Hitachi TI snapshots.