Hitachi Block Replication Configuration Wizard

Ops Center Protector User Guide

Version
7.7.x
Audience
anonymous
Part Number
MK-99PRT002-08
ft:lastEdition
2023-10-26

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

CAUTION:
When 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.
Note: Protector 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.
Figure. Replicate Configuration Wizard - Configure New or Adopt Existing Replication
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.
Note: To 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.
Figure. Replicate Configuration Wizard - Configure New Replication
Control Description
Replication Type Select the type of replication to create:
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.
Figure. Replicate Configuration Wizard - Adopt Existing Replication
Note: Adoption 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:
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.
Note: If the mirror unit of an active replication is changed after initial data flow activation then:
  1. S-VOLs and pairing relationships for the replication will be destroyed (or dissociated if previously adopted).
  2. 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.
Figure. Replicate Configuration Wizard - Adoption Summary

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.