Go to main content
1/18
Contents
List of Figures
List of Tables
Title and Copyright Information
Preface
Audience
Prerequisites
About This Book
How Do I Choose a Solution for My Needs?
Documentation Accessibility
What's New?
1
Introduction to Disaster Recovery
Defining the Recovery Time Objective (RTO)
Defining the Recovery Point Objective (RPO)
Handling Temporary Outages
Key Concept: Synchronization Point Recovery
Relating RPO to Synchronization Point Recovery
Planning for Data High Availability (D-HA)
Highly-Available Physical Tape
Highly-Available Virtual Tape
D-HA and Synchronization Point Recovery
Conducting True Disaster Recovery
Planning for DR Testing
Data Movement for DR Testing
DR Testing With Physical Export/Import
DR Testing With CDRT
DR Testing with VSM Cross-Tape Replication
2
Doing Physical Exports and Imports
Exporting and Importing by Management Class
Example: Exporting by Management Class from the Source VSM System
Example: Importing by Management Class into the Target VSM System
Exporting and Importing by Storage Class
Example: Exporting by Storage Class from the Source VSM System
Example: Importing by Storage Class into the Target VSM System
Export/Import for VLE
3
Using the ELS External Vaulting Feature
Preparing for ELS External Vaulting
Creating MVCs for DR and LTR
DELSCR Considerations When Using the Vaulting Feature
What Happens When Vaulted Volumes Return to the ACS?
Vaulting MVCs for DR
Basic DR Vaulting with MVCs
Step 1 – Creation of Vault VTVs/MVCs
Step 2 – Exporting the Vault MVCs
Step 3 – (Optional) Write Additional Datasets to Manifest File Tape
Step 4 – Eject Vault MVCs
Step 5 - Eject Native Volumes (Including Manifest File Tape)
Step 6 – Create a Pull List of Volumes for Return from the Vault
Step 7 – Prepare Vaulted MVCs for Return
Step 8 – Prepare Vaulted Native Volumes for Return
Step 9 - Entering Returned Volumes
Multiple Week DR Vaulting with MVCs
DR Vaulting with MVCs in a Remote Library
Vaulting MVCs for LTR
Ejecting Specific Volumes to a Local (Floor) Vault
4
Using Cross-TapePlex Replication in a DR Solution
How Does CTR Work?
CTR VTV Read-Only Considerations
Configuring for CTR
The Setup: Configuring and Starting CTR
Defining Policies for CTR
Policies for the Sending TapePlex
Policies for the Receiving TapePlex
Using CTR When the Remote Site Has No LPARs
Using CTR as a DR Solution
Using CTR for Business Continuance
Using CTR for Business Resumption
Disaster Recovery Testing Using Cross-Tapeplex Replication
DR Testing When the DR Site Has No LPARs
Managing VTVs Replicated Using Cross-TapePlex Replication (CTR)
5
Configuring a Remote Library
Modifying the SMC SCMDS File
Updating the VTCS CONFIG Deck to Define a Remote Library
MVC Pool Considerations
6
Using Clustered VTSS Configurations
What is Clustered VTSS?
Clustered VTSS Requirements
How Clustered VTSS Configurations Work
How VTSS Reconciliation Works
Uni-Directional and Bi-Directional Clusters
Uni-Directional Clusters
How Uni-Directional VTSS Clusters Work
Bi-Directional Clusters
How Bi-Directional VTSS Clusters Work
Extended Clustering
Synchronous or Asynchronous Replication
Implementing Synchronous Replication
Implementing Asynchronous Replication with Job Monitoring
Clustering with TCP/IP Connections
The TCP/IP Environment
Configuring VTCS for TCP/IP CLINKs
CONFIG CLINK Statement
7
Using the Concurrent Disaster Recovery Test Software
Metadata Considerations
Where Does CDRT Get Its VTV Data?
What Happens to Data When the Test is Over?
Managing CDRT Resources
Volume Resources
Scratch Subpools
MVC Resources
VTSS Resources
Non-shared VTSS Resources
Clustered VTSS in CDRT
Preparing a VTSS Cluster for a DR Test:
Managing VTSS Contents Before and After the DR Test
Shared VTSS Resources
ACS Resources
DR Test ACS Restrictions
DR Production Host Requirements
DR Test Host Requirements
VLE Resources
VTCS Policies
Defining MGMTCLAS/STORCLAS for Non-Shared VTSSs
Defining MGMTCLAS for Shared VTSSs
Optimizing Access to Test and Production Resources
Running a DR Test
Cleaning Up After a DR Test
Cleaning Up After a DR Test
Resuming Normal Operations
Operational Scenarios
Scenario 1: Production and Test Sites, ACS at Each Site, Spare VTSS at Test Site
Example JCL for Scenario 1
Scenario 2: Production and Test Sites, ACS at Each Site, VTSS Takeover at Test Site
Example JCL for Scenario 2
Scenario 3: Production and Test Sites, ACS at Each Site, No VTSSs
Example JCL for Scenario 3
Scenario 4: Clustered VTSSs with Production and DR Test Sites
Example JCL for Scenario 4
Scenario 5: Production and Test Sites, ACS and VLE at Each Site
Example JCL for Scenario 5
Scenario 6: Production and Test Sites, VLE Only at Each Site
Example JCL for Scenario 6
Scenario 7: Clustered VTSSs (Tapeless) with Production and DR Test Sites
Example JCL for Scenario 7
8
Creating System Recovery Points in VSM Environments
Checkpointing Examples
Example 1: Local MVC Copies and Remote MVC Copies
Example 2: Using CONFIG RECLAIM PROTECT
9
Using VLE for Disaster Recovery
Normal Production Mode
Running a DR Test with VLE
Cleanup After a DR Test with VLE
Using VLE for Business Continuance
A
Clustered VTSS Examples
Uni-Directional Clustered VTSS
Configuring and Managing a Uni-Directional Clustered VTSS System
Bi-Directional Clustered VTSS
Configuring and Managing a Bi-Directional Clustered System
Extended Clustering
Configuring and Managing a 3 VTSS Clustered System
VSM5 to VSM5 Cluster with TCP/IP CLINKs
VSM5 to VSM 6 Cluster with TCP/IP CLINKs, Cross-Connected VLEs
VSM 6 to VSM 6 ”Tapeless” Cluster with TCP/IP CLINKs
Should you Use Uni-Directional or Bi-Directional?
Glossary
Index
Scripting on this page enhances content navigation, but does not change the content in any way.