Onboard the primary and secondary storage systems in Ops Center Protector.
- To add a block node to the nodes inventory, click Nodes in the navigation sidebar. Click the plus sign (+).
- In the Create Node window, select Storage. Select Hitachi Block Device as the storage type to launch the Hitachi Block Storage Node wizard. Follow the wizard prompts to complete the workflow.
- Specify the node name, select the check box to confirm the requirements, and then click Next.
- Select the resource group to which this node is allocated for the purposes of RBAC and click Next. All nodes are automatically allocated to the 'default' resource group.
- Select an Ops Center Protector node to act as a proxy and click Next.
Note: The proxy node is responsible for interfacing with the block storage system. It can be a Windows or Linux machine with the Ops Center Protector Client software installed and must be connected using a command device to the Block storage system. The command device must only have user authentication enabled. The proxy node must have supported version of CCI installed. See the Command Control Interface Installation and Configuration Guide for more information.
- Enter the directory location on the proxy node where Ops Center Protector can place metadata files related to Block snapshots and replications. Click the Browse button to open the Path window if required.
Note: The metadata directory is defined once for this proxy and all storage nodes on this proxy will use this setting. It cannot be changed after initial configuration.
- Specify the storage system. You can either select from detected storage systems or specify the IP address of a storage system.
Note: For HUS VM storage systems, use the IP address of the SVP. For VSP storage systems, use the IP address of CTL1 or CTL2. DO NOT use the IP address of the SVP.
- Specify the credentials for the storage system.
Enter the username and password for the Block storage.Note:
- The username specified must be a member of the Storage Administrator (Provisioning, Local Copy, Remote Copy) and Security Administrator (View Only, View and Modify) on the Block device. If the Block storage cannot be accessed or its credentials are invalid then the node will fail authorization. The configuration wizard can be reopened to correct any errors.
- The password for authorizing a Block storage system must contain only CCI command characters: A-Zaz0- 9'-./:@\_
-
Specify the LDEV Provisioning Range. You can select one of the following options:
- All: Select this option if you want Ops Center Protector to automatically detect the LDEV range from which snapshots and replications should be allocated.
- User defined: Select this option if you want to manually specify the LDEV range from which snapshots and replications should be allocated.
- Start: Enabled only if User defined is selected. Enter the lower limit of the LDEV range to use for allocation.
- End: Enabled only if User defined is selected. Enter the upper limit of the LDEV range to use for allocation.
-
Specify the command device specification and priority.
If no command devices are specified, Ops Center Protector will attempt to control the hardware storage device using any fibre connected command device, available to the Proxy Node specified, in an order specified by HORCM. If one or more command devices are specified, Ops Center Protector will attempt to control the hardware storage device using a command device in the order specified by the user. If the first command device fails, Ops Center Protector will progress to the next. If all specified command devices fail then the operation fails. Ops Center Protector will not attempt to use any command devices that are not specified, even if they are available.
For example, it is possible to specify a specific fibre command device, followed by any fibre command device, followed by a specific IP command device.
-
Configure the command device.
- Fibre: You can either use any available fibre command device or select from detected fibre command devices.
- IP: Enter the IP address and port number of the command device.
Note: When configuring IP command devices for VSP storage devices, we recommend adding one for CTL1 and one for CTL2, to maintain dual redundancy. For HUS VM storage devices, use the IP address of the SVP. For VSP storage devices, use the IP address of CTL1 or CTL2. DO NOT use the IP address of the SVP. -
Specify the LDEV ranges for each VSM.
Note: Note: global-active device replications require P-VOLs and S-VOLs to have matching virtual serial numbers and virtual LDEV IDs. To avoid virtual LDEV ID collisions between global-active device volumes and non-global-active device S-VOLs (created by Ops Center Protector for other types of replications and snapshots), it is possible to define virtual LDEV ID ranges to be used by those non-global-active device operations. Virtual LDEV ranges can be specified for each VSM (Virtual Storage Machine) to be used.
-
Configure the virtual LDEV range.
- Enter the VSM serial number.
- Enter the lower limit of the LDEV range to use for allocation.
- Enter the upper limit of the LDEV range to use for allocation.
-
Specify the ports used for provisioning.
Enter the port identifier in the following format:
CLc-s
where:
- c is the physical channel number in the range 1 …n
- s is the physical slot number in the range A … Z Note: If more than one provisioning port is selected, the port with the fewest LUNs will be used.
- Review the summary of the Block storage system and click Finish.