CA VM:Backup for z/vm

Transcription

1 CA VM:Backup for z/vm HiDRO Feature Disaster Recovery Using CA VM:Backup and HiDRO Release 2.8

2 This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 Contents Changes in BrightStor VM:Backup HiDRO Documentation Changes... About This Book Example Conventions... Related Documentation... vii x x Chapter 1. Installing BrightStor VM:Backup and HiDRO Installing BrightStor VM:Backup... 1 Installing HiDRO... 1 Chapter 2. Preparing Your Disaster Recovery Plan Converting to an Integrated Backup System... 4 Incorporate BrightStor VM:Backup... 4 Incorporate HiDRO... 4 HiDRO and BrightStor VM:Backup Disaster Recovery Utilities and Interfaces... 5 HiDRO Utilities... 5 BrightStor VM:Backup Utility and Interface... 5 Setting Up HiDRO... 5 Make an IPLable Copy of HiDRO... 6 Identify System Packs... 8 Create the VMIMAGE Userid... 9 Define Cycles of Offsite Tapes Define the VMIMAGE Backups (VMIMAGE SETUP) Setting Up BrightStor VM:Backup Create Full and Incremental Backup Job Templates Create a Backup Job Template for Backing Up BrightStor VM:Backup Ignored Processing Options Backup Tapes Create a Copy of the VMBRITS Utility Create CMS Restore Job Templates Example Create SFS Restore Job Templates HDR Contents iii

4 Chapter 3. Creating Your Disaster Recovery Backups Creating the Backups Assembling Your Disaster Recovery Package to Send Offsite Chapter 4. Recovering from a Disaster Restoring Your System Packs Using HiDRO Restore System Packs: VM Not Available Restore System Packs: VM Available DRESTORE Utility Automate DASD and Tape Drive Attaches Restoring the Rest of Your System Using BrightStor VM:Backup Restore BrightStor VM:Backup Using VMBRITS Restore CMS Data Restore SFS Using BrightStor VM:Backup Efficiently Using Multiple BrightStor VM:Backup Restore Machines Considerations Restoring the Catalog Minidisk Separately Performing Housekeeping Tasks Index iv Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

5 Figures Figure 1. SYBGENI Generate Stand Alone IPL Module Screen (IPL001)... 7 Figure 2. DRESTORE Menu HDR Contents v

6 vi Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

7 Changes in BrightStor VM:Backup HiDRO BrightStor VM:Backup HiDRO Release 2.7D, Gen Level 0212, is released as part of the CA-VM:Manager Release 2.8, Service Pack 01. For a complete listing of all changes in CA-VM:Manager Service Pack 01, see the Release Summary document. Documentation Changes This section lists the documentation changes specific to HiDRO. Technical changes to existing information in this guide are identified by vertical bars in the outer page margins. " References to the product name now contain the Computer Associates brand name. This change is reflected in product initialization messages. This change is reflected throughout the product documentation set, and in some messages. " Computer Associates no longer supports the BrightStor VM:Backup VMBSAR utility, and recommends that you instead use HiDRO for your backup and restore disaster recovery procedures. If, for some reason, your site still uses the VMBSAR utility, be aware that there is no version of the VMBSAR utility that supports 3590 tape devices. " Some procedures have been updated to reflect the addition of the Computer Associates licensing program file, CALMP KEYS file used by BrightStor VM:Backup. This licensing method replaces the CPUID method used previously by CA-VM:Manager products. See page 8. " ThevirtualmachinesizehasbeenchangedfortheVMIMAGEuseridCPdirectory entry. See pages 9 and 10. " Added an example of using a CUTOFF record when using the BrightStor VM:Backup Template Programming Interface (TPI) to build a restore job. See page 15. " The section Using BrightStor VM:Backup Efficiently has been included in this guide. The section discusses how to use more than one BrightStor VM:Backup restore machine, and how to back up your catalog minidisk separately and use BrightStor VM:Backup to restore it. For more information, see page 30. " Miscellaneous editorial and technical changes have been made throughout this guide. HDR Contents vii

8 viii Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

9 About This Book This book is for system administrators who want to back up their systems using BrightStor VM:Backup and the BrightStor VM:Backup High-Speed Disaster Recovery Option (HiDRO) in combination. Note: All BrightStor VM:Backup releases 3.3A or above support 3590 tape devices for CMS logical and physical backups. All HiDRO Releases 2.7A or above support 3590 tape devices for CMS logical and physical backups. IMPORTANT: Computer Associates no longer supports the BrightStor VM:Backup VMBSAR utility, and recommends that you instead use HiDRO for your backup and restore disaster recovery procedures. If, for some reason, your site still uses the VMBSAR utility, be aware that there is no version of the VMBSAR utility that supports 3590 tape devices. The book assumes you are familiar with VM/CMS and that you know the conventions for naming CMS files and Shared File System (SFS) directories. If you are not familiar with these, you might need help from someone who is. The chapters in this book provide instructions on: " Installing BrightStor VM:Backup to perform file-level logical backups and restores " Installing HiDRO to perform full-pack physical backups and disaster recovery restores " Preparing your disaster recovery plan using BrightStor VM:Backup and HiDRO " Creating your BrightStor VM:Backup and HiDRO disaster recovery backups " Recovering from a disaster This book describes one possible disaster recovery scenario. You can use this example to guide you in building a plan that combines BrightStor VM:Backup and HiDRO. You should refer to the BrightStor VM:Backup and HiDRO documentation for complete information when building any disaster recovery plan. HDR Contents ix

10 Example Conventions Examples are shown throughout this book to illustrate when to use commands, how to use options, or how the system responds to your entries. The examples are illustrations only and might differ slightly from what appears on your screen. Bold characters represent user entries. If the entry is a command, it appears in lowercase letterseventhoughyoucanentercommandsineitherupperorlowercase.acommand you enter looks like this: vmbackup submit templatename If the entry is a record, it appears in uppercase letters. A record that a user enters looks like this: SERIES SYS CART Uppercase, nonbold characters represent system responses or prompts. A system response looks like this: 0 SYBCTL095I AWAITING CONSOLE RESPONSE: Related Documentation There are several books associated with BrightStor VM:Backup and HiDRO that make up each product s library. Each book addresses a different type of user depending on the tasks the user must perform. The BrightStor VM:Backup library includes the following: " BrightStor VM:Backup User s Guide. Presentsconceptsandproceduresfortasksthat end users typically perform. It also includes end-user commands and the format for those commands. " BrightStor VM:Backup Operator s Guide. Presents concepts and procedures relevant to the day-to-day operation of BrightStor VM:Backup. This book also includes operator commands and the format for those commands. " BrightStor VM:Backup System Administrator s Guide. Presentsconceptsandprocedures for tasks required to customize BrightStor VM:Backup to fit site-specific requirements through full screens. " BrightStor VM:Backup System Programmer s Reference. Explains BrightStor VM:Backup and its administration and contains reference information for performing BrightStor VM:Backup programming tasks, customizing BrightStor VM:Backup to fit site-specific requirements, and performing any required administrative operations. " BrightStor VM:Backup Template Programming Interface Guide. Describes the BrightStor VM:Backup Template Programming Interface (TPI) and explains how to create and edit TPI job template, exception, and exclusion files for BrightStor VM:Backup backup,restore,mpc,andreinitjobs. x Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

11 " BrightStor VM:Backup Messages and Codes. Lists messages and abend codes produced by BrightStor VM:Backup, the possible cause of the situation that generated the message or code, and any actions to take in response to the situation. The book also has a cross-reference that lists the first 60 characters of each BrightStor VM:Backup message in alphabetical order. The HiDRO library includes the following: " BrightStor VM:Backup HiDRO Administrator s Guide. Explains HiDRO and its administration; gives information about customizing HiDRO to fit site-specific requirements; and describes any special administrative operations that must be performed. " BrightStor VM:Backup HiDRO Installation and Upgrade Guide. Provides instructions for installing and upgrading HiDRO. " BrightStor VM:Backup HiDRO Command Reference Guide. Explains all commands involved in the backup, restore, copy, duplicate, format, and catalog operation, as well as other advanced commands. " BrightStor VM:Backup HiDRO Operator s Guide. Presents concepts and procedures relevant to the day-to-day operation of HiDRO, including controlling the event scheduler, job queue, and service virtual machines. " BrightStor VM:Backup HiDRO Messages Guide. Lists messages produced by HiDRO and the possible cause of the situation that generated the message. Other Computer Associates product manuals that are referenced in this book and to which you might want to refer include: " CA-VM:Manager Automated Implementation and Control Guide " CA-VM:Manager Installation Guide " CA-VM:Manager Upgrade Guide " CA-VM:Manager Reference Manual " CA-VM:Manager Component Interface Guide " BrightStor VM:Tape System Administrator s Guide " BrightStor VM:Tape Command Reference HDR Contents xi

12 xii Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

13 Chapter 1 Installing BrightStor VM:Backup and HiDRO Before implementing a disaster recovery plan, you need to install BrightStor VM:Backup and HiDRO. Installing BrightStor VM:Backup All BrightStor VM:Backup releases 3.3A or above support 3590 tape devices for CMS logical and physical backups. If you use BrightStor VM:Tape, BrightStor VM:Backup requires BrightStor VM:Tape Release 1.7 or later to use 3590 tapes and tape drives. You must install or upgrade to Release 1.7 of BrightStor VM:Tape before you install BrightStor VM:Backup. Follow the appropriate instructions in the following CA-VM:Manager documentation to install or upgrade BrightStor VM:Tape and BrightStor VM:Backup: " CA-VM:Manager Installation Guide " CA-VM:Manager Upgrade Guide " CA-VM:Manager Reference Manual Installing HiDRO All HiDRO Releases 2.7A or above support 3590 tape devices for CMS logical and physical backups. Follow the instructions in the BrightStor VM:Backup HiDRO Installation and Upgrade Guide to install HiDRO. HDR Installing BrightStor VM:Backup and HiDRO 1

14 2 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

15 Chapter 2 Preparing Your Disaster Recovery Plan BrightStor VM:Backup and HiDRO together form a powerful disaster recovery tool. However, successful disaster recovery depends on having a well thought out, completely documented, carefully tested, and accurately executed disaster recovery plan. You should design your disaster recovery procedures to restore your system, with or without a VM system at the remote site, with minimal manual intervention. Note: The disaster recovery procedures discussed in this chapter and in the following two chapters are based on one possible scenario for disaster recovery; you must tailor your procedures to your own site. The disaster recovery plan discussed in this guide involves the following general steps: 1. Make HiDRO available at the remote site. 2. Restore a minimal VM system by manually entering restore commands. 3. IPL VM. 4. Restore the remainder of the data center from HiDRO physical backups. 5. Restore CMS data from BrightStor VM:Backup logical incremental backups and SFS data from BrightStor VM:Backup logical full and incremental backups. 6. Perform other housekeeping tasks (for example, activate security managers). Before you begin preparing your disaster recovery plan, you must integrate BrightStor VM:Backup and HiDRO on your system. This chapter explains how to integrate the two products, describes the BrightStor VM:Backup and HiDRO utilities and interfaces involved in disaster recovery, and provides instructions on creating the components you need to include in your disaster recovery plan. HDR Preparing Your Disaster Recovery Plan 3

16 Converting to an Integrated Backup System Use the following procedures to incorporate both BrightStor VM:Backup and HiDRO into a single backup system. Incorporate BrightStor VM:Backup If you are currently running only HiDRO, replace your HiDRO file-level logical backups with BrightStor VM:Backup file-level full and incremental logical backup jobs. Review the HiDRO CMDCTL, SFSCTL, and SELECT files for each backup on the SYBMON userid to determine which ones specify logical backups. Backups whose CMDCTL files do not specify physical backups (that is, do not specify the IVORG UNDEFINED option) are by default logical backups. Backups that back up SFS data are always logical backups. Create BrightStor VM:Backup job template, exception, and exclusion files to replace each logical backup you find. Refer to the Managing Backup Job Template Files and Managing Exception and Exclusion Files chapters in the BrightStor VM:Backup System Administrator s Guide for instructions on creating these files. When reviewing the HiDRO backups, remember that domains can contain their own CMDCTL files, and that such a CMDCTL file can specify a physical backup for its domain. If you want BrightStor VM:Backup to continue to back up such a domain physically, you must specify that exception in the BrightStor VM:Backup backup job s exception file. Incorporate HiDRO If you are currently running only BrightStor VM:Backup, you must replace your VMBSAR disaster recovery backup jobs with HiDRO physical disaster recovery backups. Chapter 3, Creating Your Disaster Recovery Backups, in this guide explains how to create these backups using the VMIMAGE utility. If you do not want to use VMIMAGE, you can set up a normal HiDRO backup, changing the defaults so that the backup s CMDCTL file specifies a physical backup (IVORG UNDEFINED option). If you choose this option, you can use HiDRO to back up only your system packs, and use BrightStor VM:Backup to back up the rest of your system. Refer to the Defining and Scheduling Backups and Home Site Recovery from Loss of System Components chapters of the BrightStor VM:Backup HiDRO Administrator s Guide for instructions on setting up HiDRO backup jobs. In the latter chapter, pay particular attention to the following: " Preparing for Loss of System Data section " Information on SYSPACK backup, a sample backup provided with HiDRO that creates physical backups of selected full-pack minidisks Each method (that is, using VMIMAGE or normal HiDRO backups) has advantages and disadvantages; the documentation about the options will help you determine which is best suited to your site. 4 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

17 HiDRO and BrightStor VM:Backup Disaster Recovery Utilities and Interfaces HiDRO Utilities There are three utilities in the HiDRO disaster recovery system, as follows: Utility Function SYBGENI Creates an IPLable image of HiDRO VMIMAGE BACKUP Creates an image of non-system packs VMIMAGE SYSTEM " Creates a RESTORE command for each non-system pack, writes all of those comands to the VMIMAGE RESTCMDS file, and copies the file to the VMIMAGE 191 minidisk " Backs up all system packs and the VMIMAGE and HIDRO 191 minidisks BrightStor VM:Backup Utility and Interface The VMBRITS utility restores all BrightStor VM:Backup system minidisks backed up in CMS format after your VM system has been restored and IPLed. BrightStor VM:Backup also offers the template programming interface (TPI), which allows you to work with backup and restore job template, exception, and exclusion files outside the BrightStor VM:Backup system administrator screens. Options are sometimes available through TPI that are not availablethroughthescreens.forexample,the incremental restore job template files you create for disaster recovery must include the CUTOFF record, which is available only through TPI. Setting Up HiDRO Setting up HiDRO for disaster recovery includes these steps: " Making an IPLable copy of HiDRO " Creating the VMIMAGE userid " Identifying system packs " Defining cycles of offsite tapes " Defining the VMIMAGE backups HDR Preparing Your Disaster Recovery Plan 5

18 Make an IPLable Copy of HiDRO The SYBGENI utility, run during HiDRO installation, makes an IPLable copy of HiDRO. You should run SYBGENI again each time you apply maintenance or if you modify the HiDRO system defaults. Also, you should have at least two IPLable tapes of HiDRO, one for remote site disaster recovery and one for home site use (in case you need to restore a system pack when the system is not available). You must make each copy using SYBGENI, because you cannot duplicate HiDRO IPLable tapes. Follow these steps to make a HiDRO IPLable tape: 1. Log on to the HIDRO service virtual machine. 2. Press PF3 and quit to CMS. 3. Enter the following command to attach a tape drive to the HIDRO userid at virtual address 181, where raddr is the tape drive s real address: attach raddr to * as Mount an unlabeled scratch tape. This tape must not be specified in any of the pools in the HiDRO Tape Pool Manager. 5. Enter the following command to display the SYBGENI Generate Stand Alone IPL Module screen (IPL001): sybgeni 6 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

19 S Y B G E N I Generate Stand Alone IPL Module ======> Menu IPL Generate IPLable copy of HiDRO for : TAPE Address of printer to use for HiDRO log : List of addresses HiDRO will test for the system console = Help 7 = 2 = Generate 8 = 3 = Quit 9 = 4 = 10 = 5 = 11 = 6 = 12 = Command===> Figure 1. SYBGENI Generate Stand Alone IPL Module Screen (IPL001) 6. Update the SYBGENI Generate Stand Alone IPL Module screen and generate the IPLable tape. The screen is divided into three sections, as described below. - The first section contains one field that specifies that SYBGENI will create the IPLable copy on tape. You cannot change this field. - In the middle section, specify a real printer address to generate a hardcopy of the HiDRO log during standalone processing. HiDRO logs are useful for documentation purposes. If you plan to IPL HiDRO without a VM system, set this address to the hardware address of a system printer. If you plan to IPL HiDRO under VM (second level), find out the address of the virtual printer on the virtual machine on which HiDRO is IPLed (usually 00E). Set the real printer address to the virtual printer s address. HDR Preparing Your Disaster Recovery Plan 7

20 You can also specify a real printer address at runtime or using the SYSPRINT immediate command. If you not specify a printer address using one of these three methods, HiDRO does not generate the log. - In the bottom section of the screen, you can specify up to 10 console addresses. HiDRO looks for the system console among these consoles when you IPL. Specify only valid console addresses; if you use invalid console addresses or DASD addresses, you might get unpredicable results. If HiDRO cannot find a console address among those listed on this screen when you IPL, it will pause. Press the REQUEST key on your real system console to tell HiDRO where the system console is. If you are IPLing from a 3279, press ALT and SYSREQ simultaneously to generate an interrupt. After you update this screen, press PF2 to generate the IPLable tape. SYBGENI writes two HiDRO IPLable images to the tape, separated by a tape mark. The first image contains an IPLable copy of the current version of the HIDRO module. The second image contains an IPLable copy of the HIDRO module at the time of the most recent maintenance release. The second image is followed by two tape marks. Identify System Packs System packs are the full-pack minidisks that contain the VM operating system and the system areas, utilities, and files that facilitate the restore of non-system data once VM is running. Note: To IPL your VM operating system, sufficient space must be allocated on the system packs for VM areas (page, spool, temporary disk, and so on). Usually, the system packs include all packs that are CP-owned. In the context of disaster recovery with HiDRO, system packs also include the pack that contains the VMIMAGE 191 minidisk. The VMIMAGE 191 minidisk contains all HiDRO code, as well as generated restore commands and utility EXECs for use at the remote site. Identify and make note of the VMIMAGE minidisks that are system packs. You will need these addresses later when you create the VMIMAGE userid and when you define the VMIMAGE backups. You can also include all BrightStor VM:Backup minidisks, all HiDRO mindisks, all BrightStor VM:Tape minidisks, the VMRMAINT userid s minidisks, your security manager s minidisks, and any other minidisks or userids that will make recovering your system easier. It is not necessary to include the pack that contains the HIDRO 191 minidisk. Note: VMRMAINT s 192 minidisk contains the CALMP KEYS file that is required for BrightStor VM:Backup to be properly licensed. Without the proper LMP key, warning messages will be generated for each BrightStor VM:Backup command that is issued throughout the restore process; however, the product operation is not affected. For more information anout LMP keys, see the CA-VM:Manager Reference Guide. 8 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

21 Create the VMIMAGE Userid To easily control the full-pack definitions you are using for the disaster recovery backups, the VMIMAGE utility requires that you create a userid called VMIMAGE. The VMIMAGE userid s CP directory must include the following: " An MDISK statement for each full-pack minidisk you want HiDRO to back up. Do not include minidisks defined to SFS file pools. A physical backup of SFS domains might include a corrupt catalog structure because users might be changing the catalog while you are running the backup. Do not include guest operating systems that cannot be suspended or shut down for the duration of the backup. Use a guest-specific backup mechanism to back up those guest operating systems. " A statement that defines the VMIMAGE 191 minidisk as residing on one of the system packs and including at least the equivalent of 30 cylinders of 3380 DASD or 25 cylinders of 3390 DASD. " A statement setting the virtual machine size to at least 128 MB. Restores of HiDRO at the remote site will run on the VMIMAGE virtual machine. You can simplify the restore process by making the unit addresses in the VMIMAGE directory entry identical to the real addresses on your system. (See Automating ATTACHes on page 26.) HDR Preparing Your Disaster Recovery Plan 9

22 The following is a sample VMIMAGE CP directory entry: * * Sample directory entry for VMIMAGE machine setup. * * Please, replace all place holders with * installation-dependent * information and insert the entries into the source * directory. * * * * * VMIMAGE USERID * * * USER VMIMAGE VMIMAGE 128M 512M BG * * Enable the next line if running under VM/XA SP or VM/ESA OPTION LNKNOPAS * IPL CMS * CONSOLE M OPERATOR SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH X SPOOL 00E 3202 M * LINK MAINT RR LINK MAINT D RR LINK MAINT 19E 19E RR * * Replace the default Object Directory address (MAINT 123), * if it is different for your installation LINK MAINT RR * LINK HIDRO RR LINK HIDRO 1FF 1FF RR * MDISK VMSRES MR RIMAGE WIMAGE MIMAGE * * Substitute the real pack addresses in the following statements. * Make sure to include the system packs. MDISK VMSRES MR MDISK MR MDISK MR MDISK MR MDISK MR MDISK MR MDISK MR MDISK MR MDISK MR Define Cycles of Offsite Tapes To facilitate cycling of tapes offsite, the VMIMAGE utility requires you to define pairs of physical and logical tape pools for disaster recovery backups. The logical pool in each pair draws tapes from the physical pool in that pair. The names of each pair of physical and logical pools must match, and the name must be VMIMAGEn. Name the physical and logical pools in the first pair VMIMAGE1. If you create a second pair, name the physical and logical pools in the second pair VMIMAGE2, and so on. The numbering scheme must begin with 1 and subsequent numbers must be consecutive. 10 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

23 If you use a tape manager and you accepted the HiDRO default SCRATCH ALWAYS during tape manager installation, you will set up one pair of pools. If you are not using an external tape manager, you will set up more than one pair of pools. TocreatethespecialHiDROtapepoolsforuseonly for disaster recovery backups, follow these steps: 1. Log on to the HIDRO service virtual machine. 2. AttheHiDROMachineMainMenu,pressPF5,thenPF6toaccesstheTapePool Manager. 3. If you are using an external tape manager and the installation default SCRATCH is set to ALWAYS, create one physical pool and one logical pool and name them both VMIMAGE1.SpecifyBASEasthebackuptype.Thefollowingtableshowsasample pool setup. Physical Pools Logical Pools Backup Type Incremental Type VMIMAGE1 VMIMAGE1 BASE - Make sure the RECYCLE event with the DELETE option is scheduled to run before every backup taken by VMIMAGE or HiDRO. The RECYCLE event clears scratched tapes from the physical pools. If you are using an external tape manager but the installation default SCRATCH is set to YES or NO, or if you are not using an external tape manager, follow these steps: a. Create at least two pairs of physical and logical pools. Name the first pair VMIMAGE1, the second pair VMIMAGE2, and so on. Specify BASE as the backup type. The following table shows a sample pool setup. Physical Pools Logical Pools Backup Type Incremental Type VMIMAGE1 VMIMAGE1 BASE - VMIMAGE2 VMIMAGE2 BASE - Make sure the retention period on each logical pool is long enough for you to always have at least one set of unexpired VMIMAGEn tapes. (Ordinarily, all VMIMAGEn pools have the same retention period.) b. To each physical pool, add at least enough tapes to perform a complete backup of your system. VMIMAGE automatically rotates pairs of tape pools for you. For example, if you have two pairs of pools, HiDRO calls first for the free tapes in the VMIMAGE1 physical pool and places them in the VMIMAGE1 logical pool when they are used in the VMIMAGE1 backup. During the second VMIMAGE backup, HiDRO prompts for the tapes in the VMIMAGE2 physical pool and uses tapes from the VMIMAGE2 physical pool. HiDRO uses VMIMAGE1 during the third backup, and so forth. HDR Preparing Your Disaster Recovery Plan 11

24 After a VMIMAGE backup, send all tapes in the physical pools that were used in the backup offsite. Sending all tapes eliminates the need to determine which tapes were actually used each time VMIMAGE is run. Less operator intervention is required and you are less likely to send the wrong tapes. 4. Exit the tape pool manager. Define the VMIMAGE Backups (VMIMAGE SETUP) You define the VMIMAGE backups on the SYBMON machine by running the VMIMAGE utility with the SETUP parameter. VMIMAGE SETUP checks that all VMIMAGE pools have been defined and allows you to identify the VMIMAGE minidisks considered to be system packs. Follow these steps to run VMIMAGE SETUP: 1. Log on to the SYBMON machine and press ENTER. 2. PressPF3twicetoquittoCMS. WARNING: Do not define the VMIMAGE backups using the Define/Change Backups function on the SYBMON Machine Main Menu. Doing so would cause HiDRO to run an incorrect version of the VMIMAGE utility. 3. Enter the following command: vmimage setup 4. The utility prompts you for the VMIMAGE minidisk addresses of your system packs. Enter the minidisk addresses you recorded in the Identifying System Packs section on page 8. It is only necessary to define the VMIMAGE backups once, unless your system changes. If minidisk addresses or VMIMAGE pool definitions change, you will need to redefine the VMIMAGE backups. For information on updating VMIMAGE definitions and increasing the number of VMIMAGE pools, refer to the Hot Site Disaster Recovery chapter in the BrightStor VM:Backup HiDRO Administrator s Guide. Setting Up BrightStor VM:Backup Setting up BrightStor VM:Backup for disaster recovery includes these steps: " Creating full and incremental backup job template files " Creating a template file that will back up BrightStor VM:Backup " Creating a copy of the VMBRITS utility on tape " Creating template files that will restore from full and incremental BrightStor VM:Backup backups 12 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

25 Create Full and Incremental Backup Job Templates The Managing Backup Job Template Files chapter of the BrightStor VM:Backup System Administrator s Guide explains how to create backup job templates. This section provides additional information relating specifically to disaster recovery. " When creating the weekly BrightStor VM:Backup logical full backup job template, make sure that it: - Includes user minidisks, SFS and BFS file pools, and the 191 minidisk for each SFS file pool on your system. - Excludes full-pack minidisks and minidisks defined to SFS file pools. (VMIMAGE will back up these minidisks.) " In this guide, you will back up your SFS file pools separately from your other CMS data. You must therefore create two full backup job template files and two incremental job template files. Be sure to base the SFS incremental backup on the SFS full backup, and base the CMS incremental on the CMS full backup. " If you need to exclude domains referenced in a backup job template file, you must create an exclusion file. For example, you have set up a template file that will back up all minidisks for userid DAGNY. However, that userid has one minidisk you do not want to back up. You would specify the minidisk to exclude in an exclusion file. " If a specific domain requires special processing, you must create an exception file. For example, you have set up a template that will back up all minidisks for userid JGALT in logical format. Even though JGALT s 197 disk is CMS, you want to back up the 197 minidisk in physical format. You would specify that exceptional processing in an exception file. For information on creating exception and exclusion files, refer to the Managing Exception and Exclusion Files chapter in the BrightStor VM:Backup System Administrator s Guide. Create a Backup Job Template for Backing Up BrightStor VM:Backup Define one backup job template file to back up all BrightStor VM:Backup system minidisks. You cannot specify any other userids or minidisks in this file. Because the VMBRITS utility can only restore data backed up in CMS format, you must specify the logical backup format in this file. (This setting does not affect the CHECKDISK minidisk, which is automatically backed up physically because it is a CMS-reserved minidisk.) VMBACKUP TEMPDIST, located on the BrightStor VM:Backup 192 minidisk, is a sample backup job template file that backs up BrightStor VM:Backup system minidisks. This file was included on the distribution tape. To use VMBACKUP TEMPDIST, copy the file to the BrightStor VM:Backup A-disk, rename it VMBACKUP TEMPLATE, and modify it as necessary. Refer to the Managing Backup Job Templates chapter in the BrightStor VM:Backup System Administrator s Guide for more information about backing up BrightStor VM:Backup system minidisks. HDR Preparing Your Disaster Recovery Plan 13

26 Ignored Processing Options To makes sure it never takes an inconsistent backup of itself, BrightStor VM:Backup ignores certain processing options, even if you specify them. When backing itself up, BrightStor VM:Backup: " Does not create catalog files. BrightStor VM:Backup cannot write to the catalog minidiskatthesametimeitistryingtobackuptheminidisk. " Always performs a full backup. BrightStor VM:Backup cannot detect incremental changes that occurred since a previous system backup because the backup job does not create a catalog. " Ignores specifications in the exception file associated with the backup job template file to quiesce minidisks or to use encryption. " Does not create keyword data reports. BrightStor VM:Backup cannot write to the reportminidiskatthesametimeitistryingtobackuptheminidisk. " Always runs with the EXCLUSIVE option set on. No other job can run while BrightStor VM:Backup is taking a backup of itself. Backup Tapes As with other backup jobs, BrightStor VM:Backup updates the resource pools for the tapes used during a BrightStor VM:Backup system backup at the end of the job. If the interface to BrightStor VM:Tape is used, the BrightStor VM:Tape TMC is also updated. You cannot use a DASDtape to back up BrightStor VM:Backup. Create a Copy of the VMBRITS Utility The VMBRITS utility, running under CMS, restores all BrightStor VM:Backup system minidisks backed up in CMS format. You can also use it to restore from an incomplete tape set if necessary. To create a tape that includes this utility, load the VMBRITS EXEC file and the READLREC MODULE file onto a tape. Both of these files reside on the BrightStor VM:Backup 192 minidisk. Create CMS Restore Job Templates For instructions on creating restore job template files that restore CMS data from incremental backups, refer to the TPI Files for Restore Jobs part of the BrightStor VM:Backup Template Programming Interface Guide. BrightStor VM:Backup performs an incremental-only restore of a minidisk from a backup cycle when you build a CATSEARCH or VOLSEARCH restore job using TPI, and specify acutoffrecord. 14 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

27 Example Today is January 8. Full physical and logical backups were taken on January 1, and an incremental backup was taken on each of the next six days (January 2 through 7) based on the full logical backup. You want to restore the basic system from the physical full-pack backups, then apply the incremental changes from the incremental logical backups. 1. Restore your entire basic system as of January 1 using your full physical backups. 2. Use TPI to build a restore job. The job must include the following record: CUTOFF 01/02/97 00:00:00 Refer to the BrightStor VM:Backup Template Programming Interface Guide for information about building and submitting TPI jobs and for more information about the CUTOFF record. 3. Enter this command to import the incremental restore template file to the BrightStor VM:Backup 191 minidisk: vmbackup import templatename $templat (replace Note: You will need to modify this template at your disaster recovery site. Create SFS Restore Job Templates You are not required to create the restore templates for SFS filepools. The System Administrator Main Menu in BrightStor VM:Backup provides this function. From the System Administrator Main Menu: 1. Select option 7, Submit special SFS/BFS restores. The Submit Special SFS/BFS Restores menu appears. 2. Select option 3, Restore a file pool or user storage groups in a file pool. TheRestore a File Pool menu appears. For more information on starting special SFS and BFS restores, see the BrightStor VM:Backup System Administrator s Guide. If you will be restoring BrightStor VM:Migrate, be sure to include the SKIP option. This option prevents BrightStor VM:Backup from restoring file spaces that already exist in the file pool. Also, consider whether you want BrightStor VM:Backup to issue the CMS command ENROLL PUBLIC for the file pool (in TPI, INCLUDE PUBLIC record). Issuing the ENROLL PUBLIC command is one of two actions required to enable users not enrolled in a particular file pool to access files and directories of users who are enrolled in that file HDR Preparing Your Disaster Recovery Plan 15

28 pool. The other required action is for the users who are enrolled in the file pool to grant access to their files and directories to either PUBLIC or the users who are not enrolled in the file pool. Refer to the IBM SFS and CRR Planning, Administration, and Operation publication for detailed information on the ENROLL PUBLIC command. 16 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

29 Chapter 3 Creating Your Disaster Recovery Backups Once you have set up HiDRO, BrightStor VM:Backup, and your disaster recovery plan, you can create your disaster recovery backups using the procedure described in this chapter. Note: The disaster recovery procedures in this chapter are based on one possible scenario for disaster recovery. You must tailor your disaster recovery procedures to your own site. Creating the Backups The following procedure uses the HiDRO VMIMAGE utility and runs the BrightStor VM:Backup CMS backup separately from the BrightStor VM:Backup SFS backup. 1. At some point when your system load is fairly light (for example, Friday night), run your weekly BrightStor VM:Backup CMS full logical backups and SFS full logical backups. From CMS, enter this command for each backup, where templatename is the nameofthetemplateyoucreated: vmbackup submit templatename 2. After the backups complete, review the jobs VMBACKUP NOTE files for processing errors. If the backups completed successfully, enter this command to back up BrightStor VM:Backup, where templatename is the name of the template you created to back up BrightStor VM:Backup: vmbackup submit templatename After the backup job completes, review the job s VMBACKUP NOTE files for processing errors. 3. On the following day (in this scenario, Saturday), run the HiDRO VMIMAGE BACKUP utility. Enter this command: smsg sybmon cmd vmimage backup WARNING: You must run the VMIMAGE BACKUP utility before you run the VMIMAGE SYSTEM utility, because the VMIMAGE SYSTEM utility uses information generated by the VMIMAGE BACKUP utility. HDR Creating Your Disaster Recovery Backups 17

30 The backup job can generate several output files: a log file (VMIMAGEn LGmmddyy), a failed commands file (VMIMAGEn FCmmddyy), and a summary file (VMIMAGEn SMmmddyy). Check the VMIMAGEn LGmmddyy file; if any tasks did not complete successfully, follow these steps: a. Look in the VMIMAGEn FCmmddyy file for information about the problems. b. Correct the problems. c. Use the SENDFILE command to send the VMIMAGE n FCmmddyy file to the SYBMON machine. SYBMON restarts the job and runs the tasks that are in the FCmmddyy file. WARNING: Do not run VMIMAGE BACKUP more than once before running VMIMAGE SYSTEM. Doing so could cause the VMIMAGE SYSTEM utility to generate incorrect restore commands or to use the wrong tape pool. If you misplace the failed commands file, start the VMIMAGE SYSTEM utility, cancel it, and then rerun VMIMAGE BACKUP. Print the VMIMAGEn SMmmddyy file and any summary files generated when you submitted failed commands. Refer to the Running Backups chapter of the BrightStor VM:Backup HiDRO Administrator s Guide for more information about the log, failed commands, and summary files. 4. After the VMIMAGE BACKUP utility completes successfully, run the VMIMAGE SYSTEM utility. Enter this command: smsg sybmon cmd vmimage system After the VMIMAGE SYSTEM utility ends, check the output files as described in the previous step to determine whether the VMIMAGE SYSTEM utility completed successfully. Then print the VMIMAGEn LGmmddyy file, the VMIMAGEn SMmmddyy file, and any log and summary files generated when you submitted failed commands. The VMIMAGEn SMmmddyy file lists the volsers of the tapes that contain backups of your system packs and the HIDRO A-disk; you will need this list when you recover your system. 5. On the following day (in this scenario, Sunday): - Run a BrightStor VM:Backup CMS incremental logical backup. Base this backup on the BrightStor VM:Backup CMS full backup and any incremental backups taken after the full. - Then run a BrightStor VM:Backup SFS incremental logical backup based on the BrightStor VM:Backup SFS full backup. Enter this command for each: vmbackup submit templatename 18 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

31 6. After the backups complete, review the jobs VMBACKUP NOTE files for processing errors. If the backups completed successfully, back up BrightStor VM:Backup again. 7. Repeat steps 5 and 6 each day until the day on which you run the next BrightStor VM:Backup full backup. Assembling Your Disaster Recovery Package to Send Offsite You should include these items in your disaster recovery package: " At least one IPLable HiDRO tape. " The backup tapes from the VMIMAGE BACKUP and SYSTEM utilities. (If you want multiple copies of your VMIMAGE backups, you can run the HiDRO physical backups again, or you can copy the backups using the HiDRO DUPLICATE operation, explained in TheDuplicateOperationchapter of the BrightStor VM:Backup HiDRO Command Reference Guide.) " The backup tape containing the backup of BrightStor VM:Backup. " The tapes containing all BrightStor VM:Backup full and incremental backups. " The tape containing the NSS files and spool files you will need to recover your system, especially the CMS NSS file. " An IPLable ICKDSF tape. This tape allows you to initialize and prepare DASD volumes for a standalone disaster recovery. " The tape containing the copy of the BrightStor VM:Backup VMBRITS utility (includes the VMBRITS EXEC and READLREC MODULE files). " A map of your CP directory. " Hardcopies of: - The log file (VMIMAGEn LGmmddyy), the summary file (VMIMAGEn SMmmddyy), and log and summary files generated when you submitted failed commands after running the VMIMAGE SYSTEM utility. - The summary file (VMIMAGEn SMmmddyy) from the VMIMAGE BACKUP utility step. - Optionally, a printed copy of the VMIMAGE RESTCMDS file; this file, located on the VMIMAGE 191 minidisk, contains the restore commands generated by the VMIMAGE SYSTEM utility. " A copy of the BrightStor VM:Backup and HiDRO manuals. " Emergency LMP keys obtained from Computer Associates. HDR Creating Your Disaster Recovery Backups 19

32 20 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

33 Chapter 4 Recovering from a Disaster This chapter describes how to use HiDRO and BrightStor VM:Backup to recover from loss of critical system components, as follows: " Restore your system packs using HiDRO " Restore the rest of your system using BrightStor VM:Backup " Use BrightStor VM:Backup more efficiently Note: The disaster recovery procedures in this chapter are based on one possible scenario for disaster recovery. You must tailor your disaster recovery procedures to your own site. Restoring Your System Packs Using HiDRO This section explains how to restore your system packs when VM is not available and when VM is available. It also describes how to increase the efficiency of the HiDRO restore process by automating DASD volume and tape drive attaches. Restore System Packs: VM Not Available When VM is not available at a site, follow these basic steps to restore system packs: " IPLing HiDRO " Restoring system packs " Replacing your CP nucleus (optional) " IPLing VM " Attaching DASD volumes and tape drives " Restoring DASD volumes During this restore process, you will use HiDRO in standalone mode to restore your system packs. Follow these steps: 1. Mount the IPLable tape of HiDRO you created using the SYBGENI utility and IPL HiDRO from that tape. HiDRO automatically uses the system console whose unit address was specified when you ran SYBGENI. If the unit address was not specified or was specified incorrectly, press the REQUEST or ENTER key; HiDRO determines the address of the system console and issues prompts to that device. If your time-of-day (TOD) clock HDR Recovering from a Disaster 21

34 needs to be reset, HiDRO prompts you for that information. HiDRO then displays the following message: 0 SYBCTL095I AWAITING CONSOLE RESPONSE, ADDRESS 0009; STATUS: IDLE 2. Restore each system pack by entering this RESTORE command: ruraddr 1 to u raddr 2 (ivol (volser 1 volser 2...volser n ) itape (unl) Substitutable raddr 1 raddr 2 volser 1 volser 2...volser n Specifies Real address of the tape drive on which to mount the tapes containing the backup of the system pack Real address of the DASD volume to which to restore the system pack Volsers of the tapes containing the backup of the system pack HiDRO prompts for and restores from the backup tapes in the exact order you specify, so be sure to specify the volsers of the tapes in the order in which the tapes were used during the backup. The volsers are listed at the end of the VMIMAGE SYSTEM utility s VMIMAGEn LGmmddyy and VMIMAGEn SMmmddyy files. 3. IPL the operating system you just restored in the simplest state possible. Do not autolog any service virtual machines and do not activate the security system. 4. Restore the CMS NSS you backed up previously (see Assembling Your Disaster Recovery Package to Send Offsite page 19). 5. Log on to the VMIMAGE userid. Attach to the userid all remaining full-pack DASD volumes you need to restore. Attach each volume as the virtual address specified in the VMIMAGE userid s CP directory entry for the volume. (The VMIMAGE SYSTEM utility used the virtual addresses specified in the directory entry when it generated the RESTORE command for each volume.) Determine which tape drives you want to use in the restore and attach them to the VMIMAGE userid. The number of packs you can restore concurrently depends on the virtual machine size of the VMIMAGE userid. For information on simplifying this step, refer to Automating DASD Volume and Tape Drive Attaches on page Restore the full-pack DASD volumes using the HiDRO DRESTORE utility, described on page Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

35 Restore System Packs: VM Available When VM is available at a site, follow these basic steps to restore system packs: " IPLing HiDRO " Attaching DASD volumes and tape drives " Restoring DASD volumes Follow these steps to perform a warm site restore: 1. Log on to a userid (for example, MAINT) on the starter system. Make sure the userid has the following characteristics: - Class B privileges to execute the required DASD volume and tape drive attaches. - A virtual machine large enough to support the number of tape drives you want to use. (OPCORE, the memory needed to run a single restore task, is by default 1392K, but this default might have been changed at your shop.) - A permanent disk with at least 30 cylinders, to accommodate the VMIMAGE 191 minidisk. Do not use a temporary disk because if CP abended, or were shut down, you would lose checkpoint capability. In addition, make sure there is another userid you can use as an OPERATOR userid. 2. Attach a tape drive at virtual address 181. Mount the IPLable tape of HiDRO you created using the SYBGENI utility and IPL HiDRO from the tape. HiDRO displays the following message: 0 SYBCTL095I AWAITING CONSOLE RESPONSE, ADDRESS 0009; STATUS: IDLE 3. Mount the backup tape created by the VMIMAGE SYSTEM utility at virtual address 181. Enter this command to restore the VMIMAGE 191 minidisk from that tape to the permanent minidisk you defined in step 1: r u 181 to u vaddr (ivol volser itape (unl) Substitutable vaddr volser Specifies Virtual address of the permanent minidisk Volser of the backup tape 4. Determine which full-pack DASD volumes you need to restore and attach them to the userid you are logged onto. Attach each volume as the virtual address specified in the userid s CP directory entry for the volume. (The VMIMAGE SYSTEM utility used the virtual addresses specified in the directory entry when it created the RESTORE command for each volume.) Determine which tape drives you want to use in the restore and attach them to the userid you are logged onto. The number of packs you can restore concurrently depends on the virtual machine size of the VMIMAGE userid. HDR Recovering from a Disaster 23

36 For information on simplifying this step, refer to Automating DASD Volume and Tape Drive Attaches on page Restore the full-pack DASD volumes using the DRESTORE utility, described below. DRESTORE Utility The HiDRO DRESTORE utility processes the RESTORE commands in the VMIMAGE RESTCMDS file created during the VMIMAGE SYSTEM utility step. DRESTORE maintains a checkpoint restart file and manages any failed commands produced during the recovery. If the VM operating system or the service virtual machine running the restores abends or is shut down during the restore, DRESTORE ensures a smooth recovery of the restore process. DRESTORE [ GLOBAL option 1...option n ] You can specify any global options except SYSPRINT, USERCLASS, and CONCLASS. (See the BrightStor VM:Backup HiDRO Command Reference Guide for more information.) The two global options described below are commonly used with DRESTORE: Syntax OPERATOR operator-id MAXTAPE n, wheren is maximum number of tape drives to use Function Specify this option if the userid of the operator at the remote site differs from the OPERATOR userid in the HiDRO installation defaults Specifythisoptionifyouwanttousemoretapedrives than are specified for MAXTAPE in the HiDRO installation defaults 24 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

37 When you run the DRESTORE utility, the following menu displays: Select from the HIGHLIGHTED files and ENTER selection NUMBER of file to USE or Q to QUIT 1 VMIMAGE RESTCMDS A 2 CHKPT SYSIN A 3 FAILED COMMANDS A 4 FAILED DRESTORE A Q to QUIT DRESTORE Restore from the beginning (First time) To restart an interrupted job (System Restart) Retry failed restores; CHKPT SYSIN A also processed To use the ACCUMULATED failed jobs; FAILED COMMANDS A also processed To exit to CMS The first time you start DRESTORE, enter 1. For later restarts pick the appropriate choice. Figure 2. DRESTORE Menu As the instructions at the bottom of the screen indicate, you should enter 1 for the first execution of DRESTORE so that HiDRO uses only the VMIMAGE RESTCMDS file. If any failures occur, enter 2, 3, or4 for subsequent executions. While DRESTORE is running, the utility issues mount requests to the operator userid. You can use the summary file generated by the VMIMAGE BACKUP utility to pre-sort the backup tapes in the order DRESTORE will request them. If autoloaders are available, you can mount all tape volumes needed to restore a particular DASD volume when DRESTORE requests the first tape. HDR Recovering from a Disaster 25

38 Automate DASD and Tape Drive Attaches You can automate the process of attaching the volumes you want to restore and the tape drives you want to use in the restore by writing an EXEC that issues all the ATTACH commands. The syntax of the ATTACH command is: CP ATTACH raddr * vaddr For a DASD volume, substitute the following values: Substitutable Specifies raddr Real address of the volume to restore * Your userid vaddr Virtual address of the volume to restore as specified in the CP directory entry for the VMIMAGE userid For a tape drive, substitute the following values: Substitutable Specifies raddr Real address of the tape drive to attach * Your userid vaddr Virtual address at which HiDRO is to use the tape The EXEC should reside on the HiDRO 201 minidisk. The VMIMAGE SYSTEM utility copies it to the VMIMAGE 191 minidisk during the backup process. WARNING: Do not create the EXEC on the VMIMAGE 191 minidisk. The VMIMAGE SYSTEM utility reformats that minidisk each time it runs. 26 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

39 Restoring the Rest of Your System Using BrightStor VM:Backup This section explains how to: " Restore BrightStor VM:Backup using the VMBRITS utility " Restore CMS minidisk data not restored by HiDRO from incremental BrightStor VM:Backup backups " Restore SFS from the full and incremental BrightStor VM:Backup backups if you have SFS data Two variations on the methods described in this section can increase the speed with which you restore your system after a disaster: " Using more than one BrightStor VM:Backup restore machine " Backing up your catalog minidisk separately and using BrightStor VM:Backup to restore it See Using BrightStor VM:Backup Efficiently on page 30 for information on using these methods. Restore BrightStor VM:Backup Using VMBRITS Follow these steps to restore your BrightStor VM:Backup system using the VMBRITS utility: 1. Log on to the BrightStor VM:Backup service virtual machine. 2. Format the BrightStor VM:Backup system minidisks, as follows: format unit vaddr (blk blksize Substitutable vaddr blksize Specifies Virtual address of the minidisk to format Blocksize of the backed up minidisk The BrightStor VM:Backup system minidisks are as follows: Minidisk Typical virtual address Local 191 Program files 192 Catalog 1B0 Resource pool 1C0 System 1E0 (continued) HDR Recovering from a Disaster 27

40 Minidisk Report All DASDtape Typical virtual address 1E1 3. Use CMS to format and reserve the restart recovery (typically 1D1) minidisk as follows: format 1d1 filemode (blk 4096 reserve check point filemode 4. Attach a tape drive as virtual address To restore BrightStor VM:Backup, run the VMBRITS utility by entering: vmbrits VMBRITS prompts you to specify: - Userid and virtual address of the first minidisk to restore from tape. - Virtual address of a target minidisk to restore the minidisk to. The target minidiskmusthavethesameblocksizeasthesourceminidisk,andyoumust have read/write access to it. - The names of the files to restore. To restore the entire minidisk, enter **,then press ENTER without typing anything on the command line. VMBRITS then prompts you for the same information for the next minidisk to restore from tape. After you specify the final minidisk, press ENTER twice. VMBRITS prompts you to mount the tape containing the data to restore. Mount the tape and press ENTER again. VMBRITS starts scanning the tape for the requested data. When VMBRITS locates one of the specified minidisks, it restores the requested files. VMBRITS does not issue any messages if it cannot locate a minidisk; you must check the job report to verify that VMBRITS restored all requested minidisks. 6. Initialize BrightStor VM:Backup. Restore CMS Data Follow these steps to finish restoring your CMS minidisks by restoring their incremental changes: 1. Enter this command to export the CMS incremental restore job template file created andimportedearlier(seecreate CMS Restore Job Templates on page 14) from the BrightStor VM:Backup 191 minidisk to your 191 minidisk: vmbackup export templatename template 28 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

41 2. Modify the CUTOFF record in the template to specify the date on which you took the first incremental backup. For example, suppose today is January 8. Full physical and logical backups were taken on January 1, and an incremental backup was taken on each of the next six days (January 2 through 7) based on the previous day s backup. You would set the CUTOFF record as follows: CUTOFF 01/02/02 00:00:00 3. Enter this command to import the incremental restore template file back to the BrightStor VM:Backup 191 minidisk: vmbackup import templatename $templat (replace 4. Enter this command to submit the restore job, where templatename isthenameofthe CMS restore job template: vmbackup submit templatename Restore SFS Follow these steps to restore each of your SFS file pools. 1. Make sure these minidisks exist for the file pool service virtual machine: - Service virtual machine (191 minidisk) - Control minidisk - Two log minidisks - Catalog minidisks - User data minidisks 2. Enter this command to initialize the file pool from the file pool server console: fileserv generate 3. Enter this command to start the file pool server from the file pool server console: fileserv start 4. If your site uses BrightStor VM:Migrate to manage the file pools you are restoring, you must also restore file pools that contain BrightStor VM:Migrate program files and control data. Restore BrightStor VM:Migrate as follows: a. Restore the BrightStor VM:Migrate file space, the log file space, and, if your site uses a fast recall area, the fast recall area file space. b. Restore all minidisks and file spaces associated with BrightStor VM:Migrate. c. Initialize BrightStor VM:Migrate. HDR Recovering from a Disaster 29

42 5. From a BrightStor VM:Backup system administrator userid, enter this command to submit the job that will restore the rest of the file pool, where templatename is the name of the SFS full restore job template file: vmbackup submit templatename Using BrightStor VM:Backup Efficiently Variations on the methods described can increase the speed with which you restore your system after a disaster. You can do the following: " Use more than one BrightStor VM:Backup restore machine. " Back up your catalog minidisk separately and use BrightStor VM:Backup to restore it. Note: This section assumes that all files required to recover VM and the BrightStor VM:Backup system after a site disaster are stored on minidisks. Using Multiple BrightStor VM:Backup Restore Machines To speed up the restore process, you can set up multiple BrightStor VM:Backup service virtual machines and run them in restore-only mode. If a backup job is submitted to BrightStor VM:Backup while it is running in restore-only mode, BrightStor VM:Backup sends a message to the submitting userid explaining that the job cannot be run. Set up the restore-only BrightStor VM:Backup service virtual machines as explained in the steps below. Then access the catalog minidisk with a read-only link so the service virtual machines can share the catalog minidisk and process restore jobs, and reinitialize BrightStor VM:Backup. BrightStor VM:Backup can only initialize with the catalog minidisk linked read-only if index files already exist on the minidisk. If they do not exist, BrightStor VM:Backup will attempt to write them to the catalog minidisk, and initialization will fail. If you know that catalog index files do not exist, link the catalog minidisk read/write and initialize BrightStor VM:Backup; BrightStor VM:Backup will write the index files. Then shut down BrightStor VM:Backup and proceed with the instructions in this section to set up multiple restore-only machines. To set up restore-only service virtual machines, follow these steps: 1. Create multiple userids, using a standard naming convention, such as VMBRES01 and VMBRES02, with the same basic directory entry as BrightStor VM:Backup. In the directory entry for each of the userids you create, add LINK statements for each of the R/O minidisks listed below, and create minidisks for the R/W references: - R/O link to the BrightStor VM:Backup CATDISK at 1B0 - R/W CHECKDISK at 1D1 (one cylinder) - R/W POOLDISK at 1C0 (same size as BrightStor VM:Backup) 30 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

43 - R/W SYSDISK at 1E0 (same size as BrightStor VM:Backup) - R/W REPORTDISK at 1E1 (same size as BrightStor VM:Backup) - R/W 191 minidisk (same size as BrightStor VM:Backup) - R/O link to the BrightStor VM:Backup 192 minidisk as R/O link to VMRMAINT 192 minidisk as 1FF (for BrightStor VM:Backup LMP keys) For systems using BFS, add the following directory statement to the directory entry for each of the userids you create: IUCV *IDENT resid where resid specifies the unique name of the BrightStor VM:Backup restore machine you are creating. 2. For each restore machine userid you create, do the following: a. Link to the BrightStor VM:Backup 191 and 1C0 minidisks to copy the data from those disks during initialization. These links give the restore machines access to the VMBACKUP CONFIG file, any existing restore template files, and the BrightStor VM:Backup resource pools. Note: If this is not the first time you copied the files, be careful that the restore machine s PROFILE EXEC is not overlayed. b. The first time you copy the files, modify the PROFILE EXEC of each restore machine to initialize using the VMBSYS command instead of the VMISTART command. This eliminates the need to modify the existing VMRMAINT CONFIG file and VMSISTART COMMANDS file, and add MDISK files for the restore machines on the VMRMAINT userid. Also add a LINK to the BrightStor VM:Backup 191 and 1C0 minidisks. This will enable you to copy the files necessary each time you use these restore machines. c. If the VMRMAINT 192 disk is not linked as 1FF, the CALMP KEYS file is not available for your restore machines, and warning messages will be issued for each BrightStor VM:Backup command issues during the restore. If you do not have access to the CALMP KEYS file, you can add a 1FF minidisk and put the emergency LMP keys in the CALMP KEYS file. d. For systems using BFS, you must also modify the RESID record in the VMBACKUP CONFIG file on each restore machine s 191 so that the resid it specifies matches the resid specified on the IUCV *IDENT statement in directory entry for each restore machine userid you create. 3. Add the following records to the BrightStor VM:Tape VMTAPE CONFIG file: PRODUCT VMBACKUP VMBACKUP MASTER PRODUCT VMBACKUP VMBRES01 PRODUCT VMBACKUP VMBRES02 HDR Recovering from a Disaster 31

44 Add any other necessary PRODUCT VMBACKUP configuration file records. This allows BrightStor VM:Tape to communicate with each of the BrightStor VM:Backup restore machines. 4. Copy the VMBACKUP MODULE file located on the common disk (the VMRMAINT 193 minidisk) by entering the following commands: copyfile vmbackup module filemode vmbres01 = = ( olddate copyfile vmbackup module filemode vmbres02 = = ( olddate This allows you to communicate with each restore machine. Considerations To prevent a tape volser from being requested by two jobs at the same time by the same restore machine, you may want to restrict the number of concurrent restore jobs to one for each restore machine. You can do this on either the MULT configuration file record in the VMBACKUP CONFIG file or through the Manage Configuration Options system administrator function screens (refer to the BrightStor VM:Backup System Administrator s Guide). When setting up your restore machines, take into account the number of streams used by the backup jobs. For example, BrightStor VM:Backup may have assigned volumes to streams in the following arrangement during a backup job: Stream Volumes assigned 1 VMPK01 VMPK03 VMPK99 2 VMPK02 VMPK04 VMSRES 3 VMPK05 VMPK06 VMPK07 VMPK08 4 VMPK09 VMPK11 VMPK13 5 VMPK10 VMPK12 VMPK14 Use five restore machines, with each machine being responsible for restoring the volumes from one stream. If you do not use five machines, avoid multiple jobs that simultaneously restore minidisks that were backed up within the same stream. This prevents two or more restoremachinesfromaskingforthesametapeatthesametime. If you are not using BrightStor VM:Tape, assign tape drives to each machine to avoid channel contention. Restoring the Catalog Minidisk Separately Ifthecatalogminidiskislargeandrestoretimeiscritical,youcanspeeduptherecovery process by restoring the catalog minidisk separately from the other BrightStor VM:Backup system minidisks. Use BrightStor VM:Backup to restore the catalog minidisk. VMBCAT TEMPDIST, located on the BrightStor VM:Backup 192 minidisk, is a sample restore job template file that restores the catalog minidisk. This file was included on the distribution tape. To use VMBCAT TEMPDIST, copy the file to the BrightStor VM:Backup A-disk, rename it VMBCAT TEMPLATE, and modify it as necessary. 32 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

45 Follow these steps to restore the catalog minidisk: 1. Create a temporary catalog minidisk for BrightStor VM:Backup as follows: a. Define a one-cylinder TDISK at virtual address 185 and format it. b. Add an asterisk to the beginning of the CATDISK record in the VMBACKUP CONFIG file to comment it out. The record will look as follows: * CATDISK 1B0 c. Add this record to the VMBACKUP CONFIG file: CATDISK Then, enter: detach 1b0 3. Initialize BrightStor VM:Backup as usual. 4. Use the restore job template file VMBCAT TEMPLATE to restore the catalog minidisk from the tape. Make sure the job template file specifies the correct information. 5. When the restore job has completed, end BrightStor VM:Backup. In the VMBACKUP CONFIG file, delete the CATDISK 185 record and remove the asterisk from the * CATDISK 1B0 comment. The record will look as follows: CATDISK 1B0 6. Relink the 1B0 minidisk and make sure the catalog minidisk was restored intact. 7. Detach the temporary catalog minidisk at virtual address Reinitialize BrightStor VM:Backup. 9. Create restore job template files for the DASD volumes at your site and start the restore jobs. Performing Housekeeping Tasks You can now perform the housekeeping tasks that will restore your enterprise system to its usual level of functioning. For example, activate your security system, set up your RSCS links, and initialize guest operating systems. HDR Recovering from a Disaster 33

46 34 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

47 Index Numbers 3590 tape device support HiDRO, 1 VM:Backup, 1 B backup job templates, creating to backup VM:Backup, 13 backups, disaster recovery, creating, 17 BFS directory statement for restore-only machines, 31 RESID record for restore machines, 31 BFS restore job templates, creating, 15 Byte File System (BFS). See entries under BFS; SFS (Shared File System), restoring C CALMP KEYS file, 8, 31 catalog minidisk, backing up and restoring separately for disaster recovery, 32 CMS minidisks, restoring, 28 CMS NSS file, 19, 22 CMS restore job templates, creating, 14 conventions, examples, x CUTOFF record, example from incremental-only minidisk restore, 15 D DASD, automating attaches during restores, 26 directory entry, sample, VMIMAGE userid, 10 disaster recovery, ix disaster recovery package, items to include, 19 disaster recovery plan, general guidelines, 3 disaster recovery using VM:Backup backing up and restoring catalog minidisk separately, 32 using multiple restore machines, 30 ways to increase speed of recovery, 27, 30 disaster recovery using VMBRITS and VM:Backup using multiple restore machines, 30 ways to increase speed of recovery, 27, 30 disaster recovery using VMBSAR, VMBRITS, and VM:Backup, ICKDSF tape, 19 disaster recovery, hot site creating backup job template to backup VM:Backup, 13 creating CMS restore job templates, 14 creating copy of VMBRITS utility, 14 creating full and incremental backup job templates, 13 creating SFS restore job templates, 15 defining tape cycles, 10 defining VMIMAGE backups, 12 Plan, 3 preparing for, 17 VMIMAGE BACKUP,running, 17 DRESTORE utility menu, 25 HDR Index 35

48 syntax, 24 E examples conventions, x system responses and prompts, x user entries, x F full backup job templates, creating for VM:Backup, 13 H HiDRO 3590 support, 1 incorporating into single system, 4 installing, 1 recovering from disaster automating DASD and tape drive attaches, 26 restoring system packs, 21 setting up for disaster recovery creating VMIMAGE userid, 9 defining offsite tape cycles, 10 defining VMIMAGE backups, 12 identifying system packs, 8 making an IPLable copy of HiDRO, 6 overview, 5 special tape pools, 11 VM:Backup 3590 support, 1 installing, 1 I ignored processing options, VM:Backup, 14 incremental backup job templates, creating for VM:Backup, 13 incremental-only files, restoring, 14 incremental-only minidisk restores, sample CUTOFF record, 15 IPL001 screen, 7 IPLable copy of HiDRO, creating, 6 L LMP keys, 8, 19 M MAXTAPE, with DRESTORE, 24 minidisk restores, sample CUTOFF record from incremental-only restore, 15 multiple VM:Backup restore machines, 30 N normal HiDRO backup, to incorporate HiDRO, 4 notations, examples, x O offsite disaster recovery package, items to include, 19 offsite tape cycles, defining, 10 OPERATOR, with DRESTORE, 24 P POSIX. See SFS, BFS consoles, specifying in SYBGENI, 8 printers, specifying in SYBGENI, 7 R recovering from disaster HiDRO automating DASD and tape drive attaches, 26 restoring system packs, 21 housekeeping tasks, 33 VM:Backup, 21 overview, 27 restoring catalog minidisks separately, 32 restoring CMS minidisks, 28 restoring SFS, 29 restoring using VMBRITS, 27 references, x related documentation, x REQUEST Key, Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR

49 responses, x restore-only mode, during disaster recovery, 30 restoring, incremental-only files, 14 S screens DRETORE utility menu, 25 SYBGENI Generate Stand Alone IPL Module (IPL001), 7 SFS, restoring file pools, 29 SFS restore job templates, creating, 15 submitting, incremental-only restore jobs, 14 SYBGENI utility, 5 SYBGENI Generate Stand Alone IPL Module screen, 7 system packs identifying, 8 restoring VM available, 23 VM not available, 21 system responses and prompts, x T tape drives, automating attaches during restores, 26 tapes creating HiDRO tape pools, 11 pools for disaster recovery, 11 TPI, general, 5 U user entries, x utilities HiDRO DRESTORE, 24 SYBGENI, 5 VMIMAGE BACKUP, 5 VMIMAGE SYSTEM, 5 VM:Backup, VMBRITS, 5, 27 VMIMAGE BACKUP, 17 VMIMAGE SYSTEM, 17 V VM product publications, x VM:Backup ignored backup processing options, 14 incorporating into single system, 4 recovering from disaster overview, 27 restoring catalog minidisks separately, 32 restoring CMS minidisks, 28 restoring SFS, 29 restoring using VMBRITS, 27 running in restore-only mode, 30 setting up for disaster recovery creating backup job template to backup VM:Backup, 13 creating CMS restore job templates, 14 creating copy of VMBRITS utility, 14 creating full and incremental backup job templates, 13 creating SFS restore job templates, 15 creating SFS/BFS restore job templates, 15 overview, 12 system minidisks, 27 tapes to use for backing up VM:Backup, 14 usingefficientlyduringrestores,30 number of streams for backup streams, 32 VM:Backup Template Programming Interface. See TPI VMBRITS utility, 5 creating copy to restore VM:Backup, 14 restoring VM:Backup, 27, 28 VMBSAR utility, ix, 4 VMIMAGE 191 minidisk, 8 VMIMAGE BACKUP utility, 5 output files, 18 restrictions, 17, 18 running, 17 VMIMAGE backups, defining, 12 VMIMAGE RESTCMDS, 19 VMIMAGE SYSTEM utility, 5 output files, 18 restrictions, 17, 18 running, 18 VMIMAGE userid creating, 9 sample directory entry, 10 virtual machine size, 9 HDR Index 37

50 VMIMAGE utility SETUP parameter, 12 to incorporate HiDRO, 4 38 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR