Global-Active Device User Guide

Version: 9.8.5
Audience: anonymous
Part Number: MK-98RD9024-16

Overview of global-active device
About global-active device
Global-active device components
Global-active device solutions
Fault-tolerant storage infrastructure
Failover clustering without storage impact
Server load balancing without storage impact
System configurations for GAD solutions
Global-active device and global storage virtualization
About the virtual ID
GAD status monitoring
GAD status
GAD status transitions
Pair status
GAD suspend types
I/O modes
Relationship between GAD status, pair status, and I/O mode
Global-active device and server I/O
Server I/O (GAD status: Mirrored)
Server I/O (GAD status: Mirroring or Quorum disk blocked or no quorum disk volume)
Server I/O when the GAD status is Suspended
Server I/O when the GAD status is Blocked
Quorum disk and server I/O
GAD pairs without a quorum disk
I/O stoppage detected in the counterpart system
I/O stoppage not detected in the counterpart system
Server I/Os and data mirroring with blocked quorum disk or without quorum disk volumes
Quorum disk status
Recovering from Failed quorum disk status
Initial copy and differential copy
GAD consistency groups
Operations on GAD pairs by consistency group
Suspension of GAD pairs by consistency group
Use cases for consistency groups
Batch failover
Resuming operations by using consistent backup data
GAD consistency group statuses
I/O preference mode when remote path failed in a GAD pair
Unintended switchover in a cross-path configuration with the preferred and nonpreferred path settings using ALUA enabled
Unintended failover in a server cluster configuration
Storage system interoperability and required microcode versions
Modes of operation
User interfaces for global-active device operations
Command Control Interface
Hitachi Command Suite
Configuration workflow for global-active device
System requirements
Requirements and restrictions
Interoperability requirements
Volume types that can be used for GAD
Dynamic Provisioning / Dynamic Tiering / Active flash
Preparing a virtual volume for use as an S-VOL
ShadowImage
Limitations when sharing GAD and ShadowImage volumes
SI operations and GAD pair status
GAD operations and SI pair status
Thin Image
Limitations for using both GAD and Thin Image
Thin Image operations and GAD status
GAD operations and Thin Image pair status
GAD operations and Thin Image Advanced pair status
Use cases for pairing GAD volumes with SI or HTI
Universal Replicator
GAD pair and Universal Replicator pair interoperability
Data Retention Utility
GAD status and I/O allowance by access attribute
Volume Migration
Restrictions for using GAD with Volume Migration
GAD status and Volume Migration pair operations
Volume Migration pair statuses and GAD pair operations
LUN Manager
Virtual Partition Manager
Nondisruptive migration
Restrictions for using GAD with nondisruptive migration
GAD status and nondisruptive migration pair operations
Volume Shredder
Performance Monitor
Server I/Os added to Performance Monitor
Port I/Os added to Performance Monitor
Planning for global-active device
Storage system preparation
Adding and removing cache and shared memory
Adding and removing cache memory
Adding shared memory
Removing shared memory
Advanced system settings
Planning system performance
Setting preferred and nonpreferred paths
Setting preferred and nonpreferred paths using ALUA
Setting preferred and nonpreferred paths using HDLM
Hitachi Dynamic Link Manager
Planning physical paths
Determining the required bandwidth
Fibre Channel connections
iSCSI data path requirements
Connection types
Direct connection
Connection using switches
Connection using channel extenders
Planning ports (VSP 5000 series)
Fibre Channel used as remote paths
Planning the quorum disk
Installation of the external storage system
Relationship between the quorum disk and number of remote connections
Suspended pairs depending on failure location (quorum disk not shared)
Suspended pairs depending on failure location (quorum disk shared)
Relationship between quorum disks and consistency groups
Response time from the external storage system
Cache pending rate of the CLPR to which the quorum disk is assigned
Planning GAD pairs and pair volumes
Differential data
Maximum number of GAD pairs
Calculating the number of cylinders
Calculating the number of bitmap areas
Calculating the number of available bitmap areas
Calculating the maximum number of pairs
S-VOL resource group and storage system: same serial number and model
Restrictions when creating an LU whose LU number is 2048 or greater
Configuration and pair management using CCI
Global-active device system configuration
Primary storage system settings
Secondary storage system settings
CCI server configuration
External storage system settings
Workflow for creating a GAD environment
Initial state
Adding the external storage system for the quorum disk
Verifying the physical data paths
Creating command devices
Creating the configuration definition files
Starting CCI
Connecting the primary and secondary storage systems
Setting the port attributes (VSP 5000 series)
Adding remote connections
Creating the quorum disk
Setting the port attributes for connecting the external storage system
Creating external volume groups
Creating external volumes
Setting external volumes as quorum disks
Setting up the secondary storage system
Creating a resource group (P-VOL not registered to a VSM)
Creating a resource group (P-VOL registered to a VSM)
Reserving a host group ID
Deleting the virtual LDEV ID of the S-VOL
Reserving an LDEV ID for the S-VOL
Setting the GAD reserve attribute on the S-VOL
Creating a host group
Creating a pool
Creating the S-VOL
Adding an LU path to the S-VOL
Updating the CCI configuration definition files
Shutting down CCI
Editing CCI configuration definition files
Restarting CCI
Creating the GAD pair
Verifying the virtual LDEV ID at the secondary site
Revising the virtual LDEV ID at the secondary site
Setting the ALUA mode
Creating a global-active device pair
Adding an alternate path to the S-VOL
Setting a nonpreferred cross path
Releasing the differential data managed in a pool
GAD 3DC delta resync (GAD+UR) operations
GAD 3DC delta resync system configuration
Sites
Storage systems
Servers
Networks
GAD+UR pairs
Primary storage system settings
GAD secondary storage system settings
UR secondary storage system settings
CCI server configuration
Workflow for creating a GAD 3DC delta resync environment
Initial state
Preparing the UR secondary site
Installing the software products
Creating command devices
Creating the UR delta resync pairs
Creating the configuration definition file
Starting CCI
Connecting the GAD secondary system and the UR secondary system
Setting the port attributes
Adding remote connections
Setting up the GAD secondary storage system
Setting up the UR secondary storage system
Updating the CCI configuration definition files
Creating the UR delta resync pairs
Creating the UR pairs in a GAD+UR configuration
Setting port attributes
Adding remote connections
Setting up the primary storage system
Updating the CCI configuration definition files
Creating the UR pairs
Starting GAD+UR operations
GAD pair operations
Overview of GAD pair operations
Creating GAD pairs
Creating a GAD pair with I/O preference mode when remote path failed
Suspending GAD pairs
Enabling the ALUA mode of an existing GAD pair
Resynchronizing GAD pairs
Changing I/O preference mode when remote path failed for an existing pair
Deleting GAD pairs
Forcibly changing the I/O mode of GAD pairs for recovery
Recovering when I/O mode is Block for both P-VOL and S-VOL
Recovering when P-VOL cannot be checked and S-VOL is suspended with I/O mode Block
Recovering when P-VOL is suspended with I/O mode Local and S-VOL is suspended with I/O mode Block
Changing preferred path settings
Managing pairs in a GAD 3DC delta resync environment
Executing delta resync
Notes on delta resync
In case of delta resync failure
Resynchronizing GAD pairs in a GAD 3DC delta resync environment
Deleting GAD pairs in a GAD 3DC delta resync environment
Using Hitachi Command Suite to set up global-active device
Setting up a global-active device environment
About global-active device setup
Prerequisites for global-active device setup
Select primary and secondary storage systems
Configuring remote paths
Configuring the quorum disk
Configuring pair management servers
Configuring the virtual storage machine
Monitoring and managing global-active device pairs
Allocating global-active device pairs
Allocating global-active device pairs based on like volumes
Allocating global-active device pairs using allocated volumes
Checking global-active device pair status
Monitoring global-active device pair performance
Unallocating global-active device pairs
Unallocating individual global-active device volumes
Discontinuing a global-active device environment
Disaster recovery of global-active device
Failure locations
SIMs related to GAD
Pair condition before failure
Pair condition and recovery: server failures
Pair condition and recovery: path failure between the server and storage system
Recovering from a path failure: server to primary storage system
Recovering from a path failure: server to secondary storage system
Pair condition and recovery: P-VOL failure (LDEV blockade)
Recovering the P-VOL (DP-VOL) (pair status: PAIR)
Recovering the P-VOL (other than DP-VOL) (pair status: PAIR)
Pair condition and recovery: S-VOL failure (LDEV blockade)
Recovering the S-VOL (DP-VOL) (pair status: PAIR)
Recovering the S-VOL (other than DP-VOL) (pair status: PAIR)
Pair condition and recovery: full pool for the P-VOL
Recovering a full pool for the P-VOL (pair status: PAIR)
Pair condition and recovery: full pool for the S-VOL
Recovering a full pool for the S-VOL (pair status: PAIR)
Pair condition and recovery: path failure, primary to secondary storage system
Recovering paths, primary to secondary storage system (pair status: PAIR)
Pair condition and recovery: path failure, secondary to primary storage system
Recovering paths, secondary to primary storage system (pair status: PAIR when a volume is set for the quorum disk)
Recovering paths, secondary to primary storage system (pair status: PAIR when no volume is set for the quorum disk)
Pair condition and recovery: primary storage system failure
Setting correct virtual LDEV ID values
Pair condition and recovery: secondary storage system failure
Pair condition and recovery: path failure, primary to external storage system
Recovering the path: primary to external storage system (pair status: PAIR)
Pair condition and recovery: path failure, secondary to external storage system
Recovering the path: secondary to external storage system (pair status: PAIR)
Pair condition and recovery: quorum disk failure
Recovering the quorum disk (pair status: PAIR)
Recovering from quorum disk failures
Replacing a failed external storage system with a new one
Recovering from the FAILED status
Pair condition and recovery: external storage system failure
Pair condition and recovery: other failures
Recovery procedure for GAD pair suspension due to other failures
Recovering the storage systems: primary site failure with external storage system
Reversing the P-VOL and S-VOL
Creating GAD pairs when virtual LDEV IDs are deleted from the P-VOL and S-VOL
Creating GAD pairs when virtual LDEV IDs are set for the P-VOL and S-VOL
Resolving failures in multiple locations
Pair condition and recovery: quorum disk and primary-to-secondary path failure
Recovering the quorum disk and primary-to-secondary path failure (VSP 5000 series)
Disaster recovery in a GAD 3DC delta resync environment
Status before failure
Recovering from primary site and P-VOL failures (GAD+UR)
Recovering from a primary site failure (GAD+UR)
Recovering from a P-VOL failure (LDEV blockade) at the primary site (GAD+UR)
Reversing the GAD P-VOL and S-VOL (GAD+UR)
Recovering from secondary site and S-VOL failures (GAD+UR)
Recovering from a secondary site failure (GAD+UR)
Recovering from a failure (LDEV blockade) on an S-VOL at the secondary site (GAD+UR)
Recovering from a failure at the primary and secondary sites (GAD+UR)
Recovering from a failure on the UR delta resync pair (VSP 5000 series)
Recovering from a failure on the UR delta resync pair (VSP E series)
Recovering from a quorum disk failure (GAD+UR)
Recovering from a quorum disk failure when one GAD volume is accessible
Recovering from a quorum disk failure when neither GAD volume is accessible
Maintenance of global-active device
Replacing the external storage system while keeping GAD pairs
Expansion of DP-VOL capacity while keeping pair status
Expanding DP-VOL capacity used in GAD pair
Expansion order policy when GAD pair shares the same volumes with other software
Expanding DP-VOL capacity when GAD pair is used with Universal Replicator
Expanding DP-VOL capacity when GAD pair is used with ShadowImage
Calculating the numbers of differential and pair tables for each pair
Expanding DP-VOL capacity when GAD pair is used with Thin Image
Calculating the snapshot estimated manageable capacity, the numbers of cache management devices, and the subscription limit of the V-VOL capacity
Expansion order policy in configuration where P-VOL in remote replication shares the same volume with S-VOL in local replication
Expansion order policy in 3DC cascade, 3DC multi-target, or 3DC delta resync configuration with remote replications
Expansion order when remote replications in a 3DC cascade configuration share the same volumes with local replications (ShadowImage/Thin Image)
Recovering from failure if one volume capacity in GAD pair cannot be expanded
Recovering from failure if one volume capacity in GAD pair has been expanded
Planned outage of global-active device storage systems
Planned power off/on: primary storage system
Powering off the primary storage system
Powering on the primary storage system
Planned power off/on: secondary storage system
Powering off the secondary storage system
Powering on the secondary storage system
Planned power off/on of the external storage system, I/O at primary site
Powering off the external storage system, I/O at primary site
Powering on the external storage system, I/O at primary site
Planned power off/on of the external storage system, I/O at secondary site
Powering off the external storage system, I/O at secondary site
Powering on the external storage system, I/O at secondary site
Planned power off/on: primary and secondary storage systems
Powering off the primary and secondary storage systems
Powering on the primary and secondary storage systems
Planned power off/on of the primary and external storage systems
Powering off the primary and external storage systems
Powering on the primary and external storage systems
Planned power off/on of the secondary and external storage systems
Powering off the secondary and external storage systems
Powering on the secondary and external storage systems
Planned power off/on of all GAD storage systems
Powering off the primary, secondary, and external storage systems
Powering on the primary, secondary, and external storage systems
Planned outage of storage systems in a GAD 3DC delta resync environment
Planned power off/on: primary GAD+UR storage system
Powering off the GAD+UR primary storage system
Powering on the GAD+UR primary storage system
Planned power off/on: GAD secondary storage system
Powering off the GAD secondary storage system
Powering on the GAD secondary storage system
Planned power off/on: UR secondary storage system
Powering off the UR secondary storage system
Powering on the UR secondary storage system
Planned power off/on: external storage system, I/O at primary site (GAD+UR)
Powering off the external storage system, I/O at primary site (GAD+UR)
Powering on the external storage system, I/O at primary site (GAD+UR)
Planned power off/on: external storage system, I/O at secondary site (GAD+UR)
Powering off external storage system, I/O at secondary site (GAD+UR)
Powering on external storage system, I/O at secondary site (GAD+UR)
Volume migration using GAD
Required source and target storage systems
Migrating volumes using GAD
Reusing volumes after data migration
Reusing a volume that was an S-VOL
Reusing a volume that was a P-VOL
Deleting used volumes
Deleting a volume with the reserve attribute
Deleting a volume that was a P-VOL
Migrating GAD pairs nondisruptively using GAD
Requirements for GAD pair migration
Restrictions and behavior when migrating GAD pairs
System configurations and configuration definition files for migrating GAD pairs
Example of storage system configuration and configuration definition file at the source GAD primary site
Example of storage system configuration and configuration definition file at the source GAD secondary site
Example of storage system configuration and configuration definition file at the target GAD primary site
Example of storage system configuration and configuration definition file at the target GAD secondary site
Migrating GAD pair workflow
Creating a temporary GAD pair used for data migration
Creating a target GAD pair
Suspending the source GAD pair by specifying the P-VOL
Starting the host access to the S-VOL of the temporary GAD pair for data migration
Suspending the temporary GAD pair for data migration by specifying the S-VOL
Starting the host access to the S-VOL of the target GAD pair
Deleting the source GAD pair and the temporary GAD pair for data migration
Removing the source storage systems
Stopping GAD pair migration to return the operations to the source GAD pair
Disaster recovery when migrating GAD pairs
Failure on the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 1 on the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 2 on the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 3 on the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 4 on the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 5 on the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 6 on the primary storage system of the source GAD pair
Failure on the secondary storage system of the source GAD pair
Recovering from a failure that occurred during phase 1 on the secondary storage system of the source GAD pair
Recovering from a failure that occurred during phase 2 on the secondary storage system of the source GAD pair
Recovering from a failure that occurred during phases 3 to 6 on the secondary storage system of the source GAD pair
Failure on the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 1 on the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 2 on the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 3 on the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 4 on the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 5 on the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 6 on the primary storage system of the target GAD pair
Failure on the secondary storage system of the target GAD pair
Recovering from a failure that occurred during phase 1 on the secondary storage system of the target GAD pair
Recovering from a failure that occurred during phases 2 to 4 on the secondary storage system of the target GAD pair
Recovering from a failure that occurred during phases 5 to 6 on the secondary storage system of the target GAD pair
Failure on the P-VOL of the source GAD pair (LDEV blockade)
Recovering from a failure (LDEV blockade) that occurred during phase 1 on the P-VOL of the operating GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 2 or 3 on the P-VOL of the source GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 4 on the P-VOL of the operating GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 5 on the P-VOL of the source GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 6 on the P-VOL of the source GAD pair
Failure on the S-VOL of the source GAD pair (LDEV blockade)
Recovering from a failure (LDEV blockade) that occurred during phase 1 on the S-VOL of the source GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 2 on the S-VOL of the source GAD pair
Recovering from a failure (LDEV blockade) that occurred during phases 3 to 6 on the S-VOL of the source GAD pair
Failure on the P-VOL of the target GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 1 on the S-VOL of the temporary GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 2 on the S-VOL of the temporary GAD pair
Recovering from a failure (LDEV blockade) that occurred during phases 3 and 4 on the S-VOL of the temporary GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 5 on the S-VOL of the temporary GAD pair
Recovering from a failure (LDEV blockade) that occurred during phase 6 on the S-VOL of the temporary GAD pair
Failure on the S-VOL of the temporary GAD pair for data migration
Recovering from a failure (LDEV blockade) that occurred during phases 1 to 6 on the S-VOL of the target GAD pair
Failure in the remote path from the primary to the secondary storage system of the source GAD pair
Recovering from a failure that occurred during phase 1 in the remote path from the primary to the secondary storage system of the source GAD pair
Recovering from a failure that occurred during phase 2 in the remote path from the primary to the secondary storage system of the source GAD pair
Recovering from a failure that occurred during phases 3 to 6 in the remote path from the primary to the secondary storage system of the source GAD pair
Failure in the remote path from the secondary to the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 1 in the remote path from the secondary to the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 2 in the remote path from the secondary to the primary storage system of the source GAD pair
Recovering from a failure that occurred during phases 3 to 6 in the remote path from the secondary to the primary storage system of the source GAD pair
Failure in the remote path from the primary storage system of the source GAD pair to the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 1 in the remote path from the primary storage system of the source GAD pair to the primary storage system of the target GAD pair
Recovering from a failure that occurred during phases 2 to 4 in the remote path from the primary storage system of the source GAD pair to the primary storage system of the target GAD pair
Recovering from a failure that occurred during phases 5 and 6 in the remote path from the primary storage system of the source GAD pair to the primary storage system of the target GAD pair
Failure in the remote path from the primary storage system of the target GAD pair to the primary storage system of the source GAD pair
Recovering from a failure that occurred during phases 1 and 3 in the remote path from the primary storage system of the target GAD pair to the primary storage system of the source GAD pair
Recovering from a failure that occurred during phase 4 in the remote path from the primary storage system of the target GAD pair to the primary storage system of the source GAD pair
Recovering from a failure that occurred during phases 5 to 6 in the remote path from the primary storage system of the target GAD pair to the primary storage system of the source GAD pair
Failure in the remote path from the primary to the secondary storage system of the target GAD pair
Recovering from a failure that occurred during phase 1 in the remote path from the primary to the secondary storage system of the target GAD pair
Recovering from a failure that occurred during phases 2 to 4 in the remote path from the primary to the secondary storage system of the target GAD pair
Recovering from a failure that occurred during phases 5 and 6 in the remote path from the primary to the secondary storage system of the target GAD pair
Failure in the remote path from the secondary to the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 1 in the remote path from the secondary to the primary storage system of the target GAD pair
Recovering from a failure that occurred during phases 2 to 5 in the remote path from the secondary to the primary storage system of the target GAD pair
Recovering from a failure that occurred during phase 6 in the remote path from the secondary to the primary storage system of the target GAD pair
Planned outage of the storage system during GAD pair migration
Migrating GAD+UR pairs nondisruptively using GAD
Information to know before migrating GAD+UR pairs using GAD
System configurations for migrating GAD+UR pairs
Example of storage system configuration at the source GAD primary site
Example of storage system configuration at the source GAD secondary site
Example of storage system configuration at the source UR secondary site
Example of storage system configuration at the target GAD primary site
Example of storage system configuration at the target GAD secondary site
Example of storage system configuration at the target UR secondary site
GAD+UR pair migration workflow
Configuring the secondary site of the temporary GAD pair used for migration
Configuring the target GAD secondary site
Configuring the target UR secondary site
Creating the target UR delta resync pair
Creating the target UR pair
Moving operations to the target GAD+UR environment and starting operations
Removing the source GAD and UR pairs
Recovering from a failure during GAD+UR pair migration using GAD
Recovering from a source GAD primary site failure
Recovering from a source GAD secondary site failure
Recovering from a source UR secondary site failure
Recovering from a target GAD primary site failure
Recovering from a target GAD secondary site failure
Recovering from a target UR secondary site failure
Recovering from a P-VOL failure (LDEV blockade) at the source GAD primary site
Recovering from a P-VOL failure (LDEV blockade) at the target GAD primary site
Recovering from a physical path failure between the storage systems at the source GAD primary site and secondary site
Recovering from a physical path failure between the storage systems at the primary and secondary sites of the temporary GAD pair used for migration
Recovering from a source UR pair failure (full journal volume)
Planned outage during GAD+UR pair migration using GAD
Planned power off/on: source GAD primary storage system
Planned power off/on: source GAD secondary storage system
Planned power off/on: source UR secondary storage system
Powering off the source UR secondary storage system
Powering on the source UR secondary storage system
Planned power off/on: target GAD primary storage system
Powering off the target GAD primary storage system
Powering on the target GAD primary storage system
Migrating UR pairs nondisruptively using GAD
Workflows for migrating the UR environment using GAD
Information to know before migrating using GAD
System configuration examples
Storage system configuration example at source UR primary site
Storage system configuration example at source UR secondary site
Storage system configuration example at target UR primary site
Storage system configuration example at target UR secondary site
CCI server configuration
Migration workflows
Status before starting migration
Configuring GAD secondary site
Preparing the target UR secondary site
Installing software licenses
Creating command devices on the target UR secondary storage system
Workflow for creating UR pairs in the target environment
Creating the CCI configuration definition files
Starting CCI
Connecting the target UR primary system to the UR secondary system
Setting the port attributes for the remote conections (VSP G1x00, VSP F1500)
Adding remote connections
Setting up the target UR primary system and secondary system
Creating pools for journal volumes
Creating journal volumes
Creating journals
Updating the CCI configuration definition files
Shutting down CCI instances
Editing CCI configuration definition files (UR migration)
Restarting CCI instances
Creating the target UR pairs
Starting operations of the target UR pairs
Removing the source environment
Stopping the source UR operation
Suspending the GAD pair
Deleting the source UR pair
Deleting the GAD pair
Removing the remote connections
Stopping and restarting the CCI instances
Disaster recovery during UR pair migration
Status prior to a failure
Examples of recovery procedures from a source UR primary site failure or a P-VOL failure (LDEV blockade)
Examples of recovery procedures from a source UR primary site failure
Recovery procedures from a source UR primary site failure that occurs when data is being migrated “during migration”
Recovery procedures from a source UR primary site failure that occurs after data migration is complete “during migration”
Recovery procedures from a source UR primary site failure that occurs before deleting a source UR pair "after migration is complete"
Removing the source UR environment to recover from a failure that occurs on the source UR primary storage system
Examples of procedures from a P-VOL failure (LDEV blockade) at the source primary site
Recovery procedures from a source UR P-VOL failure that occurs when data is being migrated “during migration”
Recovery procedures from a source UR P-VOL failure that occurs after data migration is complete “during migration”
Recovery procedures from a source UR P-VOL failure that occurs before deleting a source UR pair "after migration is complete"
Examples of recovery procedures from a target UR primary site failure or an S-VOL failure (LDEV blockade)
Examples of recovery procedures from a target UR primary site failure
Recovery procedures from a target UR primary site failure that occurs when data is being migrated “during migration”
Recovery procedures from a target UR primary site failure that occurs after data migration is complete “during migration”
Recovery procedures from a target UR primary site failure that occurs before deleting source UR pair "after migration is complete"
Examples of recovery procedures from a GAD S-VOL failure (LDEV blockade) at the target primary site
Recovery procedures from the target primary site GAD S-VOL failure (LDEV blockade) that occurs when data is being migrated “during migration"
Recovery procedures from the target primary site GAD S-VOL failure (LDEV blockade) that occurs after data migration is complete “during migration”
Recovery procedures from the target UR primary site GAD S-VOL failure (LDEV blockade) that occurs before deleting a source UR pair "after migration is complete"
Examples of recovery procedures from a source UR secondary site failure or an S-VOL failure (LDEV blockade)
Examples of recovery procedures from a source secondary site failure
Recovering from a source UR secondary site failure that occurs when data is being migrated “during migration”
Recovering from a source UR secondary site failure that occurs after data migration is complete “during migration”
Recovering from a source UR secondary site failure that occurs before deleting the source UR pairs "after migration is complete"
Examples of recovery procedures from an S-VOL failure (LDEV blockade) at the source UR secondary site
Recovering at the source UR primary site, a UR S-VOL failure (LDEV blockade) that occurs when data is being migrated “during migration”
Recovering from a source UR S-VOL failure (LDEV failure) that occurs after data migration is complete “during migration”
Recovering from a source UR S-VOL failure (LDEV failure) that occurs before deleting the source UR pairs "after migration is complete"
Examples of recovery procedures from a target UR primary site failure or an S-VOL failure (LDEV blockade)
Examples of recovery procedures from a target secondary site failure
Recovering from a target UR secondary site failure that occurs after data migration is complete "during migration"
Recovering from a target UR secondary site failure that occurs before deleting a source UR pair "after migration is complete"
Examples of recovery procedures from an S-VOL failure (LDEV blockade) at the target UR secondary site
Recovering from a target UR S-VOL failure (LDEV blockade) that occurs after data migration is complete "during migration"
Recovering from a target UR S-VOL failure (LDEV blockade) that occurs before deleting the source UR pairs "after migration is complete"
GAD pair and UR pair interoperability for UR environmental migration using GAD
Planned outages during UR pair migration using GAD
Planned power off/on: source UR primary storage system
Powering off the source UR primary storage system
Powering on the source UR primary storage system
Planned power off/on: target UR primary storage system
Powering off the target UR primary storage system
Powering on the target UR primary storage system
Troubleshooting
General troubleshooting
Troubleshooting related to remote path status
Error codes and messages
Troubleshooting for CCI
SIM reports of GAD operations
Procedure for recovering pinned track of a GAD volume
Restoring pair statuses when a GAD consistency group contains local I/O mode pairs and block I/O mode pairs
Restoring pair statuses in the consistency group when the primary volume is at the primary site
Restoring pair statuses in the consistency group when the primary volume is at the secondary site
Correspondence between GUI operations and CLI commands
Correspondence between GUI operations and CCI commands
Parameter range for CCI options

Back to home page