V11 SP8

Configuring the HDS CCI Engine on the Array Console

For the VMware agent, the following apply:

  • The Virtual Server Agent client computer can be a Windows physical server or a Windows virtual machine (VM), with Hitachi Data Systems (HDS) Command Devices exposed through physical Raw Device Mapping (RDM).
  • For storage area network (SAN) mode, the Virtual Server Agent client computer must be a physical server.
  • Verify that all HDS prerequisites are installed and configured on the Virtual Server Agent client computer.
  • Expose HDS Command Devices to the Virtual Server Agent's proxy computer.


To configure the HDS Command Control Interface (CCI) engine on the Array Console, complete the following tasks:

  1. Before changing any settings or mapping or unmapping a Command Device, shut down all Hitachi Open Remote Copy Manager (HORCM) instances that Commvault created.
  2. Configure enough destination ShadowImage volume (S-VOL) devices to meet your retention requirements.
  3. For each host computer that is connected to the storage array, complete the following steps to configure a Command Device:

    • On the Command Device interface, select the User Authentication attribute.
    • On the Command Device interface, clear the Command Device Security and Device Group Definition attributes.
  4. For Thin Image (TI) operations on the Virtual Storage Platform (VSP) and on the Hitachi Unified Storage Virtual Machine (HUS VM) series, do the following:
    1. Create TI pools.
    2. Unmap the virtual volumes (V-VOLs) that the TI snapshot backup will use.
    3. Create V-VOLs that match the exact block size of the production volume (P-VOL) devices. For V-VOLs to be created automatically by the IntelliSnap feature, select the snapshot configuration property Create VVOLs for Thin Image in Array Management.
    4. For the Hitachi virtual storage machine (VSM) storage array, use volumes that belong to the VSM resource group.
  5. For ShadowImage (SI) operations on the VSP series and on the HUS VM series, create S-VOL devices that match the exact block size of the P-VOL devices.

    Do not map existing S-VOL devices unless you also select the Use preexisting clones property in the Snap Configuration tab.