The following prerequisites are for snapshotting and replicating Hitachi Block volumes:
- A machine (known as an ISM) must be assigned that controls the Block storage device. This node is a Windows or Linux machine with the client software installed.
- All primary data (paths or application data) to snapshot or replicate within the same data protection policy must exist on the same storage device.
- The block storage system must:
- Support the data protection technologies you intend to use.
- Have the correct firmware version installed.
- Have the correct SVOS version installed.
- For all replication types, the P-VOLs must be set up in the host group.
- To resize logical devices represented by the Block Host node that are part of a replication or snapshot pair, the array account must have the Support Personnel permission.
- For GAD, the quorum disks or quorum-less disks must be provided. In most cases, one quorum device between participating storage systems is satisfactory. For best practices see the Global-Active Device User Guide.
- For GAD, configure the storage system to allow virtualized LDEVs if they are required (where supported by the storage system).
- Port security must be enabled.
- Primary volumes must be set up using other Hitachi management tools.
- For application consistent snapshots, the application must be installed and configured to use P-VOLs on a storage system. For details on the application configuration, see the associated application guide.
- The password for authorizing a Block Device node must contain only useable CCI command characters: A-Za-z0-9’-./:@\_
- The device must have adequate shared memory (see Provisioning and Technical Guides).
- Pools must be created in another tool before selecting
a data protection target storage system:
- For standard mode (non-cascading) TI, the TI Pools must be set up.
- For cascade mode TI, the Dynamic Provisioning Pools must also be set up as a hybrid pools, otherwise a TI pool is also required.
- For SI, TC, UR and GAD, the Dynamic Provisioning Pools must be set up.
- The following licensed features may be required depending on the features being used:
- Dynamic Provisioning.
- Storage Navigator.
- Thin Image (for TI snapshot and RTI replication scenarios).
- ShadowImage (for SI replication scenarios).
- TrueCopy (for TC replication scenarios).
- Universal Replicator (for UR replication scenarios).
- Global-Active Device (for GAD replication scenarios).
- Remote Replication Extended (for 3DC scenarios).
- The ISM node controlling the block storage device must have:
- The correct version of Hitachi CCI installed.
- A dedicated user for use with the data protection software (specified when creating the Hitachi Block Device node) must be created on the storage device with a minimum of the following roles:
- Storage Administrator (Provisioning)
- Storage Administrator (Local Copy)
- Storage Administrator (Remote Copy)
- Security Administrator (View and Modify)
The user must also have access to Resource Group 0 on the storage device.
- Fibre connectivity (including zoning) or iSCSI connectivity and pre-configured RCU paths between storage systems for remote replication technologies is required.
- If physical and software block devices are being configured in a single environment, it is essential that they do not share an ISM node.