Data Flows

Two-step teardown reduces the possibility of inadvertently tearing down Block Storage replications due to accidental deactivation of a dataflow, or activation of an erroneous dataflow.

With two-step teardown, on deactivation of a dataflow in which a replication operation appears, or reactivation of a data flow where a replication operation has been removed, the replication is now flagged as being eligible for teardown in the Restore and Storage inventories. When a replication operation is deactivated, the underlying replication on the hardware will continue to operate as normal, except that any further batch resynchronizations will not be scheduled.

The final teardown operation must be explicitly initiated by the user, via the Storage inventory.

If a user initiated teardown operation fails, it is not automatically retried, so needs to be re-initiated by the user. Teardown failure may occur in the case of GAD 3DC dataflows, where teardowns must be performed in a specific order. Prior to the introduction of two-step teardown, automatic retries were performed indefinitely until successful.

It is possible to disable two-step teardown on a per ISM basis via a configuration file, so different teardown policies can be implemented within the same environment.

Parent Topic

• About data flows

Data flows drawn in the Protector UI are abstractions that hide the underlying hardware and software implementation. Before a data flow can be constructed, Protector Client software must be installed on the physical nodes connected to the storage devices, and the equivalent nodes must be created in the Nodes Inventory. The relationship between storage devices, Clients and nodes appearing in the Nodes Inventory is described in About nodes.

As an example of how a data flow is implemented, consider the backup of a file path on a server to a repository. In this case, the source and destination storage devices are file system volumes mounted on separate servers. Protector Client software must be installed on both servers. These Protector Clients are automatically detected by the Protector Master and appear in the Nodes Inventory as OS Hosts. The source OS Host can be used 'as-is' to identify the volume and file path in the backup policy. The Repository node is created via the UI; the destination OS Host node being selected as the proxy when configuring the node. When the rules for this data flow are activated, the source server will transmit the files identified in the policy over the network to the repository on the destination server. The figure below shows the data flow as it appears on the UI with the underlying implementation shown beneath.

A more complex example is a data flow representing application data, stored on a source block storage device, being replicated to a destination block storage device. The source block device has LDEVs mounted to an application server machine that are being used to store the application data. Protector Client software must be installed on the application server and on servers at the source and destination sites that are designated to control the block devices. The application server must have prerequisites installed to enable Protector to interact with the application software. The servers (ISMs) at the source and destination sites must have prerequisites installed to enable Protector to interact with the block devices. All three Protector Clients will be automatically detected by the Protector Master and appear in the Nodes Inventory as OS Hosts. Source and destination Block Device nodes are created via the UI; the source and destination OS Host nodes representing the ISMs being selected as proxies when configuring the nodes. When the rules for this data flow are activated, the source (VSP 1) will replicate the LDEVs identified in the policy over the data link to the destination (VSP 2). The figure below shows the data flow as it appears on the UI with the underlying implementation shown beneath. Note that the source Block Device node is required by Protector to control the replication, but does not appear on the data flow.

Parent Topic

• About data flows

Many-to-one topologies should be used only where absolutely necessary. These topologies allow data from multiple nodes to be stored on a single destination node. For example, two or more source nodes replicate to a common backup server.

Consider whether the source nodes should be treated as a cohesive node group rather than individually.

If the source nodes are not functionally related then consider drawing separate data flows for each one; this will allow rules activation/deactivation for each flow to be decoupled.

Parent Topic

• About data flows

One-to-many topologies are one of the standard building blocks for creating complex data flows. These topologies allow data from one node to be stored on multiple destination nodes. For example, one source node replicates to a DR server and a repurposing server. A policy is applied to the source node and all destination nodes.

Parent Topic

• About data flows

In a cascading topology, a source node sends data to a primary destination node and then on to a secondary destination node. The primary use case is to copy the data to an intermediary site and then onto a remote site. The secondary use case is for local repurposing, where multiple copies of the same data can be mounted to different servers and used by different sets of users. The primary and secondary destination nodes both store the data. By sending all data to local and remote sites, the disaster recovery options are improved. A policy is applied to the source node, the local and the remote destination nodes.

Parent Topic

• About data flows

Ops Center Protector is designed to allow data to be filtered according to defined policies, and for data to be either sent directly to a node or routed through one or more intermediate nodes.

Typically, a set of policies can be implemented by using parallel or serial data flows with different tradeoffs. Consider a scenario where the following backup policies are required:

• The entire contents of a source machine need to be backed up to a destination machine for disaster recovery purposes.
• Only databases from that same source machine need to be backed up to a different destination machine for testing purposes.

Parent Topic

• About data flows

Child Topics

• About the parallel data flow solution
• About the serial data flow solution

About the parallel data flow solution

For the parallel solution the source node has two policies assigned; one for the whole machine (replicating all attached logical devices to myVSP1) and one for the databases (replicating only a subset of those logical devices to myVSP2). Because there are two movers in parallel, data that is common to both policies must be transmitted by the source node twice. This could be considered wasteful as it doubles the computing load and network bandwidth usage. However:

• This topology is more fault tolerant since one destination node does not depend on the other destination node to implement its policy.
• For Host based data flows, very fine grain data classification filters, separate bandwidth throttling and/or scheduling windows can be applied to each branch of the data flow.

Parent Topic

• About parallel versus serial data flows

About the serial data flow solution

For the serial solution the same policies are applied as in the parallel solution, the difference is that the data going to the second destination node is routed through the first destination node. This reduces the data traffic on the source node since it only has to transmit it once. However the policy on the second destination node now requires the first destination to be running and available on the network.

Parent Topic

• About parallel versus serial data flows

It is important to create data flows that are well formed, understandable, manageable and maintainable. To achieve these goals it is advisable to adhere to a number of guidelines when constructing them.

The Data Flow Wizard has an intentionally small workspace area. This is done to dissuade users from drawing overly complex data flows. It is possible to pan and zoom the workspace to aid working on lower resolution displays. This feature should not be used to create a large drawing area.

Data flows should always be drawn with data flowing in the reading direction appropriate for the locale. The general convention for such diagrams is left to right. Although top to bottom data flows can be drawn, mover labels will not be displayed in this format.

Position nodes on diagrams so that adequate space is left between them for the operation name, operation type and mover label to be drawn below the movers.

Make full use of the ability to name and describe nodes, node groups, policies, operations, data flows, movers and schedules. Use consistent naming conventions and descriptions that convey intent; this will greatly enhance understanding of the purpose of a data flow for other users and will aid ongoing maintenance. Devise and adhere to a common naming convention based on the guidelines described in About best practices for naming objects.

A central principle for determining which nodes and policies should be placed on each data flow is to consider the granularity with which you want to be able to activate and deactivate individual data protection policies. If you combine too many flows and policies into a single diagram, then it will not be possible to deactivate a single policy without deactivating many others. For this reason it is recommended that you:

• Consider how you may want to activate and deactivate separate policies.
• Aim, wherever possible, to have only one flow and one policy per diagram.
• Only place related nodes⁽¹⁾ and policies on the same data flow. Note that a policy can contain multiple operations, and for hardware orchestration data flows, all operations on a PVOL should be contained within the same data flow.
• Separate unrelated policies sharing the same data flow into separate diagrams.
• Only use one-to-many topologies if all the participating nodes and policies are related.
• Consider placing multiple instances of the same node on one diagram to improve presentation.
• Use node groups for source nodes that share identical policies.
• Use separate data flows in place of many-to-one topologies, unless absolutely necessary.

^{1. Related nodes and policies typically form part of the same business process.}

Parent Topic

• About data flows

Providing meaningful names for the objects you create in Protector is one of the best ways to ensure that your data protection strategy is understandable, manageable and maintainable. The following guidelines will help you achieve this:

• Adopt a naming convention that results in similar concepts being listed together when sorted alphabetically. For example VSPCorporate and VSPUKOffice are preferable to CorpVSP and UKOfficeVSP.
• In general, Protector names should use nouns to describe objects and verbs to describe operations that are specific to the business processes in which they are used rather than Protector terminology.
• Names should be unique enough so as to avoid misunderstanding and confusion.

  For example: Site1Broadstone and Site11London are preferable to Site1 and Site11.

• Node names should describe the node's role in the organization and possibly its location. Avoid describing its type or other generic attributes that can be determined from the Node Details.

  For example: VSPTexasSalesCorp is preferable to PrimaryVSPG400.

• Node Group names should describe the node group's role in the organization and possibly its location. Avoid describing its type or other generic attributes that can be determined from the Node Group Details.

  For example: ClusterDbLegal is preferable to OracleRAC.

• Policy names should describe what the policy does, specifically in the context of the organization's data protection strategy. Avoid describing its classifications, filters, operations, scheduling or other generic attributes that can be determined from the Policy Details.

  For example: OracleDRMajorHeadOffice is preferable to UniversalRepOraclePolicy.

• Operation names should describe what the operation does, specifically within the context of the policy in which it is used. Avoid describing its type, scheduling or other generic attributes that can be determined from the Policy Operation Details.

  For example: ReplicateLocal and ReplicateOffsite are preferable to Replicate1 and Replicate2.

• Data Flow names should describe the data protection policy that is being implemented, specifically within the context of the organization's data protection strategy. Avoid describing attributes that can be determined from the Data Flows Inventory, Data Flow Details or Monitor Details.

  For example: OracleFailOverToSubOffice is preferable to ReplicateOracleDataFlow.

• Mover labels should describe the purpose of the mover and/or the association between the nodes it connects. Avoid describing the operation name or operation type since these already appear in the Data Flow Details.

  For example: Fine Grain Protection is preferable to Weekly backup.

• Schedule names should describe the purpose of the schedule. If the schedule is related to a specific policy then name it after that policy. Avoid describing its type or other attributes that can be determined from the Schedule Details.

  For example: BackupWindowOvernight is preferable to Weekdays10PMTo6AM.

Parent Topic

• About data flows

The repository is updated periodically using scheduled resynchronizations. This method involves a scan of the source machine’s file system. With batch resynchronization, the changed blocks are transferred. By default, the block size that is transferred is 2 MB; it is 16 KB if fine change detection is configured in the store template for Gen 1 repositories or in the Policy definition for Gen 2 repositories. An entire file is transferred if it is less than one block. Batch backup is useful for data that does not change often, such as data contained on the operating system disk.

Fine change detection should be used with the batch mover if there are frequent, widely distributed changes to files. Typically however, content on file servers does not benefit from fine change detection, because Microsoft Office documents are automatically compressed by the applications. This means that the smallest of modification causes a completely different file to be created, negating any benefit from detecting changed blocks.

Parent Topic

• About Repository and HCP based backups

The data capture system is highly granular, with the option to tightly define the type of data that is transferred within the policy classification. Unlike systems that replicate all contents on the volume, Ops Center Protector's Host Based data protection technologies replicate only specified data, thereby saving bandwidth and storage space.

Parent Topic

• About Repository and HCP based backups

Source side deduplication is a mechanism within Protector that improves network bandwidth utilization by avoiding sending the same data multiple times.

In simple terms, as soon a block on the source machine is detected as changed during post-scan in a batch policy, those blocks are transferred to the repository. Source side deduplication uses Single Instance Store (SIS), a one-by-one method of scanning/transferring data from source to repository during initial synchronization and subsequent resynchronizations. If, for example, twenty 5TB source nodes (each having much of the data duplicated across them) are backed up, the repository will ingest data from the first source node, go to the second source node and compare its data with what is already ingested, then transfer only non-duplicate data. This process is repeated with the remaining source nodes.

Even if some duplicate files get through, with source side dedupe enabled, SIS post processing will remove those duplicates. SIS post processing is applied to the dataset once per day during repository cleanup.

The changed block transfer method is far more efficient and has less impact than traditional backup systems.

Parent Topic

• About Repository and HCP based backups

Ops Center Protector has the ability to replicate data being sent to an on-site repository, to an off-site repository without needing to gather the data from the source machine(s) again. This minimises the load on the source machines and quickly and efficiently transfers the data off-site.

Using Smart Repository Sync, the secondary repository creates backups from the primary repository by taking the incremental changes required to create a new snapshot; the source node is not involved in this process. The secondary repository has the following capabilities:

• The user selects which backups are sent to the secondary repository. You may choose to only send a subset of the primary.
• You do not have to use the same schedule. You may for instance back up to the primary repository every hour but to the secondary once a day.
• You can have different retention. You may for example keep backups on the first repository for a week and on the secondary repository for 6 months.

Repository to repository backups should be scheduled such that the secondary (off-site) repository takes the latest completed backup from the primary (on-site) repository. The secondary repository backup is therefore scheduled to run on completion of the primary's backup.

When the policy is first triggered, the on-site repository will be resynchronised with the source. The empty off-site repository will then be synchronised with the on-site repository. Depending the amount of backup data and the bandwidth of the network between the on-site and off-site repositories, this initial synchronisation process can take a considerable time (many hours) to complete. To overcome this, a technique called 'repository seeding' (see How to seed an offsite repository) may be used for efficiently setting up an off-site data store, reducing the time and bandwidth required to load the initial backup into the secondary repository. Once seeded, the amount of data transferred between the on-site and off-site repositories is much reduced and dependent only on the data change rate of the source machine(s).

Parent Topic

• About Repository and HCP based backups

File system data from any supported OS, that is backed up to a Protector repository using a batch mover, can be tiered to HCP cloud storage platform. A repository store is tiered to an associated HCP namespace. Each tiered repository stream (a file can consist of one or more streams) is saved as an HCP object within its related namespace, along with metadata that enables it to be restored back to the original source node. If a previously tiered repository stream is modified, then the entire stream is tiered to HCP again. Once a stream is tiered to HCP it is removed from the repository.

Repository ingestion rate throttling helps to constrain repository data store size growth. If a repository's tiering queue gets too large, the repository will stop receiving data from the source until the tiering queue length reduces. High and low watermarks control the growth of a repository, allowing newly ingested files to occupy the space that tiered files previously occupied. By default up to 50 streams can be tiered concurrently to HCP, with another 50 queued awaiting tiering, before repository ingestion is paused. If performance outweighs repository growth in your environment, please contact Protector product support to adjust the throttling behaviour.

Protector does not set a retention on HCP objects. When a tiered stream is no longer referenced by any repository snapshots, the corresponding object will be deleted from HCP. A repository must be present in an active data flow and configured to tier to the HCP to be able to delete objects. When a repository store is deleted, the corresponding namespace for that store will be deleted from HCP.

Deleting a repository node will not remove the repository streams or the data tiered to HCP. To remove all Protector's data tiered to HCP after deleting a repository node, use the HCPDM utility provided by HCP.

Parent Topic

• About Repository and HCP based backups

When constructing a data flow containing Hitachi Block based storage devices, it is necessary to use the correct combination of mover type (Batch or Live/Continuous) in conjunction with a given snapshot or replication technology (Thin Image, Refreshed Thin Image, ShadowImage, TrueCopy, Universal Replicator or Global-Active Device).

The term Differential Snapshot means that a new target volume(s) is created each time the operation is triggered. The target volume(s) remain suspended after creation. The target records the deltas so the source is also required to reconstruct the full data set.

The term Refreshed Snapshot means that a new static target volume(s) is created the first time the operation is triggered. The same target volume(s) is refreshed with new deltas from the source on subsequent triggers. The target volume(s) remain suspended after creation. The target records the deltas and thus the source is also required to reconstruct the full data set.

The term Batch Replication means a static target volume(s) is created the first time the operation is triggered. After initial synchronization, the replication is suspended. Subsequent triggers result in a resynchronization from the source, after which the target volume(s) are suspended.

The term Live Replication means a static target volume(s) is created the first time the operation is triggered. The source and target volume(s) are continuously kept in sync (paired) either by copy-on-write (COW) or copy-after-write CAW) data transfer mechanisms. The replication pairs can be paused and resumed as required.

The following table lists typical block based data flow scenarios along with the move types that can be used.

(1) Continuous SI can also be used in these topologies to vary the use case.

(2) Continuous SI cannot be used in these topologies since it is not possible to chain a remote replication from Continuous SI.

Parent Topic

• About Hitachi Block based backup technologies

Thin Image enables rapid creation of in-system, space efficient, read/write, volume-consistent snapshots and subsequent rollback of entire volumes.

Snapshots of a volume in the storage system are stored in a dedicated area called the Thin Image pool. For floating snapshots, where no LDEV is assigned until it is mounted, no data movement occurs and thus creation of a snapshot is near instantaneous. For non-floating snapshots, the auxiliary tasks of creating an LDEV and a LUN will take some time.

Once a snapshot is created, subsequent updates to the primary data causes the storage system to move the data blocks being updated to the TI pool. TI pool usage thus increases as the primary data changes and snapshots are retained.

When accessing a snapshot, the storage system presents the virtualized contents by merging the primary volume with its differentials held in the TI pool.

When deleting a snapshot, the storage system releases the differentials held in the TI pool. When multiple snapshots are involved, the delete operation may take some time. The differentials are reference counted and will only be deleted when no remaining snapshot requires them.

When handling multiple primary volumes, the storage system takes a snapshot of each volume sequentially. This means that a slight difference can be seen across the snapshot timestamps. If exactly the same timestamp is required among the snapshot set (for crash-consistent backup), the snapshot set should be created using Consistency Groups (CTGs).

When taking a snapshot, there are two options for the target volumes:

• Differential Snapshot: Creates a new snapshot for each backup and deletes it when the retention time expires. This simplifies the management of numerous snapshots and is suitable for backup operations. Data Retention Utility (DRU) protection can be applied to the snapshot's LDEV so that it can be used as a read-only volume or to protect it against both read and write operations.
• Refreshed Snapshot: Creates a new snapshot for the first backup, and then resynchronizes it on the following backups. This enables static target volumes (Port, Host Group and LUN, although the LUN may not remain constant depending on the mount host OS) and is suitable for repurpose operations.

Floating Device is an improved snapshot capability, used in conjunction with Thin Image, that simplifies snapshot management. With this capability snapshots can be created without creating target volumes upfront. This means that the limit on the number of snapshots in the entire storage system is increased (the number of snapshots of a specific primary volume is 1024). To revert the snapshot it is only necessary to select the required timestamp. To mount the snapshot for re-purposing, it must be mapped to a specific LDEV/LUN. After the snapshot is un-mounted, the volumes will be deleted by Protector as part of the unmount process.

Parent Topic

• About Hitachi Block based backup technologies

Child Topics

• About cascaded Thin Image snapshots

ShadowImage enables the creation of in-system, RAID-protected, read/write, volume-consistent, full clones.

As with TI snapshots, consistent clones can be created using Consistency Groups (CTGs).

When taking a clone of a primary volume the storage system copies all of the data to the secondary volume. The point at which this is done depends on the split type selected:

• Quick Split - copying from primary to secondary is performed in the background so that the secondary is immediately available for reading/writing. The performance of the primary may be affected if access the secondary references data that has not yet been copied from the primary. In this case, on-demand copying of that data from the primary is required.
• Steady Split - copying from primary to secondary is performed in the foreground before the secondary is made available for reading/writing. The creation of the secondary takes time depending on volume size.

If using Dynamic Provisioning (DP) volumes for both primary and secondary volumes, the copy is applied only for the allocated area; the unallocated area is ignored.

Once the clone is created, the storage system updates the bitmap for the primary, which records which blocks have been modified. Pair resynchronization can be performed in one of the following ways:

• Quick Resync - resynchronization is performed in the background and on-demand. The secondary is briefly made read only (for less than 1 second), after which it becomes available for reading/writing (i.e it enters the PAIR state in less than 1 second). The performance of the primary may be affected if access to the secondary requires on-demand resyncing from the primary.
• Normal Copy - the secondary is made unavailable while the resynchronization is performed. The resync takes time depending on the size of differentials between the primary and secondary.

When the secondary is accessed, behaviour depends on the mode of operation as follows:

• Steady Split and Normal Copy - the storage system presents the actual contents of the secondary volume. This is in contrast to TI snapshots, where a merging process is required between the primary and secondary volumes to reconstruct the data.
• Quick Split and Quick Resync - the storage system presents the actual contents of the secondary volume. However a merging process may be required between the primary and secondary volumes to reconstruct the accessed block of data, if the background copy of that block has not yet been performed.

The following table shows how Quick Split and Quick Resync (indicated by the suffix q) are affected by upstream and downstream operations in an SI data flow:

When the clone is deleted the storage system releases the bitmap.

Protector supports Steady Split/Normal Copy and Quick Split/Quick Resync.

Continuous ShadowImage can be used to:

• Protect access to local TI snapshots if the production volumes fail.
• Isolate production volumes from performance impacts caused by heavy I/O on local TI snapshots.
• Allow multiple scheduled mount operations (beyond the limits imposed by SI mirror counts) without affecting the original backup, through the use of Refreshed TI.

The typical use cases for continuous ShadowImage include:

• Repurpose on Demand - using continuous SI, keeps a close copy of the primary volume and allows pause and mount for repurposing.
• Protected Backup - using continuous SI to TI snapshots, retains snapshots in the event that the primary volume fails.
• DRU Protected Backup - using continuous SI to TI snapshots with DRU, retains snapshots with DRU lock in the event that the primary volume fails.
• Repurposing (TI) - using continuous SI to RTI snapshots, provides multiple repurposing copies, possibly in excess of the SI limit.
• Repurposing (SI) - using continuous SI to batch SI, provides a repurposing copy.
• Repurposing (SI) with Backup - using continuous SI to batch SI to TI snapshots, provides a repurposing copy with snapshots for protection.
• Repurposing (SI) with DRU Backup - using continuous SI to batch SI to TI snapshots with DRU, provides a repurposing copy with snapshots for protection with DRU lock.

Parent Topic

• About Hitachi Block based backup technologies

TrueCopy provides remote, volume consistent, synchronous replication.

When establishing a replication between primary and secondary volumes, the storage system copies all the data from the primary to the secondary volume. Depending on the volume size, the creation of replicas takes time. As with ShadowImage, data copy can be optimized by using DP volumes.

After creation of the replicas, the storage system maintains the replica on the secondary volume by synchronously transferring each write made to the primary. In synchronous (copy on write) mode, the storage system signals write I/O completion only when it has been transferred to the secondary volume. The write order is completely guaranteed so that the secondary volume is crash-consistent at any point in time.

In the COPY state, no read/write operation is permitted to the secondary volume. To access the secondary volume, the replication must be paused (i.e. the pair is placed in the suspended state). As with ShadowImage, a bitmap is maintained for later pair synchronization. When the replication is deleted the storage system releases the bitmap.

Parent Topic

• About Hitachi Block based backup technologies

Universal Replicator performs volume consistent, asynchronous replication.

When establishing a replication to a target secondary volume, the storage system copies all the data to the secondary volume. Depending on the volume size, the creation of the replica takes time. As with TrueCopy, the copying can be optimized using DP volumes.

After the replication is created, the storage system maintains the replica on the secondary volume, transferring each write to the secondary volume. In asynchronous mode, the storage system signals each write completion as soon as it is performed on the primary volume, it then transfers it to the secondary volume (copy after write). Journalling ensures the write order is completely guaranteed so that the secondary volume is crash-recoverable at any point in time.

In the replicating state, no read/write operations are permitted to the secondary volume. To access to the secondary volume, the replication must be paused (placed in the suspended state). Universal Replicator maintains a journal of the primary volume for later pair synchronization. In contrast to TrueCopy, long duration pausing can be tolerated by configuring sufficiently large UR journals. When the replication is deleted the storage system releases the UR journals.

The use of Consistency Groups (CTGs) is mandatory for Universal Replicator.

Parent Topic

• About Hitachi Block based backup technologies

Global-Active Device allows volume consistent, remote, active-active replication.

When establishing a replication, the storage system copies all the data to the secondary volume. Depending on the volume size, the creation of the replica takes time. As with TrueCopy, you can optimize the process using DP volumes.

After creating the replication, the storage system maintains the replica on the secondary volume. The copy mechanism and data consistency is the same as for TrueCopy.

Unlike TrueCopy, read/write operations are permitted on both the primary and secondary volume even in the replicating state, hence both sides of the replication pair are said to be active. All updates to the secondary volume are also transferred back to the primary volume. When the replication is paused (i.e. placed in the suspended state), the storage system determines the owner volume using the quorum disk and prohibits any read/write access to the non-owner volume.

As with TrueCopy, a bitmap is maintained for pair re-synchronization. When the replication is deleted, the storage system releases the bitmap.

Protector is not be able to operate any dataflow containing a GAD replication if the primary and secondary have been swapped externally, since path resolution will see the original secondaries as the new primaries. The swap must be reversed externally to its normal direction.

Parent Topic

• About Hitachi Block based backup technologies

Child Topics

• About Global-Active Device Cross Path

About Global-Active Device Cross Path

In a GAD cross-path and multi-path environment, the application servers may have one or more LUN paths to the PVOL, and also one or more LUN paths to the S-VOL. The GAD pair may also have one or more LUN paths between them.

Protector is capable of configuring and adopting hardware path, file system path and application replications for GAD cross-path and multi-path scenarios.

In situations where the Application Host or OS Host has a LUN path to a GAD P-VOL and also has a LUN path to the S-VOL of that replication, Protector will resolve application paths including that P-VOL when the host has one or more LUN paths to both volumes involved in the replication.

Protector can:

• Adopt the replication
• Re-evaluate the replication if it already exists in Protector
• Create a snapshot of the replication's P-VOL
• Swap the replication

This feature requires raidscan (version 01-41-03/03 or later), which, when issued against the secondary volumes of a remote replication, includes the serial number of the array hosting the primary volumes.

This feature only considers cross paths to the primary application. Failover support for secondary applications is not supported.

Parent Topic

• About Global-Active Device replication

Three datacentre (3DC) cascade using TrueCopy and Universal Replicator provides the maximum level of data protection by combining synchronous replication between the primary and local secondary site, cascaded with asynchronous replication between the local secondary and remote tertiary site.

If a component failure or power failure occurs at the primary site, production can be handed over to the local site with no data loss.

If a site failure or localised natural disaster occurs, both the primary and local site may be lost. In this case production can be handed over to the remote site with minimal data loss.

Consider the following when using 3DC cascade:

• Due to the cascading topology, a failure at the local site will prevent both the synchronous asynchronous replications, leaving the primary site unprotected. To avoid this situation, it is recommended to use the 3DC multi-target configuration instead.

Parent Topic

• About Hitachi Block based backup technologies

Three datacentre (3DC) multi-target using Global-Active Device, TrueCopy and Universal Replicator provides the same level of data protection, equivalent to 3DC cascade, but improves upon it by solving the issue of local secondary site failure leaving the primary site unprotected. If the local secondary site fails, replication between the primary and remote secondary site can continue uninterrupted.

3DC multi-target may also be configured using Universal Replicator instead of TrueCopy. Symmetric configuration and operation simplifies component failure and site failure since both are handled with a single set of operations. Consider this option if simplicity of operation is the first priority.

Parent Topic

• About Hitachi Block based backup technologies

Three datacentre (3DC) multi-target with delta is an improvement on 3DC multi-target that provides on-going protection even in the event of a failure at the primary site.

A replication from the production site to the local secondary site is configured using Universal Replicator. A replication from the production site to the remote secondary site is configured using Global-Active Device or TrueCopy. Additionally, a suspended, asynchronous Universal Replicator (delta-UR) replication is established between the local and remote secondary sites. The local and remote secondary sites will be near identical once pairing with the primary site is complete. Differences that appear between the secondary sites over time, due to a number of factors, are tracked by the suspended delta-UR replication.

Failure of the local or remote secondary site is handled in the same way as for 3DC multi-target, in that the primary site remains protected by the surviving secondary site.

In the event that the production site fails, the local secondary site can take over. The local secondary site is then rapidly brought under the protection of the remote secondary site by resuming the suspended delta-UR replication. Because only the deltas between the local and remote secondary sites need to be resynchronized, this pairing takes only a short time to achieve, meaning that the local site only remains unprotected for a brief period. Without the pre-existing, suspended delta UR between the local and remote secondary sites, it could take hours or even days to establish a replication between the secondary sites, leaving the local secondary site vulnerable for an extended period while this takes place.

Parent Topic

• About Hitachi Block based backup technologies

Static clones of a clone enables multiple repurposing with heavy workloads (read/write I/O).

A 1st level clone (golden image) is created based on a schedule. The golden image can then be manually replicated as 2nd level clones for repurposing. The 2nd level of clones need to be static because the re-purpose servers require static access points (Port, Host Group and LUN although the LUN may not remain constant, depending on the mount host OS) for mounting the volumes.

If re-purposing beyond the ShadowImage limitation of two 2nd level clones is required, use Thin Image on the 2nd level.

Parent Topic

• About Hitachi Block based backup technologies

Clone with replication enables disaster recovery and local backup and/or local re-purposing.

A replica of the production data is maintained on the remote site using TrueCopy, Universal Replicator or Global-Active Device. The remote replication is used for disaster recovery.

Local clones are created based on a schedule using ShadowImage. These clones can be used for fast operational recovery or repurposing.

Parent Topic

• About Hitachi Block based backup technologies

Snapshot with replication enables disaster recovery and local backup.

A replica of the production data is maintained on the remote site using TrueCopy, Universal Replicator or Global-Active Device. The remote replication is used for of disaster recovery.

Local snapshots are created based on a schedule using Thin Image. These clones can be used for fast operational recovery.

Parent Topic

• About Hitachi Block based backup technologies

Snapshot of a clone enables ad-hoc backup for repurposing.

A clone is created using batch or continuous ShadowImage and is made available for repurposing.

A snapshot is taken so that the clone can be reverted quickly if required. Reversion may be needed when performing recurrent testing or configuration change/patching (that may fail) on the repurposed clone.

Parent Topic

• About Hitachi Block based backup technologies

Replication of a clone enables remote backup without DR.

An in-system clone is created using ShadowImage based on a schedule. The cloned point-in-time image is then replicated using TrueCopy or Universal Replicator. Having an intermediate clone means that the replication process does not have any impact to the production volume. The replication is performed as a batch copy, so limited RPO is achievable (typically a few hours). For this reason, this technique is not common for high end storage systems.

Parent Topic

• About Hitachi Block based backup technologies

Remote snapshot enables disaster recovery with remote backup.

A replication is created using TrueCopy, Universal Replicator or Global-Active Device to maintain a replica image of production data on the remote site.

A snapshot is created from the remote replica based on a schedule.

This achieves a high level of disaster recovery, while remote site snapshots enable quick operational recovery even during disaster recovery.

Parent Topic

• About Hitachi Block based backup technologies

Local and remote snapshots enable disaster recovery with backups.

A replication is created using TrueCopy, Universal Replicator or Global-Active Device to keep a replica image of production data on the remote site.

Snapshots of the local production data and remote replica are created based on the same schedule.

This keeps the data consistent on the both sites, simplifying the process of operational recovery during site failover, contributing to a better RTO.

Parent Topic

• About Hitachi Block based backup technologies

Remote clone enables disaster recovery with remote backup and/or remote repurposing.

A replication is created using TrueCopy, Universal Replicator or Global-Active Device to maintain the replica of production data on the remote site.

Clones of the remote replica are created using ShadowImage based on a schedule.

Replication achieves the highest level of disaster recovery, while remote snapshots/clones enable quick operational recovery even during disaster recovery. Also, repurposing with remote snapshots/clones avoids any performance impact to the production site.

Parent Topic

• About Hitachi Block based backup technologies

Local and remote clones offer the same benefits as local and remote snapshots, with the additional benefit of protecting the data from physical failure of the production or replica volumes.

Note the local and remote clones do not allow the user to recover to a point-in-time. The clone is completely refreshed so that it is equal to the primary or secondary volume. Operational recovery is therefore more limited as a result.

Parent Topic

• About Hitachi Block based backup technologies

Local snapshot and remote clones enables disaster recovery with tiered backup.

A replication is created using TrueCopy, Universal Replicator or Global-Active Device to keep a replica image of production data on the remote site.

Local snapshots of the production data and remote clones of the replica are created using Thin Image and ShadowImage respectively, based on different schedules.

Keeping different data on each site enables quick recovery on the production site, while satisfying the long-term protection on the remote site.

This scenario can be flipped (i.e. local clone and remote snapshot) so that the clone is maintained at the local site and the snapshots at the remote site. Protector also supports snapshots and clones on the local and remote site concurrently.

Parent Topic

• About Hitachi Block based backup technologies

Ops Center Protector can adopt and manage ShadowImage, TrueCopy, Universal Replicator and Global-Active Device replications that already exist on Hitachi Block storage hardware. An adopted replication can then be managed via the GUI.

To adopt a replication, the user must specify a replication policy that identifies the required source LDEV(s) or Host Group, draw an appropriate data flow that identifies the source and destination storage devices, replication type (and mirror number for SI and UR), mark the policy for adoption and then activate the rules.

A replication can be dissociated from Ops Center Protector without being removed from the storage hardware.

When adopting replications Ops Center Protector will behave in the following ways depending on the policy and data flow attributes supplied by the user when attempting to perform the adoption process:

Parent Topic

• About Hitachi Block based backup technologies

This dialog is displayed when one or more data flows are activated.

Rules files control the operation of the Ops Center Protector components on each node in the data flow definition. Rules files are generated by the Rules Compiler after policies have been created, the data flows have been defined and policies assigned to source and destination nodes.

CautionIf you modify a policy or data flow that is currently active, then the data flow must be reactivated before your changes will take effect.

Control	Description
Compilation Details	This lists the output from the rules compiler and shows error, warning and information messages. If the compilation is successful, it includes a summary of what policies each node in the data flow will be implementing, forwarding or processing. The data flow can be activated. If the compilation is successful but contains warnings, then the information contained here will assist you in resolving potential issues with the data flow and/or policies. The data flow can be activated. If the rules fail to compile then the information contained here will assist you in resolving issues with the data flow and/or policies. You may need to iterate through several compilation cycles to remove all compilation errors. The data flow cannot be activated. CautionAlways inspect the compiler output. A successful compilation may contain warning messages which you should review. Successful compilation only indicates that the rules are valid, it does not imply that they are verified against your data protection requirements. Please regularly inspect the Default Dashboard and related status screens to ensure that your data is being protected in the manner you intended. Compiler errors are commonly caused by: incorrect or incomplete policies incomplete data flow definitions incorrect or incomplete data flow item attributes incomplete or ambiguous routes for policies missing parameters on destination nodes adding, editing or deleting policy classifications or operations without updating data flows
Compilation Outcome	Indicates one of the following: Blue - the rules are being compiled. Please wait. Green - the rules have been compiled successfully. The data flows and policies are valid (but not necessarily correct) and can be activated. Amber - the rules have been compiled successfully with warnings. The data flows and policies are valid (but not necessarily correct) and can be activated. The data flows and/or policies contain warnings that may need to be rectified. Red - the rules have not been compiled. The data flows and or policies contain errors that must be rectified before the data flows can be activated.
Activate	This button is only enabled once the rules have compiled successfully. Click to distribute the rules to the affected nodes and activate them. The policies will then take effect depending on the availability of affected nodes, operations, trigger conditions or schedules defined. The Logs Inventory can be used to watch and review the progress of data flow activation. Note Rules activation methods depend on the type of policy: Host based: An initial 2 minute rules settlement period is applied after activation to allow rules to reach all participating nodes. If any operation is triggered within the settlement period it will be deferred until after it has expired. Block based: If the current rules are null or they predate the new rules, the ISM will wait up to 2 minutes for a new rule set to arrive. An information level log will be generated if this delay is invoked: Storage proxy node does not have required rules, waiting up to <DELAY> seconds. If, after waiting, the rules are still out of date, the ISM will attempt to use the rules it currently has. All: If a node in the data flow definition is unavailable, then the rules files cannot be sent to that node; activation continues for the available nodes. When the activation is complete, the new rules are activated on all available nodes. When the absent node becomes available and reconnects to the master, the new rules are sent automatically to that node and activated immediately after they are received. If any nodes are deleted from a previously activated data flow definition, then these nodes are deactivated when the new rules are activated. If any such node is not currently available, it is deactivated as soon as it reconnects to the master.

Parent Topic

• Data Flows Inventory

This wizard is displayed when a new data flow is being created.

The Data Flow Wizard performs two principal functions:

• Defines the routing of policies that move data from source nodes to destination nodes.
• Assign policies to nodes on your network, defining what data to backup and the methods of protection to employ.

Control	Description
Name	Enter a name for the Data Flow.
Description	Optional. Enter a short description of the Data Flow.
Tags	Add the tags to be associated with the object being created.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Edit Type	Enter the Edit Type.
Tags	Add the tags to be associated with the object being created.
Cancel	Discards all changes and reverts to the previous page.
Apply	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Control	Description
Resource Groups	It allows the user to view the access permissions for those items granted to specific users and groups. NoteA single Data Flow can be assigned to multiple resource groups.

Nodes Tab

Control	Description
Filter on Node Name	Filters the displayed results based on Node Name.
Filter on Node Type	Filters the displayed results based on Node Type.
Nodes List	List the available source and destination nodes that can be dragged onto the Data Flow Workspace.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Node Groups Tab

Control	Description
Filter on Group Name	Filters the displayed results based on Node Group Name.
Node Group List	List the available node groups that can be dragged onto the Data Flow Workspace.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Data Flow Workspace and Applied Policies

Control	Description
Connect To	Enabled only when a single node is selected on the diagram. Click to create a connection from the selected node to another node on the diagram. When the connector is displayed, click again on the destination node to complete the connection. By default the Mover Type is set to Batch; the properties associated with each connection can be edited via the Mover Settings controls (see 'Mover Settings' controls below). Only compatible elements can be connected. TipConnections can also be created by dragging a destination node from the node list, over a source node to pick up the connector and then dropping it at the desired location. Alternatively you can drag a source node already on the diagram, over a destination node on the diagram and drop it there.
Delete	Enabled only when one or more nodes or movers are selected on the diagram. Removes the selected node(s) or mover(s) from the diagram. You can also press the Delete key.
Node or Node Group Icon	Each node type is represented by a different icon (see Node Type Icons). The currently selected node is enclosed in a box. TipIf a warning condition is detected whilst constructing a data flow (e.g. a policy has only been assigned to a source node) then a red warning triangle will appear next to the offending node.
Multiple Selection	Click and drag the cursor over nodes on the workspace to select multiple nodes and movers. Alternatively press and hold CTRL and click multiple nodes.
Select All	Click on the workspace then press CTRL+A to select all nodes and connectors.
Drag and Drop	Select and drag one or more nodes or movers to reposition them on the workspace. If the user moves a node, the icon will appear green if the node is dragged over another node it can be connected to, or red if not. If the user moves multiple items, the icons will not change color as creating connections from/to multiple items at once is not supported. If the user attempts to drop multiple items over the top of another item, the action will be canceled.
Next Node	Click to move the focus to the next node on the data flow.
Zoom In/Out	Click the buttons next to the workspace, press +/- on the keypad or hold down the CTRL key whilst using the mouse wheel to zoom in and out. The current zoom level is displayed between the zoom buttons. Click the zoom level to reset to 100% zoom.
Fit to Screen	Click the button next to the workspace or press the HOME key to select a zoom level that allows the entire data flow to fit within the bounds of the workspace.
Pan	Right click anywhere on the workspace and drag the cursor.
Applied Policies (all)	If no nodes or movers are selected on the data flow workspace, then the area to the right of the workspace lists all the policies that have been applied in the data flow. Click the button next to the policy name to open the Policy Details for that policy in a new browser tab.

Policies

Control	Description
Policies (source node selected)	If a single source node is selected on the data flow canvas, then the area to the right of the canvas lists all the policies that can be or are applied to that node. Apply policies to the node by clicking the required policy names. NoteIf the selected policy requires a destination node to complete the policy definition, the source node displays a warning symbol to indicate that the policy definition is incomplete.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Movers are connectors that represent how data is transferred from source node to destination node.

The mover provides options on how to route data for policies. If a source node is configured to implement a policy, then any movers connected to it automatically route that policy. If the mover is not configured to implement a policy, then the nodes further downstream are not able to either configure or implement the policy.

Mover Settings

Control	Description
Routed Policies (mover selected)	If a mover is selected on the data flow canvas, then the area to the right of the canvas lists all the policies that are routed by that mover.
Transfer Type	Changes the mover type to one of the following: Batch (solid line) - data is moved in batches based on a schedule or trigger event. Continuous (dotted line) - used only for Hardware operations. Failover (dashed line) - used only for 3DC delta resync data flows. Defines a suspended replication path, between the secondary and tertiary site, that can be invoked if the primary site fails. The arrowhead indicates the direction of data flow during normal backup operations. NoteIt is import to use a mover type that is compatible with the operation type specified in the Policy. This requires an understanding of the snapshot and replication technologies being used. If an incompatible mover type is used, then you will only be notified about the error when you attempt to compile the rules. Remove the replication from the data flow. Reactivate the data flow. Replace the replication on the data flow using the required mover type.
Label	By default the mover label displayed on the connector is empty. This can be replaced with a label describing the connection on the data flow. This feature can be useful in situations where there is more than one mover connected to a node.
Enable network data compression	For Host based operations only (ignored for Hardware based operations). Turns on data compression on the datalink between two nodes. NoteCompression decreases network utilization, but increases CPU usage.
Bandwidth Settings	For Host based operations only (ignored for Hardware based operations). Opens Mover Bandwidth Settings Dialog to enable you to control the amount of bandwidth that data transfers use so that a network connection can be used simultaneously with other applications in the environment.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Policies

Control	Description
Policies (destination node selected)	If a single destination node is selected on the data flow canvas, then the area to the right of the canvas lists all the policies and their contained operations that can be or are applied to that node. Apply operations to the node by clicking the required operation names. A dialog opens, appropriate to the destination node type, that allows those properties to be specified (see Configure Operation Properties). The policies listed here are restricted to those that have been applied to upstream nodes and those that the destination node has the appropriate capabilities to receive. NoteA single policy can have several operations within it for a given data classification. The destination indicates which of those operations it can implement by displaying only the supported operation check boxes. The policy name check box cannot be selected by the user, the individual operations within the policy must be selected.
Configure Operation Properties	When an operation is applied to a destination node you may need to specify properties for that operation. Click this button to open a dialog, appropriate to the destination node type, that allows those properties to be specified: Generation 1 Repository Backup Configuration Dialog Hitachi Block Snapshot Configuration Wizard Hitachi Block Replication Configuration Wizard Hitachi Block Mount Configuration Wizard Once the properties are specified, the button is replaced with a summary of the properties. Click the Edit button next to the summary to reopen the dialog to change any properties. The operation type is displayed in italics next to the mover along with the user defined label. NoteFor Hitachi Block Replication Operation Properties: Once the operation properties have been configured and the data flow has been activated, the properties cannot be changed. Redistributing rules for the active data flow with edited properties will not change them. To change the operation properties, the existing data flow must first be deactivated then reactivated with the new properties. Deactivating the data flow will mark the replication eligible for tear down.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Parent Topic

• Data Flows Inventory

Child Topics

• Mover Bandwidth Settings Dialog
• Generation 1 Repository Backup Configuration Dialog
• Hitachi Block Snapshot Configuration Wizard
• Hitachi Block Replication Configuration Wizard
• Hitachi Block Mount Configuration Wizard

Mover Bandwidth Settings Dialog

This dialog is used to specify when and how much bandwidth can be used by Protector to transfer data across the datalink between two nodes.

You can assign specific bandwidth constraints for defined time windows so that a network connection can be used simultaneously with other applications in the environment. For instance, you can decide to decrease bandwidth during the workday when bandwidth is required for production and increase it at night to allow backups to utilize maximum bandwidth.

Note If the amount of data that must be replicated continuously exceeds the current bandwidth quota, then data is cached on the source until the bandwidth increases. Cache size on the Source Node can be adjusted to avoid any problems with non-transferred data reaching the cache limit. The configuration file distributor.cfg contains the values MaxDiskCache and MaxMemoryCache which can be increased if the cache limit becomes a problem.

Control	Description
Week Grid	Click the cells in the grid, corresponding to the hour-long periods where you want to throttle network bandwidth used by Protector, to one of the following levels (cells cycle through the three states each time they are clicked): High - (Dark Green) High Speed throttling at the setting defined below. Low - (Light Green) Low Speed throttling at the setting defined below. None - (White) Default Speed throttling at the setting defined below.
Unlimited/Thottled	Sets the default speed to the maximum allowed (Unlimited) by the network or to a predefined level (Throttled).
Default Speed	Specifies the default throttle level. This may be set to any value including 0.
High Speed	Specifies the high throttle level. This must be set to a non-zero value and greater than the Low Speed level.
Low Speed	Specifies the low throttle level. This must be set to a non-zero value and less than the High Speed level.

Parent Topic

• Data Flow Wizard

Generation 1 Repository Backup Configuration Dialog

This dialog is displayed when you assign an operation to a Generation 1 Repository node on a data flow.

When using a repository as a destination for a data flow a number of configuration options are available. These destination options for a repository node are contained within Store Templates. Each repository node can be associated with multiple stores templates. There are two default store templates (Standard and Deduplicated), however additional templates can be created.

Control	Description
Select Destination Template	Enter or select a Destination Template from the dropdown list. Once selected, the settings of the store template are displayed below.
Manage Store Templates	Click this link to add to or edit the available destination templates. The Generation 1 Repository Destination Templates Inventory is opened in a new browser tab. NoteOnce you have finished adding or editing templates in the new tab, simply close the tab and continue working with the Operation Properties Dialog. Any changes you have made to the templates will be applied, although they may not appear in the dialog unless you re-select the template.
Settings	Lists the settings for the selected template.

Parent Topic

• Data Flow Wizard

Child Topics

• Generation 1 Repository Destination Templates Inventory

Generation 1 Repository Destination Templates Inventory

This inventory is displayed when managing Destination Templates for a Generation 1 Repository node.

Control	Description
Edit	Edits an existing template in the inventory. The Destination Template Wizard is launched to enable the template's attributes to be changed.
Edit Permissions	Edits an existing template's access permissions. The Access Control Permissions Inventory is launched to enable the template's access permissions to be changed.
Delete	Enabled only when one or more Templates is selected. Deletes the selected item from the inventory.
Add	Creates a new Template. The Destination Template Wizard is launched to guide you through the process.
System Generated Templates	At least two system generated Templates are available when the product is installed. These Templates cannot be deleted since they provide basic functionality. System generated Templates are marked with a icon to indicate that they cannot be modified. Click the template's name to open the Destination Template Details to enable the parameters to be viewed.
User Defined Template(s)	Any number of user defined Templates can be created. These are displayed in the inventory. Click the template's name to open the Destination Template Details to enable the parameters to be viewed.
Filter on Template Name	Filters the displayed results based on the template name.
Filter on Template Type	Filters the displayed results based on the template type.

Parent Topic

• Generation 1 Repository Backup Configuration Dialog

Child Topics

• Destination Template Wizard
• Destination Template Details

Destination Template Wizard

This wizard is displayed when a new Destination Template is being created.

Control	Description
Name	Enter a name for the template.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Resource Groups	It allows the user to view the access permissions for those items granted to specific users and groups. NoteA single Destination Template can be assigned to multiple resource groups.

Control	Description
Source side deduplication	On occasions where many machines have identical roles within the data flow and also contain very similar data (for instance, OS data and installed software on machines on a corporate network) then a network speedup can be obtained by avoiding sending the same data multiple times. Check this option to make use of this.
Fast incremental based on file modification date	If this is checked then Ops Center Protector decides what files need resynchronizing based on whether the modification date has changed. This reduces the time taken to resynchronize, but can be disabled if it is known that software is installed that will modify files without updating their size or modification date. NoteIf only file metadata changes between batch backups (e.g. file ownership or file permissions), then the changes are not captured. These changes are only captured when the file data changes.
Fine change detection	Reduces the amount of data transferred and stored during a resynchronization. An entire file is transferred if it has changed and is less than one block in size. (This option should be used sparingly as there is a processing overhead.)
Deduplicate snapshots	Enables the storage group to deduplicate data across snapshots so the storage group only stores a single copy of the data. This option has a processing overhead.
Preserve hard links	Performs checks so that only one instance of the data is stored, regardless of the number of links pointing to it. This option increases the file system scan time during a resynchronization or batch backup. NoteAs of Protector 6.5, this option is enabled by default. This is not retrospective and will only apply when new stores are created.
Files excluded from global deduplication	A semicolon-separated list of file extensions to be excluded from the store group’s duplication detection can be entered here.
Automatic Validation	Automatically resynchronize source to the destination based on a schedule. One of the following options can be selected: Only if required – Will trigger resynchronization only if the destination is out of sync with the source nodes. Always – Will always perform a resynchronization with the source nodes based on the schedule. Never – An automatic validation will never be performed. Checking this option will disable the remaining options.
Select a Schedule	Select a schedule to trigger automatic validation. NoteSchedules are created for automatic validation the same way as schedules for a policy. A schedule for automatic validation must use a Trigger, by default a pre created schedule named Trigger at 4 AM every day is selected.
Check all files during validation	Ignores file modification date and checks every file for changes.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new settings. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Parent Topic

• Generation 1 Repository Destination Templates Inventory

Destination Template Details

This page displays the details of a Destination Template and enables you launch the wizard to edit them.

Control	Description
Edit	Launches the Repository page of the Destination Template Wizard to enable you to edit the template.
Permissions	Displays the Access Control Permissions Inventory to enable you to view and edit the template's permissions.
Repository Destination Settings	These are the settings entered via the Repository page of the Destination Template Wizard when the Template was created.
Automatic Validation	These are the settings entered via the Repository page of the Destination Template Wizard when the Template was created. Click on the Schedule name to open the Schedule Details in a separate browser tab.

Parent Topic

• Generation 1 Repository Destination Templates Inventory

Hitachi Block Snapshot Configuration Wizard

This dialog is displayed when you assign a snapshot operation to a node that hosts data stored on an Hitachi Block device.

CautionWhen a snapshot operation runs, Protector locks the meta_resource of the Block device until the operation completes. Block operations are queued waiting to get the resource lock; this can impact RPO.

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.

Note

• The classifications that are applicable to Hitachi Block Snapshot operations are Path, Application, Hypervisor and Hitachi Block.
• Protector does not support any Hitachi Block storage LDEV with more than one partition or volume.
• If Protector is subsequently uninstalled, the existing snapshots and mounted volumes are left in place.

Tip

• The actions that are performed by Protector as it executes a backup policy are captured by the Log Manager. Detailed logs and their attachments can be exported as a text file. (See Export Logs Dialog for more information.)
• Details of the hardware resources (LDEVs) used for a particular snapshot can be found in the Hitachi Block Device Details.

Control	Description
Storage Node	Specifies the target storage node where the P-VOL and snapshot S-VOLs are allocated.
Snapshot Pool	Specifies the target storage pool from which snapshot S-VOLs are allocated. Select a Thin Image Pool or a Dynamic Provisioning Pool. Caution 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. NoteThin Image and Dynamic Provisioning Pools must be created using Storage Navigator prior to selecting the Target Storage in Protector. TipIf the P-VOL has an association with a VSM or you select a target storage pool associated with a VSM then Protector will attempt to make the virtual and the physical ID of the S-VOL holding the snapshot identical. For this to work, an LDEV with a physical ID within the defined virtual LDEV range for the selected VSM must available for use.
Advanced Configuration	Click to step through the advanced configuration option pages of the wizard, described below.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Specifies the resource group to be used for S-VOLs, in order to support snapshots and replications from VSM volumes (adding volumes to a VSM is performed by adding the volumes to the correct resource group).

Control	Description
Automatically Selected	Allows Protector to automatically select a resource group in the following order of priority: If there are existing S-VOLs, then the resource group used by those will be selected. The resource group used by the P-VOLs, if the replication is in-system and the P-VOLs are all in one resource group. Resource group 0. NoteIf existing S-VOLs are in multiple resource groups, then the operation will fail with an error.
User Selected	Specify the Resource Group in the associated combo-box. NoteIf there are existing S-VOLs, then the resource group used by those will be selected. If the existing S-VOLs are in multiple resource groups or in a resource group that contradicts the user specification, then the operation will fail with an error.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Specifies how the snapshot is provisioned and its mode of operation. Snapshots are created as differential, in-system snapshots using Thin Image.

CautionBlock storage has a limit of 1024 snapshots per LDEV. Ensure that the RPO and Retention periods are set such that this limit is not exceeded (i.e. Retention / RPO is less than or equal to 1024).

Control	Description
Consistency group	When performing a crash consistent snapshot (for example: using the hardware path classification), use this option to make it truly crash consistent. The hardware has a limited number of consistency groups available so they should be used sparingly.
Fully Provisioned	By default, this option is deselected and the snapshot will be provisioned using floating devices. Where supported by the array the storage device can store a larger number of snapshots using floating device.
Cascade Mode	The snapshot can be cascaded. This allows Protector to mount either the original snapshot or a duplicate of the original. Mounting a duplicate enables modifications to be made without affecting the original snapshot. Refer to About cascaded Thin Image snapshots for further guidance on configuring and mounting cascade mode snapshots.
Cascade Pool	If Fully Provisioned is selected above, it may be necessary to specify a dynamic or hybrid pool where Protector can create snapshot S-VOLs.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Specifies how secondary LDEVs and snapshot groups will be named.

Control	Description
Secondary Logical Device Name	Specifies how S-VOLs will be named: Match Origin - The S-VOL will be given the same name as that used for the origin P-VOL (i.e. the left-most volume in the data flow). Custom - The S-VOL will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the secondary LDEVs' name to view the available substitution variables: %ORIGIN_SERIAL% - S/N of leftmost array in data flow. E.g. output string: 210613 %ORIGIN_LDEV_ID% - ID of leftmost LDEV in data flow. E.g. output string: 00:3A:98 %ORIGIN_LDEV_NAME% - name of leftmost LDEV in data flow. %PRIMARY_SERIAL% - S/N of primary array in this operation. E.g. output string: 442302 %PRIMARY_LDEV_ID% - ID of primary LDEV in this operation. E.g. output string: 00:4C:EB %PRIMARY_LDEV_NAME% - name of primary LDEV in this operation. %SECONDARY_SERIAL% - S/N of secondary array in this operation. E.g. output string: 356323 %SECONDARY_LDEV_ID% - ID of secondary LDEV in this operation. E.g. output string: 01:F4:35 %CREATION_DATE% - date secondary LDEV was created by this operation. E.g. output string: 20180427 %CREATION_TIME% - time secondary LDEV was created by this operation. 1130
Snapshot Group Name	Specifies how the snapshot group will be named when the Provisioning Options - Consistency group option is not selected. Automatically Generated - The snapshot group name is generated by Protector based on the rules context ID and policy name. Custom - The snapshot group is named using the string provided (limited to 28 characters). An '@' separator followed by a unique ID is then automatically appended to this name. The unique ID is composed of 3 base 36 characters and is required to enable Protector to manage the groups.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

If Fully Provisioned is selected on the Provisioning Options page on this wizard, these options are enabled to specify Data Retention Utility (DRU) protection parameters.

CautionProtector cannot mount a DRU protected snapshot. However a cascaded snapshot can be created and mounted if the original has Cascade mode enabled.

Control	Description
Protection Type	One of the following can be selected: None - DRU protection is not applied the snapshot Host Read Only (wtd) - Prevents hosts writing to the snapshot LDEV. Full (wtd + svd) - As for wtd, plus the array is prevented from changing the contents of a snapshot LDEV using resync or restore. It also prevents deletion, mapping and unmapping of the snapshot from its LDEV. NoteDRU can prevent mounting if the OS rejects a read-only volume (mount via cascade snapshot is unaffected, and therefore recommended).
Duration Of Settings Lock (Days)	CautionDRU protection cannot be removed while the lock is active. Specify a duration in days during which the applied DRU protection cannot be removed. Once this duration has expired the protection is not automatically removed; it must be removed manually.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Summarizes the configuration settings made by the user.

Parent Topic

• Data Flow Wizard

Hitachi Block Replication Configuration Wizard

This wizard is displayed when you assign a replication operation to a Hitachi Block Device node on a data flow.

CautionWhen a replication operation runs, Protector locks the meta_resource of the Block Device until the operation completes. Block operations are queued waiting to get the resource lock; this can impact RPO.

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.

Note

• The classifications that are applicable to Hitachi Block Replication operations are File Path, Application, Hypervisor and Hitachi Block LDEV.
• Protector does not support any Hitachi Block storage LDEV with more than one partition or volume.
• If Protector is subsequently uninstalled, the existing replications and mounted volumes are left in place.

NoteProtector will attempt to match destination LDEV IDs with those used by the source (except for in-system SI and RTI replications where this is impossible). The LDEV ID must be within the range configured for the target storage system and the LDEV ID must not be in use. If the LDEV ID cannot be matched on the target then the first available in-range LDEV ID will be selected.

Note

Once the operation properties have been configured and the data flow has been activated, the properties cannot be changed. Reactivating rules for the active data flow with edited properties will not change them.

To change the operation properties, the existing data flow must first be deactivated then reactivated with the new properties. Deactivating the data flow will tear down the current replication.

Tip

• The actions that are performed by hardware orchestration as it executes a block backup policy are captured by the Log Manager. Detailed logs and their attachments can be exported as a text file. (See Export Logs Dialog for more information.)
• Details of the hardware resources (LDEVs) used for a particular replication can be found in the Hitachi Block Device Details.

Control	Description
Configure new replication	Creates a new replication defined by the user defined parameters. The Configure New Replication page of the wizard is displayed next.
Adopt existing replication	Adopts the replication defined by the user defined parameters from the matching pre-existing one on the hardware. The Adopt Existing Replication page of the wizard is displayed next.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

NoteTo change the Create / Adopt configuration of an existing dataflow it is necessary to deactivate the dataflow, dissociate the replication record, then edit the dataflow to create/adopt and then activate the dataflow.

Control	Description
Replication Type	Select the type of replication to create: In System Clone - opens the Replication Configuration Wizard - In-System Clone. Refreshed Snapshot - opens the Replication Configuration Wizard - Refreshed Snapshot. Asynchronous Remote Clone - opens the Replication Configuration Wizard - Asynchronous Remote Clone. Asynchronous Remote Failover - opens the Replication Configuration Wizard - Asynchronous Remote Failover. Synchronous Remote Clone - opens the Replication Configuration Wizard - Synchronous Remote Clone. Active-Active Remote Clone - opens the Replication Configuration Wizard - Active-Active Remote Clone.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

NoteAdoption requires the rules to be activated and the relevant policy to be triggered. Refer to About Hitachi Block replication adoption before using this feature.

Control	Description
Replication Type	Select the type of replication to adopt: In System Clone - see About ShadowImage replication Refreshed Snapshot - see About Thin Image differential and refreshed snapshots Asynchronous Remote Clone - see About Universal Replicator Asynchronous Remote Failover - see About three datacentre multi-target with delta Synchronous Remote Clone - see About TrueCopy replication Active-Active Remote Clone - see About Global-Active Device replication
Mirror Unit	Identify the mirror unit number of the replication to be adopted. Adoption requires at least one existing pair on the selected mirror unit. NoteIf the mirror unit of an active replication is changed after initial data flow activation then: S-VOLs and pairing relationships for the replication will be destroyed (or dissociated if previously adopted). The replication will then be recreated (or readopted if previously adopted) on data flow reactivation. A warning is issued by the rules compiler prior to activation.
Copy Pace	Determines how quickly the storage array will be told to copy data for the adopted replication. The array’s default is Slow (3), Protector defaults to Medium (8).
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Shows a summary of the replication configuration specified by the user. All other parameters defining the replication are obtained from the hardware when the data flow is activated and triggered.

Parent Topic

• Data Flow Wizard

Child Topics

• Replication Configuration Wizard - In-System Clone
• Replication Configuration Wizard - Refreshed Snapshot
• Replication Configuration Wizard - Asynchronous Remote Clone
• Replication Configuration Wizard - Asynchronous Remote Failover
• Replication Configuration Wizard - Synchronous Remote Clone
• Replication Configuration Wizard - Active-Active Remote Clone

Replication Configuration Wizard - In-System Clone

Control	Description
Capacity Saving Mode	One of the following options: Match Source Volumes – When provisioning S-VOLs Capacity Saving will match the settings of the source volumed. Compression - When provisioning S-VOLs Compression will be enabled, the data compression function utilizes the LZ4 compression algorithm to compress the data. Deduplication and Compression - When provisioning S-VOLs Deduplication and Compression will be enabled. The data deduplication function deletes duplicate copies of data written to different addresses in the same pool and maintains only a single copy of the data at one address. None - When provisioning S-VOLs Capacity Saving will not be used
Capacity Saving Process Mode	Only available when a Capacity Saving Mode other than None is selected. Can be one of the following: Inline - When you apply capacity saving with the inline mode the compression and deduplication processing are performed synchronously for new write data. The inline mode minimizes the pool capacity required to store new write data but can impact I/O performance more than the post-process mode. Post Process - When you apply capacity saving with the post-process mode the compression and deduplication processing are performed asynchronously for new write data. Storage Default – match the default option set on the storage array. Match Source Volume – match the settings of the source volume.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Pool	Specifies the target storage pool from which replication LDEVs are allocated. Provides a list of available pools giving name and available space. NoteAll replication types have pool except Asynchronous Remote Failover (Universal Replicator). Select a Dynamic Provisioning Pool for all replication types. NoteDynamic Provisioning Pools must be created using Storage Navigator prior to selecting the Target Storage/Pool in Protector.
Mirror Unit	The mirror unit number for the replication can be set to 0, 1 or 2. Select Allocate Automatically to allow Protector to choose one. NoteIf the mirror unit of an active replication is changed after initial data flow activation then: S-VOLs and pairing relationships for the replication will be destroyed (or dissociated if previously adopted). The replication will then be recreated (or readopted if previously adopted) on data flow reactivation. A warning is issued by the rules compiler prior to activation.
Copy Pace	Determines how quickly the storage array copies data. The array’s default is Slow (3), Protector defaults to Medium (8).
Use Consistency Group	All P-VOLs in a replication are, by default, placed in the same consistency group to ensure consistency of data across all volumes. This option allows this behavior to be disabled.
Quick Resync/Split	If selected, then Quick Split and Quick Resynch operations are performed by the storage hardware in the background, so that the secondary is available for reading/writing almost immediately after the replication is paused or resynchronized (depending on downstream data flow operations). If deselected then Steady Split and Normal Copy operations are performed in the foreground and the secondary is made available only once the operation is completed.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Configure Resource Group	Specifies the resource group to be used for S-VOLs, in order to support snapshots and replications from VSM volumes (adding volumes to a VSM is performed by adding the volumes to the correct resource group). NoteIf there are existing S-VOLs, then the resource group used by those will be selected. If the existing S-VOLs are in multiple resource groups or in a resource group that contradicts the user selection, then the operation will fail with an error. This setting should not be modified for existing replications. Automatically Selected - Allows Protector to automatically select a resource group in the following order of priority: If there are existing S-VOLs, then the resource group used by those will be selected. The resource group used by the P-VOLs, if the replication is in-system and the P-VOLs are all in one resource group. Resource group 0. NoteIf existing S-VOLs are in multiple resource groups, then the operation will fail with an error. User Selected - The user specifies the Resource Group.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Secondary Logical Device Name	Specifies how S-VOLs will be named: Match Origin - The S-VOL will be given the same name as that used for the origin P-VOL (i.e. the left-most volume in the data flow). Custom - The S-VOL will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the secondary LDEVs' name to view the available substitution variables: %ORIGIN_SERIAL% - S/N of leftmost array in data flow. E.g. output string: 210613 %ORIGIN_LDEV_ID% - ID of leftmost LDEV in data flow. E.g. output string: 00:3A:98 %ORIGIN_LDEV_NAME% - name of leftmost LDEV in data flow. %PRIMARY_SERIAL% - S/N of primary array in this operation. E.g. output string: 442302 %PRIMARY_LDEV_ID% - ID of primary LDEV in this operation. E.g. output string: 00:4C:EB %PRIMARY_LDEV_NAME% - name of primary LDEV in this operation. %SECONDARY_SERIAL% - S/N of secondary array in this operation. E.g. output string: 356323 %SECONDARY_LDEV_ID% - ID of secondary LDEV in this operation. E.g. output string: 01:F4:35 %CREATION_DATE% - date secondary LDEV was created by this operation. E.g. output string: 20180427 %CREATION_TIME% - time secondary LDEV was created by this operation. 1130
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Shows a summary of the replication configuration specified by the user.

Parent Topic

• Hitachi Block Replication Configuration Wizard

Replication Configuration Wizard - Refreshed Snapshot

NoteRefreshed Thin Image must be used with a Batch mover on the data flow.

The replication is created as a single, differential, in-system snapshot using Thin Image. The snapshot is refreshed on each batch resync rather than creating a new snapshot for each resync.

When an RTI data flow is deactivated, the refreshed snapshot is deleted.

Control	Description
Pool	Specifies the target storage pool from which replication LDEVs are allocated. Provides a list of available pools giving name and available space. NoteAll replication types have pool except Asynchronous Remote Failover (Universal Replicator). Select a Thin Image Pool or a Dynamic Provisioning Pool. NoteThin Image and Dynamic Provisioning Pools must be created using Storage Navigator prior to selecting the Target Storage/Pool in Protector.
Use Consistency Group	All P-VOLs in a replication are, by default, placed in the same consistency group to ensure consistency of data across all volumes. This option allows this behavior to be disabled.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Configure Resource Group	Specifies the resource group to be used for S-VOLs, in order to support snapshots and replications from VSM volumes (adding volumes to a VSM is performed by adding the volumes to the correct resource group). NoteIf there are existing S-VOLs, then the resource group used by those will be selected. If the existing S-VOLs are in multiple resource groups or in a resource group that contradicts the user selection, then the operation will fail with an error. This setting should not be modified for existing replications. Automatically Selected - Allows Protector to automatically select a resource group in the following order of priority: If there are existing S-VOLs, then the resource group used by those will be selected. The resource group used by the P-VOLs, if the replication is in-system and the P-VOLs are all in one resource group. Resource group 0. NoteIf existing S-VOLs are in multiple resource groups, then the operation will fail with an error. User Selected - The user specifies the Resource Group.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Secondary Logical Device Name	Specifies how S-VOLs will be named: Match Origin - The S-VOL will be given the same name as that used for the origin P-VOL (i.e. the left-most volume in the data flow). Custom - The S-VOL will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the secondary LDEVs' name to view the available substitution variables: %ORIGIN_SERIAL% - S/N of leftmost array in data flow. E.g. output string: 210613 %ORIGIN_LDEV_ID% - ID of leftmost LDEV in data flow. E.g. output string: 00:3A:98 %ORIGIN_LDEV_NAME% - name of leftmost LDEV in data flow. %PRIMARY_SERIAL% - S/N of primary array in this operation. E.g. output string: 442302 %PRIMARY_LDEV_ID% - ID of primary LDEV in this operation. E.g. output string: 00:4C:EB %PRIMARY_LDEV_NAME% - name of primary LDEV in this operation. %SECONDARY_SERIAL% - S/N of secondary array in this operation. E.g. output string: 356323 %SECONDARY_LDEV_ID% - ID of secondary LDEV in this operation. E.g. output string: 01:F4:35 %CREATION_DATE% - date secondary LDEV was created by this operation. E.g. output string: 20180427 %CREATION_TIME% - time secondary LDEV was created by this operation. 1130
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control

Description

Snapshot Group Name

Specifies how the snapshot group will be named. Automatically Generated - The snapshot group name is generated by Protector based on the rules context ID and policy name. Custom - The snapshot group is named using the string provided (limited to 28 characters). An '@' separator followed by a unique ID is then automatically appended to this name. The unique ID is composed of 3 base 36 characters and is required to enable Protector to manage the groups.

Shows a summary of the replication configuration specified by the user.

Parent Topic

• Hitachi Block Replication Configuration Wizard

Replication Configuration Wizard - Asynchronous Remote Clone

Control	Description
Capacity Saving Mode	One of the following options: Match Source Volumes – When provisioning S-VOLs Capacity Saving will match the settings of the source volumed. Compression - When provisioning S-VOLs Compression will be enabled, the data compression function utilizes the LZ4 compression algorithm to compress the data. Deduplication and Compression - When provisioning S-VOLs Deduplication and Compression will be enabled. The data deduplication function deletes duplicate copies of data written to different addresses in the same pool and maintains only a single copy of the data at one address. None - When provisioning S-VOLs Capacity Saving will not be used
Capacity Saving Process Mode	Only available when a Capacity Saving Mode other than None is selected. Can be one of the following: Inline - When you apply capacity saving with the inline mode the compression and deduplication processing are performed synchronously for new write data. The inline mode minimizes the pool capacity required to store new write data but can impact I/O performance more than the post-process mode. Post Process - When you apply capacity saving with the post-process mode the compression and deduplication processing are performed asynchronously for new write data. Storage Default – match the default option set on the storage array. Match Source Volume – match the settings of the source volume.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Pool	Specifies the target storage pool from which replication LDEVs are allocated. Provides a list of available pools giving name and available space. NoteAll replication types have pool except Asynchronous Remote Failover (Universal Replicator). Select a Dynamic Provisioning Pool. NoteDynamic Provisioning Pools must be created using Storage Navigator prior to selecting the Target Storage/Pool in Protector.
Mirror Unit	The mirror unit number for the replication can be set to 0, h1, h2 or h3. Select Allocate Automatically to allow Protector to choose one. NoteIf the mirror unit of an active replication is changed after initial data flow activation then: S-VOLs and pairing relationships for the replication will be destroyed (or dissociated if previously adopted). The replication will then be recreated (or readopted if previously adopted) on data flow reactivation. A warning is issued by the rules compiler prior to activation.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Select existing journals	Select this option to use journals that already exist on the source and destination storage arrays. The Select existing journals wizard page is displayed next.
Create new journals	Select this option to have Protector configure new journals on the source and destination storage arrays. The Create journals wizard page is displayed next.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

NoteThe journals must be unique to each operation and policy in the data flow. The journal should also be used exclusively by Protector.

Control	Description
Source Journal	Specifies the node and journal on the source side of the replication.
Destination Journal	Specifies the journal on the destination side of the replication.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

NoteThe journals must be unique to each operation and policy in the data flow. The journal should also be used exclusively by Protector.

Control	Description
Source Journal Pool	Specifies the node and pool where the source side journal will be created.
Destination Journal Pool	Specifies the pool where the destination side journal will be created.
Journal Sizes	Specifies the size of the source and destination journal. NoteJournal sizing is based on data change rate and link bandwidth. Refer to your storage array documentation for details.
Journal Names	The journals will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the journal name to view the available substitution variables.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Select Remote Path Group	Specifies the Remote Path Group to be used for the replication. Automatically Selected - Allows Protector to automatically select a Remote Path Group NoteFor GAD it is recommended the user specifies a group to avoid sharing with other replications. User Selected - The user specifies the Remote Path Group. WARNINGYou cannot specify the "User Selected" option and select a path group with an ID of 0. To use a path group with an ID of 0, specify the "Automatically Selected" option. The path group with the lowest ID will be selected (which will be ID 0, if a path group with that ID exists). Remote path groups are listed in the format: Path Group Id: 0x51 Port Mappings: 5E <-> 3E The arrow depicts the direction of the path, either left to right or bidirectional. The arrows can also have a line through them depicting the path is currently broken. Only remote path groups that are suitable for the replication are displayed, for example for GAD only bidirectional path groups are listed.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Configure Resource Group	Specifies the resource group to be used for S-VOLs, in order to support snapshots and replications from VSM volumes (adding volumes to a VSM is performed by adding the volumes to the correct resource group). NoteIf there are existing S-VOLs, then the resource group used by those will be selected. If the existing S-VOLs are in multiple resource groups or in a resource group that contradicts the user selection, then the operation will fail with an error. This setting should not be modified for existing replications. Automatically Selected - Allows Protector to automatically select a resource group in the following order of priority: If there are existing S-VOLs, then the resource group used by those will be selected. The resource group used by the P-VOLs, if the replication is in-system and the P-VOLs are all in one resource group. Resource group 0. NoteIf existing S-VOLs are in multiple resource groups, then the operation will fail with an error. User Selected - The user specifies the Resource Group.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

CautionIf replication S-VOLs are exposed to a host, the user is responsible for ensuring they are not in use during replication resynchronization. Failing to do so may result in a critical failure of the host.

NoteProtector analyses the LUN IDs of the P-VOLs in all host group paths and, if consistent and available, uses these LUN IDs for all S-VOL host group paths either during initial set-up, mounting, or when adding additional LUNs on demand.

To provide a graceful fallback:

• If the P-VOL LUN IDs are not consistent in all host group paths Protector will still use a consistent ID for S-VOL mappings, but these will not necessarily match any of the P-VOL LUN IDs.
• If a P-VOL has a consistent ID in all host group paths, but this LUN ID is not available in all S-VOL host group paths then Protector will choose a different, consistent LUN ID for the S-VOL for all host group paths.
• When not able to match LUN IDs with those used by P-VOLs and/or the S-VOLs, Protector chooses an unused LUN ID. In order to keep LUN ID’s compatible with VMware and Hyper-V when selecting LUN ID’s Protector will first attempt to select ID’s at or below 255. If this is not it will then attempt at or below 1024, followed by at or below 2048. Finally, at or below the array maximum. A warning will be displayed when an ID can not be found in a range.

Some systems expect LUN ID 0 to be used only as a boot volume. Protector will therefore only use LUN ID 0 for the S-VOL host group paths if the P-VOL LUN ID is 0.

Control	Description
Use Protector Provisioned Host Group	Protector will create a LUN path from each S-VOL it provisions in a placeholder host group. If this option is not selected, at least one Secondary Host Group must be specified below.
Enforce LUN ID Matching	For environments where LUN ID consistency is mandatory, selecting this option will cause the replication to fail if: The P-VOL does not have a consistent LUN ID in all host group paths. The P-VOL LUN ID is not available in all S-VOL host group paths.
Secondary Host Groups	Specify zero or more host groups that Protector will configure to provide access to the S-VOL(s) when configuring replication scenarios. If no host groups are specified here then Protector will place the S-VOL(s) in it's dummy host group. 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. TipUse this option to specify host groups that enable access to S-VOL(s) when configuring GAD cross-path and multi-path and other replication scenarios where the S-VOL(s) will need to be accessed (e.g. during failover).
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Secondary Logical Device Name	Specifies how S-VOLs will be named: Match Origin - The S-VOL will be given the same name as that used for the origin P-VOL (i.e. the left-most volume in the data flow). Custom - The S-VOL will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the secondary LDEVs' name to view the available substitution variables: %ORIGIN_SERIAL% - S/N of leftmost array in data flow. E.g. output string: 210613 %ORIGIN_LDEV_ID% - ID of leftmost LDEV in data flow. E.g. output string: 00:3A:98 %ORIGIN_LDEV_NAME% - name of leftmost LDEV in data flow. %PRIMARY_SERIAL% - S/N of primary array in this operation. E.g. output string: 442302 %PRIMARY_LDEV_ID% - ID of primary LDEV in this operation. E.g. output string: 00:4C:EB %PRIMARY_LDEV_NAME% - name of primary LDEV in this operation. %SECONDARY_SERIAL% - S/N of secondary array in this operation. E.g. output string: 356323 %SECONDARY_LDEV_ID% - ID of secondary LDEV in this operation. E.g. output string: 01:F4:35 %CREATION_DATE% - date secondary LDEV was created by this operation. E.g. output string: 20180427 %CREATION_TIME% - time secondary LDEV was created by this operation. 1130
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Shows a summary of the replication configuration specified by the user.

Parent Topic

• Hitachi Block Replication Configuration Wizard

Replication Configuration Wizard - Asynchronous Remote Failover

Control	Description
Capacity Saving Mode	One of the following options: Match Source Volumes – When provisioning S-VOLs Capacity Saving will match the settings of the source volumed. Compression - When provisioning S-VOLs Compression will be enabled, the data compression function utilizes the LZ4 compression algorithm to compress the data. Deduplication and Compression - When provisioning S-VOLs Deduplication and Compression will be enabled. The data deduplication function deletes duplicate copies of data written to different addresses in the same pool and maintains only a single copy of the data at one address. None - When provisioning S-VOLs Capacity Saving will not be used
Capacity Saving Process Mode	Only available when a Capacity Saving Mode other than None is selected. Can be one of the following: Inline - When you apply capacity saving with the inline mode the compression and deduplication processing are performed synchronously for new write data. The inline mode minimizes the pool capacity required to store new write data but can impact I/O performance more than the post-process mode. Post Process - When you apply capacity saving with the post-process mode the compression and deduplication processing are performed asynchronously for new write data. Storage Default – match the default option set on the storage array. Match Source Volume – match the settings of the source volume.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Mirror Unit	The mirror unit number for the replication can be set to 0, h1, h2 or h3. Select Allocate Automatically to allow Protector to choose one. NoteIf the mirror unit of an active replication is changed after initial data flow activation then: S-VOLs and pairing relationships for the replication will be destroyed (or dissociated if previously adopted). The replication will then be recreated (or readopted if previously adopted) on data flow reactivation. A warning is issued by the rules compiler prior to activation.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Select existing journals	Select this option to use journals that already exist on the source and destination storage arrays. The Select existing journals wizard page is displayed next.
Create new journals	Selecf this option to have Protector configure new journals on the sournce and destination storage arrays. The Create journals wizard page is displayed next.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

NoteThe journal must be unique to each operation and policy in the data flow. The journal should also be used exclusively by Protector.

Control	Description
Source Journal	Specifies the node and journal on the source side of the replication.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

NoteThe journal must be unique to each operation and policy in the data flow. The journal should also be used exclusively by Protector.

Control	Description
Source Journal Pool	Specifies the node and pool where the source side journal will be created.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Select Remote Path Group	Specifies the Remote Path Group to be used for the replication. Automatically Selected - Allows Protector to automatically select a Remote Path Group NoteFor GAD it is recommended the user specifies a group to avoid sharing with other replications. User Selected - The user specifies the Remote Path Group. WARNINGYou cannot specify the "User Selected" option and select a path group with an ID of 0. To use a path group with an ID of 0, specify the "Automatically Selected" option. The path group with the lowest ID will be selected (which will be ID 0, if a path group with that ID exists). Remote path groups are listed in the format: Path Group Id: 0x51 Port Mappings: 5E <-> 3E The arrow depicts the direction of the path, either left to right or bidirectional. The arrows can also have a line through them depicting the path is currently broken. Only remote path groups that are suitable for the replication are displayed, for example for GAD only bidirectional path groups are listed.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Secondary Logical Device Name	Specifies how S-VOLs will be named: Match Origin - The S-VOL will be given the same name as that used for the origin P-VOL (i.e. the left-most volume in the data flow). Custom - The S-VOL will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the secondary LDEVs' name to view the available substitution variables: %ORIGIN_SERIAL% - S/N of leftmost array in data flow. E.g. output string: 210613 %ORIGIN_LDEV_ID% - ID of leftmost LDEV in data flow. E.g. output string: 00:3A:98 %ORIGIN_LDEV_NAME% - name of leftmost LDEV in data flow. %PRIMARY_SERIAL% - S/N of primary array in this operation. E.g. output string: 442302 %PRIMARY_LDEV_ID% - ID of primary LDEV in this operation. E.g. output string: 00:4C:EB %PRIMARY_LDEV_NAME% - name of primary LDEV in this operation. %SECONDARY_SERIAL% - S/N of secondary array in this operation. E.g. output string: 356323 %SECONDARY_LDEV_ID% - ID of secondary LDEV in this operation. E.g. output string: 01:F4:35 %CREATION_DATE% - date secondary LDEV was created by this operation. E.g. output string: 20180427 %CREATION_TIME% - time secondary LDEV was created by this operation. 1130
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Shows a summary of the replication configuration specified by the user.

Parent Topic

• Hitachi Block Replication Configuration Wizard

Replication Configuration Wizard - Synchronous Remote Clone

Control	Description
Capacity Saving Mode	One of the following options: Match Source Volumes – When provisioning S-VOLs Capacity Saving will match the settings of the source volumed. Compression - When provisioning S-VOLs Compression will be enabled, the data compression function utilizes the LZ4 compression algorithm to compress the data. Deduplication and Compression - When provisioning S-VOLs Deduplication and Compression will be enabled. The data deduplication function deletes duplicate copies of data written to different addresses in the same pool and maintains only a single copy of the data at one address. None - When provisioning S-VOLs Capacity Saving will not be used
Capacity Saving Process Mode	Only available when a Capacity Saving Mode other than None is selected. Can be one of the following: Inline - When you apply capacity saving with the inline mode the compression and deduplication processing are performed synchronously for new write data. The inline mode minimizes the pool capacity required to store new write data but can impact I/O performance more than the post-process mode. Post Process - When you apply capacity saving with the post-process mode the compression and deduplication processing are performed asynchronously for new write data. Storage Default – match the default option set on the storage array. Match Source Volume – match the settings of the source volume.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Pool	Specifies the target storage pool from which replication LDEVs are allocated. Provides a list of available pools giving name and available space. NoteAll replication types have pool except Asynchronous Remote Failover (Universal Replicator). Select a Dynamic Provisioning Pool. NoteDynamic Provisioning Pools must be created using Storage Navigator prior to selecting the Target Storage/Pool in Protector.
Ignore	When writing to the primary volumes, confirm the write regardless of whether the data has been copied successfully to secondary volumes (Fence Level Never) .
Fail source write	Only confirm primary volume writes if the data is successfully copied to the secondary volume, generate a write error if not (Fence Level Data).
Fail source write if not in error status	Only generate a write error if the data is not successfully copied to the secondary volume and the replication has not been put into an error status PSUE (Fence Level Status).
Copy Pace	Determines how quickly the storage array copies data. The array’s default is Slow (3), Protector defaults to Medium (8).
Use Consistency Group	All P-VOLs in a replication are, by default, placed in the same consistency group to ensure consistency of data across all volumes. This option allows this behaviour to be disabled.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Select Remote Path Group	Specifies the Remote Path Group to be used for the replication. Automatically Selected - Allows Protector to automatically select a Remote Path Group NoteFor GAD it is recommended the user specifies a group to avoid sharing with other replications. User Selected - The user specifies the Remote Path Group. WARNINGYou cannot specify the "User Selected" option and select a path group with an ID of 0. To use a path group with an ID of 0, specify the "Automatically Selected" option. The path group with the lowest ID will be selected (which will be ID 0, if a path group with that ID exists). Remote path groups are listed in the format: Path Group Id: 0x51 Port Mappings: 5E <-> 3E The arrow depicts the direction of the path, either left to right or bidirectional. The arrows can also have a line through them depicting the path is currently broken. Only remote path groups that are suitable for the replication are displayed, for example for GAD only bidirectional path groups are listed.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Configure Resource Group	Specifies the resource group to be used for S-VOLs, in order to support snapshots and replications from VSM volumes (adding volumes to a VSM is performed by adding the volumes to the correct resource group). NoteIf there are existing S-VOLs, then the resource group used by those will be selected. If the existing S-VOLs are in multiple resource groups or in a resource group that contradicts the user selection, then the operation will fail with an error. This setting should not be modified for existing replications. Automatically Selected - Allows Protector to automatically select a resource group in the following order of priority: If there are existing S-VOLs, then the resource group used by those will be selected. The resource group used by the P-VOLs, if the replication is in-system and the P-VOLs are all in one resource group. Resource group 0. NoteIf existing S-VOLs are in multiple resource groups, then the operation will fail with an error. User Selected - The user specifies the Resource Group.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

CautionIf replication S-VOLs are exposed to a host, the user is responsible for ensuring they are not in use during replication resynchronization. Failing to do so may result in a critical failure of the host.

NoteProtector analyses the LUN IDs of the P-VOLs in all host group paths and, if consistent and available, uses these LUN IDs for all S-VOL host group paths either during initial set-up, mounting, or when adding additional LUNs on demand.

To provide a graceful fallback:

• If the P-VOL LUN IDs are not consistent in all host group paths Protector will still use a consistent ID for S-VOL mappings, but these will not necessarily match any of the P-VOL LUN IDs.
• If a P-VOL has a consistent ID in all host group paths, but this LUN ID is not available in all S-VOL host group paths then Protector will choose a different, consistent LUN ID for the S-VOL for all host group paths.
• When not able to match LUN IDs with those used by P-VOLs and/or the S-VOLs, Protector chooses an unused LUN ID. In order to keep LUN ID’s compatible with VMware and Hyper-V when selecting LUN ID’s Protector will first attempt to select ID’s at or below 255. If this is not it will then attempt at or below 1024, followed by at or below 2048. Finally, at or below the array maximum. A warning will be displayed when an ID can not be found in a range.

Some systems expect LUN ID 0 to be used only as a boot volume. Protector will therefore only use LUN ID 0 for the S-VOL host group paths if the P-VOL LUN ID is 0.

Control	Description
Use Protector Provisioned Host Group	Protector will create a LUN path from each S-VOL it provisions in a placeholder host group. If this option is not selected, at least one Secondary Host Group must be specified below.
Enforce LUN ID Matching	For environments where LUN ID consistency is mandatory, selecting this option will cause the replication to fail if: The P-VOL does not have a consistent LUN ID in all host group paths. The P-VOL LUN ID is not available in all S-VOL host group paths.
Secondary Host Groups	Specify zero or more host groups that Protector will configure to provide access to the S-VOL(s) when configuring replication scenarios. If no host groups are specified here then Protector will place the S-VOL(s) in it's dummy host group. 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. TipUse this option to specify host groups that enable access to S-VOL(s) when configuring GAD cross-path and multi-path and other replication scenarios where the S-VOL(s) will need to be accessed (e.g. during failover).
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Secondary Logical Device Name	Specifies how S-VOLs will be named: Match Origin - The S-VOL will be given the same name as that used for the origin P-VOL (i.e. the left-most volume in the data flow). Custom - The S-VOL will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the secondary LDEVs' name to view the available substitution variables: %ORIGIN_SERIAL% - S/N of leftmost array in data flow. E.g. output string: 210613 %ORIGIN_LDEV_ID% - ID of leftmost LDEV in data flow. E.g. output string: 00:3A:98 %ORIGIN_LDEV_NAME% - name of leftmost LDEV in data flow. %PRIMARY_SERIAL% - S/N of primary array in this operation. E.g. output string: 442302 %PRIMARY_LDEV_ID% - ID of primary LDEV in this operation. E.g. output string: 00:4C:EB %PRIMARY_LDEV_NAME% - name of primary LDEV in this operation. %SECONDARY_SERIAL% - S/N of secondary array in this operation. E.g. output string: 356323 %SECONDARY_LDEV_ID% - ID of secondary LDEV in this operation. E.g. output string: 01:F4:35 %CREATION_DATE% - date secondary LDEV was created by this operation. E.g. output string: 20180427 %CREATION_TIME% - time secondary LDEV was created by this operation. 1130
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Shows a summary of the replication configuration specified by the user.

Parent Topic

• Hitachi Block Replication Configuration Wizard

Replication Configuration Wizard - Active-Active Remote Clone

Note

• GAD is only available on VSP G series because virtualized LDEVs are required.
• Configuration or adoption of GAD cross-path scenarios requires CCI version 01-41-03/03 or greater to be installed on the ISM node.
• Primary volumes must be set up within a host group prior to configuring a GAD replication using Protector.
• GAD replications require the P-VOL and S-VOL to have matching virtual serial numbers and virtual LDEV IDs. Selecting Automatically Selected in the Configure Resource Group page of the wizard ensures this is done.
• Any LUN path to the secondary volume will become inaccessible if the GAD replication is deleted from Protector (i.e. torn down). This occurs because the virtual LDEV ID is automatically deleted from the S-VOL, causing host I/Os to be rejected. To recover from this, either recreate the GAD pair (if the pair was deleted unintentionally) or assign a new virtual ID to the clone S-VOL

Control	Description
Capacity Saving Mode	One of the following options: Match Source Volumes – When provisioning S-VOLs Capacity Saving will match the settings of the source volumed. Compression - When provisioning S-VOLs Compression will be enabled, the data compression function utilizes the LZ4 compression algorithm to compress the data. Deduplication and Compression - When provisioning S-VOLs Deduplication and Compression will be enabled. The data deduplication function deletes duplicate copies of data written to different addresses in the same pool and maintains only a single copy of the data at one address. None - When provisioning S-VOLs Capacity Saving will not be used
Capacity Saving Process Mode	Only available when a Capacity Saving Mode other than None is selected. Can be one of the following: Inline - When you apply capacity saving with the inline mode the compression and deduplication processing are performed synchronously for new write data. The inline mode minimizes the pool capacity required to store new write data but can impact I/O performance more than the post-process mode. Post Process - When you apply capacity saving with the post-process mode the compression and deduplication processing are performed asynchronously for new write data. Storage Default – match the default option set on the storage array. Match Source Volume – match the settings of the source volume.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Pool	Specifies the target storage pool from which replication LDEVs are allocated. Provides a list of available pools giving name and available space. NoteAll replication types have pool except Asynchronous Remote Failover (Universal Replicator). Select a Dynamic Provisioning Pool. NoteDynamic Provisioning Pools must be created using Storage Navigator prior to selecting the Target Storage/Pool in Protector.
Target Quorum	Selects the volume to use as the quorum disk. Note A Quorum disk is required to manage each GAD replication pair. It is best practice to allocate a separate Quorum disk for each pair. Both Quorum and Quorum-less disks are available for selection.
Mirror Unit	The mirror unit number for the replication can be set to 0 or h1. Select Allocate Automatically to allow Protector to choose one.
Copy Pace	Determines how quickly the storage array copies data. The array’s default is Slow (3), Protector defaults to Medium (8).
Use Consistency Group	All P-VOLs in a replication are, by default, placed in the same consistency group to ensure consistency of data across all volumes. This option allows this behavior to be disabled.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Select Remote Path Group	Specifies the Remote Path Group to be used for the replication. Automatically Selected - Allows Protector to automatically select a Remote Path Group NoteFor GAD it is recommended the user specifies a group to avoid sharing with other replications. User Selected - The user specifies the Remote Path Group. WARNINGYou cannot specify the "User Selected" option and select a path group with an ID of 0. To use a path group with an ID of 0, specify the "Automatically Selected" option. The path group with the lowest ID will be selected (which will be ID 0, if a path group with that ID exists). Remote path groups are listed in the format: Path Group Id: 0x51 Port Mappings: 5E <-> 3E The arrow depicts the direction of the path, either left to right or bidirectional. The arrows can also have a line through them depicting the path is currently broken. Only remote path groups that are suitable for the replication are displayed, for example for GAD only bidirectional path groups are listed.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Configure Resource Group	Specifies the resource group to be used for S-VOLs, in order to support snapshots and replications from VSM volumes (adding volumes to a VSM is performed by adding the volumes to the correct resource group). NoteIf there are existing S-VOLs, then the resource group used by those will be selected. If the existing S-VOLs are in multiple resource groups or in a resource group that contradicts the user selection, then the operation will fail with an error. This setting should not be modified for existing replications. Automatically Selected - Allows Protector to automatically select a resource group in the following order of priority: If there are existing S-VOLs, then the resource group used by those will be selected. The resource group used by the P-VOLs, if the replication is in-system and the P-VOLs are all in one resource group. Resource group 0. NoteIf existing S-VOLs are in multiple resource groups, then the operation will fail with an error. User Selected - The user specifies the Resource Group.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

CautionIf replication S-VOLs are exposed to a host, the user is responsible for ensuring they are not in use during replication resynchronization. Failing to do so may result in a critical failure of the host.

NoteProtector analyses the LUN IDs of the P-VOLs in all host group paths and, if consistent and available, uses these LUN IDs for all S-VOL host group paths either during initial set-up, mounting, or when adding additional LUNs on demand.

To provide a graceful fallback:

• If the P-VOL LUN IDs are not consistent in all host group paths Protector will still use a consistent ID for S-VOL mappings, but these will not necessarily match any of the P-VOL LUN IDs.
• If a P-VOL has a consistent ID in all host group paths, but this LUN ID is not available in all S-VOL host group paths then Protector will choose a different, consistent LUN ID for the S-VOL for all host group paths.
• When not able to match LUN IDs with those used by P-VOLs and/or the S-VOLs, Protector chooses an unused LUN ID. In order to keep LUN ID’s compatible with VMware and Hyper-V when selecting LUN ID’s Protector will first attempt to select ID’s at or below 255. If this is not it will then attempt at or below 1024, followed by at or below 2048. Finally, at or below the array maximum. A warning will be displayed when an ID can not be found in a range.

Some systems expect LUN ID 0 to be used only as a boot volume. Protector will therefore only use LUN ID 0 for the S-VOL host group paths if the P-VOL LUN ID is 0.

Control	Description
Use Protector Provisioned Host Group	Protector will create a LUN path from each S-VOL it provisions in a placeholder host group. If this option is not selected, at least one Secondary Host Group must be specified below.
Enforce LUN ID Matching	For environments where LUN ID consistency is mandatory, selecting this option will cause the replication to fail if: The P-VOL does not have a consistent LUN ID in all host group paths. The P-VOL LUN ID is not available in all S-VOL host group paths.
Secondary Host Groups	Specify zero or more host groups that Protector will configure to provide access to the S-VOL(s) when configuring replication scenarios. If no host groups are specified here then Protector will place the S-VOL(s) in it's dummy host group. 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. TipUse this option to specify host groups that enable access to S-VOL(s) when configuring GAD cross-path and multi-path and other replication scenarios where the S-VOL(s) will need to be accessed (e.g. during failover).
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Secondary Logical Device Name	Specifies how S-VOLs will be named: Match Origin - The S-VOL will be given the same name as that used for the origin P-VOL (i.e. the left-most volume in the data flow). Custom - The S-VOL will be named using the naming rule provided. The naming rule can consist of literal strings and/or one or more substitution variables listed. Click Display variables which can be used for the secondary LDEVs' name to view the available substitution variables: %ORIGIN_SERIAL% - S/N of leftmost array in data flow. E.g. output string: 210613 %ORIGIN_LDEV_ID% - ID of leftmost LDEV in data flow. E.g. output string: 00:3A:98 %ORIGIN_LDEV_NAME% - name of leftmost LDEV in data flow. %PRIMARY_SERIAL% - S/N of primary array in this operation. E.g. output string: 442302 %PRIMARY_LDEV_ID% - ID of primary LDEV in this operation. E.g. output string: 00:4C:EB %PRIMARY_LDEV_NAME% - name of primary LDEV in this operation. %SECONDARY_SERIAL% - S/N of secondary array in this operation. E.g. output string: 356323 %SECONDARY_LDEV_ID% - ID of secondary LDEV in this operation. E.g. output string: 01:F4:35 %CREATION_DATE% - date secondary LDEV was created by this operation. E.g. output string: 20180427 %CREATION_TIME% - time secondary LDEV was created by this operation. 1130
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Shows a summary of the replication configuration specified by the user.

Parent Topic

• Hitachi Block Replication Configuration Wizard

Hitachi Block Mount Configuration Wizard

This wizard is displayed when you assign a mount operation to a Hitachi Block storage node on a data flow.

Note

• When mounting a snapshot that contains a mounted subdirectory, the subdirectory will be mounted as expected. However, the volume referenced by the subdirectory will also be mounted as a separate drive. Unmount will unmount both the expected and additional mounts.
• The automated mount operation is not suitable for Oracle ASM. The disks are be presented to the OS but need to be manually mounted.

NoteOperating system specific behaviour:

OS	Note
Linux	When mounting a Linux snapshot to a different Linux machine; in order for the user and group names to be displayed correctly the users and groups must have the same ID's as the source.
SUSE Linux	SUSE Linux is not able to perform automated mount operations if hosted on VMware. (RHEL and OEL Linux work as expected).
AIX	The system command importvg is invoked by Protector to mount snapshots to the user specified location. importvg creates a directory for the user specified location plus an empty directory corresponding to the original mount point. Neither of these directories are removed by Protector when the snapshot is eventually unmounted, although neither will contain any data.

Control	Description
Repurpose	Perform the mount sequence for the repurposing scenario (refer to About the repurposing mount sequence for details). NoteRepurpose is not valid for continuous replication; the rules compiler will issue an error if a continuous mover is used on the data flow in conjunction with this type of mount operation.
Proxy Backup	Perform the mount sequence for the proxy backup scenario (refer to About the proxy backup mount sequence for details). NoteA proxy backup of a live replication will generate a warning in the compiler to tell the user that their replication will be paused until the proxy backup is complete.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
SAN	Adds the replication to a Host Group.
Host	Adds the replication to a Host Group and confirms that it is available from the specified Host.
OS	Adds the replication to a Host Group and mounts it on the specified Host's operating system.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Host Group	Manually specify or select a host group to use to expose a snapshot or replication. NoteWhen exposing an LDEV, the host group specified must be in the same resource group as the secondary volumes.
Add Host Group	Click this button to add host groups when specifying a multi-path mount operation.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Control	Description
Automatically discover	Protector will automatically select a host group to use to expose the snapshot or replication.
Selected	The user must specify one or more host groups to use to expose the snapshot or replication.
Select a Host Group	Manually specify or select a host group to use to expose a snapshot or replication. NoteWhen exposing an LDEV, the host group specified must be in the same resource group as the secondary volumes.
Add Host Group	Click this button to add host groups when specifying a multi-path mount operation.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
OS Host	Specify the machine to mount to or expose to. NoteUnless the user selects a host group, the machine where the volume is to be mounted must have an existing volume on the same storage device. If there is no connection between the mount host and the block storage device then Protector will fail the mount operation after a timeout of 30 minutes.
VMware host	Expose the volumes to the specified VMware host to enable them to be mounted to the VM. NoteExposing using a VMware host requires that a VMware ESXi/vCenter node be configured.
Datastore	Specifies a destination datastore when mounting to a VMware virtual machine which is part of a cluster, in which case the default datastore may not be a suitable place to save the RDM mount information. If the datastore field is left blank then mount information is saved alongside the VM.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Next	Takes the user to the next screen in the wizard.

Control	Description
Original	The replication is mounted at its original location. NoteMounting at the original location will fail if there is already a volume mounted at that location.
Drive starting at letter	When mounting a replication that contains multiple volumes, the first volume will mount at the specified drive and subsequent drives are used for each additional volume.
Directory	When mounting a replication that contains multiple volumes, each volume will be assigned a separate subdirectory. Click Browse to view the drives and directories on the selected host. To create a new directory, type in the required path. NoteProtector does not check to make sure the directory selected as the mount point is empty. This means it is possible to mount a snapshot inside or even over the top of another mounted volume. This should be avoided.
Cancel	Discards all changes and reverts to the previous page.
Previous	Takes the user to the previous screen in the wizard.
Finish	Commits the new changes. Pages currently open in other tabs and windows will need to be reloaded before the changes are seen by the user.

Parent Topic

• Data Flow Wizard

This page displays the details of a Data Flow and enables you launch the wizard to edit, activate, deactivate and change access permissions.

Control	Description
Edit	Launches the Data Flow Wizard to enable you to edit the data flow.
Tag	Modifies the tags of an existing object from the either the inventory screen or the details screen of the object.
Compile	Displays the Activate Data Flow Dialog and attempts to compile the rules for the data flow. If compilation is successful then the rules can be activated.
Deactivate	Deactivates the selected data flow and removes its rules. CautionIf the deactivated data flow contains storage hardware based operations, this will remove the pairing relationships.
Edit Permissions	Displays the Access Control Permissions Inventory to enable you to view and edit the data flow's permissions.
Data Flow Canvas	Shows the Data Flow diagram in read-only mode.
Applied Policies	The area to the right of the workspace lists all the policies that have been applied in the data flow. Click the node or mover of interest to view the applied policies and mover settings.
Summary	The area to the right of the workspace lists the Status of the data flow.
Status	The Status of the data flow can be Active or Inactive.
Activated	If the data flow is Active then Activated shows the date and time the data flow was activated.
Modified Since Activation	If the data flow is Active then Modified Since Activation shows if the data flow has been modified since it was activated, this can be either Yes or No. If the value is Yes then the currently distributed rules are different to those shown in the data flow.
Monitor	Displays the Monitor Details screen for this data flow

Parent Topic

• Data Flows Inventory