Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

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.

Hardware device nodes, server nodes and logical nodes in a Protector environment
GUID-162CF81D-43CC-4460-8C5E-9577D8CD9854-low.png

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.

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 Storage 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.

Nodes Inventory
GUID-7998362B-E495-4EB4-AD73-7EA93D4DF672-low.png
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEdits an existing node in the inventory. The Node Type Wizard is launched to enable the node's attributes to be changed.
GUID-E5F1CBC8-471E-4699-9E6D-E16DF64C3EA3-low.pngTagModifies the tags of an existing object from the either the inventory screen or the details screen of the object.
GUID-2C6F7E2E-8716-421F-8DDF-141841BC472F-low.png AuthorizeEnabled 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.
GUID-6053C78F-82FB-46F7-8B6A-29A4C4FB1998-low.png DeauthorizeEnabled 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
  • Before deauthorizing nodes that are no longer required, they must first be deleted from the current data flow definitions, then any modified active data flows must be reactivated. If any attempt is made to deauthorize a node that is implementing rules in the currently active data flows, an error message is generated for each such node and the node remains authorized.
  • It is possible to de-authorize a node with active mounts. This should be avoided because once de-authorized it is not possible to unmount.
GUID-5D95EEC8-1BB8-447B-8E01-6AEADE47FD30-low.png Upgrade ClientsEnabled 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
  • Only OS Host nodes can be upgraded. It is recommended to upgrade nodes in batches of 20.
  • It is recommended to manually upgrade the master node.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png Delete NodeEnabled 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.
Create a new itemAdds 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
  • DHCP renewal can cause temporary disconnection of a node.
  • If the host of a virtual machine(s) creates a Windows restore point, then the virtual machine(s) can temporarily disconnect.
  • If a node has been assigned to another master, it will not appear in the inventory.
GUID-B5E256D3-F815-49A9-8EA5-DC99F840B208-low.png Filter on Node NameFilters the displayed results based on Node Name.
Filter on User TagsFilters the displayed results based on Tags contained in the data flow.
Filter on Node TypeFilters the displayed results based on Node Type.
Filter on Operating SystemFilters the displayed results based on Operating System.
Filter on Connection StateFilters the displayed results based on Connection State.
Filter on Authorization StateFilters the displayed results based on Authorization State.

Node Type Wizard

This wizard is launched when a new Node is added to or edited in the Nodes Inventory.

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.

NoteNode names are limited to a maximum of 64 characters.
Node Type Wizard - Application
GUID-6EFD2E0B-97AF-4B39-A5F7-9C45059D3265-low.png
ControlDescription
GUID-48D6BFFE-9187-4487-BE36-82A72F523A72-low.png Oracle DatabaseCreates an application node representing an Oracle database server or RAC. The Oracle Application Node Wizard is launched to guide you through the process.
Select Node Type Wizard - Host
GUID-84C1B2AA-002B-43D5-AF59-45DE4091DAC8-low.png
ControlDescription
GUID-1DE14298-4A5F-47C1-A905-E0FECC3BBCC2-low.png Hitachi Block HostCreates 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.
Select Node Type Wizard - Hypervisor
GUID-E4DD06E1-CED3-45B4-AA6B-FD1758598A6F-low.png
ControlDescription
GUID-47765E5F-A8CD-4891-9D61-0EE482D68FB5-low.png VMwareCreates a hypervisor node representing ESX or VCenter. The VMware Node Wizard is launched to guide you through the process.
Select Node Type Wizard - Storage
GUID-C3859A59-8F40-46BE-8EF8-1C939DC80359-low.png
ControlDescription
GUID-1EEFFE98-5BD2-43D5-A245-59745620E039-low.png Hitachi Block DeviceCreates a device node responsible for managing a Hitachi Block device. The Hitachi Block Storage Node Wizard is launched to guide you through the process.
GUID-8A5BE607-4435-4377-AF3B-7130EE9C0C7C-low.png Hitachi Content PlatformCreates a cloud node for targeting Hitachi Content Platform. The Hitachi Content Platform Storage Node Wizard is launched to guide you through the process.
GUID-3A1E09FA-690D-4A53-8CF2-A1A7202BBF2A-low.png Hitachi Logical Block DeviceCreates a device node with limited access to a Hitachi Block device. The Hitachi Logical Block Storage Node Wizard is launched to guide you through the process.
GUID-D4DBF015-8F0F-46FC-BC78-1E345460AF57-low.png RepositoryCreates a disk based target for storing backups. The Repository Storage Node Wizard is launched to guide you through the process.
GUID-DEE3C93C-8BBB-480F-8DD3-16AF3893C6E2-low.pngAmazon S3Creates a device node responsible for managing an Amazon Simple Storage Service backup. The Amazon S3 Storage Node Wizard is launched to guide you through the process.
Oracle Application Node Wizard

This wizard is launched when a new Oracle Database Node is added to the Nodes Inventory.

NoteIf you have a clustered Oracle environment and add or remove nodes to or from the cluster, the Protector Oracle application node must be updated so that the Oracle environment can be rediscovered. Any active data flows including that node must be reactivated to update the rules.
Oracle Database Node Wizard - Specify Node Name
GUID-0A9B7D93-94FB-4E7B-9777-9E03AA36414C-low.png
Control Description
Node Name Enter a name for the Oracle node.
TagsModifies the tags of an existing object from the either the inventory screen or the details screen of the object.
Oracle DB Node Wizard - Allocate node to Access Control Resource Group
GUID-9B1C834F-3781-4CFD-AE1B-3526C4B51C63-low.png
Control Description
Resource GroupsSelect 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.
Oracle DB Node Wizard - Discover Oracle environment
GUID-2D9469B5-CF40-4A9F-9221-0BDF77A1183B-low.png
Control Description
Node running Oracle to be used for discoverySelect 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.
Note
  • 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.
Oracle DB Node Wizard - Specify Oracle ASM credentials
GUID-B03183A8-045C-4DC1-8B4F-5598347AF6D3-low.png
Control Description
Operating System Select one of the following:
  • Default - use the default owner of the Oracle database from the grid environment.
  • Specify operating system user - specify the operating system user for the Oracle database.
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:
  • Default - use the default database user to execute the SQL commands on the Oracle ASM instance
  • Specify database user - specify the Oracle Database user who can execute the SQL commands on the Oracle ASM instance
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.
Oracle DB Node Wizard - Review database configuration
GUID-74BD96B9-C063-4DDC-BC11-7EBAE282BA2A-low.png
Control Description
SID Click on a database's SID to open the Specify Database credentials dialog (see below).
Rediscover DatabasesClick this button to refresh the cached details.
Oracle DB Node Wizard - Specify Database credentials
GUID-CCB003CF-645C-4A8C-8460-96C348934675-low.png
Control Description
Operating System Select one of the following:
  • Default - use the owner of the Oracle database binary.
  • Specify operating system user - specify the operating system user.
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:
  • Default - use the default database user to execute the SQL commands on the Oracle ASM instance
  • Specify database user - specify the database user who can execute the SQL commands on the Oracle ASM instance
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.
Oracle DB Node Wizard - Summary
GUID-63400856-6BDA-4B46-A6B4-0FD5E877FB9D-low.png
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.

NoteA physical Block Device node must be created using the Hitachi Block Storage Node Wizard before any Block Host nodes can be created on it.
NoteA Block Host node can also be based off of a Logical Block Device, this must also have been created before setting up the Block Host node using the Hitachi Logical Block Storage Node Wizard.

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.

Hitachi Block Host Wizard - Specify Node name
GUID-E65F5F8E-B28C-4C5E-B76D-59A8F5476A52-low.png
ControlDescription
Node NameEnter a name for the Block Host node.
TagsAdd the tags to be associated with the object being created.
Hitachi Block Host Wizard - Allocate node to Access Control Resource Group
GUID-DCF7141E-8219-4B5E-B466-E3A0CB11A4E2-low.png
ControlDescription
Resource GroupsSelect 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.
Hitachi Block Host Wizard - Select Hitachi Block Device
GUID-8DBFE8F5-95BF-49F7-BFCA-FE6E16780686-low.png
ControlDescription
Hitachi Block DeviceEnter or select a Hitachi Block node or Hitachi Logical Block node name from the dropdown list.
Hitachi Block Host Wizard - Specify Logical Devices
GUID-1F9C6BEB-F85E-4286-B078-7A16FC5FB2FF-low.png
ControlDescription
Included Logical DevicesEnter 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 DevicesEnter 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

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

Note
  • 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.
Hitachi Block Host Wizard - Summary
GUID-F044B649-B7A8-489E-8D74-3EF4177B1D80-low.png
ControlDescription
SummarySummary of the settings entered.
VMware Node Wizard

This wizard is launched when a new VMware Node is added to the Nodes Inventory.

NoteIf you use vCenter to manage an ESX/ESXi host, then a proxy node cannot be created for that host. Create a proxy using the managing vCenter node instead.
VMware Node Wizard - Specify Node name
GUID-FF01A7D4-5BBC-4E34-A8FC-C33A35CCABD4-low.png
Control Description
Node Name Enter a name for the VMware node.
TagsAdd the tags to be associated with the object being created.
VMware Node Wizard - Allocate node to Access Control Resource Group
GUID-CD734185-2424-4E02-8D25-D6007067A862-low.png
ControlDescription
Resource GroupsSelect 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.
VMware Node Wizard - Select node to communicate with VMware Server
GUID-4EA5F719-7D11-4202-8067-FA06001BBDC5-low.png
Control Description
Proxy NodeSelect a proxy node for the vCenter or ESX/ESXi host.
Note
  • If using tags, VMware Power CLI 6.5.0 or later must be installed on the proxy node. You will need to restart the proxy node after completing the installation.
  • If you change the proxy of a VMware node while the node is in an activate data flow, or if you change the vCenter or ESX/ESXi host credentials, then you must reactivate affected data flows in order for the changes to take effect.
  • When performing host based backups, avoid excessive traffic across the network by selecting a proxy node that is as close as possible to the eventual destination of the backup data.
  • If the proxy shares access over a SAN to disks used by the VMware datastores and this provides faster data transfer rates than the LAN (NBD), then the VMware SAN Transport Mode will be used during host based backup to transfer data directly from the datastores to the proxy.
VMware Node Wizard - Specify VMware Server
GUID-9653859E-8F91-457D-A8F2-DCCD9E297323-low.png
The same VMware node can be used in both host based and block storage based data flows.
Control Description
Host name or IP Address of vCenter / ESXi ServerSpecify the vCenter or ESX/ESXi host name or IP address.
VMware Node Wizard - Specify VMware Credentials
GUID-9C36E2A6-69F7-415A-BF86-156D53ECF091-low.png
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.
VMware Node Wizard - Summary
GUID-C7E9E6F1-4DB7-494E-8935-E1401C73D0F5-low.png
Control Description
SummarySummary 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, Site Recovery Manager SRA or vRealize Orchestrator workflow) must have the following privileges assigned in vSphere:

TipSome privilege names have changed subtly between vSphere Client UI versions, so a little interpretation may be required. The names used here are consistent with those specified in https://docs.vmware.com/en/VMware-vSphere/6.5/vsphere-esxi-vcenter-server-65-security-guide.pdf
  • 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)
  • 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
  • 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 Storage Node Wizard

This wizard is launched when a new Hitachi Block Node is added to the Nodes Inventory.

Hitachi Block Device Wizard - Specify Node Name
GUID-113FBF1E-79F6-426E-A526-05FE8CB76D5C-low.png
ControlDescription
Node NameEnter a name for the Hitachi Block storage node.
TagsAdd 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.

Hitachi Block Device Wizard - Allocate node to Access Control Resource Group
GUID-6139CE67-7243-4A06-A6DE-C8E5232B042F-low.png
ControlDescription
Resource GroupsSelect 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.
Hitachi Block Device Wizard - Select proxy node
GUID-47CE11FA-634E-4AAE-BC2B-E8BDB8F3B868-low.png
ControlDescription
Proxy NodeSelect 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.
Hitachi Block Device Wizard - Select Metadata Directory
GUID-F2E4CA6D-BE82-44E7-BE2E-92E47932DEA9-low.png
ControlDescription
Common Metadata DirectoryEnter 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.
NoteThis screen is only displayed during node creation, it is not displayed in edit mode.
Hitachi Block Device Wizard - Specify Device
GUID-310A6E3F-647D-438A-A794-2AADF88FFB27-low.png
ControlDescription
Select from detected storage devicesSelect 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 portSelect 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.

Hitachi Block Device Wizard - Specify credentials for device
GUID-15CCEE89-5D87-4282-B7DA-298449434670-low.png
ControlDescription
Storage Device Serial NumberDisplays the serial number of the Block device specified in the previous step.
UsernameEnter 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. 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.
PasswordEnter the password for the Block device.
NoteThe password for authorizing a Block device must contain only useable CCI command characters: A-Za-z0-9’-./:@\_
Hitachi Block Device Wizard - Specify LDEV Provisioning Range
GUID-9BFC7033-3AFA-4FD6-ACF0-5EA7D30FBA15-low.png
ControlDescription
AllSelect this option if you want Protector to automatically detect the LDEV range from which snapshots and replications should be allocated.
User definedSelect 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.

StartEnabled only if User defined is selected. Enter the lower limit of the LDEV range to use for allocation.
EndEnabled only if User defined is selected. Enter the upper limit of the LDEV range to use for allocation.
Hitachi Block Device Wizard - Command Device Specification and Priority
GUID-E9DE1742-A6F3-450B-8F18-7AC47318EDA8-low.png

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.

ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled when only one command device is selected. Launches the Configure Command Device wizard below to allow the settings to be edited.
GUID-C4D33EF3-52EC-4289-ABA0-DE3741E1FEED-low.png Increase PriorityEnabled when only one command device is selected. Increases the priority of the selected command device.
GUID-101B8ECA-BB8B-4C5C-A9CB-89C4BC4DEC76-low.png Decrease PriorityEnabled when only one command device is selected. Decreases the priority of the selected command device.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled when one or more command devices are selected. Deletes selected command device.
AddLaunches the Configure Command Device wizard below to guide you through setting up a fibre or IP command device.
Hitachi Block Device Wizard - Configure Command Device - Fibre
GUID-D2502209-DD1F-49CB-8848-F56F6319FEF4-low.png
ControlDescription
Use any available fibre command deviceSelect 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 devicesSelect 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.
Hitachi Block Device Wizard - Configure Command Device - IP
GUID-1485B9F5-DA0D-4FFA-A8ED-03ED3217C9F0-low.png
NoteWhen configuring IP command devices for VSP G1x00 storage devices, we recommend adding one for CTL1 and one for CTL2, to maintain dual redundancy.
ControlDescription
IP Address or HostnameEnter 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 NumberEnter the port number of the command device.
Hitachi Block Wizard - Specify LDEV Ranges for each VSM
GUID-6AE4BB95-EA01-451B-84FD-D0D9DD91E37B-low.png
NoteGAD replications require P-VOLs and S-VOLs to have matching virtual serial numbers and virtual LDEV IDs. To avoid virtual LDEV ID collisions between GAD volumes and non-GAD S-VOLs (created by Protector for other types of replications and snapshots), it is possible to define virtual LDEV ID ranges to be used by those non-GAD operations. Virtual LDEV ranges can be specified for each VSM (Virtual Storage Machine) to be used.
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled 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.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only if one or more Virtual LDEV ranges are selected. Deletes the Virtual LDEV range(s) from the list.
AddAdds 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.
Hitachi Block Wizard - Configure Virtual LDEV Range
GUID-77C72821-BF54-40AD-8156-70E97C613D87-low.png
CautionThese ranges are used to control the virtual LDEV IDs used for non-GAD replications and snapshots. They must be defined to exclude the IDs of any GAD volumes. Failure to provide such a range (or providing an incorrect range) may result in ID clashes when attempting to set up GAD replications.
ControlDescription
VSM Serial NumberEnter the serial number of the VSM you intend to use within Protector.
Start of LDEV rangeEnter the lower limit of the LDEV range to use for allocation.
End of LDEV rangeEnter the lower limit of the LDEV range to use for allocation.
Hitachi Block Device Wizard - Specify ports used for provisioning
GUID-C11170CF-C11B-4323-8841-762718DA5A6E-low.png
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled 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.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only if one or more provisioning ports are selected. Deletes the port(s) from the list.
AddAdds 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.
Hitachi Block Device Wizard - Specify Port
GUID-8215E555-A098-4470-AF4A-0EE86C809A5B-low.png
NoteIf more than one provisioning port is selected, then the port with the least amount of LUNs will be used.
ControlDescription
PortEnter 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
Hitachi Block Wizard - Summary
GUID-DDFB57CB-FA4A-415A-B4AC-0E229F4B3FD3-low.png
ControlDescription
SummarySummary 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.

NoteEnsure that the Proxy Node defined within the wizard and the Hitachi Content Platform node are time synced. If the time is different by over 5 minutes, then the node creation and future backup may fail. It is recommend that the system time on all nodes should have the correct date/time associated with their particular region and time zone.
Hitachi Content Platform Wizard - Specify Node Name
GUID-05DF876B-D58D-4EB3-A145-D7BB9714BDB9-low.png
ControlDescription
Node NameEnter a name for the HCP storage node.
TagsAdd the tags to be associated with the object being created.
Hitachi Content Platform Wizard - Allocate node to Access Control Resource Group
GUID-A40156D7-3C9F-4879-B131-C674A6A1D196-low.png
ControlDescription
Resource GroupsSelect 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.
Hitachi Content Platform Wizard - Select Node Generation
GUID-A92B4243-DB99-4C73-B69D-CD612228C657-low.png
ControlDescription
Generation 2Select this for a generation 2 storage node which is compliant with the new Universal Backup Infrastructure interface. This is the recommended option.
Generation 1Select 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.
Hitachi Content Platform Wizard - Specify Node creation mode
GUID-94C0BC01-CF96-4A88-A147-90F89BED0BBA-low.png
ControlDescription
Create a new HCP nodeSelect this to setup a new HCP node.
Import an existing HCP nodeSelect this to import an existing HCP node.
Hitachi Content Platform Wizard - Select Proxy Node
GUID-CB5E1AF2-2291-499B-923E-B5E784AEF7BA-low.png
ControlDescription
Proxy NodeSelect a Protector node to act as a proxy.
Hitachi Content Platform Wizard - Specify node Metadata cache directory
GUID-35635627-9424-4909-B51C-7B8014603630-low.png
ControlDescription
Metadata DirectoryEnter 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.
Hitachi Content Platform Wizard - Configure HCP Tenant
GUID-79C62781-20B5-4C45-ACB9-68D34F361D48-low.png
ControlDescription
Tenant Host NameEnter the host name for the tenant in the form <tenant>.<hcp_name>.<domain>.
Enable HTTPSHTTPS is used by default to transfer data to and from HCP, but this can be disabled if performance takes precedence over security. Restoring data that was tiered using Protector 5.x either requires HTTPS or the namespace settings must be manually altered to allow it.
UsernameEnter a user name for the tenant specified above.
PasswordEnter the password for the user.
Hitachi Content Platform Wizard - Configure HCP Namespace defaults
GUID-56BE8F2A-28B8-47EA-ABB3-3A1EF0363A4A-low.png
ControlDescription
NamespaceThis 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 LevelThis is the percentage of free space at which additional backups are prevented
Hitachi Content Platform Wizard - Summary
GUID-36F55DBE-5049-4011-8DBC-4457B7B65323-low.png
ControlDescription
SummarySummary of the settings entered.
Hitachi Logical Block Storage 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.

NoteA Physical Block node must be created using the Hitachi Block Storage Node Wizard before any Logical Block nodes can be created on it.
Hitachi Logical Block Wizard - Specify Node name
GUID-E5F2C893-5EF6-4284-AF4B-4DAEA1AF40EC-low.png
ControlDescription
Node NameEnter a name for the Logical Block node.
TagsAdd 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 GroupType the name of the resource group or select one from the drop down list.
Hitachi Logical Block Wizard - Allocate node to Access Control Resource Group
GUID-FF5C1290-8BEC-4569-864E-939F3D4ED13E-low.png
ControlDescription
Resource GroupsAll 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.
Hitachi Logical Block Wizard - Select Hitachi Block Device
GUID-5CDB6008-D3BA-4A9E-8191-4A604B0BB621-low.png
ControlDescription
Hitachi Block Device NodeEnter or select the name of the Physical Block node on which the Logical Block node will be based .
Hitachi Logical Block Wizard - Specify LDEV Provisioning Range
GUID-DD7E84D0-CFA8-4063-BE5F-44082FD31851-low.png
ControlDescription
LDEV RangeSpecify 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.

Hitachi Logical Block Wizard - Specify Primary LDEV accessible to this device
GUID-7B7D65C8-28CC-4111-AAD7-FF663F520F36-low.png

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.

NoteThis information is optional. If nothing is specified here, then no P-VOLs will be available for snapshotting or replicating on this logical block device.
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled 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.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only if one or more LDEV Filters are selected. Deletes the LDEV Filter(s) from the list.
AddAdds 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.
Hitachi Logical Block Wizard - Specify Primary LDEVs filter
GUID-29759119-855C-44D1-8160-40C7048D9562-low.png
Specify one or more of the following parameters to identify the Primary LDEV(s):
NoteThe terms entered here are logically ANDed together, so an LDEV will only be selected if it matches the Name Pattern AND ID Range AND Host Group ID.
ControlDescription
LDEV Name PatternEnter 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 RangeEnter the range of the Primary LDEV IDs that will be made available on this logical block device.
Host Group IDEnter a Host Group identifier.
TipHost Group ID is normally used alone rather than in combination with the other filter terms presented here.
Hitachi Logical Block Wizard - Specify ports used for provisioning
GUID-697066E8-87E0-432E-849D-9FDFBF79C5A5-low.png
NoteThis information is optional. Protector creates dummy Host Groups for its own processing needs. If nothing is specified here, then Protector will use any available port when creating these dummy Host Groups.
TipUse this list to restrict Protector to using LUN allocations on designated ports only.
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled 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.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only if one or more provisioning ports are selected. Deletes the port(s) from the list.
AddAdds 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.
Hitachi Logical Block Wizard - Specify Port
GUID-4F64A114-4514-4162-9F33-297E5112DD3B-low.png
ControlDescription
PortSpecify a port that can be used by Protector for its own processing needs.

Enter a 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
Hitachi Logical Block Wizard - Specify Journals accessible to this device
GUID-A01777D0-A16D-4D45-8667-28435CE7A9C1-low.png
NoteThis information is optional. If nothing is specified here, then no source or destination Journals will be available for Universal Replicator on this logical block device.
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled 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.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only if one or more Journal Ranges are selected. Deletes the Journal Range(s) from the list.
AddAdds 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 RangesThe Journal Range to be used.
Hitachi Logical Block Wizard - Specify Journal range
GUID-12D6328C-2653-439B-B2CD-86F7FF8C9FD4-low.png
ControlDescription
Journal ID RangeEnter the Journal ID range that will be made available on this logical block device.
Hitachi Logical Block Wizard - Specify Host Groups accessible to this device
GUID-E7A5D31F-EBBD-4940-B395-1C8CD354E5C9-low.png
NoteThis information is optional. If nothing is specified here, then no Host Groups will be available on this logical block device for:
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled 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.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only if one or more Host Group Filters are selected. Deletes the Host Group Filter(s) from the list.
AddAdds 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.
Hitachi Logical Block Wizard - Specify Host Group filter
GUID-0268B328-868C-4ED9-92FF-8C3DD5F779D7-low.png
Specify one or more of the following parameters to identify the Host Groups:
NoteThe terms entered here are logically ANDed together, so a Host Group will only be selected if it matches the Name Pattern AND ID Range AND Port ID.
ControlDescription
Host Group Name PatternEnter a regular expression (see Basic regular expressions) to identify matching Host Group Names.
Host Group ID rangeEnter the lower and upper limit of the Host Group ID range to use.
Port IDEnter 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
Hitachi Logical Block Wizard - Specify Pools accessible to this device
GUID-DD2A3500-AF64-4BEA-83B9-907BC7361F63-low.png
NoteThis information is optional. If nothing is specified here, then no Pools will be available on this logical block device for creating snapshots or replications.
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEnabled 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.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only if one or more Pool Filters are selected. Deletes the Pool Filter(s) from the list.
AddAdds 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 FilterThe Pool Filter(s) to be used.
Hitachi Logical Block Wizard - Specify Pool filter
GUID-00F9E091-E23B-4195-85B5-D98B67957D15-low.png
Specify one or more of the following parameters to identify the Pools:
NoteThe terms entered here are logically ANDed together, so a Pool will only be selected if it matches the Name Pattern AND ID Range.
ControlDescription
Pool Name PatternEnter a regular expression (see Basic regular expressions) to identify matching Pool Names.
Pool ID rangeEnter the Pool ID range to use.
Hitachi Logical Block Wizard - Summary
GUID-4BB79E19-B296-4C10-B3AE-B1516CC7D909-low.png
ControlDescription
SummarySummary 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.

Commonly used regex matching terms
Type of MatchRegex ExampleActionExplanation
Contains the sub-string (case sensitive)thisMatches any string containing the sub-string this, respecting the case

e.g.:

Grab this thistle

A sub-string on its own will be matched anywhere within the search string.
Contains the sub-string (case insensitive)(?i)thisMatches any string containing the sub-string this, without regard to case

e.g.:

Grab ThiS thIstle

The (?i) mode modifier turns off case sensitive matching
Starts with the sub-string^thisMatches any string starting with this

e.g.:

this is a tree

The ^ anchor means the sub-string must appear at the start of the string being searched
Ends with the sub-stringthat$Matches any string ending with that

e.g.:

don't touch that

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.:

this time it matters

and:

that's life

and:

other types available

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.:

you can't touch this

and:

please don't do that

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.:

this is the answer to that

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.

Repository Wizard - Specify Node name
GUID-63B7F311-8AD5-42B3-992F-A5E2E68D6ED8-low.png
ControlDescription
Node NameEnter a name for the Repository node.
NoteRepository nodes that are hosted on the same Proxy Node must be uniquely named.
TagsAdd the tags to be associated with the object being created.
Repository Wizard - Allocate node to Access Control Resource Group
GUID-0D74A380-8DE1-466E-AD55-007CD75EF658-low.png
ControlDescription
Resource GroupsSelect 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.
Repository Wizard - Select Proxy Node
GUID-C41185FA-0F15-4C5A-B216-83BCE3EB22E4-low.png
ControlDescription
Proxy NodeEnter or select the node that will host the Repository.
Repository Wizard - Specify creation mode
GUID-C6194DFE-8E00-40A4-A2F9-79F1CB937519-low.png
ControlDescription
ModeSelect one of the following options:
  • Create a new Repository
  • Import an existing Repository
If selection Import an existing Repository, you will be presented with the following wizard page.
OR: Repository Wizard - Select existing repository directory
GUID-9E9EA1E6-D43F-45B9-A86C-313F57959C3D-low.png
ControlDescription
DirectoryEnter 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.
Repository Wizard – Select node generation
GUID-94EE9F99-E7CF-476C-A5A1-785C57B84078-low.png
ControlDescription
Generation 1A 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.
Generation2It 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.
Repository Wizard – Specify Repository directories
GUID-F34D736D-7BF7-4658-87E6-301C088DE82B-low.png
ControlDescription

Root Directory

The root directory is the location where the configuration data for the repository is held.
Data DirectoryThe data directory holds the actual backed up data contents of the repository.
Metadata DirectoryThe 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 DirectoryThe checksum directory is used to store the checksums generated when Fine Change Detection is enabled.
Repository Wizard – Configure Repository encryption
GUID-EBF86B61-F96B-4E49-A2FC-7B7AEEA1B985-low.png
ControlDescription
Enable Repository EncryptionYou 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 PassphraseEnter 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 PassphraseRe-enter the encryption password to ensure it has been typed correctly.
Repository Wizard – Configure Repository settings
GUID-7E20B1E6-4CB1-4448-A3C7-695DFCCB0F5A-low.png
ControlDescription
Optimize for Cloud ReplicationAligns block boundaries between the repository and the cloud in order to make cloud uploads more efficient.
Single Instance Repository dataEnables 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 LevelWhen 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 LevelWhen 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 SizeSets the block size the repository uses. It is recommended that this matches the filesystem block size where possible.
Repository Wizard - Summary
GUID-B979757A-09D2-4EE3-A284-D825CC44CFA8-low.png
ControlDescription
SummarySummary of the parameters entered above.
Amazon S3 Storage Node Wizard

This wizard is launched when a new Repository Node is added to the Nodes Inventory.

NoteEnsure that the Proxy Node defined within the wizard and the Amazon S3 Proxy node are time synced. If the time is different by over 5 minutes, then the node creation and future backup may fail. It is recommend that the system time on all nodes should have the correct date/time associated with their particular region and time zone.
Amazon S3 Wizard - Specify Node Name
GUID-CB87AF3E-460B-41A2-B3A7-1B8F85BBF544-low.png
ControlDescription
Node NameEnter a name for the Amazon S3 node.
NoteRepository nodes that are hosted on the same Proxy Node must be uniquely named.
TagsAdd the tags to be associated with the object being created.
Amazon S3 Wizard - Allocate Node to Access Control Resource Group
GUID-F98C0146-7507-4D70-9CC3-ACF2F8BAC0D3-low.png
ControlDescription
Resource GroupsSelect 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.
Amazon S3 Wizard - Specify Creation Mode
GUID-563A6CCF-8F7E-42BD-A468-6E0AB59617BD-low.png
ControlDescription
ModeSelect one of the following options:
  • Create a new Amazon S3 node
    • This will start a new store in Amazon S3.
  • Import an existing Repository
    • This will utilise a backup store that already exists in Amazon S3.
Subsequent screens are the same for either choices.
Amazon S3 Wizard - Select Proxy Node
GUID-DDFE86B3-0062-43E7-A443-04D2D30A731C-low.png
ControlDescription
Proxy NodeEnter or select the node that will host the Amazon S3 proxy.
Amazon S3 Wizard - Specify Node Metadata Cache Directory
GUID-ABCC5F6E-0456-4A64-B73A-B22E12137CE1-low.png
ControlDescription
DirectoryEnter the path of the directory where you want to create the new Amazon 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 are stored in Amazon S3. This is only a cache and can be rebuilt from the Amazon S3 content if lost.

Amazon S3 Wizard - Configure S3
GUID-8F1A6393-0FB9-4547-B2AF-FDF45294FCFB-low.png
ControlDescription
Access Key ID Amazon S3 Access Key ID. This is the equivalent of a user . See Amazon S3 documentation for further information.
Secret Access KeyAmazon S3 Secret Access Key. This is the equivalent of a password. See Amazon S3 documentation for further information.
Bucket NameThis 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.
RegionThis 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.
Amazon S3 Wizard - Summary
GUID-A8A7B028-564F-4C61-BAF0-CFED522D0B51-low.png
ControlDescription
SummarySummary 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.

Node Details (OS Host)
GUID-DF83B70E-3051-4914-AD1F-8590B460BB38-low.png
Common Controls (Displayed for all node types)
ControlDescription
LogsIndicates the number of unacknowledged error logs in red. If there are no errors then a green tick is displayed instead. Summarises the number of unacknowledged errors and warnings. Opens the Logs Inventory.
JobsIndicates the number of failed jobs in red. If there are no failed jobs then a green tick is displayed instead. Summarises the number of failed, paused and in-progress jobs. Opens the Jobs Inventory.
SummaryIndicates the following:
  • Status (Online/Offline) - indicates if the node is contactable by the Master node.
  • Protector Version - The version number of the Protector software running on the node.
  • Tags
OS Host Specific Controls
ControlDescription
ConfigurationIndicates the following:
  • Operating System - the name of the operating system on the node.
  • Virtual Machine - indicates the machine is running on a hypervisor.
  • IP Addresses - all the IP addresses in use on the node.
Hosted NodesLists all the nodes for which this node acts as the proxy.
Oracle Specific Controls
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the Oracle Application Node Wizard to enable the parameters to be edited.
DetailsDisplays the node's online status.
ConfigurationDisplays the node type and configuration.
Host NodesLists all the nodes that act as the proxy for this node.
VMware Specific Controls
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the VMware Node Wizard to enable the parameters to be edited.
ConfigurationIndicates the following:
  • VMware Username.
  • VMware Server.
Hitachi Block Specific Controls
ControlDescription
GUID-8E270223-62F5-4D7B-90CF-AF2233B30A3C-low.png ManageOpens the storage Hitachi Block Device Details for this node.
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the Hitachi Block Storage Node Wizard to enable the parameters to be edited.
GUID-E5F1CBC8-471E-4699-9E6D-E16DF64C3EA3-low.pngTagAdd the tags to be associated with the object being created.
Configuration Indicates the following:
  • Storage Serial.
  • Username.
  • LDEV Range.
PortList the available ports for this node.
Command Device TypeLists the command devices and their type.
Virtual SerialLists the Virtual Serial devices.
Hosted NodesLists all the nodes for which this node acts as the proxy.
Hitachi Block Host Specific Controls
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the Hitachi Block Host Node Wizard to enable the parameters to be edited.
DetailsDisplays the node's online status.
ConfigurationIndicates the Hitachi Block Device on which this node is based.
Included Logical DevicesList the LDEVs represented by this node.
Excluded Logical DevicesList the LDEVs excluded for this node.
Hitachi Logical Block Specific Controls
ControlDescription
GUID-8E270223-62F5-4D7B-90CF-AF2233B30A3C-low.png ManageOpens the storage Hitachi Block Logical Device Details for this node.
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the Hitachi Logical Block Storage Node Wizard to enable the parameters to be edited.
DetailsDisplays the node's online status.
ConfigurationIndicates the parent Hitachi Block Device Node.
LDEV RangeThe LDEV provisioning ranges available for this node.
Repository Specific Controls
ControlDescription
GUID-8E270223-62F5-4D7B-90CF-AF2233B30A3C-low.png ManageOpens the storage Generation 1 Repository Details for this node.
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the Repository Storage Node Wizard to enable editing the capacity level.
DetailsDisplays the nodes proxy.
AttributesIndicates the follow:
  • Generation – The generation of the repository (affects supported options).
  • Encryption – Repository encryption enabled or disabled.
  • Cloud Optimized – (Generation 2) Data chunk size optimized for cloud storage. Enabled or disabled.
  • Single Instancing – (Generation 2) Store a single instance of a block. Enabled or disabled.
  • Capacity Warning Level – Percentage of disk space at which the repository enters the warning state.
  • Capacity Critical Level – Percentage of disk space at which the repository will automatically unmount.
  • Block Size.
PathsIndicates the following:
  • Root Directory.
  • Data Directory.
  • Metadata Directory.
  • Checksums Directory.
Hitachi Content Platform Specific Controls
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the Hitachi Content Platform Storage Node Wizard to enable the parameters to be edited.
ConfigurationIndicates the following:
  • Generation – The generation of the HCP node.
  • Metadata directory.
  • Username - The username used when connecting to the HCP Tenant Console.
  • Tenant Address - The address used when connecting to the HCP Tenant Console.
  • HTTPS - Use HTTP or HTTPS when transferring data to and from HCP.
Namespace
  • Name.
  • Created.
  • Hard Quota – The size of name space.
  • Soft Quota – Percentage of hard quota.

Node Type Icons

The node icons and indicators used in the lists of unauthorized and authorized nodes.

IconDescription
GUID-802B82F5-F660-4AE9-987C-2BEC8D418DB8-low.pngMaster Node - Indicates that this node is the master node.
GUID-EC8C73D0-3181-4DF7-B9D8-563FB0D463B9-low.png OS Host Node - A Workstation, Laptop or Server node with the Protector services installed.
GUID-D4DBF015-8F0F-46FC-BC78-1E345460AF57-low.pngRepository Node - A node with the Protector Repository component installed. Used to store snapshots of data backed up from various types of source nodes.
GUID-47765E5F-A8CD-4891-9D61-0EE482D68FB5-low.pngVMware ESX Node - A node containing virtual machines, and accessed through a separate proxy node.
GUID-8A5BE607-4435-4377-AF3B-7130EE9C0C7C-low.pngHitachi Content Platform Node - A node representing an Hitachi Content Platform.
GUID-1EEFFE98-5BD2-43D5-A245-59745620E039-low.pngHitachi Block Node - A node representing a Hitachi Block Storage Device.
GUID-1DE14298-4A5F-47C1-A905-E0FECC3BBCC2-low.pngHitachi Block Host Node - A node that represents a number of Hitachi Block Storage volumes.
GUID-3A1E09FA-690D-4A53-8CF2-A1A7202BBF2A-low.pngHitachi Logical Block Device Node - A logical view of Hitachi Block Storage Device node, having limited access to its resources.
GUID-48D6BFFE-9187-4487-BE36-82A72F523A72-low.pngOracle Node - Represents a cluster of servers running as an Oracle RAC that accesses databases on shared disks.
GUID-7246603A-A0D8-48D5-988C-54444159C32A-low.pngUnknown Node - The master node is unable to determine any node details, and cannot connect to it.
GUID-B33A6556-3CCE-45ED-9526-5419C3BAC8A5-low.pngInactive 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.
GUID-53BBC528-FBE4-4D0D-BD78-246DDC3164A3-low.pngNode Group - Represents a group of nodes that can be treated identically when assigning policies or monitoring activities.
GUID-DEE3C93C-8BBB-480F-8DD3-16AF3893C6E2-low.pngAmazon S3 Node - A node representing an Amazon S3 Bucket

Node Status Indicators

Small graphical indicators that provide visual cues as to a particular node’s status.

IconDescription
GUID-EC1C5E83-C8E7-4295-BF48-0F05578F6382-low.pngUnauthorized Node - The node has Protector installed but has not been authorized by the Master node, so cannot interact with other Protector nodes.
GUID-548F548E-D971-477B-8655-0F8DB9F38C85-low.pngAuthorized Online Node - The node has Protector installed and has been authorized by the Master node, so can interact with other Protector nodes.
GUID-7C18CB49-A428-4F78-A99F-17F5C7C4A506-low.pngOffline - The node is not contactable from the Master so its status cannot be determined.
GUID-0BC0CC66-7F27-4E79-BE6D-B1796138FF4E-low.pngSnapshotted 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.

Node Groups Inventory
GUID-B9AD3D9D-56C3-4291-9F0A-CC9D27481F22-low.png
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditEdits an existing node group in the inventory. The Node Group Wizard is launched to enable the group's attributes to be changed.
GUID-C06C9D94-4B99-4317-AFE8-EF7DB67C63CB-low.png DeleteEnabled only when one or more Node Group is selected. Deletes the selected item from the inventory. The associated Nodes are not deleted.
AddCreates a new Node Group. The Node Group Wizard is launched to guide you through the process.
GUID-53BBC528-FBE4-4D0D-BD78-246DDC3164A3-low.pngUser defined Node Group(s)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 NameFilters the displayed results based on Node Name.
Filter on User TagsFilters the displayed results based on Tags contained in the data flow.
Filter on Node TypeFilters the displayed results based on Node Type.

Node Group Wizard

This wizard is launched when a new Node Group is added to the Node Groups Inventory.

Node Group Wizard - Specify name and description
GUID-9760FC65-2F05-4A76-967B-16915835E508-low.png
ControlDescription
NameEnter the name of the node group.
DescriptionOptional. Enter a description of the node group.
TagsAdd the tags to be associated with the object being created.
Node Group Wizard - Specify Node Group Type
GUID-7E9450B9-6ADD-4256-B9C9-C41BF329DBAC-low.png
ControlDescription
Node TypeSpecifies the node type that this group will contain. Only node types that can have a common policy assigned are available.
Operating SystemIf the OS Host node type is selected then this control is enabled so that a specific operating system can be selected.
Node Group Wizard - Manage Nodes
GUID-DDA14759-8AAC-42B5-B36F-BF0F3CC32BF2-low.png
ControlDescription
Node NameFilters the list of nodes displayed below by name.
Click to addLists all available nodes of the specified type. Click on the name of the node you want to add to this node group.
Click to removeLists 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.

Node Group Details
GUID-6C3D5ED9-C6C4-4A99-8B39-CE1F5E47C025-low.png
ControlDescription
GUID-2DB31664-7FB9-441F-8595-06A8E5A178EF-low.png EditLaunches the Node Group Wizard to enable you to view and edit the node group.
GUID-E5F1CBC8-471E-4699-9E6D-E16DF64C3EA3-low.pngTagModifies the tags of an existing object from the either the inventory screen or the details screen of the object.
GUID-EC8C73D0-3181-4DF7-B9D8-563FB0D463B9-low.png Nodes in groupClick the node name to open the Node Details to enable you to view the node's status and details.

Node Tasks

This section describes node configuration tasks that users will perform with Ops Center Protector.

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).

NoteOS Host nodes do not need to be added to the Nodes Inventory because they are automatically detected by the Master when the Client software component is installed.

The specific role of a node is determined when it is added to the Nodes Inventory as follows:

Procedure

  1. Click Nodes on the Navigation Sidebar to open the Nodes Inventory.

  2. Click Create new item to open the Node Type Wizard.

  3. 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.
  4. 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

  1. Click Nodes on the Navigation Sidebar to open the Nodes Inventory.

  2. Select the tile for the node you want to authorize by clicking in its top left corner.

    Unauthorized nodes display a GUID-EC1C5E83-C8E7-4295-BF48-0F05578F6382-low.png icon in the top right corner
  3. Click Authorize Node above the inventory area.

  4. Wait a few moments for the node to be authorized.

    Authorized nodes display a GUID-548F548E-D971-477B-8655-0F8DB9F38C85-low.png icon in the top right corner.

 

  • Was this article helpful?