Nodes and Node Groups
Node Concepts
This section describes Ops Center Protector's node management features.
For further information, refer to:
About nodes
The figure below shows how nodes created within the Protector UI are implemented by the Protector Client software installed on servers in the protected environment (see Installation Tasks). These servers communicate directly with physical hardware storage devices and hypervisors that are to be protected or used as backup destinations. One Protector Client can communicate with more than one storage device, however when doing this, many factors must be considered, including hardware performance and system availability.

Protector Client software must be installed on each server participating in the data protection environment. One server has the Protector Master software installed on it and acts as the central controller and the connection point for the web based user interface. Active data protection policies will continue to function with or without the Master being available, because the participating Clients operate autonomously using rules distributed from the Master.
Physical storage devices and hypervisors interface with Protector via servers having Protector Client software installed on them. One Protector Client can be used to communicate with more than one storage device, however when doing this, many factors must be considered, including server hardware performance and the impact on system availability should that server go down.
The physical environment is represented within Protector as nodes created within the Nodes Inventory, these represent data sources and destinations as follows:
- OS Host nodes are automatically added to the inventory. These represent every server that has Protector Master or Client software installed on it. A basic OS Host node can only be used as a file system data source on a data flow and can only support path and disk type classifications.
- Repository nodes require a Protector Client with access to suitable disk storage capacity to act as a host. Repository nodes act as data destinations on data flows performing backup and continuous data protection operations. Repositories are implemented entirely by software processes within the Protector Client. Depending on the backup data change rate and number of policies, servers that host repositories can be subject heavy network, processor and disk I/O loading, so it is important to specify the correct hardware and monitor performance (see About Repositories for further guidance).
- HCP nodes do not require a Protector Client to be specified. They act as data destinations on data flows, but must be accessed via a Repository acting as a cache when performing tiering operations.
- VMware nodes require a Protector Client with network access to the vCenter or ESXi host. These nodes act as data sources on data flows, enabling users to specify VMware specific policies and backup operations to repository or block storage destination nodes.
- Block Device nodes require a Protector Client with block prerequisites installed to act as an ISM (see Hitachi Block prerequisites). Block Device nodes act as both data sources and destinations on data flows, enabling users to specify block specific policies with snapshot and replication operations to other Block Device nodes. Note that Block Host and Logical Block nodes can only be used as data sources.
- Block Host and Logical Block nodes can only be created by specifying a Block Device node upon which they are based. These nodes represent a subset of the resources available on the Block Device node upon which they are based.
- Oracle DB node requires a Protector Client to be installed on the application server. Appropriate prerequisites (detailed in the relevant Protector Application Guide) must also be installed to enable Protector to interact with the application. These nodes act as data sources on data flows, enabling users to specify application specific policies and backup operations to repository or block storage destination nodes.
Removing a node from Protector may require access to the entity that it represents. For example, removing a Block Device node from Protector requires access to the storage system it represents. Therefore, it is not recommended to decommission an entity from the environment until all nodes representing it have been removed from Protector. Removing the nodes from Protector without the hardware may require manual intervention from support.
About node groups
Ops Center Protector allows you to assign machines to groups. A machine can belong to more than one group.
Policies can be assigned to individual machines or to a node group. This feature provides an easy method to manage large sets of machines, eliminating the need to create and assign policies for individual machines.
Once policies have been assigned to a node group on a data flow and activated, the whole group can be monitored easily. You can expand a group to see activity within that group.
About multi-tenancy for Hitachi block storage
Ops Center Protector implements multi-tenancy by limiting which resources each tenant has access to on a block storage device that it shares with other tenants. Each tenant operates within its own environment that is defined using RBAC Resource Groups and their associated Source and Logical Block nodes. Nodes within each tenant's environment are unable to be seen or accessed by other tenants, despite the fact that they share a common block storage device.
Each tenant accesses the common block storage device using its own Logical Block Device node and the associated RBAC Access Control Profiles control which resources are available to each tenant. Configuration of the Logical Block Device nodes is performed by the storage administrator having jurisdiction over that device, using the Hitachi Logical Block Device Node Wizard. These Logical Block Device nodes are then used by the backup administrator for each tenant to gain access to the resources allocated to them on the block storage device. The master node is thus able to present only those block storage device resources that it is authorized to use when constructing data flows and policies.
Nodes UI Reference
This section describes the Nodes UI, accessed via the Navigation Sidebar.
Nodes Inventory
This inventory lists all the nodes in a Protector network, be they online, offline, authorized or deauthorized.

Control | Description |
![]() | Edits an existing node in the inventory. The Node Type Wizard is launched to enable the node's attributes to be changed. |
![]() | Modifies the tags of an existing object from the either the inventory screen or the details screen of the object. |
![]() | Enabled only if one or more unauthorized nodes is selected in the inventory. Attempts to authorize the selected nodes with the Master node. Only nodes that have been authorized by the Master node may perform Protector functions. NoteIf an attempt is made to authorize an inactive or unknown node, or if the master node fails to communicate with the node, an error log is generated and the node remains unauthorized. |
![]() | Enabled only if one or more authorized nodes is selected in the inventory. Attempts to deauthorize the selected nodes. Nodes that have been deauthorized cannot perform Protector functions. Note
|
![]() | Enabled only if one or more authorized nodes is selected in the inventory.
Attempts to remotely upgrade the Protector software installed on the selected nodes. The required
upgrade installer and configuration files must be present in the C:\Programs
Files \Hitachi\Protector\runtime\updater folder on the Master node. Note
|
![]() | Enabled only if one or more nodes is selected in the inventory. The node is deleted from the inventory. NoteIf an OS Host node is still running the Protector hub process and is configured to use the current Master node, then the node will re-appear as an unauthorized node as it periodically reconnects to the master node. Protector should be uninstalled from the node to stop this periodic reconnection. |
![]() | Adds a new node to the inventory. The Node Type Wizard is launched to guide you through the process. |
Existing Node(s) | Nodes on which Protector has been installed are automatically detected and listed here along side those that have been added by the user. The Node Details is displayed to enable the node's details to be viewed and edited. Note
|
![]() | Filters the displayed results based on Node Name. |
Filter on User Tags | Filters the displayed results based on Tags contained in the data flow. |
Filter on Node Type | Filters the displayed results based on Node Type. |
Filter on Operating System | Filters the displayed results based on Operating System. |
Filter on Connection State | Filters the displayed results based on Connection State. |
Filter on Authorization State | Filters the displayed results based on Authorization State. |
Node Type Wizard
Nodes can be created to represent subsystems that interact with Protector. Data from these systems can then be integrated into the usual Protector workflow.
Authorization will fail if the supplied configuration is invalid. To alter the configuration, edit the node's settings. Any changes will come into effect the next time data flows using the node are reactivated.

Control | Description |
![]() | Creates an application node representing Microsoft SQL Server . The Microsoft SQL Server Node Wizard is launched to guide you through the process. |
![]() | Creates an application node representing an Oracle database server or RAC. The Oracle Application Node Wizard is launched to guide you through the process. |

Control | Description |
![]() | Creates a host node that represents a number of Hitachi Block Storage volumes. The Hitachi Block Host Node Wizard is launched to guide you through the process. |

Control | Description |
![]() | Creates a hypervisor node Microsoft Hyper-V. The Hyper-V Node Wizard is launched to guide you through the process. |
![]() | Creates a hypervisor node representing ESX or VCenter. The VMware Node Wizard is launched to guide you through the process. |

Control | Description |
![]() | Creates a storage node responsible for managing an Amazon SimpleStorage Service backup. The Amazon S3 Storage Node Wizard is launched to guide you through the process. |
![]() | Creates a device node responsible for managing a Hitachi Block device. The Hitachi Block Device Node Wizard is launched to guide you through the process. |
![]() | Creates a storage node for targeting Hitachi Content Platform. The Hitachi Content Platform Storage Node Wizard is launched to guide you through the process. |
![]() | Creates a storage node for targeting Hitachi Content Platform for cloud scale. The Amazon S3 Storage Node Wizard is launched to guide you through the process. |
![]() | Creates a device node with limited access to a Hitachi Block device. The Hitachi Logical Block Device Node Wizard is launched to guide you through the process. |
![]() | Creates a disk based target for storing backups. The Repository Storage Node Wizard is launched to guide you through the process. |
Microsoft SQL Server Node Wizard
Protector will launch this wizard when a new Microsoft SQL Server node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the Microsoft SQL Server node. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Node running Microsoft SQL Server | Select an OS Host node which is part of the Microsoft SQL Server standalone or cluster environment |
Configuration to protect | Select the Microsoft SQL Server environment you want this node to represent. |
Rediscover SQL Server Environment | Click in case you want to refresh the list of available SQL Server configurations. |

Control | Description |
Summary | Summary of the settings and nodes selected in the node creation wizard. |
Oracle Application Node Wizard
This wizard is launched when a new Oracle Database Node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the Oracle node. |
Tags | Modifies the tags of an existing object from the either the inventory screen or the details screen of the object. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Node running Oracle to be used for discovery | Select the Protector client node that communicates with the Oracle server. This node will then discover the Oracle environment. |
Rediscover Oracle Environment | Click this button to refresh the cached details. |
- If your Oracle setup uses ASM you can optionally specify which user is used to manage ASM.
- If your Oracle setup does not use ASM, this dialog will not be displayed.

Control | Description |
Operating System | Select one of the following:
|
Domain | For non-default operating system user only. If a Windows operating system is used, enter the domain name of the system to access Oracle ASM. |
Username | For non-default operating system user only. Enter the Oracle Database username for the Oracle ASM. |
Password | For non-default operating system user only. Enter the operating system username's password for the Oracle ASM. |
Database | Select one of the following:
|
Username | For non-default database user only. Enter the Oracle Database username of the user who can execute the SQL commands on the Oracle ASM instance. |
Password | For non-default database user only. Enter the password of the user who can execute the SQL commands on the Oracle ASM instance. |

Control | Description |
SID | Click on a database's SID to open the Specify Database credentials dialog (see below). |
Rediscover Databases | Click this button to refresh the cached details. |

Control | Description |
Operating System | Select one of the following:
|
Domain | For non-default operating system user only. If a Windows operating system is used, enter the domain name of the system to access Oracle ASM. |
Username | For non-default operating system user only. Enter the username which is used to run the operating system commands for this database. |
Password | For non-default operating system user only. Enter the username's password. |
Database | Select one of the following:
|
Username | For non-default database user only. Enter the username of the user who can execute the SQL commands. |
Password | For non-default database user only. Enter the password of the user who can execute the SQL commands. |

Control | Description |
Summary | Summary of the selected configuration. |
Hitachi Block Host Node Wizard
A Hitachi Block Host node represents a group of Hitachi Block volumes attached to a host machine.
If a user is given access to a Block Host node by placing it in a resource group that they have access to, the associated physical Block Device node must also be placed in that resource group. It is not sufficient to include only a Logical Block Device node (based on the physical Block Device node) in that resource group.

Control | Description |
Node Name | Enter a name for the Block Host node. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Hitachi Block Device | Enter or select a Hitachi Block node or Hitachi Logical Block node name from the dropdown list. |

Control | Description |
Included Logical Devices | Enter a list of LDEVs or Host Groups to be included in this Block Host (one logical device or host group specification per line) in the format described below. |
Excluded Logical Devices | Enter a list of LDEVs or Host Groups to be excluded from this Block Host (one logical device or host group specification per line) in the format described below. TipThis enables the inclusion of an entire Host Group but exclusion of individual LDEVs within that Host Group. |
LDEVS are entered using the format:
identifier
Where identifier is one of:
- ldev_id a single LDEV ID in hex or decimal
- ldev_id-ldev_id a range of LDEV IDs
- host_group_id a host group identifier using the format:
- CLc-s-h where:
- CL is a literal string
- c is the physical channel number in the range 1…n
- s is the physical slot number in the range A…Z
- h is the logical host group ID in the range 0…255
- CLc-s-h where:
For example:
0x00a0 for an LDEV specified in hexadecimal
220-230 for a range of LDEVs specified in decimal
CL2-A-12 for a host group
- Spaces and colons must not be present in the entries. If a space or colon is encountered on a line, the remaining text on that line from the space or colon will be disregarded. This allows entries that contain the LDEV name after a space or colon) to be present in the list.

Control | Description |
Summary | Summary of the settings entered. |
Hyper-V Node Wizard
This wizard is launched when a new Hyper-V Node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the Hyper-V node. |
Tags | Add the tags to be associated with the object being created |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Node running Hyper-V | Select an OS Host node which is part of the Microsoft Hyper-V standalone or cluster environment |
Username | Enter the username that will be used to perform backups and restores on this Hyper-V environment. The user requires privileges as detailed in Microsoft Hyper-V user privileges. |
Password | Enter the password for the username provided above |

Control | Description |
Configuration to protect | Select the Hyper-V environment you want this node to represent |
Rediscover Hyper-V Environment | Click in case you want to refresh the list of available Hyper-V configuration |

Control | Description |
Summary | Summary of the settings entered. |
Microsoft Hyper-V user privileges
To lookup, protect and restore Hyper-V virtual machines Protector requires credentials that are valid for all machines comprising the Hyper-V node.
In case of a cluster, these credentials must be domain credentials. For a standalone configuration, a local user is sufficient.
The user needs to be a member of the following groups in the domain and all nodes of the Hyper-V setup:
- Users
- Domain Users
- Backup Operators
- Hyper-V Administrators
- Remote Management Users
In addition, for a cluster the user requires the permission to administrate the cluster. The following command needs to be executed on every cluster node:
Grant-ClusterAccess -User domain\username -Full
VMware Node Wizard
This wizard is launched when a new VMware Node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the VMware node. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Proxy Node | Select a proxy node for the vCenter or ESX/ESXi host. Note
|

Control | Description |
Host name or IP Address of vCenter / ESXi Server | Specify the vCenter or ESX/ESXi host name or IP address. |

Control | Description |
Username | Enter the username for the vCenter or ESX/ESXi host. NoteThe user specified here must have the specified VMware user privileges. |
Password | Enter the password for the vCenter or ESX/ESXi host. |

Control | Description |
Summary | Summary of the settings entered. |
VMware user privileges
The VMware user specified when interacting with Protector (i.e. in the context of a hypervisor proxy node or Site Recovery Manager SRA , Site Recovery Manager SRA or vRealize Orchestrator workflow) must have the following privileges assigned in vSphere:
- Datastore:
- Allocate space
- Browse datastore
- Low level file operations
- Remove file
- Rename datastore
- Update virtual machine files
- Folder:
- Create folder
- Global:
- Disable methods
- Enable methods
- Licenses
- Log event
- Manage custom attributes
- Set custom attribute
- Host:
- Configuration:
- Storage partition configuration
- Connection Permission (vSphere 7 only)
- Configuration:
- Network:
- Assign network
- Configure
- Resource:
- Assign virtual machine to resource pool
- Migrate powered off virtual machine
- Migrate powered on virtual machine
- Sessions:
- Validate session
- Virtual Machine:
- Configuration:
- Add existing disk
- Add new disk
- Add or remove device
- Advanced
- Change CPU count
- Change resource
- Disk change tracking
- Disk lease
- Extend virtual disk
- Host USB device
- Memory
- Modify device settings
- Raw device
- Reload from path
- Remove disk
- Rename
- Reset guest information
- Set annotation
- Settings
- Swapfile placement
- Upgrade virtual machine compatibility
- Guest operations:
- Guest operation modifications
- Guest operation program execution
- Guest operation queries
- Interaction:
- Answer question
- Backup operation on virtual machine
- Console interaction
- Device connection
- Guest operating system management by VIX API
- Power off
- Power on
- Inventory:
- Create from existing
- Create new
- Register
- Remove
- Unregister
- Provisioning:
- Allow disk access
- Allow read-only disk access
- Allow virtual machine download
- Allow virtual machine files upload
- Mark as template
- Mark as virtual machine
- Snapshot management:
- Create snapshot
- Remove snapshot
- Revert to snapshot
- Configuration:
- dvPort group:
- Create
- Delete
- vApp:
- Add virtual machine
- Assign resource pool
- Unregister
- vSphere Tagging:
- Assign or Unassign vSphere Tag
- Assign or Unassign vSphere Tag on Object (vSphere 7 only)
The System privileges (Anonymous, Read and View) are also required. These are automatically assigned to new and existing roles, but are not visible in the vSphere Client UI.
Hitachi Block Device Node Wizard

Control | Description |
Node Name | Enter a name for the Hitachi Block storage node. |
Tags | Add the tags to be associated with the object being created. |
I confirm that ... | This checkbox must be checked to proceed with the node configuration. Caution
Resources or replication relationships created or adopted by Protector must only be managed, modified and deleted via Protector. Failure to do so will cause unpredictable consequences and is not supported unless specifically advised to do so by the Protector documentation. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Proxy Node | Select a Protector node to act as a proxy. CautionISM nodes and
their associated CMDs used to control storage devices must not be shared with applications
other than those forming part of the Ops Center suite. NoteThe proxy node is responsible for interfacing with the Block storage device. It can be a Windows or Linux machine with the Protector Client software installed and must be connected via a command device to the Block storage device. The command device must only have user authentication enabled. The proxy node must have supported version of CCI installed. Refer to the Command Control Interface documentation available at https://knowledge.hitachivantara.com. |

Control | Description |
Common Metadata Directory | Enter a directory on the Proxy node where Protector can place metadata files related to Block snapshots and replications. Click the Browse button to open the Path Dialog if required. NoteThe 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. |

Control | Description |
Select from detected storage devices | Select this option to specify the hardware storage device by serial number. A list of storage device serial numbers, available to the proxy node selected in the previous step, is displayed in the dropdown menu below. |
Specify by IP or Hostname with a port | Select this option to specify the hardware storage device using the IP address or hostname and port number of an IP command device on the storage device. Additional fibre and IP command devices can be added at a step later in the wizard. Note
For HUS VM storage devices, use the IP address of the SVP. For VSP G1x00 storage devices, use the IP address of CTL1 or CTL2. DO NOT use the IP address of the SVP. When performance is important or where high workloads are expected, the use of Fibre Channel command devices is highly recommended. Using IP command devices will result in slower performance. |

Control | Description |
Storage Device Serial Number | Displays the serial number of the Block device specified in the previous step. NoteWhen the serial number is displayed it is the serial number as provided by CCI, as such the serial number for the VSP 5000 series will have a “5” added to the beginning. Whereas the serial number for the VSP G1x00 and VSP F1500 will have a 3 added to the beginning. |
Username | Enter the username for the Block device. NoteThe 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. In addition, the Support Personnel role is required for changing the Array SOM settings that allow LDEV resizing for replications. If the Block device cannot be accessed or its credentials are invalid then the node will fail authorization. The configuration wizard can be reopened to correct any errors. |
Password | Enter the password for the Block device. NoteThe password for authorizing a Block device must contain only useable CCI command characters: A-Za-z0-9’-./:@\_ |

Control | Description |
Enable | Allows the configuration of the Global Replication Roprts to be filled out. |
CM-REST Server Address | Enter either the Host Name or the IP Address of the CM-REST server. |
Port Number | Enter the port number for the CM-REST server. |
HTTPS | Select to enable secure communications to the CM-REST server. |
Ignore SSL certificate errors | Select to ignore SSL certificate errors when communicating with the CM-REST server. |
Username and Password | Enter the username and password for the storage array. NoteIf CM-REST is on the same server as the Block Device Node then the credentials must be different. |
Refresh Interval | Enter the required interval between refreshes of the GRR reports. NotePopulating the data in the GRR reports requires interaction with the storage array and therefore on busy systems it is not recommended to have short refresh times as this may affect performance of the system. |

Control | Description |
All | Select this option if you want 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. Note
All replication and snapshot S-VOLs must be created using free LDEV IDs that are mapped to the meta_resource group, and have virtual LDEV IDs matching their corresponding physical LDEV IDs. For fully provisioned snapshots and all replications, this applies to the operation that creates that snapshot or replication. For floating device snapshots and snapshots mounted using cascade mode, this applies to the mount or restore operation. For fully provisioned snapshots mounted using cascade mode, this applies both to the operation that creates that snapshot and to the mount or restore operation. If an operation tries to create one or more LDEVs, that operation will fail if there are not enough free LDEV IDs that meet the above conditions. |
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. |

The user able to specify zero or more fibre or IP command devices in priority order.
If no command devices are specified, then Protector will attempt to control the hardware storage device via 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, then Protector will attempt to control the hardware storage device via a command device in the order specified by the user. If the first command device fails, Protector will progress to the next. If all specified command devices fail then the operation fails. 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.
Control | Description |
![]() | Enabled when only one command device is selected. Launches the Configure Command Device wizard below to allow the settings to be edited. |
![]() | Enabled when only one command device is selected. Increases the priority of the selected command device. |
![]() | Enabled when only one command device is selected. Decreases the priority of the selected command device. |
![]() | Enabled when one or more command devices are selected. Deletes selected command device. |
![]() | Launches the Configure Command Device wizard below to guide you through setting up a fibre or IP command device. |

Control | Description |
Use any available fibre command device | Select this option to insert an entry in the command device list that allows Protector to use any available fibre command device. |
Select from detected fibre command devices | Select this option to insert a specific fibre command device in the list. The detected fibre command devices are displayed in the dropdown menu below using their decimal LDEV ID. |

Control | Description |
IP Address or Hostname | Enter the IP address or hostname of the command device to add to the list. Note
For HUS VM storage devices, use the IP address of the SVP. For VSP G1x00 storage devices, use the IP address of CTL1 or CTL2. DO NOT use the IP address of the SVP. |
Port Number | Enter the port number of the command device. |

Control | Description |
![]() | Enabled only if one Virtual LDEV range is selected. The Configure Virtual LDEV Range page of the wizard (see below) is displayed to enable a port to be added. |
![]() | Enabled only if one or more Virtual LDEV ranges are selected. Deletes the Virtual LDEV range(s) from the list. |
![]() | Adds a new Virtual LDEV range to the list. The Configure Virtual LDEV Range page of the wizard (see below) is displayed to enable a Virtual LDEV Range to be added. |
Virtual Serial(s) | The Virtual Serial(s) and associated LDEV Ranges that will be used. |

Control | Description |
VSM Serial Number | Enter the serial number of the VSM you intend to use within Protector. |
Start of LDEV range | Enter the lower limit of the LDEV range to use for allocation. |
End of LDEV range | Enter the lower limit of the LDEV range to use for allocation. |

Control | Description |
![]() | Enabled only if one provisioning port is selected. The Specify Port page of the wizard (see below) is displayed to enable a port to be added. |
![]() | Enabled only if one or more provisioning ports are selected. Deletes the port(s) from the list. |
![]() | Adds a new provisioning port to the list. The Specify Port page of the wizard (see below) is displayed to enable a port to be added. |
Provisioning Port(s) | Lists the ports that will be used for provisioning. |

Control | Description |
Port | Enter the port identifier in the following format: CLc-s where:
|

Control | Description |
Summary | Summary of the settings entered. |
Hitachi Content Platform Storage Node Wizard
This wizard is launched when a new Hitachi Content Platform Node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the HCP storage node. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Generation 2 | Select this for a generation 2 storage node which is compliant with the new Universal Backup Infrastructure interface. This is the recommended option. |
Generation 1 | Select this for a generation 2 storage node which required data to be sent via a generation 1 repository. Clicking Next will take you to the Configure Tenant Page. |

Control | Description |
Create a new HCP node | Select this to setup a new HCP node. |
Import an existing HCP node | Select this to import an existing HCP node. |

Control | Description |
Proxy Node | Select a Protector node to act as a proxy. |

Control | Description |
Metadata Directory | Enter a directory on the Proxy node where Protector can place metadata files related to HCP data. Click the Browse button to open the Path Dialog if required. |

Control | Description |
Tenant Host Address | Enter the host name for the tenant in the form <tenant>.<hcp_name>.<domain>. |
Ignore SSL certificate errors | Allows the system to be used without properly configured SSL certificates. |
Username | Enter a user name for the tenant specified above. |
Password | Enter the password for the user. |

Control | Description |
Namespace | This is automatically generated for a generation 1 HCP node and is therefore greyed out. For a generation 2 HCP node enter the desired namespace |
Initial Quota (GB) | Change the namespace quota from the default if required. It is important to
estimate the quota required. Too small a value will result in tiering being stopped
if the quota is exhausted. Too large a value will waste total tenant quota. This value is not displayed when importing an existing generation 2 HCP node. NoteChanging the quota for an existing
HCP node will
only affect newly created namespaces. Existing namespaces created by Protector on that node
will not be affected. |
Namespace Soft Quota Level | This is the percentage of free space at which additional backups are prevented |

Control | Description |
Summary | Summary of the settings entered. |
Hitachi Logical Block Device Node Wizard
Hitachi Logical Block Storage Nodes implement multi tenancy by limiting what resources each tenant has access to on a physical block storage device shared with other tenants.
The Hitachi Logical Block Storage Node Wizard is used by storage administrators to create logical views of a physical storage device, so that multiple tenants can use a common device without interfering with each other's resources. About multi-tenancy for Hitachi block storage describes how Protector implements this arrangement.

Control | Description |
Node Name | Enter a name for the Logical Block node. |
Tags | Add the tags to be associated with the object being created. |
Add to access control resource group | Check this box if you want to add it to a different resource group. |
Resource Group | Type the name of the resource group or select one from the drop down list. |

Control | Description |
Resource Groups | All nodes are automatically allocated to the 'default' RBAC resource group. Select the additional resource group(s), from those listed, to which this node will be allocated for the purposes of RBAC. Allocation to resource groups can also be done via the Access Control Resource Groups Inventory. |

Control | Description |
Hitachi Block Device Node | Enter or select the name of the Physical Block node on which the Logical Block node will be based . |

Control | Description |
LDEV Range | Specify the LDEV range on the physical storage device that will be made available by this logical storage device for provisioning S-VOLs. Note
All replication and snapshot S-VOLs must be created using free LDEV IDs that are mapped to the meta_resource group, and have virtual LDEV IDs matching their corresponding physical LDEV IDs. For fully provisioned snapshots and all replications, this applies to the operation that creates that snapshot or replication. For floating device snapshots and snapshots mounted using cascade mode, this applies to the mount or restore operation. For fully provisioned snapshots mounted using cascade mode, this applies both to the operation that creates that snapshot and to the mount or restore operation. If an operation tries to create one or more LDEVs, that operation will fail if there are not enough free LDEV IDs that meet the above conditions. |

Specifies the P-VOL(s) on the physical block device that will be available to this logical block device for snapshotting or replication. LDEVs can be specified by name, range and host group.
Control | Description |
![]() | Enabled only if one Primary LDEV is selected. The Specify Primary LDEVs filter page of the wizard (see below) is displayed to enable an LDEV Filter to be added. |
![]() | Enabled only if one or more LDEV Filters are selected. Deletes the LDEV Filter(s) from the list. |
![]() | Adds a new LDEV Filter to the list. The Specify Primary LDEVs filter page of the wizard (see below) is displayed to enable an LDEV Filter to be added. |
Existing LDEV Filter(s) | Lists the LDEV Filter(s) that will be used. |

Control | Description |
LDEV Name Pattern | Enter a regular expression (see Basic regular expressions) to identify matching Primary LDEV Names that will be made available on this logical block device. |
LDEV ID Range | Enter the range of the Primary LDEV IDs that will be made available on this logical block device. |
Host Group ID | Enter a Host Group identifier. TipHost Group ID is normally used alone rather than in combination with the other filter terms presented here. |

Control | Description |
![]() | Enabled only if one provisioning port is selected. The Specify Port page of the wizard (see below) is displayed to enable a port to be edited. |
![]() | Enabled only if one or more provisioning ports are selected. Deletes the port(s) from the list. |
![]() | Adds a new provisioning port for use by Protector to the list. The Specify Port page of the wizard (see below) is displayed to enable a port to be added. |
Provisioning Port(s) | Lists the provisioning ports that will be used. |

Control | Description |
Port | Specify a port that can be used by Protector for its own processing needs. Enter a port identifier in the following format: CLc-s where:
|

Control | Description |
![]() | Enabled only if one Journal Range is selected. The Specify Journal range page of the wizard (see below) is displayed to enable a journal range to be added. |
![]() | Enabled only if one or more Journal Ranges are selected. Deletes the Journal Range(s) from the list. |
![]() | Adds a new Journal Range to the list. The Specify Journal range page of the wizard (see below) is displayed to enable a Journal Range to be added. |
Journal Ranges | The Journal Range to be used. |

Control | Description |
Journal ID Range | Enter the Journal ID range that will be made available on this logical block device. |

- Mounting (see Hitachi Block Snapshot or Replication Mount Wizard and Hitachi Block Mount Configuration Wizard).
- Specifying GAD cross-path replication secondary Host Groups (see Hitachi Block Replication Configuration Wizard).
Control | Description |
![]() | Enabled only if one Host Group is selected. The Specify Host Group Filter page of the wizard (see below) is displayed to enable a Host Group to be added. |
![]() | Enabled only if one or more Host Group Filters are selected. Deletes the Host Group Filter(s) from the list. |
![]() | Adds a new Host Group Filter to the list. The Specify Host Group Filter page of the wizard (see below) is displayed to enable a Host Group Filter to be added. |
Host Group Filter(s) | The Host Group Filter to be used. |

Control | Description |
Host Group Name Pattern | Enter a regular expression (see Basic regular expressions) to identify matching Host Group Names. |
Host Group ID range | Enter the lower and upper limit of the Host Group ID range to use. |
Port ID | Enter the port identifier in the following format: CLC-S where:
|

Control | Description |
![]() | Enabled only if one Pool Filter is selected. The Specify Pool filter page of the wizard (see below) is displayed to enable a Pool Filter to be added. |
![]() | Enabled only if one or more Pool Filters are selected. Deletes the Pool Filter(s) from the list. |
![]() | Adds a new Pool Filter to the list. The Specify Pool filter page of the wizard (see below) is displayed to enable a Pool Filter to be added. |
Existing Pool Filter | The Pool Filter(s) to be used. |

Control | Description |
Pool Name Pattern | Enter a regular expression (see Basic regular expressions) to identify matching Pool Names. |
Pool ID range | Enter the Pool ID range to use. |

Control | Description |
Summary | Summary of the settings entered. |
Basic regular expressions
Regular expressions (regex) are a powerful method of pattern matching in character strings. This topic describes a few basic regex terms. For a full explanation of regular expressions, please refer to one of the many books or online resources available.
Type of Match | Regex Example | Action | Explanation |
Contains the sub-string (case sensitive) | this | Matches any string containing the sub-string this , respecting the casee.g.:
| A sub-string on its own will be matched anywhere within the search string. |
Contains the sub-string (case insensitive) | (?i)this | Matches any string containing the sub-string this , without regard to casee.g.:
| The (?i) mode modifier turns off case sensitive matching |
Starts with the sub-string | ^this | Matches any string starting with this e.g.:
| The ^ anchor means the sub-string must appear at the start of the string being searched |
Ends with the sub-string | that$ | Matches any string ending with that e.g.:
| The $ anchor means the sub-string must appear at the end of the string being searched |
Starts with any of the sub-strings | ^(this|that|other) | Matches any string starting with this or that or other e.g.:
and:
and:
| The | alternation operator indicates any sub-string in brackets will be matched |
Contains any of the sub-strings | (this|that) | Matches any string containing this or that e.g.:
and:
| The | alternation operator indicates either sub-string in brackets will be matched |
Starts with sub-string 1 and ends with sub-string 2 | ^this.*that$ | Matches any string staring with this and ending with that e.g.:
| The . metacharacter matches any character, then the * quantifier indicates that zero or more of them will be matched |
Repository Storage Node Wizard
This wizard is launched when a new Repository Node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the Repository node. NoteRepository nodes that are hosted on the same Proxy Node must be uniquely named. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Proxy Node | Enter or select the node that will host the Repository. |

Control | Description |
Mode | Select one of the following options:
|

Control | Description |
Directory | Enter the path of the directory where the existing repository resides or select the path by clicking the Browse button to open the Path Dialog. Clicking next will take you to the Summary Page. |
Encryption Passphrase (optional) | If the repository was encrypted, enter the password specified when it was created if you want to mount it immediately. The passphrase can be entered later if you intend to leave it unmounted for now. |

Control | Description |
Generation 1 | A generation 1 repository should only be selected if it is being used to receive data from another generation 1 repository. Generation 1 repositories are deprecated and wherever possible generation 2 repositories should be used. |
Generation2 | It is recommended to select a Generation 2 repository for all new repository setups. A generation 2 repository supports all new capabilities and utilizes the UBI framework. |

Control | Description |
Root Directory | The root directory is the location where the configuration data for the repository is held. |
Data Directory | The data directory holds the actual backed up data contents of the repository. |
Metadata Directory | The metadata directory holds the information that describes how the data in the data directory needs to be combined to make up a recovery point which can then be restored. |
Checksum Directory | The checksum directory is used to store the checksums generated when Fine Change Detection is enabled. |

Control | Description |
Enable Repository Encryption | You can optionally encrypt the contents of your repository to enhance security of the data stored in it. In-place encryption may not be allowed in some territories, this capability is controlled by license. |
Encryption Passphrase | Enter an encryption password of your choosing. This will be required by anyone who accesses the repository. CautionAn encrypted repository cannot be recovered without the password. If the password is forgotten, then the data in that repository will be inaccessible. |
Confirm Encryption Passphrase | Re-enter the encryption password to ensure it has been typed correctly. |

Control | Description |
Optimize for Cloud Replication | Aligns block boundaries between the repository and the cloud in order to make cloud uploads more efficient. |
Single Instance Repository data | Enables the repository to perform file stream level single instancing. This reduces the space backups take up if you have multiple backups of the same file. |
Capacity Warning Level | When the used space on the filesystem which hosts the repository reaches this percentage level warning logs will be generated advising of low disk space. |
Capacity Critical Level | When the used space on the filesystem which hosts the repository reaches this percentage level an error log will be generated, and the repository will unmount. |
Block Size | Sets the block size the repository uses. It is recommended that this matches the filesystem block size where possible. |

Control | Description |
Summary | Summary of the parameters entered above. |
Import an existing Repository

Control | Description |
Directory | Enter the path of the directory where the existing repository resides or select the path by clicking the Browse button to open the Path Dialog. Clicking next will take you to the Summary Page. |
Encryption Passphrase (optional) | If the repository was encrypted, enter the password specified when it was created if you want to mount it immediately. The passphrase can be entered later if you intend to leave it unmounted for now. |

Control | Description |
Summary | Summary of the parameters entered for Import Repository Wizard. |
Amazon S3 Storage Node Wizard
This wizard is launched when a new Amazon S3 Node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the S3 node. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Mode | Select one of the following options:
|

Control | Description |
Proxy Node | Enter or select the node that will host the S3 proxy. |

Control | Description |
Directory | Enter the path of the directory where you want to create the new S3 metadata cache or select the path by clicking the Browse button to open the Path Dialog. The metadata cache holds an index and metadata for backups that arestored in the S3 cloud. This is only a cache and can be rebuilt from the S3 cloud content if lost. |

Control | Description |
Access Key ID | Amazon S3 Access Key ID. This is the equivalent of a user . See Amazon S3 documentation for further information. |
Secret Access Key | Amazon S3 Secret Access Key. This is the equivalent of a password. See Amazon S3 documentation for further information. |
Bucket Name | This a name of where you will store data in the Amazon S3. It needs to be globally unique across all users of AWS across all regions. Consider the bucket name to be akin to a URL and it uses the DNS compliant naming conventions. See Amazon S3 documentation for further information. |
Region | This is the region where the store will be created. Generally, you should select a store closest to your geographic region. See Amazon S3 documentation for further information. |
HCP Cloud Scale Storage Node Wizard
This wizard is launched when a new HCP cloud scale node is added to the Nodes Inventory.

Control | Description |
Node Name | Enter a name for the HCP node. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Resource Groups | Select the resource group(s) to which this node will be allocated for the purposes of RBAC. All nodes are automatically allocated to the 'default' resource group. |

Control | Description |
Mode | Select one of the following options:
|

Control | Description |
Proxy Node | Enter or select the node that will host the S3 proxy. |

Control | Description |
Directory | Enter the path of the directory where you want to create the new S3 metadata cache or select the path by clicking the Browse button to open the Path Dialog. The metadata cache holds an index and metadata for backups that arestored in the S3 cloud. This is only a cache and can be rebuilt from the S3 cloud content if lost. |

Control | Description |
S3 Service Endpoint | The HTTP endpoint to communicate with the HCP cloud scale S3 service. |
Ignore SSL certificate errors | Ignore SSL errors when using self-signed certificates. |
S3 Access Key | This is the equivalent of a user. |
S3 Secret Key | This is the equivalent of a password. |
Bucket Name | This a name of where you will store data on the HCP cloud scale device. Consider the bucket name to be akin to a URL and it uses the DNS compliant naming conventions. |

Control | Description |
Summary | Summary of the parameters entered above. |
Node Details
This page displays the details of an existing node and enables the wizard to be launched to edit them.

Control | Description |
Logs | Indicates the number of unacknowledged error logs in red. If there are no errors then a green tick is displayed instead. Summarizes the number of unacknowledged errors and warnings. Opens the Logs Inventory. |
Jobs | Indicates the number of failed jobs in red. If there are no failed jobs then a green tick is displayed instead. Summarizes the number of failed, paused and in-progress jobs. Opens the Jobs Inventory. |
Summary | Indicates the following:
|
Data Instances | Indicates the following:
|
Control | Description |
Configuration | Indicates the following:
|
Hosted Nodes | Lists all the nodes for which this node acts as the proxy. |
![]() | Enables disables SSL encyption on the node. For more details see How to enable or disable encryption on a node. |
Control | Description |
![]() | Launches the Oracle Application Node Wizard to enable the parameters to be edited. |
Details | Displays the node's online status. |
Configuration | Displays the node type and configuration. |
Host Nodes | Lists all the nodes that act as the proxy for this node. |
Control | Description |
![]() | Launches the VMware Node Wizard to enable the parameters to be edited. |
Configuration | Indicates the following:
|
Control | Description |
![]() | Opens the storage Hitachi Block Device Details for this node. |
![]() | Launches the Hitachi Block Device Node Wizard to enable the parameters to be edited. |
![]() | Add the tags to be associated with the object being created. |
Configuration | Indicates the following:
|
Port | List the available ports for this node. |
Command Device Type | Lists the command devices and their type. |
Virtual Serial | Lists the Virtual Serial devices. |
Hosted Nodes | Lists all the nodes for which this node acts as the proxy. |
Control | Description |
![]() | Launches the Hitachi Block Host Node Wizard to enable the parameters to be edited. |
![]() | Add the tags to be associated with the object being created. |
![]() | Launches the Hitachi Block Host Resize Dialog to expand the one or more LDEVs associated with this Block Host node. |
Summary | Displays the node's online status and tags. |
Configuration | Indicates the Hitachi Block Device on which this node is based. |
Included Logical Devices | List the LDEVs represented by this node. |
Excluded Logical Devices | List the LDEVs excluded for this node. |
Control | Description |
![]() | Opens the storage Hitachi Block Logical Device Details for this node. |
![]() | Launches the Hitachi Logical Block Device Node Wizard to enable the parameters to be edited. |
![]() | Add the tags to be associated with the object being created. |
Details | Displays the node's online status. |
Configuration | Indicates the parent Hitachi Block Device Node. |
LDEV Range | The LDEV provisioning ranges available for this node. |
Control | Description |
![]() | Opens the storage Generation 1 Repository Details for this node. |
![]() | Launches the Repository Storage Node Wizard to enable editing the capacity level. |
![]() | Add the tags to be associated with the object being created. |
Details | Displays the nodes proxy. |
Configuration | Indicates the follow:
|
Paths | Indicates the following:
|
Control | Description |
![]() | Launches the Hitachi Content Platform Storage Node Wizard to enable the parameters to be edited. |
![]() | Add the tags to be associated with the object being created. |
Configuration | Indicates the following:
|
Namespace |
|
Node Type Icons
Icon | Description |
![]() | Master Node - Indicates that this node is the master node. |
![]() | OS Host Node - A Workstation, Laptop or Server node with the Protector services installed. |
![]() | Repository Node - A node with the Protector Repository component installed. Used to store snapshots of data backed up from various types of source nodes. |
![]() | VMware ESX Node - A node containing virtual machines, and accessed through a separate proxy node. |
![]() | Hitachi Content Platform Node - A node representing an Hitachi Content Platform. |
![]() | Hitachi Block Node - A node representing a Hitachi Block Storage Device. |
![]() | Hitachi Block Host Node - A node that represents a number of Hitachi Block Storage volumes. |
![]() | Hitachi Logical Block Device Node - A logical view of Hitachi Block Storage Device node, having limited access to its resources. |
![]() | Oracle Node - Represents a cluster of servers running as an Oracle RAC that accesses databases on shared disks. |
![]() | Unknown Node - The master node is unable to determine any node details, and cannot connect to it. |
![]() | Inactive Node - Indicates that the node is not currently running the Protector hub process, or it is not currently attached to the network. The master node is currently unable to connect to the node. |
![]() | Node Group - Represents a group of nodes that can be treated identically when assigning policies or monitoring activities. |
![]() | S3 Node - A node representing an S3 Bucket |
Node Status Indicators
Small graphical indicators that provide visual cues as to a particular node’s status.
Icon | Description |
![]() | Unauthorized Node - The node has Protector installed but has not been authorized by the Master node, so cannot interact with other Protector nodes. |
![]() | Authorized Online Node - The node has Protector installed and has been authorized by the Master node, so can interact with other Protector nodes. |
![]() | Offline - The node is not contactable from the Master so its status cannot be determined. |
![]() | Snapshotted Node - Indicates that the node has a policy containing a snapshot operation applied to it. |
Node Groups UI Reference
This section describes the Node Groups UI, accessed via the Navigation Sidebar.
For further information, refer to:
Node Groups Inventory
This inventory lists all defined Node Groups.

Control | Description |
![]() | Edits an existing node group in the inventory. The Node Group Wizard is launched to enable the group's attributes to be changed. |
![]() | Enabled only when one or more Node Group is selected. Deletes the selected item from the inventory. The associated Nodes are not deleted. |
![]() | Creates a new Node Group. The Node Group Wizard is launched to guide you through the process. |
![]() | Any number of user defined Node Groups can be created. These are displayed in the inventory. Click on the node group name to open the Node Group Details which enables the group to be viewed and edited. |
Filter on Name | Filters the displayed results based on Node Name. |
Filter on User Tags | Filters the displayed results based on Tags contained in the data flow. |
Filter on Node Type | Filters the displayed results based on Node Type. |
Filter on Contains Node | Filters the displayed results to groups that contain the node entered. |
Node Group Wizard
This wizard is launched when a new Node Group is added to the Node Groups Inventory.

Control | Description |
Name | Enter the name of the node group. |
Description | Optional. Enter a description of the node group. |
Tags | Add the tags to be associated with the object being created. |

Control | Description |
Node Type | Specifies the node type that this group will contain. Only node types that can have a common policy assigned are available. |
Operating System | If the OS Host node type is selected then this control is enabled so that a specific operating system can be selected. |

Control | Description |
Node Name | Filters the list of nodes displayed below by name. |
Click to add | Lists all available nodes of the specified type. Click on the name of the node you want to add to this node group. |
Click to remove | Lists all the nodes currently in this group. Click on the name of the node you want to remove from this node group. |
Node Group Details
This page displays the details of a Node Group and enables you launch the wizard to edit them.

Control | Description |
![]() | Launches the Node Group Wizard to enable you to view and edit the node group. |
![]() | Modifies the tags of an existing object from the either the inventory screen or the details screen of the object. |
![]() | Click the node name to open the Node Details to enable you to view the node's status and details. |
Node Tasks
For further information, refer to:
How to add a node
Before you begin
The node must have the Protector Client software component installed (see How to install/upgrade Protector on Windows and Linux or AIX).
The specific role of a node is determined when it is added to the Nodes Inventory as follows:
Procedure
Click Nodes on the Navigation Sidebar to open the Nodes Inventory.
Click Create new item to open the Node Type Wizard.
Select the type of node to be added then click Start.
The Node Type Wizard will guide you through creating a node of the required type.Finally click Finish and the new node will appear in the Nodes Inventory.
How to authorize a node
Before you begin
The node must appear in the Nodes Inventory (see How to add a node).
Nodes must be authorized by the Master node, before they are allowed to participate in a data flow, as follows:
Procedure
Click Nodes on the Navigation Sidebar to open the Nodes Inventory.
Select the tile for the node you want to authorize by clicking in its top left corner.
Unauthorized nodes display aicon in the top right corner
Click Authorize Node above the inventory area.
Wait a few moments for the node to be authorized.
Authorized nodes display aicon in the top right corner.
NoteFor extra security it is possible to verify the SSL/TLS fingerprint of the client node prior to authorization see How to verify the SSL/TLS fingerprint of a client node prior to authorising
How to stop the services
Before you begin
Sometimes it is necessary to stop the Protector services on a node, this needs to be done locally on the node itself.
- Open a console/command prompt window (On Windows select "Run as administrator", On Linux ensure you are running with root privileges using sudo))
- Within the command window change directory to the Protector 'bin' directory
- To stop the hub services – run the command:
diagdata --stop
How to start the services
Before you begin
If the Protector services have been stopped the services need to be restarted locally on the node itself.
- Open a console/command prompt window (On Windows select "Run as administrator", On Linux ensure you are running with root privileges using sudo))
- Within the command window change directory to the Protector 'bin' directory
- To stop the hub services – run the command:
diagdata --start
How to enable or disable encryption on a node
Before you begin
The node must appear in the Nodes Inventory (see How to add a node.
Nodes must be authorized by the Master node see How to authorize a node.
Procedure
Click Nodes on the Navigation Sidebar to open the Nodes Inventory.
Select the node you want to set the encryption state by clicking in its node name green text. The Node Details is displayed to enable the node's details to be viewed and edited.
Click Enable\Disable Encryption above the inventory area.
A popup message will be displayed indicating the encryption has been enabled or disabled as appropriate.
The Encryption entry in the Configuration table will be updated with the current state
How to change the account credentials for a Block Device node
Before you begin
It is assumed that there is already a block device configured and connected to a storage array.
Procedure
Click Nodes on the Navigation Sidebar to open the Nodes Inventory.
Select the tile for the Block Device Node you want to change the credentials for by clicking in its top left corner.
Click Edit Node above the inventory area.
Click through the Hitachi Block Device Node Wizard until you reach the ‘Specify credentials for device’ screen
Enter the new username/password as required.
Click through the rest of the wizard and click finish at the end. The credentials will now be updated for this Block Device node.