Storage
Storage Concepts
This section describes Ops Center Protector's storage management features.
For further information, refer to:
About storage
The storage inventory provides access to all the available data storage types managed by Ops Center Protector as follows:
- Generation 1 and Generations 2 Repository - batch backups of applications, VMs and filesystems.
- Hitachi Content Platform - batch backup of applications, VM's and filesystems.
- Amazon S3 - batch backup of applications, VM's and filesystems.
- Hitachi Block and Logical Block - snapshots and replications of applications, VMs, filesystems and LDEVs.
- Logs relating to the device
- Jobs relating to the device
- Device configuration
- Storage and Store Details
- Repositories:
- Mount/Unmount
- Hitachi
Block:
- View all host groups, journals, logical devices
- View pool usage
- Mount, unmount, revert, adjust expiry, transfer ownership or delete snapshots
- Mount, unmount, pause, resume, swap, dissociate or delete replications
About Repositories
The Protector Repository Gen 2 is a performance and capacity optimised object store. It conforms to the Unified Backup Infrastructure storage specification. Refer to the Unified Backup Infrastructure concept for more details.
The Repository differs from other native object storage in that it supports snapshots natively utilising re-direction on write. This allows for highly efficient management of shared data blocks and space reclamation is both fast and automatic.
There are no practical limits to the size of objects or number of objects in a repository.
To achieved optimal data reduction, it retains both object level and block level check sums.
For performance optimization, the Gen 2 Repository can be setup to be split across different storage. See Repository Storage Node Wizard for more details.
- Data directory – this is the where the bulk of the data is stored. Mass storage devices with performance characteristics of fast write streaming storage is ideal.
- Metadata Directory and Checksum Directory holds the metadata and the repository structure information. These benefits from fast random access such as SDD and NVMe storage. Typically these should be around 5% of the Data Directory capacity.
Hardware and OS recommendations
This section describes the ideal additional specification information for a repository machine. For more information see the product support matrices at https://www.hitachivantara.com/en-us/products/data-protection/ops-center-protector.html#tech-specifications .
Hardware:
As usual in most scenarios more is better but a point of diminishing returns will be reached. The most beneficial upgrade is extending the available memory. The repository storage group processes themselves never use a large amount of memory, but increasing memory beyond 16GB will ensure there is plenty of head room.
More important when specifying CPU, is the generation of CPU technology. Because moving mass data is at the core of what the repository does, faster memory will have a greater impact than for a normal application so the faster memory the better.
File System:
In addition to optimising the disk layout, it is also important to use the correct block size for NTFS. NTFS volumes should be formatted using 16k block size with a repository storage group default setting. It should under no circumstances be larger than the repository DataBlockShift
setting which is 16k by default. If the NTFS block size is larger, then it will force the filesystem to read the block before it performs a write.
E.g. with a 64k NTFS block size, if Ops Center Protector needs to update a single repository block of 16k, it will write out the 16k block to the file system. However the file system will need to read the 64k NTFS block, change the relevant 16k section and then write back the full 64k block. This badly degrades performance, but it may not be noticeable when the repository is initially populated since these full backups would likely be large 2MB writes across several blocks. The degradation in performance would only be noticed over time when smaller, incremental updates start occurring.
Shutdown Time:
Windows only allows a few seconds for all services to shutdown before forcibly terminating them. An Ops Center Protector repository storage group can take a significant amount of time to close especially if it is busy synchronizing many machines at the point of a system shutdown.
The time Windows allows for process shutdown can be changed via the Windows registry. The registry entry to change this is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout
The value is in milliseconds; by default it is either 12000 or 20000 depending on OS version. It is important for the repository to shutdown correctly so we highly recommend changing this value to 5 minutes (300000 milliseconds).
The knock on effect is that your server may take longer to shutdown, this setting applies to all services, so if a service is badly behaved and does not shutdown when asked, then the machine will take the full 5 minutes (plus OS cleanup time) to shutdown.
About Cloud Nodes (Amazon S3, HCP and HCP Cloud Scale)
Cloud storage nodes, Amazon S3, HCP and HCP cloud scale are used to transfer application data to cloud storage. All use the S3 protocol for communication.
Cloud storage nodes represent the storage in Amazon S3 cloud or on the HCP. When creating the node, you will define the necessary credentials to access the S3 service. These include:
- Access Key ID
- Secret Access Key
- Bucket Name
- Region (Amazon S3 only)
Additionally, you will define a Proxy node that will be the intermediary between the application and the S3 service. The proxy node can be any Windows or Linux OS nodes.
The role of the proxy node is to:
- Provide a secure system that can access the S3 service. Although the proxy node can be the same OS host as an application, it is recommended for security reason that this is an independent system to that of the application. The benefit of this is that this system can be given limited access ensuring that the application servers do not have access to the S3 credentials. This S3 node can then be used by multiple applications without the danger of compromising security or data leakage. It also means that the application servers do not need direct access to the internet.
- Provide a cache of the recovery points stored on the S3 server. This cache is only a copy of the index information and metadata, it is not the data itself and can be rebuilt from the S3 content. Having the cache however improves responsiveness of the system and decreases some of the S3 access, thereby saving cost.
- Provide an UBI compliant application interface. This allows you to use S3 storage with any of the next generation applications in the same fashion that you can use Generation 2 Repository. For a list of UBI compliant applications see XYZ. As UBI compliant storage, the S3 node can also receive data from or send data to other UBI compliant storage, such Generation 2 Repository or Generation 2 Hitachi Content Platform. This means it can be used to form a layered data retention solution.
Cloud storage node key features include:
Search friendly native format
A key feature of S3 support is to keep data stored on S3 in a native format as much as practicable. Any files less then 4GB in size, has its data stored in a single object. This means that 3rd party search, indexing and analytics tools can process the data in S3 directly. By default, files bigger than 4GB are split into 4GB segments that can easily be stitched together if required.
Delta block differencing
To reduce bandwidth and improve transfer speeds, by leveraging S3 partial transfers only the block changes within a file are sent to S3.
Virtual snapshots
A system whereby data is retained and indexed in S3 in such a way that recovery points use objects that are whole and not need rehydration but will share data that is common between other recovery points, saving storage space and providing optimal recovery speed.
Multi-factor parallelism
To further optimise data transfer speed in addition to delta block differencing, multiple objects are sent to S3 at the same time and multiple data blocks within those objects are sent separately to S3 in parallel.
Self-consistent store
Although some metadata is cached on the proxy, the data stored in S3 is self-consistent. Should a site experience complete data loss, a new instance of Protector can be spun and an S3 node can be configured to import the data.
Storage UI Reference
This section describes the Storage UI, accessed via the Main Banner.
For further information, refer to:
Storage Inventory
This inventory contains storage information relating to all available storage nodes:
- Generation 1 Repository
- Generation 2 Repository
- Hitachi Block physical and logical storage devices
- HCP Storage Node
- Amazon S3 Storage Node
- HCP cloud scale storage node

Control | Description |
Storage Node(s) | Opens one of the following pages depending on the storage type: |
Filter on Name | Filters the displayed results based on Node Name. |
Filter on User Tags | Filters the displayed results based on Tags. |
Filter on Type | Filters the displayed results based on Node Type:
|
Hitachi Block Device Details
This page displays the details of a Block Storage device and enables monitoring of its activities, state, and the snapshots and replications stored within it.

Control | Description |
![]() | Refreshes the Host Groups, Journals, Pools and Logical Devices data. NoteA refresh must be performed to
update information held on the storage array. |
![]() | Opens the Hitachi Block Device Advanced Settings Dialog to allow the advanced settings of the storage system to be modified. |
Logs | Indicates the number of unacknowledged error logs in red. If there are no errors then a green tick is displayed instead. Numbers at the bottom show the 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. Numbers at the bottom show active and paused jobs. Opens the Jobs Inventory. |
Details | Indicates the following:
|
![]() | Takes you to the equivalent Node Management Node Details. |
Configuration | Shows the configuration of the Hitachi Block Device. |
Object Cache | Shows last updated date and time for Pools, Journals, Resource Groups, Quora, Host Groups, Remote Path Groups, and Logical Devices of Hitachi Block Device. For details on the cache refreshing see Hitachi Block Device Scheduled Cache Refresh NoteThis screen in the UI does not automatically refresh. While the values are refreshed on a schedule it is necessary to reload the page in the browser to get an up to date view of the values. |
![]() | Duplicates the Refresh button at the top of the page. |
![]() | Indicates the number of Host Groups on the Device visible to the CCI user identified when the Block storage node was configured. If Host Groups exist in a resource group to which the user does not have access then they will not be displayed here. Click on the icon to open the Hitachi Block Host Groups Inventory. |
![]() | Indicates the number of Journals on the Device visible to the CCI user identified when the Block storage node was configured. Click on the icon to open the Hitachi Block Journals Inventory |
![]() | Indicates the number of Pools (Total, Snapshot and Dynamic) on the Device. Click on the icon to open the Hitachi Block Pools Inventory |
![]() | Indicates the number of Logical Devices on the Device. If Logical Devices exist in a resource group to which the user does not have access then they will not be displayed here. Click on the icon to open the Hitachi Block Logical Devices Inventory |
![]() | Indicates the number of Quorums on the device. Click on the icon to open the Hitachi Block Quorums Inventory . |
![]() | Indicates the number of Remote Path Groups on the device. Click on the icon to open the Hitachi Block Remote Path Groups Inventory |
![]() | Indicates the number of Snapshots on the Device that have been created by Protector. Click on the icon to open the Hitachi Block Snapshots Inventory |
![]() | Indicates the number of Replications on the Device that have been created or adopted by Protector. Click on the icon to open the Hitachi Block Replications Inventory |
![]() | Indicates the number of Resource Groups on the device. Click on the icon to open the Hitachi Block Resource Groups Inventory. |
Hitachi Block Host Groups Inventory
This inventory lists all Host Groups defined on a Hitachi Block storage device.

Control | Description |
![]() | Refreshes the displayed inventory. CautionHost Group details are
only refreshed when refreshed manually. To ensure the latest information is
displayed, this page must be manually refreshed periodically. |
![]() | Click on a Host Group to open the Hitachi Block Host Group Details. |
Filter on Name | Filters the displayed results based on the Host Group Name. |
Filter on Port | Filters the displayed results based on the Port. |
Hitachi Block Host Group Details
This page shows the details of a Host Group on a Hitachi Block storage device.

Control | Description |
Summary | Summarises Host Group details. |
Hitachi Block Journals Inventory
This inventory lists all Journals on a Hitachi Block storage device.

Control | Description |
![]() | Refreshes the displayed inventory. |
![]() | Opens the Hitachi Block Journal Expansion Dialog to enable the capacity of the selected journal to be increased. |
![]() | Deletes the selected journal(s) from the storage system. A confirmation dialog opens to confirm the action. |
![]() | Click on a Journal to open the Hitachi Block Journal Details. |
Filter Journal ID | Filters the displayed results based on the Journal ID. |
Filter on Use State | Filters the displayed results based on the use state of the Journal |

Control | Description |
New Journal Size | Enter a new size for the journal. The new size must be larger than the current size. |
Hitachi Block Journal Details
This page shows the details of a Journal on a Hitachi Block storage device.

Control | Description |
![]() | Opens the Hitachi Block Journal Expansion Dialog to enable the capacity of the selected journal to be increased. |
![]() | Deletes the selected journal(s) from the storage system. A confirmation dialog opens to confirm the action. |
Summary | Summarises the Journal details. |
Logical Devices | Displays information on the Logical Devices for the Journal. |
Hitachi Block Pools Inventory
This inventory lists all Pools on a Hitachi Block storage device.
Filling a Thin Image pool to capacity will invalidate all snapshot data contained within that pool. All snapshots in the pool will have to be deleted before snapshotting can be resumed.

Control | Description |
![]() | Refreshes the displayed inventory. CautionPool usage is only refreshed when refreshed manually. If these values are being used to monitor pool usage they must be manually refreshed periodically. |
![]() | Click on a Pool name to open the Hitachi Block Pool Details. NoteThe pool capacity indicator bar
changes colour when thresholds defined on and read from the storage array are
crossed:
(1) Thin Image pools only have a single threshold defined on the array. Protector transitions straight from the normal state to the depletion state. For dynamic pools containing replication S-VOLs, the replication will transition to an error state when the pool is full. |
Filter on Name | Filters the displayed results based on the Pool Name. |
Filter on Type | Filters the displayed results based on the Pool Type:
|
Hitachi Block Pool Details
This page shows the details of a Pool on a Hitachi Block storage device.

Control | Description |
Summary | Summarises the Pool details. |
Hitachi Block Logical Devices Inventory
This inventory lists all Logical Devices on a Hitachi Block storage device.

Control | Description |
![]() | Refreshes the displayed inventory. CautionLogical Device Inventory is only refreshed when refreshed manually. To ensure the latest information is displayed this page should be manually refreshed periodically. |
![]() | Click on a Logical Device to open the Hitachi Block Logical Device Details. |
Filter on Name | Filters the displayed results based on the Logical Device Name. |
Hitachi Block Logical Device Details
This page shows the details of a Logical Device on a Hitachi Block storage device.

Control | Description |
Summary | Summarises the Logical Device details. |
Hitachi Block Snapshots Inventory
This page provides an inventory of all the Snapshots stored on a Block Storage Device.

Control | Description |
![]() | Enabled only if one VMware Block snapshot is enabled. Opens the Hitachi Block VMware Snapshot Restore Wizard to guide you through restoring VM's from the snapshot Note: The restore operation may take several minutes to complete. |
![]() | Enabled only if one or more Snapshots are selected. Opens the Hitachi Block Snapshot or Replication Mount Wizard to guide you through mounting the Snapshot. NoteThe mount operation can take several minutes to complete. |
![]() | Enabled only if one mounted snapshot is selected. Unmounts the selected snapshot. NoteThe unmount operation can take several minutes to complete. |
![]() | Enabled only if one or more Snapshots are selected. Opens the Hitachi Block Revert Wizard to guide you through reverting the Snapshot. |
![]() | Opens the Hitachi Block Change Snapshot Expiry Date Dialog to enable the expiry date of the selected snapshot(s) to be modified. |
![]() | Enabled only if one or more Snapshots are selected. Deletes the snapshot from the pool. A confirmation dialog opens to confirm the action. If the snapshot record contains fully provisioned LDEVs then the user can view these details prior to deletion. |
![]() | Click on the Snapshot's Date and Time to open the Hitachi Block Snapshot Details (Storage). |
![]() | Indicates that the snapshot has DRU protection applied. The protection can be removed (subject to lock duration) via the Hitachi Block Record Details (Storage). |
Filter on Capture Date | Filters the displayed results based on the Date Range specified in the Date Time Range Picker. |
Filter on Application Node | Filters the displayed results based on source application node. |
Filter on Application Node Type | Filters the displayed results based on source application node type |
Filter on Mount status | Filters the displayed results based on mount status of the snapshot |
Filter on Dataflow | Filters the displayed results based on Dataflow |
Filter on Policy | Filters the displayed results based on the Policy. |
Filter on Operation Name | Filters the displayed results based on mount status of the operation name |
Hitachi Block Snapshot Details (Storage)
This page shows the details of a Snapshot on a Hitachi Block storage device.

Control | Description |
![]() | Opens the Hitachi Block Rename Secondary LDEVs Dialog to enable renaming of LDEVs using a fixed string and/or substitution variables. |
![]() | Opens the Hitachi Block Snapshot or Replication Mount Wizard to guide you through mounting the snapshot. NoteThe mount operation can take several minutes to complete. |
![]() | Unmounts the snapshot. The export is deleted. NoteThe unmount operation can take several minutes to complete. |
![]() | Opens the Hitachi Block Revert Wizard to guide you through reverting the snapshot. |
![]() | Opens the Hitachi Block Change Snapshot Expiry Date Dialog to enable the expiry date of the snapshot to be modified. |
![]() | If the snapshot was created with DRU protection and the protection lock duration has expired, this will remove the protection. |
![]() | Deletes the snapshot from the pool. A confirmation dialog opens to confirm the action. |
Summary | Identifies the hardware storage device, application, policy etc. Click on the policy name to open the Policy Details. |
State | Indicates the status of the snapshot. |
Links | Provides links to the following pages that provide additional information about the snapshot:
|
Nodes | Shows the source and destination nodes involved in the snapshot. You can click on either node to go to their Node Details |
![]() | Opens Hitachi Block Snapshot - Pools, listing the pools used in this snapshot. |
![]() | Opens Hitachi Block Snapshot - Logical Devices, listing the LDEVs in this snapshot. |
![]() | Opens Hitachi Block Snapshot - Pairs, listing the pairs in this snapshot. |
Hitachi Block Rename Secondary LDEVs Dialog

Control | Description |
Name |
Enter the string to be used to rename all secondary LDEVs for the given snapshot or replication. The name can consist of literal strings and/or any of the variables listed below the edit box.
TipUse the cut and paste tools in your browser to insert the required variable (including the surrounding % delimiters) to ensure the correct format and spelling.
For example: Snap_%ORIGIN_SERIAL%_%ORIGIN_LDEV_ID% might result in each secondary LDEV being renamed: Snap_434525_00:3A:98 Note
|
Hitachi Block Change Snapshot Expiry Date Dialog

Control | Description |
Expiry Date | Enter the date and time that the snapshot will expire and be deleted. Opens the Date Time Picker. |
Hitachi Block Record Details (Storage)
This page shows the details of a record on a Hitachi Block storage device.

Control | Description |
Phase 1..n |
Identifies the paths, logical devices, chains and operation information for the snapshot. For policies having multiple data classifications or an application classification, the operation is performed in multiple phases. The record for each phase is displayed separately. |
Hitachi Block Snapshot - Pools
Lists the pools used in a particular snapshot.

Control | Description |
Snapshot Pools list | Each pool is listed, along with its attributes. |
Hitachi Block Snapshot - Pairs
Lists the pairs in a particular snapshot. This data is collected from [raidcom get snapshot] – for more information about certain context-sensitive values, please consult the relevant CCI documentation.

Control | Description |
ID | Displays the ID of the LDEV. |
Storage | Displays the serial number of the storage array. |
Status | Not populated. |
Attribute | Displays the status for this LDEV in this pair (eg COPY, PAIR, PSUS, SSUS). Not populated for Original Secondaries if the snapshot is floating and unmounted. |
% | Not populated. |
M | Not populated. |
IO Mode | Not populated. |
Direction (no column header) | Displays an arrow pointing from P-VOL to S-VOL. |
Mirror Unit | Displays the mirror unit for the P-VOL of this pair. |
Type | Displays the type of this pair (eg [TI]). |
Fence Level | Not populated. |
Quorum | Not populated. |
Snapshot Pairs list | Each pair is listed, identifying the source LDEV's properties on the left and the destination LDEV's properties on the right, separated by an arrow indicating the direction of the snapshot. |
Filter by Original Primary Volume Status | Filters the list by local volume status. |
Filter by Original Primary Volume Attribute | Filters the list by local volume attribute. |
Filter by Original Secondary Volume Status | Filters the list by remote volume status. |
Filter by Original Secondary Volume Attribute | Filters the list by remote volume attribute. |
Hitachi Block Snapshot - Logical Devices
Lists the LDEVs used in a particular snapshot.

Control | Description |
Snapshot LDEVs list | Each LDEV is listed, along with its attributes. |
Hitachi Block Replications Inventory
This page provides an inventory of all the Replications stored on a Block Storage node.



Records for replications in active data flows (marked Refreshed Full Copy or Active Full Copy) cannot be deleted.
If an S-VOL has been added to a host group, or has a LUN path allocated outside of Protector then it will not be deleted.
If an S-VOL has been renamed outside of Protector, then it will not be deleted because Protector will be unable to locate it.

Control | Description |
![]() | Enabled only if the a VMware Replication is selected. Opens the Hitachi Block VMware Snapshot Restore Wizard. |
![]() | Enabled only if one or more Replications are selected. Opens the Hitachi Block Snapshot or Replication Mount Wizard to guide you through mounting the Replication. NoteThe mount operation can take several minutes to complete. |
![]() | Enabled only if one mounted replication is selected. Unmounts the selected replication. NoteThe unmount operation can take several minutes to complete. |
![]() | Enabled only if one or more Replications are selected. Pauses the Replication. Opens the following dialog: Selecting this option will pause the replication and make the S-VOLs writable (instead of the P-VOL). This operation is carried out without needing to contact the primary array or storage proxy to allow continuation from a primary site failure. NoteThis option is only relevant for remote replications – if selected for local replication it will be ignored. |
![]() | Enabled only if one or more Replications are selected. Resumes a paused Replication. |
![]() | Enabled only if one or more Replications are selected. Opens the Hitachi Block Replication Swap Wizard to guide you through swapping the Replication direction. |
![]() | If a Swap operation cannot be completed due to a P-VOL or data link fault between the primary and secondary device, then the replication will enter the SSWS state (suspended for swapping) indicating that the swap is not yet complete. Unsuspend enables the replication process to be re-established once the cause has been rectified. |
![]() | Enabled only if one or more replications are selected. Opens the Hitachi Block Add to Host Groups Dialog to enable LDEVs to be added to host groups in addition to the default ProtectorProvisionedHostGroup used by Protector. NoteA job is queued to perform the operation on the array and this may take some time to complete. |
![]() | Enabled only if one replication is selected. Opens the Hitachi Block Remove from Host Groups Dialog to enable LDEVs to be removed from host groups, including the default ProtectorProvisionedHostGroup used by Protector. NoteA job is queued to perform the operation on the array and this may take some time to complete. |
![]() | Enabled only if one or more Replications are selected. Dissociates a replication that was previously adopted by Protector. Removes the selected replication(s) from Protector including state information such as direction and mount location. The replication remains active on the hardware device(s). The word 'DISSOCIATE' must be entered before the command is executed. CautionDissociating a replication removes all knowledge of the replication from Protector, including state information such as direction and mount location. |
![]() | Enabled only if one or more Replications are selected. Initiates the teardown of the selected replications. The word 'TEARDOWN' must be entered before the command is executed. |
![]() | Enabled only if one or more Replications are selected. Deletes the replication record from Protector. The replication is also removed from the block storage device. |
![]() | Click on the Replication's Date and Time to open the Hitachi Block Replication Details (Storage). |
![]() | Displayed on a replication tile next to the replication icon. Indicates that a replication is eligible for teardown. |
Filter on Capture Date Time | Filters the displayed results based on the replication Caputre Date Time range specified in the Date Time Picker. |
Filter on Application Node | Filters the displayed results based on the Source Application Node from which the replication is made. |
Filter on Application Node Type | Filters the displayed results based on the Source Application Node Type. |
Filter on Mounted status | Filters the displayed results based on the mount status |
Filter on Eligible for Teardown Status | Filters the displayed results based on the Eligible for Teardown status |
Filter on Data Flow | Filters the displayed results based on the Data Flow where the replication is defined |
Filter on Policy | Filters the displayed results based on the Policy where the replication is defined. |
Filter on Operation Name | Filters the displayed results based on the operation name defined within the policy. |
Filter on Type | Filters the displayed results based on the replication type. |
Hitachi Block Replication Details (Storage)
This page shows the details of a Replication on a Hitachi Block storage device.

Control | Description |
![]() | Opens the Hitachi Block Rename Secondary LDEVs Dialog to enable renaming of LDEVs using a fixed string and/or substitution variables. |
![]() | Opens the Hitachi Block Snapshot or Replication Mount Wizard to guide you through mounting the Replication. NoteThe unmount operation can take several minutes to complete. |
![]() | Unmounts the selected replication. The export is deleted. NoteThe unmount operation can take several minutes to complete. |
![]() | Enabled only if one or more Replications are selected. Pauses the Replication. Opens the following dialog: Selecting this option will pause the replication and make the S-VOLs writable (instead of the P-VOL). This operation is carried out without needing to contact the primary array or storage proxy to allow continuation from a primary site failure. NoteThis option is only relevant for remote replications – if selected for local replication it will be ignored. |
![]() | Resumes a paused Replication. |
![]() | Opens the Hitachi Block Replication Swap Wizard to guide you through swapping the Replication direction. |
![]() | If a Swap operation cannot be completed due to a P-VOL or data link fault between the primary and secondary device, then the replication will enter the SSWS state (suspended for swapping) indicating that the swap is not yet complete. Unsuspend enables the replication process to be re-established once the cause has been rectified. |
![]() | Opens the Hitachi Block Add to Host Groups Dialog to enable LDEVs to be added to host groups in addition to the default ProtectorProvisionedHostGroup used by Protector. A job is queued to perform the operation on the array and this may take some time to complete. |
![]() | Opens the Hitachi Block Remove from Host Groups Dialog to enable LDEVs to be removed from host groups, including the default ProtectorProvisionedHostGroup used by Protector. A job is queued to perform the operation on the array and this may take some time to complete. |
![]() | Modifies the tags of an existing object from the either the inventory screen or the details screen of the object. |
![]() |
CautionDissociating a replication removes all knowledge of the replication from Protector, including state information such as direction and mount location.
|
![]() | Initiates the forcing of the GAD IO mode. The word ‘FORCE’ must be entered, and the storage array which you want to be the writable before the command is executed. The side selected will be made writable and if the Array and the Storage Proxy for the other side of the GAD is contactable it will be place into a Blocked state. NoteThis feature can only be used on a paused or failed GAD replication. This can not be used on an Active Active GAD replication. |
![]() | Initiates the teardown of the replication. The word 'TEARDOWN' must be entered before the command is executed. |
![]() | Deletes the replication record from Protector. The replication is also removed from the block storage device. |
Summary | Identifies the hardware storage device, application, policy and general status. |
State | Indicates the status of the replication. |
Nodes | Indicates the Nodes involved in the replication. Opens the Node Details for the node selected. |
Links | Provides links to the following pages that provide additional information about the replication:
|
![]() | Opens Hitachi Block Replication - Journals, listing the journals used in this
replication. NoteYou must manually refresh the journal information from the Hitachi Block Journals Inventory to ensure the current list of Journals is up to
date |
![]() | Opens Hitachi Block Replication - Pools, listing the pools used in this replication. Note:
You must manually refresh the pool information from the Hitachi Block Pools Inventory to ensure the current list of Pools is up to
date |
![]() | Opens Hitachi Block Replication - Host Groups, listing the host groups for this replication.
Note: You must manually refresh the Host Group information from the Hitachi Block Host Groups Inventory to ensure the current list of Host groups is up to
date |
![]() | Opens Hitachi Block Replication - Logical Devices, listing the LDEVs in this replication. NoteYou
must manually refresh the Logical Device information from the Hitachi Block Logical Devices Inventory to ensure the current list of Logical Devices is
up to date |
![]() | Opens Hitachi Block Replication - Pairs, listing the pairs in this replication. |
Hitachi Block Add to Host Groups Dialog
This dialog is displayed when adding an existing replication S-VOL to another host group(s).

Control | Description |
Host Groups | Specify zero or more host groups that Protector will configure to provide access to the S-VOL. Click the Add Host Group button to insert another Host Group selection control. Click the Remove button next to a Host Group selection control to delete it. Note
If a LUN path to be created already exists, Protector will not attempt to add it again, or to change its ID. The specified host groups must be in the same resource group as the secondary volumes. For GAD replications, if the host group names and port IDs match between primary and secondary storage nodes, Protector will attempt to match the LUN IDs used for the S-VOLs with those of the respective P-VOLs. If this cannot be achieved then a warning will be logged and the next available LUN ID will be used. |
Hitachi Block Remove from Host Groups Dialog
This dialog is displayed when removing an existing replication S-VOL from a host group(s).

Control | Description |
Host Groups | Specify one or more host groups to remove the S-VOL from. Click the check box next to the Host Group(s) from which the S-VOL is to be removed. NoteIt is not possible to remove the last remaining Host Group if the S-VOL still has replication or snapshot pairings. |
Hitachi Block Replication - Journals
Lists the journals used in a particular UR replication.

Control | Description |
![]() | Opens the Hitachi Block Journal Expansion Dialog to enable the capacity of the selected journal to be increased. |
Replication Journals list | Each journal is listed, along with its attributes. |
Hitachi Block Replication - Pools
Lists the pools used in a particular replication.

Control | Description |
Replication Pools list | Each pool is listed, along with its attributes. |
Hitachi Block Replication - Host Groups
Lists the Host Groups used in a particular replication.

Control | Description |
Replication Host Groups list | Each host group is listed, along with its attributes. |
Hitachi Block Replication - Logical Devices
Lists the LDEVs used in a particular replication.

Control | Description |
Replication LDEVs list | Each LDEV is listed, along with its attributes. |
Hitachi Block Replication - Pairs
Lists the pairs in a particular replication. Depending on pair type, this data is collected from [pairdisplay] or [raidcom get snapshot] – for more information about certain context-sensitive values, please consult the relevant CCI documentation.

Control | Description |
ID | Displays the ID of this LDEV. |
Storage | Displays the serial number of the storage array hosting this LDEV. |
Status | Displays the status for this LDEV in this pair (eg COPY, PAIR, PSUS, SSUS, SSWS). |
Attribute | Displays the attribute for this LDEV in this pair (eg P-VOL, S-VOL, SMPL). |
% | Displays the % value for this LDEV in this pair. The meaning of this value is context-sensitive, depending upon the pair status and pair type. This value is taken directly from the pairdisplay command. For guidance on how to interpret this value please consult the pairdisplay information in the CCI Command Reference. |
M | Displays the M value for this LDEV in this pair. The meaning of this value is context-sensitive, depending upon the pair status and pair type. This value is taken directly from the pairdisplay command. For guidance on how to interpret this value please consult the pairdisplay information in the CCI Command Reference. |
I/O Mode | Displays the I/O Mode for this LDEV (eg L/M, B/B). Only populated for pairs of type [Active-Active Remote Clone]. |
Direction (no column header) | Displays an arrow pointing from P-VOL to S-VOL. |
Mirror Unit | Displays the mirror unit for the P-VOL of this pair. |
Type | Displays the type of this pair (eg [SI], [TC]). |
Fence Level | Displays the fence level for this pair. Only populated for pairs of remote replication types. |
Quorum | Displays the quorum ID for this pair. Only populated for pairs of type [Active-Active Remote Clone]. |
Replication Pairs list | Each pair is listed, identifying the source LDEV's properties on the left and the destination LDEV's properties on the right, separated by an arrow indicating the direction of the replication. |
Filter by Original Primary Volume Status | Filters the list by local volume status. |
Filter by Original Primary Volume Attribute | Filters the list by local volume attribute. |
Filter by Original Secondary Volume Status | Filters the list by remote volume status. |
Filter by Original Secondary Volume Attribute | Filters the list by remote volume attribute. |
Hitachi Block Remote Path Groups Inventory
This inventory lists all Remote Path Groups on a Hitachi Block storage device.

Control | Description |
![]() | Refreshes the displayed inventory. CautionRemote Path Group Inventory is only refreshed when refreshed manually. To ensure the latest information is displayed this page should be manually refreshed periodically. |
![]() | Click on a Path Group to open the Hitachi Block Remote Path Group Details. |
Filter on ID | Filters the displayed results based on the Path Group ID. |
Filter on Serial | Filters the displayed results based on the serial number of the remote array. |
Filter on Storage | Filters the displayed results based on the type of storage. |
Filter on Port type | Filters the displayed results based on the type of port. |
Hitachi Block Remote Path Group Details
This page shows the details of a Remote Path Group on a Hitachi Block storage device.

Control | Description |
Summary | Summarises the Logical Device details. |
Local | Details the remote path group. |
Remote | Details the remote storage node. |
Nodes | Provides links to both the local and remote storage screens. |
Remote Paths | Shows the paths in the remote path group. |
Outbound replications | Shows outbound (local) replications managed by Protector using the remote replication path. |
Inbound replications | Shows inbound (remote) replications managed by Protector using the remote replication path. |
Hitachi Block Device Advanced Settings Dialog
This dialog is displayed when the advanced settings for a block device node is being modified.

Control | Description |
Replication Resize | Changes the replication resize option. This option determines if, or when replications will utilize Hierarchical Memory. A replication must be using hierarchical memory to support expansion of replicated Logical Devices. NoteThe option "For new replications" may not always be available if it is not supported by the hardware. |
Hitachi Block Device Scheduled Cache Refresh
The various caches for the Block Device are refreshed on a scheduled basis. The defaults for these refreshes are as detailed in the following table:
Item | Refresh Frequency |
Pools | 2 minutes |
Journals | 2 minutes |
Resources | 2 minutes |
Quora | 1 hour |
Host Groups | 1 hour |
Remote Path Groups | 1 hour |
LDEVs | 24 hours |
These defaults are configurable on a per storage proxy basis so Block Devices sharing the same proxy node will have the same settings. If alternative configurations are required contact support for assistance.
Hitachi Block Quorums Inventory
This page lists all the Quorums on a Hitachi Block Storage device.

Control | Description |
![]() | Refreshes the Cache and initiates the refreshing the Resources. NoteA refresh must be performed to update information held on the Quorum screen. |
Filter on Name | Filters the displayed results based on the name of the Quorum. |
Filter on Quorum ID. | Filters the displayed results based on the ID of the Quorum. |
Filter on External Serial Number | Filters the displayed results based on the External Serial Number of the Quorum. |
Filter on Logical Device ID. | Filters the displayed results based on the Logical Device ID. of the Quorum. |
This page shows the details of the Quorums on a Hitachi Block Storage Device.

Control | Description |
Summary | Summarizes Quorum details. |
Hitachi Block Resource Groups Inventory
This inventory lists all defined Resource Groups for this Block Device. Resource Group are created to define logical groups of computing resources in the context of Hitachi Block Storage Device.

Control | Description |
![]() | Refreshes the Cache and initiates the refreshing the Resources. NoteA refresh must be performed to update information held on the Quorum screen. |
Filter on Name | Filters the displayed results based on the name of the Resource Group . |
Filter on Resource Group ID. | Filters the displayed results based on the ID of the Resource Group . |
Filter on Virtual Serial Number | Filters the displayed results based on the Virtual Serial Number of the Resource Group . |
This page shows the details of the Resource Group on a Hitachi Block Storage Device.

Control | Description |
Summary | Summarizes Resource Group details. |
Generation 1 Repository Details
This page displays the details of a Gen1 Repository and enables you to monitor its activities, state and the snapshots stored within it.

Control | Description |
![]() | Mounts the repository to either its original location or to an alternative location. If the repository is being mounted to an alternate location, a full resynchronization will be required. |
![]() | Unmounts the repository. |
Jobs | Indicates the number of In Progress jobs as well as the Failed and Completed jobs in the last 72 hours. The Jobs link opens the Jobs Inventory. |
Logs | Indicates the number of New Errors, Errors and Warnings in the last 72 hours. New errors are errors that have not been acknoleged. The Logs link opens the Logs Inventory. |
Storage Details | Indicates the following:
|
Stores Details | Indicates the number of Stores within the Repository and the size of each store. The Stores link opens the Gen1 Repository Stores Inventory. |
Configuration | Indicates the following:
|
Statistics | Indicates the following:
|
Gen1 Repository Stores Inventory
This inventory lists all the Stores within a Repository.

Control | Description |
![]() | Enabled when one or more Stores are selected. Opens the Resynchronize Repository Store Dialog to resynchronize the stores with their sources. |
![]() | Enabled when one or more Stores are selected. Validates the contents of the store against the respective source nodes. NoteValidation is done for checksums of data on the source machine against those in the repository stores. Checksums for data in repository stores that are tiered to the cloud are not validated against checksums held on the cloud storage platform. |
![]() | Enabled when only one Store is selected. Opens the Create Repository User Snapshot Dialog to create a single snapshot of the whole store – not just an individual policy. Note User Snapshots are retained forever or until they are manually deleted. |
![]() | Enabled when one or more Stores are selected. This option is only available if the store is inactive – that is, no active policies currently transfer data to a store with this name. Selecting it will delete this store and all the snapshots contained within it. |
![]() | Opens the Gen1 Repository Store Details enabling you to view and perform operations on the store. |
Filter on Source Node | Filters the displayed results based on the Source node from which data is being ingested. |
Filter on Policy | Filters the displayed results based on the Policy for which the store is used. |
Filter on Type | Filters the displayed results based on the Store Type selected. |
Resynchronize Repository Store Dialog

Control | Description |
Check all files during resynchronization | Ignores file modification date and checks every file for changes. |
Create persistent snapshot | Once the resynchronization is complete, a persistent snapshot will be created. This snapshot will be retained indefinitely, but can be manually deleted. |
Resynchronize twice, initially ignoring live changes | Two resynchronizations will be performed. The first will ignore any live changes that are made; the second will not ignore them. This option is only valid for a live policy and is ignored when using batch. It is used when there are problems with disk cache overflow. Using this option will reduce the disk usage. |
Create Repository User Snapshot Dialog
This dialog is displayed when a User Snapshot is being created.

Control | Description |
Snapshot Label | Enter a name to identify the snapshot. |
Gen1 Repository Store Details
This page provides details of a Store within a Repository and contains an inventory of all the Snapshots within that Store.

Control | Description |
![]() | Opens the Resynchronize Repository Store Dialog to resynchronize the stores with their sources. |
![]() | Validates the contents of the store against the respective source nodes. |
![]() | Opens the Create Repository User Snapshot Dialog to create a single snapshot containing all the data in the store at that point in time. The snapshot is of the whole store – not just an individual policy. The data from all policies whose destination is that store will be contained within the same user snapshot. Note User snapshots are retained forever or until they are manually deleted. |
![]() | This option is only available if the store is inactive – that is, no active policies currently transfer data to a store with this name. Selecting it will delete this store and all the snapshots contained within it. |
![]() | Enabled only when a single snapshot is selected. Restores the snapshot. Opens the Restore Repository Snapshot Wizard - File System to guide you through the process. |
![]() | Enabled only when a single snapshot is selected. Analyzes the snapshot to provide details about file count, size and changes. This is done on an individual snapshot and can take a few seconds to several minutes to complete depending on repository load and snapshot size. |
![]() | Enabled only when one or more snapshots are selected. Opens the Change Repository Snapshot Retention Dialog |
![]() | Enabled only when one or more snapshots are selected. Deletes the selected snapshots. NoteThe latest snapshot cannot be deleted by the user. Also, if the snapshot is the only one remaining in the store then it will not be automatically retired. This provides a safeguard in the scenario where backups fail for a period of time, since at least one backup will be retained. |
![]() | Opens the Repository Snapshot Details (Storage) - File System to enable you to view the snapshot and perform operations on it. |
Filter on Date Range | Filters the displayed results based on the dates entered in the Date Time Range Picker. |
Repository Snapshot Details (Storage) - File System
This page provides details of a Snapshot within a Store and contains an inventory of all the Files within that Snapshots.

Control | Description |
![]() | Restores the snapshot. Opens the Restore Repository Snapshot Wizard - File System to guide you through the process. |
![]() | Analyzes the snapshot to provide details about file count, size and changes. This is done on an individual snapshot and can take a few seconds to several minutes to complete depending on repository load and snapshot size. |
![]() | Enabled only when one or more snapshots are selected. Opens the Change Repository Snapshot Retention Dialog |
![]() | Schedules the snapshot for deletion. The snapshot is not deleted immediately. No further operations can be performed on a snapshot pending deletion. |
Summary | Provides summary information about the snapshot. |
Analysis Details | Indicates details about file count, size and changes. It includes the logical size of all files contained within the snapshot. |
Files System Contents | Displays the entire directory structure and files contained within this snapshot. |
Repository Snapshot Details (Storage) - VMware

Control | Description |
![]() | Restores the snapshot. Opens the Restore from host based backup Wizard - VMware to guide you through the process. |
![]() | Analyzes the snapshot to provide details about file count, size and changes. This is done on an individual snapshot and can take a few seconds to several minutes to complete depending on repository load and snapshot size. |
![]() | Enabled only when a one or more snapshots are selected. Opens the Change Repository Snapshot Retention Dialog |
![]() | Schedules the snapshot for deletion. The snapshot is not deleted immediately. No further operations can be performed on a snapshot pending deletion. |
Summary | Provides summary information about the snapshot. |
Analysis Details | If the repository has never been analyzed then an Analyze button is displayed. Otherwise, it indicates details about file count, size and changes. It includes the logical size of all files contained within the snapshot. Click the View Modified/New File List to show details of the modified or new files in this snapshot (see below). |
Snapshot Contents | Displays the entire contents within this snapshot. |

Change Repository Snapshot Retention Dialog

Control | Description |
Retention Date | Select the new date (using the Date Time Picker) after which the backup data will be retired |
Generation 2 Repository Details
This page displays the details of a Gen2 Repository and enables you to monitor its activities, state and the snapshots stored within it.

Control | Description |
![]() | Mounts the repository to either its original location or to an alternative location. If the repository is being mounted to an alternate location, a full resynchronization will be required. |
![]() | Unmounts the repository. |
Jobs | Indicates the number of In Progress jobs as well as the Failed and Completed jobs in the last 72 hours. The Jobs link opens the Jobs Inventory. |
Logs | Indicates the number of New Errors, Errors and Warnings in the last 72 hours. New errors are errors that have not been acknoleged. The Logs link opens the Logs Inventory. |
Storage Details | Indicates the following:
|
Stores Details | Indicates the number of Stores within the Repository and the size of each store. The Stores link opens the Gen2 Repository Stores Inventory. |
Configuration | Indicates the following:
|
Gen2 Repository Stores Inventory
This inventory lists all the Stores within a Repository.

Control | Description |
![]() | Enabled when one Store is selected. This option renames the selected store and can be changed with affecting operations. |
![]() | Enabled when one store is selected. This option should only be used in very specific disaster recovery situations and under the guidance of customer support. |
![]() | Enabled when one or more Stores are selected. This option is only available if the store is inactive – that is, no active policies currently transfer data to a store with this name. Selecting it will delete this store and all the snapshots contained within it. |
![]() | Opens the Generation 2 Repository Details enabling you to view and perform operations on the store. |
Filter on Name | Filters the displayed results based on the name of the store. |
Filter on Status | Filters the displayed results based on the status of the store. |
Filter on Source Node | Filters the displayed results based on the Source node from which data is being ingested. |
Filter on Dataflow | Filters the displayed results based on the Dataflow for which the store is used. |
Filter on Policy | Filters the displayed results based on the Policy for which the store is used. |
Gen2 Repository Store Details
This page provides details of a Store within a Repository and contains an inventory of all the Snapshots within that Store.

Control | Description |
![]() | Enabled when one Store is selected. This option renames the selected store and can be changed with affecting operations. |
![]() | Enabled when one store is selected. This option should only be used in very specific disaster recovery situations and under the guidance of customer support. |
![]() | Enabled only when a single snapshot is selected. Restores the snapshot. Opens the Restore Repository Snapshot Wizard - File System to guide you through the process.. |
![]() | Enabled only when one or more snapshots are selected. Opens the Change Repository Snapshot Retention Dialog |
![]() | Enabled only when one or more snapshots are selected. Allows the ownership of the recovery point to be changed. By changing the owning resource to a node that a user has access to enables the user to see and act upon the recovery point. |
![]() | Enabled only when one or more snapshots are selected. Deletes the selected
snapshots. NoteThe latest snapshot cannot be deleted by the user. Also, if the
snapshot is the only one remaining in the store then it will not be automatically
retired. This provides a safeguard in the scenario where backups fail for a period
of time, since at least one backup will be retained. |
Filter on Date Range | Filters the displayed results based on the dates entered in the Date Time Range Picker. |
Repository Snapshot Details (Storage) - File System
Thispage provides details of a Recovery Point within a Store and contains an inventory of all the Files within that Recovery Point

Control | Description |
![]() | Restores the snapshot. Opens the Restore Repository Snapshot Wizard - File System to guide you through the process. |
![]() | Enabled only when one or more snapshots are selected. Opens the Change Repository Snapshot Retention Dialog |
![]() | Allows the ownership of the record to be changed. By changing the owning resource to a node that a user has access to enables the user to see and act upon the record. |
Calculate | Calculates the amount of space that would be freed in the repository if this recovery point was deleted. |
Files System Contents | Displays the entire directory structure and files contained within this snapshot. |
Cloud Storage Details

Control | Description |
Jobs | Indicates the number of In Progress jobs as well as the Failed and Completed jobs in the last 72 hours. The Jobs link opens the Jobs Inventory. |
Logs | Indicates the number of New Errors, Errors and Warnings in the last 72 hours. New errors are errors that have not been acknowledged. The Logs link opens the Logs Inventory. |
Storage Details | Indicates the following for HCP:
Indicates the following for S3:
|
Stores Details | Indicates the number of Stores within the Cloud and the size of each store. The Stores link opens the Cloud Stores Inventory. |
Configuration | Indicates the following for HCP:
Indicates the following for S3
|
Cloud Stores Inventory
This inventory lists all the Stores within a Cloud. This screen is the same for all cloud types.

Control | Description |
![]() | Enabled when one Store is selected. This option renames the selected store and can be changed with affecting operations. |
![]() | Enabled when one store is selected. This option should only be used in very specific disaster recovery situations and under the guidance of customer support. |
![]() | Enabled when one or more Stores are selected. This option is only available if the store is inactive – that is, no active policies currently transfer data to a store with this name. Selecting it will delete this store and all the snapshots contained within it. |
Filter on Name | Filters the displayed results based on the name of the store. |
Filter on Status | Filters the displayed results based on the status of the store. |
Filter on Source Node | Filters the displayed results based on the Source node from which data is being ingested. |
Filter on Dataflow | Filters the displayed results based on the Dataflow for which the store is used. |
Filter on Policy | Filters the displayed results based on the Policy for which the store is used. |
Cloud Store Details
This page provides details of a Store within a Cloud and contains an inventory of all the Snapshots within that Store. The screen is the same for all cloud types.

Control | Description |
![]() | Enabled when one Store is selected. This option renames the selected store and can be changed with affecting operations. |
![]() | Enabled when one store is selected. This option should only be used in very specific disaster recovery situations and under the guidance of customer support. |
![]() | Enabled only when a single snapshot is selected. Restores the snapshot. Opens the to guide you through the process. |
![]() | Enabled only when one or more snapshots are selected. Opens the Change Repository Snapshot Retention Dialog |
![]() | Enabled only when one or more snapshots are selected. Allows the ownership of the recovery point to be changed. By changing the owning resource to a node that a user has access to enables the user to see and act upon the recovery point. |
![]() | Opens the Hitachi Block Change Snapshot Expiry Date Dialog to enable the expiry date of the selected snapshot(s) to be modified. |
![]() | Enabled only when one or more snapshots are selected. Allows the ownership of the recovery point to be changed. By changing the owning resource to a node that a user has access to enables the user to see and act upon the recovery point. |
![]() | Enabled only when one or more snapshots are selected. Deletes the selected
snapshots. NoteThe latest snapshot cannot be deleted by the user. Also, if the
snapshot is the only one remaining in the store then it will not be automatically
retired. This provides a safeguard in the scenario where backups fail for a period
of time, since at least one backup will be retained. |
Filter on Date Range | Filters the displayed results based on the dates entered in the Date Time Range Picker. |
Cloud Snapshot Details (Storage) - File System
This page provides details of a Recovery Point within a Store and contains an inventory of all the Files within that Recovery Point.

Control | Description |
![]() | Restores the snapshot. Opens the Restore Repository Snapshot Wizard - File System to guide you through the process.. |
![]() | Enabled only when one or more snapshots are selected. Opens the Change Repository Snapshot Retention Dialog |
![]() | Allows the ownership of the record to be changed. By changing the owning resource to a node that a user has access to enables the user to see and act upon the record. |
Calculate | Amazon S3 only, Calculates the amount of space that would be freed in the repository if this recovery point was deleted. |
Storage Tasks
For further information, refer to:
How to view the status of a repository
Before you begin
It is assumed that a policy that creates repository snapshots has been implemented.
To view the status of a repository:
Procedure
Click Storage on the Main Banner.
The Storage Inventory is displayed.In the filters area, set the Type to Repository.
The inventory now only lists Repository storage nodes.Click on the title of the tile corresponding to the required Repository.
The Generation 1 Repository Details for the that Repository are displayed.Click one of the following buttons on the Generation 1 Repository Details:
- View Node Details to view the Node Details.
- Analyze or Refresh to analyze the repository sizes.
- Stores to view the Gen1 Repository Stores Inventory.
How to view the contents of a snapshot in a repository store
Before you begin
It is assumed that a policy that creates repository snapshots has been implemented and that at least one snapshot has been created in the designated repository store.
To view the contents of a repository snapshot:
Procedure
Click Storage on the Main Banner.
The Storage Inventory is displayed.In the filters area, set the Type to Repository.
The inventory now only lists Repository storage nodes.Click on the title of the tile corresponding to the required Repository.
The Generation 1 Repository Details for that Repository are displayed.Click the Stores button on the Generation 1 Repository Details.
The Gen1 Repository Stores Inventory is displayed.Click on the title of the tile corresponding to the required Store.
Each Store tile indicates the Source Node and Policy it is associated with.The Gen1 Repository Store Details for the that Store are displayed.Click on the title of the tile corresponding to the required Snapshot.
Each Snapshot tile indicates the Date and Time when it was created.The Repository Snapshot Details (Storage) - File System for the Snapshot are displayed.
How to view the status of a Hitachi Block storage device
Before you begin
It is assumed that a policy that creates Hitachi Block hardware snapshots has been implemented and that at least one snapshot has been created in the designated pool on the device.
To view the hardware status:
Procedure
Click Storage on the Main Banner.
The Storage Inventory is displayed.In the filters area, set the Type to Hitachi Block Device or Hitachi Logical Block Device.
The inventory lists only Hitachi Block storage nodes.Click on the title of the tile corresponding to the required device.
The Hitachi Block Device Details for the device are displayed.Click one of the following buttons on the Hitachi Block Device Details:
- Host Groups to view the Hitachi Block Host Groups Inventory
- Journals to view the Hitachi Block Journals Inventory
- Pools to view the Hitachi Block Pools Inventory
- Logical Devices to view the Hitachi Block Logical Devices Inventory
- Snapshots to view the Hitachi Block Snapshots Inventory.
- Replications or Clones to view the Hitachi Block Replications Inventory
Click on the title of a tile in the selected inventory to view the details for that item.