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
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.
WARNINGDo not decommission hardware or virtual machines before removing the nodes representing them.
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.
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.
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.
This inventory lists all the nodes in a Protector network, be they online, offline, authorized or deauthorized.
Nodes Inventory
Control
Description
Edit
Edits an existing node in the inventory. The Node Type Wizard is launched to enable the node's attributes to be changed.
Edit Tags
Modifies the tags of an existing object from the either the inventory screen or
the details screen of the object.
Authorize
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.
Deauthorize
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
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.
Upgrade Clients
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
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.
Delete
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.
Create a new item
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
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.
Filter on Node 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 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.
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
Control
Description
Microsoft SQL Server
Creates an application node representing Microsoft SQL Server . The Microsoft SQL Server Node Wizard is launched to guide you through the process.
Oracle Database
Creates 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
Control
Description
Hitachi Block Host
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.
Select Node Type Wizard - Hypervisor
Control
Description
Microsoft Hyper-V
Creates a hypervisor node Microsoft Hyper-V. The Hyper-V Node Wizard is launched to guide you through the process.
VMware
Creates a hypervisor node representing ESX or VCenter. The VMware Node Wizard is launched to guide you through the process.
Select Node Type Wizard - Storage
Control
Description
Amazon S3
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.
Hitachi Block Device
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 for cloud scale. The Amazon S3 Storage Node Wizard is launched to guide you through the process.
Protector will launch
this wizard when a new Microsoft SQL Server node is added to the Nodes
Inventory.
Microsoft SQL Node Wizard - Specify Node
Name
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.
Microsoft SQL Node Wizard - Allocate node
to Access Control Resource Group
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.
Microsoft SQL Node Wizard - Discover
Microsoft SQL environment
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.
Microsoft SQL Node Wizard -
Summary
Control
Description
Summary
Summary of the settings and nodes selected in the node creation 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
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.
Oracle DB Node Wizard - Allocate node to Access Control Resource Group
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.
Oracle DB Node Wizard - Discover Oracle environment
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.
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
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
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.
Oracle DB Node Wizard - Specify Database credentials
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.
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 Device 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 Device 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
Control
Description
Node Name
Enter a name for the Block Host node.
Tags
Add the tags to be associated with the object being created.
Hitachi Block Host Wizard - Allocate node to Access Control
Resource Group
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.
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
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.
This wizard is launched when a new Hyper-V Node is added to the Nodes Inventory.
Hyper-V Node Wizard - Specify Node name
Control
Description
Node Name
Enter a name for the Hyper-V node.
Tags
Add the tags to be associated with the object being created
Hyper-V Node Wizard - Allocate node to Access Control Resource Group
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.
Hyper-V Node Wizard - Select node running Hyper-V server
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
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:
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
Control
Description
Node Name
Enter a name for the VMware node.
Tags
Add the tags to be associated with the object being created.
VMware Node Wizard - Allocate node to Access Control Resource Group
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.
VMware Node Wizard - Select node to communicate with VMware Server
Control
Description
Proxy Node
Select 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 ServerThe 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 Server
Specify the vCenter or ESX/ESXi host name or IP address.
VMware Node Wizard - Specify VMware Credentials
Control
Description
Username
Enter the username for the vCenter or ESX/ESXi host.
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:
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.
This wizard is launched when a new Hitachi Block Node is added to the Nodes Inventory. Hitachi Block Device Wizard - Specify Node Name
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.
Hitachi Block Device Wizard - Allocate node to Access Control Resource Group
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.
Hitachi Block Device Wizard - Select proxy node
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.
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.
NoteThis screen is only displayed during node creation, it is not displayed in edit mode.
Hitachi Block Device Wizard - Specify Device
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.
Hitachi Block Device Wizard - Specify credentials for device
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’-./:@\_
Hitachi Block Device Wizard - Specify Configuration for GRR
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.
Hitachi Block Device Wizard - Specify LDEV Provisioning Range
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.
Hitachi Block Device Wizard - Command Device Specification and Priority
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
Edit
Enabled when only one command device is selected. Launches the Configure Command Device wizard below to allow the settings to be edited.
Increase Priority
Enabled when only one command device is selected. Increases the priority of the selected command device.
Decrease Priority
Enabled when only one command device is selected. Decreases the priority of the selected command device.
Delete
Enabled when one or more command devices are selected. Deletes selected command device.
Add
Launches the Configure Command Device wizard below to guide you through setting up a fibre or IP 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.
Hitachi Block Device Wizard - Configure Command Device - IP
NoteWhen configuring IP command devices for VSP G1x00 storage devices, we recommend adding one for CTL1 and one for CTL2, to maintain dual redundancy.
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.
Hitachi Block Wizard - Specify LDEV Ranges for each VSM
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.
Control
Description
Edit
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.
Delete
Enabled only if one or more Virtual LDEV ranges are selected. Deletes the Virtual LDEV range(s) from the list.
Add
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.
Hitachi Block Wizard - Configure Virtual LDEV Range
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.
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.
Hitachi Block Device Wizard - Specify ports used for provisioning
Control
Description
Edit
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.
Delete
Enabled only if one or more provisioning ports are selected. Deletes the port(s) from the list.
Add
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.
Hitachi Block Device Wizard - Specify Port
NoteIf more than one provisioning port is selected, then the port with the least amount of LUNs will be used.
Control
Description
Port
Enter the port identifier in the following format:
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
Control
Description
Node Name
Enter a name for the HCP storage node.
Tags
Add the tags to be associated with the object being created.
Hitachi Content Platform Wizard - Allocate node to Access Control Resource Group
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.
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.
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.
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
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 Device Node Wizard before any Logical Block nodes can be created on it.
Hitachi Logical Block Wizard - Specify Node name
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.
Hitachi Logical Block Wizard - Allocate node to Access Control Resource Group
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.
Enter 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
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.
Hitachi Logical Block Wizard - Specify Primary LDEV accessible to this device
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.
Control
Description
Edit
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.
Delete
Enabled only if one or more LDEV Filters are selected. Deletes the LDEV Filter(s) from the list.
Add
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.
Hitachi Logical Block Wizard - Specify Primary LDEVs filterSpecify 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.
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.
Hitachi Logical Block Wizard - Specify ports used for provisioning
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.
Control
Description
Edit
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.
Delete
Enabled only if one or more provisioning ports are selected. Deletes the port(s) from the list.
Add
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.
Hitachi Logical Block Wizard - Specify Port
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:
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
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.
Control
Description
Edit
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.
Delete
Enabled only if one or more Journal Ranges are selected. Deletes the Journal Range(s) from the list.
Add
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.
Hitachi Logical Block Wizard - Specify Journal range
Control
Description
Journal ID Range
Enter 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
NoteThis information is optional. If nothing is specified here, then no Host Groups will be available on this logical block device for:
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.
Delete
Enabled only if one or more Host Group Filters are selected. Deletes the Host Group Filter(s) from the list.
Add
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.
Hitachi Logical Block Wizard - Specify Host Group filterSpecify 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.
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:
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
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.
Control
Description
Edit
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.
Delete
Enabled only if one or more Pool Filters are selected. Deletes the Pool Filter(s) from the list.
Add
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.
Hitachi Logical Block Wizard - Specify Pool filterSpecify 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.
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 Match
Regex Example
Action
Explanation
Contains the sub-string (case sensitive)
this
Matches 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)this
Matches 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
^this
Matches 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-string
that$
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
This wizard is launched when a new Repository Node is added to the Nodes Inventory.
Repository Wizard - Specify Node name
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.
Repository Wizard - Allocate node to Access Control Resource Group
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.
Repository Wizard - Select Proxy Node
Control
Description
Proxy Node
Enter or select the node that will host the Repository.
Repository Wizard - Specify creation mode
Control
Description
Mode
Select 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.
Create New RepositoryOR: Repository Wizard - Select existing repository directory
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.
Repository Wizard – Select node generation
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.
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.
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.
Repository Wizard – Configure Repository settings
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.
Repository Wizard - Summary
Control
Description
Summary
Summary of the parameters entered above.
Import an existing Repository
OR: Repository Wizard - Select existing repository directory for Import
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.
Repository Wizard – Summary of Import Repository Wizard
Control
Description
Summary
Summary of the parameters entered for Import Repository Wizard.
This wizard is launched when a new Amazon S3 Node is added to the Nodes Inventory.
NoteEnsure that the Proxy Node defined within the wizard is time synced. If the time is different by over 5 minutes, then the node creation and future backup may fail. It is recommended that the system time on all nodes should have the correct date/time associated with their particular region and time zone.
NoteThere are some differences between the Amazon S3 node creation and the HCP cloud scale node creation which will be noted in this section. ‘S3 Node’ will be used as a general term to represent an Amazon S3 node.
S3 Node Wizard - Specify Node Name
Control
Description
Node Name
Enter a name for the S3 node.
Tags
Add the tags to be associated with the object being created.
S3 Node Wizard - Allocate Node to Access Control Resource Group
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.
S3 Node Wizard - Specify Creation Mode
Control
Description
Mode
Select one of the following options:
Create a new S3 node
This will start a new store in S3.
Import an existing S3 Node
This will utilize a backup store that already exists.
Subsequent screens are the same for either choices.
S3 Node Wizard - Select Proxy Node
Control
Description
Proxy Node
Enter or select the node that will host the S3 proxy.
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.
Amazon S3 specific configurationAmazon S3 Wizard - Configure S3
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.
This wizard is launched when a new HCP cloud scale node is added to the Nodes Inventory.
NoteEnsure that the Proxy Node defined within the wizard is time synced. If the time is different by over 5 minutes, then the node creation and future backup may fail. It is recommended that the system time on all nodes should have the correct date/time associated with their particular region and time zone.
NoteThere are some differences between the Amazon S3 node creation and the HCP cloud scale node creation which will be noted in this section. ‘S3 Node’ will be used as a general term to represent HCP cloud scale node.
HCP Node Wizard - Specify Node Name
Control
Description
Node Name
Enter a name for the HCP node.
Tags
Add the tags to be associated with the object being created.
HCP Node Wizard - Allocate Node to Access Control Resource Group
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.
HCP Node Wizard - Specify Creation Mode
Control
Description
Mode
Select one of the following options:
Create a new S3 node
This will start a new store in S3.
Import an existing S3 Node
This will utilize a backup store that already exists.
Subsequent screens are the same for either choices.
HCP Node Wizard - Select Proxy Node
Control
Description
Proxy Node
Enter or select the node that will host the S3 proxy.
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.
HCP cloud scale Wizard - Configure S3
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.
This page displays the details of an existing node and enables the wizard to be launched to edit them.
Node Details (OS Host)
Common Controls (Displayed for all node types)
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:
Status (Online/Offline) - indicates if the node is contactable by the Master node.
NoteOS Host have version. All other nodes have Proxy and Proxy Version
Proxy - Name of the OS Host node where this node reside.
Protector Version - The version number of the Protector software running on the proxy node.
Tags
Data Instances
Indicates the following:
Location – Name of the node where the data instance resides.
Data Flow – Link to the Data Flow which describes the backup instance.
Operation - Indicates operation type and name.
Count – Indicates the number of recovery points for the storage system.
Latest – Indicates the latest date and time when snapshot/backup is created.
- Indicates that one or more node are offline and as such there may be instances residing on these nodes so there is a potential that the count is incomplete.
OS Host Specific Controls
Control
Description
Configuration
Indicates 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 Nodes
Lists all the nodes for which this node acts as the proxy.
The node icons and indicators used in the lists of unauthorized and authorized nodes.
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.
Edits an existing node group in the inventory. The Node Group Wizard is launched to enable the group's attributes to be changed.
Delete Node
Enabled only when one or more Node Group is selected. Deletes the selected item from the inventory. The associated Nodes are not deleted.
Create a new item
Creates a new Node Group. The Node Group Wizard is launched to guide you through the process.
User 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 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.
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:
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
Edit
Edit Tags
Authorize
Deauthorize
Upgrade Clients
Delete 
Create a new item
Filter on Node Name
Microsoft SQL Server
Hitachi Block Host
Microsoft Hyper-V
Amazon S3
Hitachi Block Device
Hitachi Content Platform
Hitachi Logical Block Device
Repository
Increase Priority
Decrease Priority
- Indicates that one or more node are offline and as such there may be instances residing on these nodes so there is a potential that the count is incomplete.
Enable\Disable Encryption
Manage
Expand
