CA VM:Backup for z/vm

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

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 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(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.

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... 10 Define the VMIMAGE Backups (VMIMAGE SETUP)... 12 Setting Up BrightStor VM:Backup... 12 Create Full and Incremental Backup Job Templates... 13 Create a Backup Job Template for Backing Up BrightStor VM:Backup... 13 Ignored Processing Options... 14 Backup Tapes... 14 Create a Copy of the VMBRITS Utility... 14 Create CMS Restore Job Templates... 14 Example... 15 Create SFS Restore Job Templates... 15 HDR02122.7 Contents iii

Chapter 3. Creating Your Disaster Recovery Backups Creating the Backups... 17 Assembling Your Disaster Recovery Package to Send Offsite... 19 Chapter 4. Recovering from a Disaster Restoring Your System Packs Using HiDRO... 21 Restore System Packs: VM Not Available... 21 Restore System Packs: VM Available... 23 DRESTORE Utility... 24 Automate DASD and Tape Drive Attaches... 26 Restoring the Rest of Your System Using BrightStor VM:Backup... 27 Restore BrightStor VM:Backup Using VMBRITS... 27 Restore CMS Data... 28 Restore SFS... 29 Using BrightStor VM:Backup Efficiently... 30 Using Multiple BrightStor VM:Backup Restore Machines... 30 Considerations... 32 Restoring the Catalog Minidisk Separately... 32 Performing Housekeeping Tasks... 33 Index iv Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR02122.7

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

vi Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR02122.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. HDR02122.7 Contents vii

viii Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR02122.7

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. HDR02122.7 Contents ix

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 SYS001 100 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 HDR02122.7

" 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 HDR02122.7 Contents xi

xii Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR02122.7

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. HDR02122.7 Installing BrightStor VM:Backup and HiDRO 1

2 Disaster Recovery Using BrightStor VM:Backup and HiDRO HDR02122.7

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. HDR02122.7 Preparing Your Disaster Recovery Plan 3

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 HDR02122.7

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 HDR02122.7 Preparing Your Disaster Recovery Plan 5

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 181 4. 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 HDR02122.7

S Y B G E N I Generate Stand Alone IPL Module ======> Menu IPL001 +-------------------------------------------------------+ 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 1 2 3 4 5 6 7 8 9 10 +-------------------------------------------------------+.............................. 1 = 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. HDR02122.7 Preparing Your Disaster Recovery Plan 7

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 HDR02122.7

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.) HDR02122.7 Preparing Your Disaster Recovery Plan 9

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 009 3215 M OPERATOR SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH X SPOOL 00E 3202 M * LINK MAINT 190 190 RR LINK MAINT 190 19D RR LINK MAINT 19E 19E RR * * Replace the default Object Directory address (MAINT 123), * if it is different for your installation LINK MAINT 123 123 RR * LINK HIDRO 191 391 RR LINK HIDRO 1FF 1FF RR * MDISK 191 3380... 0030 VMSRES MR RIMAGE WIMAGE MIMAGE * * Substitute the real pack addresses in the following statements. * Make sure to include the system packs. MDISK... 3390 000 2226 VMSRES MR MDISK... 3390 000 2226... MR MDISK... 3390 000 2226... MR MDISK... 3390 000 2226... MR MDISK... 3390 000 2226... MR MDISK... 3390 000 2226... MR MDISK... 3390 000 2226... MR MDISK... 3390 000 2226... MR MDISK... 3390 000 2226... 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 HDR02122.7

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. HDR02122.7 Preparing Your Disaster Recovery Plan 11