8464ch14_DisasterRecoveryTesting.fm Draft Document for Review February 7, 2020 3:15 pm 15.When all of the volumes that are processed by cartridge entry on the DR host are in  SCRATCH status, they can be deleted from the TS7700 by using host EJECT processing.  This process can be done using one of the following methods: – Run a TMS job to issue the EJECTs for these volumes. – Use ISMF to EJ ECT each volume. – Use the CBRSPLCS SAMPLIB member to eject each volume. 16.Shut down the DR host. 17.If the Management Class that is used on the DR cluster from Step 6 existed before the DR  test and the Copy Mode was updated for the DR test, change the Copy Mode back to what  it was before the DR test. 18.If you want to prevent accidentally returning production volumes to SCRATCH by the DR  host, keep the Write Protect Mode enabled on the DR clusters. 19.Alternatively, you can disable Write Protect Mode in each DR cluster by using the TS7700  MI by selecting  SETTINGS  Cluster Settings  Write Protect Mode  Disable Write  Protect Mode  Submit Changes . 14.5.3 Method 3: DR Testing without Write Protect Mode 20.If any production volumes were read by the DR host from the DR cluster during the DR  test, those volumes are now owned by the DR cluster. To transfer the ownership back to  the production cluster, use the  LI REQ,OTCNTL  command with the  START  keyword. For more  information, see “Returning ownership of prod uction volumes to the production cluster” on  page 779. 2. By using the TS7700 MI, add the MEDIA1 and MEDIA2 categories that were chosen to  the TS7700 by selecting  Virtual  Categories  Add Scratch Category . 3. Choose the volume serial ranges that will be created and used for input/output processing  on the DR host. Update the TMS on the production hosts to ignore the ranges during host  cartridge entry processing (see 14.3.3, “Cartridge entry considerations” on page 777) or  use the  LI DISABLE,CBRUXENT  command to prevent host cartridge entry processing  entirely. 1. Determine which MEDIA1, MEDIA2, ERROR, and PRIVATE categories will be used by the  DR host during the DR test. These categories must be unique from any category that is  used by a production system to ensure separation of production volumes from disaster  volumes. Another method that can be used to simulate that of a real disaster is to run your DR test from  a DR host that is attached to one or more disaster clusters while the production hosts  continue to write data across the grid.  If your choice is between the use of Write Protect Mode and not using Write Protect Mode, it  is recommended to use Write Protect Mode (Method 2), to provide another level of  write-protection in case the TMS on the disaster host is not configured correctly to prevent  writes to the production volumes. As with the previous method, the steps that are described in this section were written in a  checklist format to provide a reference of the steps that are needed to complete this method.  It is advised that you review all of these steps before an actual DR exercise, and during the  DR exercise. Because the steps were written to apply to more than one TS7700 grid  configuration, ensure that you understand each step and how it applies to your environment  before running each step. To perform DR testing without Write Protect Mode, complete the following steps: 796  IBM TS7700 Release 5.0 Guide