CA VM:Backup for z/VM Administrator Guide

CA VM:Backup™ for z/VM
Administrator Guide
Release 3.5
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
Chapter 1: About This Book
Example Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Naming Conventions for Shared File System Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Chapter 2: About BrightStor VM:Backup
Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Accessing and Leaving BrightStor VM:Backup Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Moving Through Screens and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Typing Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Using PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Using the Main Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Help With Screens and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Using Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Entering CMS and CP Commands From the BrightStor VM:Backup Service Virtual Machine . . . . . . .2-6
Entering BrightStor VM:Backup Commands From CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Entering BrightStor VM:Backup Commands From CP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Entering Commands from the BrightStor VM:Backup Service Virtual Machine . . . . . . . . . . . . . . . . . . .2-7
Entering Commands from BrightStor VM:Backup Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
Help With Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Pattern Matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Help With Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9
Chapter 3: Managing Configuration Options
Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1
Contents
iii
Defining Tape Handling Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Overriding Tape Expiration Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Detaching Tape Drives Between Mounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Specifying OS Data Set Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Specifying Wait Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Defining Job Processing Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
User ID to Receive Restore Tape Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
When to Process End-User Restore Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Default Restore Time Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
User to Receive Dumps for System Abends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Number of Jobs that Can Run Concurrently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Identifying SFS File Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Chapter 4: Managing Authorizations
Authorization Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authorizing User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying Message Routing Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1
4-2
4-2
4-3
4-3
4-3
Chapter 5: Managing Resource Pools
Suspending BrightStor VM:Backup Before Updating Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Suspending BrightStor VM:Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Resuming BrightStor VM:Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Resource Pool Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Superpools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Screen Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Creating Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Enhanced Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Device and Media Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Defining DASDtape Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Specifying Empty Pool Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Using the BrightStor VM:Tape Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Modifying Resource Pool Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Updating Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Adding Individual Tape Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Adding a Series of Tape Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Discarding Tape Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Moving Tape Volumes to Another Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
iv
Administrator Guide
Creating Superpools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
Adding DASDtape Resource Pools to a New Superpool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
Updating Superpools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
Discarding Resource Pools and Superpools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
Chapter 6: Managing Backup Job Template Files
Job Template File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1
Job Template File Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
Creating or Updating Backup Job Template Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Describing the Backup Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
Specifying the Backup Job Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
Specifying Catalog Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6
Specifying Output Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8
Specifying Change Detection for a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
Specifying Report Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14
Specifying Select Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16
Specifying Tape Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16
Specifying Input Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-17
Chapter 7: Managing Restore Job Template Files
Job Template File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1
Job Template File Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
Creating or Updating Restore Job Template Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
Describing the Restore Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4
Specifying the Restore Job Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4
Specifying the Search Time Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4
Specifying Starting Input Tape for VOLSEARCH Restore Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5
Specifying Report Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6
Specifying Select Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8
Specifying the Restore Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8
Specifying the Link Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Specifying Formatting Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
Specifying Source DASD Volumes or Source/Target DASD Volumes . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
Sample Restore Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15
Sample CATSEARCH Restore Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15
Sample Restore Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Sample CATSEARCH Restore Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Sample VOLSEARCH Restore Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17
Contents
v
Chapter 8: Managing Exception and Exclusion Files
Exception and Exclusion File Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Exception and Exclusion File Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Creating or Updating an Exception File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Describing the Exception File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Record Type and Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Include/Exclude List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Specifying Special Processing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Creating or Updating an Exclusion File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Describing the Exclusion File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Exclude DASD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Exclude File Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Exclude Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Chapter 9: Managing Existing Catalogs
Catalog File Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Screen Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking Catalog Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Condensing Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Condense All Associated Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup Schedule Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discarding Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discard All Associated Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing the Catalog Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overriding the Auto-Condense or Auto-Discard Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-1
9-2
9-3
9-3
9-3
9-4
9-4
9-4
9-4
9-5
9-5
9-5
9-6
9-6
Chapter 10: Starting Special SFS and BFS Restores
Restoring a File Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Source File Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Target File Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
Administrator Guide
10-1
10-2
10-2
10-2
Restoring a User Storage Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2
Source User Storage Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2
Target User Storage Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3
Restoring File Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3
Backup Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4
Restoring a File Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5
Source File Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5
Target File Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5
Restoring User Storage Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5
Restoring File Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-6
Backup Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7
Enroll Public . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7
Restoring BFS Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8
BFS Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8
Instructions for Restoring a BFS Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-9
Chapter 11: Performing Operator and User Functions
Performing Operator Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
Performing User Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3
Index
Contents
vii
Chapter
1
About This Book
This book was written for all system administrators who are responsible for
performing the following BrightStor® VM:Backup® functions:
■
Managing BrightStor VM:Backup daily operation
■
Controlling users' authorizations and access to BrightStor VM:Backup
■
Defining how BrightStor VM:Backup processes backups and restores
■
Starting Shared File System (SFS/BFS) restores
■
Creating or changing job template, exception, and exclusion files for backup
and restore jobs
This book assumes you are familiar with VM and CMS and that you know the
conventions for naming CMS files, Byte File System (BFS) files, Shared File System
(SFS) directories, and BFS directories. It also assumes that you are familiar with
BrightStor VM:Backup functions and that you understand how you want
BrightStor VM:Backup to run in your data center. If you are not familiar with these,
you may need help from someone who is.
The information in this book is organized by task and describes how to use the
BrightStor VM:Backup system administrator screens to perform system
administrator functions. Menus and screens are explained in the order of their
appearance on the System Administrator Main Menu.
This book is designed to be used with the Systems Programmer Reference, which
explains BrightStor VM:Backup and its administration. The Systems Programmer
Reference 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.
About This Book
1–1
Example Conventions
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 may differ slightly from what appears on your screen.
Bold characters represent user entries. If the entry is a command, it appears in
lowercase letters even though you can enter commands in either upper or lower
case. A command you enter looks like this:
vmbackup cancel 10
Uppercase, nonbold characters represent system responses or prompts. A system
response looks like this:
RESTORE REQUEST 00000010 HAS BEEN CANCELED.
Naming Conventions for Shared File System Objects
The Shared File System supports two types of file spaces, directories, and files. For
clarity, this book refers to Shared File System objects in the following way:
Naming Conventions for Shared File System Objects .
1–2
Objects
Description
SFS file
Shared File System (SFS) file
BFS file
Byte File System (BFS) file
SFS directory
Directory that contains CMS files, authorizations, and aliases
BFS directory
Directory that contains BFS files, links, and other POSIX objects
SFS file space
File space that contains SFS directories, CMS files,
authorizations, and aliases
BFS file space
File space that contains BFS directories, BFS files, links, and other
POSIX objects
Administrator Guide
Chapter
2
About BrightStor VM:Backup
BrightStor VM:Backup is a full-screen data backup and restore system for VM. To
help you administer backup and restore jobs, BrightStor VM:Backup:
■
■
■
■
■
■
Allows you to use full-screen displays to define local operating controls, such
as granting user authorizations or managing the tapes used in backup jobs
Allows you to use full-screen displays to create jobs
Selectively backs up and restores CMS files or minidisks, or backs up and
restores entire DASD volumes
Selectively backs up and restores non-CMS minidisks, or specific tracks and
blocks on such minidisks
Selectively backs up and restores Shared File System (SFS) user storage
groups, SFS file spaces and directories, and BFS file spaces, selectively restores
BFS directories, or backs up and restores entire file pools
Runs multiple backup, restore, AUTOCAT, merge/purge/copy (MPC), and
tape reinitialization (REINIT) jobs concurrently
■
Restarts jobs after an abnormal system termination
■
Automatically recovers from temporary or correctable tape I/O errors
■
Restarts jobs automatically after permanent tape I/O errors
■
Automatically manages its own minidisk space
■
Backs up data to DASDtape and to physical reels and cartridges
■
■
Automatically selects the tapes needed for backup jobs and asks the operator
to mount them; for improved backup data protection, BrightStor VM:Backup
also allows BrightStor® VM:Tape® to select tapes for BrightStor VM:Backup
jobs
Creates copies of backup tapes for offsite disaster recovery
About BrightStor VM:Backup
2–1
Authorizations
Authorizations
You must be authorized as a system administrator in the BrightStor VM:Backup
system to perform the tasks and enter the commands described in this book. If you
have System Administrator authorization, you are authorized automatically to
perform user and operator restore functions.
Hardware and Software Requirements
You can access BrightStor VM:Backup through screens or line-mode commands. If
you have a display or full-screen (3270-type) terminal with a minimum of 24 lines,
you can access BrightStor VM:Backup through both screens and line-mode
commands.
For information about the following, see the Systems Programmer Reference:
■
Tape and DASD devices that BrightStor VM:Backup supports
■
VM release requirements
■
Missing interrupt handling (MIH) settings
■
Shared File System requirements
■
Interface requirements for other Computer Associates products
Accessing and Leaving BrightStor VM:Backup Screens
There are two ways to use BrightStor VM:Backup: through screens and through
line-mode commands. In either case, you must be in CMS to access BrightStor
VM:Backup.
This section explains how to access BrightStor VM:Backup through screens. For
information about accessing BrightStor VM:Backup through line-mode
commands, see the Systems Programmer Reference.
To access BrightStor VM:Backup through screens, enter the user ID of the
BrightStor VM:Backup service virtual machine. (The instructions in this book
assume that the BrightStor VM:Backup service virtual machine's user ID is
VMBACKUP.) For example, enter vmbackup.
2–2
Administrator Guide
Accessing and Leaving BrightStor VM:Backup Screens
The first time you invoke BrightStor VM:Backup after you IPL CMS, BrightStor
VM:Backup displays the following copyright screen.
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
BrightStor VM:Backup
*
Copyright 2005, Computer Associates International, Inc.
*
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This material is the confidential trade secret and proprietary*
information of Computer Associates International, Inc. It may *
not be disclosed, reproduced, used, sold, made available or
*
transferred to any third party without the prior consent of
*
Computer Associates International, Inc. All rights reserved. *
*
Use, duplication, or disclosure by Government of this
*
commercial computer software as defined in Clause
*
252.227-7014(a) (1) of the DFARs is subject to restriction
*
and shall be deemed restricted computer software as defined
*
in Clause 52.227-19 of the FAR.
*
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Screen will clear in 15 seconds or press ENTER to clear.
This screen remains on your terminal screen until you press ENTER or 15 seconds
elapse, whichever occurs first. BrightStor VM:Backup then displays the System
Administrator Main Menu.
If you want to prevent the copyright screen from appearing again, rename the
VMBACKUP COPYRGHT file on the public minidisk. The next time you enter
vmbackup, BrightStor VM:Backup displays the System Administrator Main Menu
immediately. For information about using the main menu, see Using the Main
Menu on page 2-5.
To exit the BrightStor VM:Backup screens and return to CMS, press PF3 (End) until
you reach the System Administrator Main Menu, then press PF3 (End) once more.
About BrightStor VM:Backup
2–3
Moving Through Screens and Menus
Moving Through Screens and Menus
You can move through BrightStor VM:Backup screens and menus by typing
entries and using program function (PF) keys. This section explains how to move
through screens.
Typing Entries
To enter information in fields on the screens, begin typing your entries anywhere
in the space provided. Use the tab key to move between fields. Follow the
instructions displayed on the screens.
Do not specify values that have leading and trailing underscores. BrightStor
VM:Backup recognizes only embedded underscores. For example, BrightStor
VM:Backup accepts A_FILE and B_FILE, but does not accept _AFILE and BFILE_.
Follow these guidelines when entering values such as filenames, filetypes, user
IDs, and virtual addresses on screens.
Using PF Keys
To perform some tasks on the screens, you must use the PF keys instead of entering
commands or filling in fields. The PF keys available for each screen are listed at the
bottom of that screen.
2–4
Administrator Guide
Using the Main Menu
Using the Main Menu
When BrightStor VM:Backup displays the System Administrator Main Menu,
enter the number of the option you want to use on the command line. The
following figure shows the System Administrator Main Menu.
AMENABC1
System Administrator Main Menu
VM:Backup
-------------------------------------------------------------------------------To select a function, type its number and press ENTER.
Installation and
Customization
1 Manage configuration options.
2 Manage authorizations.
3 Manage resource pools.
Administrative
Functions
4
5
6
7
Operator and
User Functions
Manage
Manage
Manage
Submit
job templates.
exception/exclusion files.
existing catalogs.
special SFS/BFS restores.
8 Perform operator functions.
9 Perform user functions.
COPYRIGHT 2005 , Computer Associates International, Inc.
-------------------------------------------------------------------------------PF: 1 Help
PF: 7 ...
===>
2 ...
8 ...
3 End
9 ...
4 Return
10 ...
5 ...
11 Print
6 ...
12 Cursor
Help With Screens and Menus
You can get information about any currently displayed menu or screen by pressing
PF1 (Help). BrightStor VM:Backup displays a help screen that describes what you
can do from the menu or screen.
When you are finished reading the help screen, press PF3 (End) to return to the
original screen.
PF Key Help
To view the PF key help screens, press PF1 (Help) from the System Administrator
Main Menu. A description of PF key functions follows the explanation of the main
menu options. Use PF7 (Backward) and PF8 (Forward) to move through the help
screens. To return to the System Administrator Main Menu, press PF3 (End).
About BrightStor VM:Backup
2–5
Using Commands
Using Commands
This section explains how to access BrightStor VM:Backup through line-mode
commands.
Entering CMS and CP Commands From the BrightStor VM:Backup Service Virtual
Machine
When you enter CMS or CP commands on the BrightStor VM:Backup console,
include the prefix cms or #cp, respectively. These prefixes distinguish these
commands from BrightStor VM:Backup commands. For example, to run
BrightStor VM:Backup in disconnected mode, enter #cp disc. The #cp prefix tells
BrightStor VM:Backup to execute the CP DISCONN command. If you do not enter
#cp, BrightStor VM:Backup interprets disc as the BrightStor VM:Backup
DISCARD command.
Entering BrightStor VM:Backup Commands From CMS
To enter BrightStor VM:Backup commands from CMS, type the name of the
BrightStor VM:Backup service virtual machine, a space, and the command, then
press ENTER. For example, to issue the SUSPEND command from CMS, enter
vmbackup suspend.
All responses to commands are edited according to your virtual machine's current
EMSG setting.
Entering BrightStor VM:Backup Commands From CP
If you are issuing BrightStor VM:Backup commands from a VM operator user ID
running in CP mode, prefix the VMBACKUP command with the CP SMSG
command. For example, to enter the SUBMIT command from a VM operator user
ID running in CP mode, enter cp smsg vmbackup submit.
WARNING! Do not enter commands or use CP SMSG with commands that result in
full-screen prompting, such as the RESTORE command.
2–6
Administrator Guide
Using Commands
Entering Commands from the BrightStor VM:Backup Service Virtual Machine
You can enter BrightStor VM:Backup commands on the BrightStor VM:Backup
console if your BrightStor VM:Backup service virtual machine is running in
connected mode. When you enter a command on the BrightStor VM:Backup
console, enter only the command; do not prefix the command with the name of the
BrightStor VM:Backup service virtual machine. For example, to issue the
SUSPEND command, enter suspend; do not enter vmbackup suspend.
When you enter commands at the BrightStor VM:Backup console, you must enter
each command on a separate command line. You cannot enter two commands,
separated by the pound sign (#) command delimiter, on a single command line;
BrightStor VM:Backup does not support the # command delimiter.
WARNING! Do not enter commands or use CP SMSG with commands that result in
full-screen prompting, such as the RESTORE command.
Entering Commands from BrightStor VM:Backup Screens
You can enter BrightStor VM:Backup, CMS, and CP commands from the command
line on BrightStor VM:Backup screens. BrightStor VM:Backup processes
commands entered in the Command column before it reads the command line.
Entering BrightStor VM:Backup Commands
Use the CP SMSG command to enter any BrightStor VM:Backup command from
the command line of a BrightStor VM:Backup screen. For example, to temporarily
halt BrightStor VM:Backup job processing from the command line of a BrightStor
VM:Backup screen, enter smsg vmbackup suspend.
Entering CP and CMS Commands
When you enter CMS or CP commands, you do not have to prefix them with cms
or cp, respectively. If the entered command is not valid for that screen, BrightStor
VM:Backup passes the command to CMS for execution. Standard CMS search
order rules apply.
About BrightStor VM:Backup
2–7
Help With Commands
Help With Commands
You can get help on BrightStor VM:Backup commands through the CMS HELP
facility. To see an overview of BrightStor VM:Backup help and a list of commands
for which help is available, enter help vmbackup from CMS.
To see the help screen for one of the commands listed in the overview, move the
cursor to that command and press PF1 (Help). When you are finished reading the
help screen, press PF3 (End) to return to the help overview screen, and press PF3
(End) again to exit the CMS HELP facility.
You can bypass the help overview screen and get help on a command directly by
entering help vmbackup and the name of the BrightStor VM:Backup command for
which you need help. For example, to see the help screen on the BrightStor
VM:Backup CANCEL command, enter help vmbackup cancel from CMS.
For more information about using the CMS HELP facility, see the CMS User Guide
for your system.
Pattern Matching
Pattern matching allows you to easily specify more than one entity at a time when
those entities have similar names. With pattern matching, you can specify all
entities that begin with, contain, or end with particular characters. Characters you
can use for pattern matching are:
This character
Matches the following
*
Any number of characters from zero on up
%
One character only
For example:
■
To specify all files whose filename ends in SALES, regardless of filetype, enter:
*sales *
■
To specify any file whose five-character filename ends in DEC and whose
filetype contains the character string REP, enter:
%%dec *rep*
2–8
Administrator Guide
Help With Messages
Help With Messages
For information about system messages you receive, you can either use the CMS
HELP facility or see the Messages and Codes. Both explain the possible causes of
these messages and tell you how to respond to them.
To use the CMS HELP facility for a BrightStor VM:Backup message, type help, a
space, the three-character product identifier (vmb), the message number, and the
severity code, then press ENTER. Do not type the three-letter code displayed after
the product identifier; this code is the routine or module that issued the message.
For example, to get help on the message VMBCOM1091E, enter the following from
CMS:
help vmb1091e
When you have finished reading the message help, press PF3 (End) to exit the CMS
HELP facility. For more information about using this facility, see the CMS User
Guide for your system.
Note: Help for messages issued from BrightStor VM:Backup utilities is not
available.
About BrightStor VM:Backup
2–9
Chapter
3
Managing Configuration Options
The VMBACKUP CONFIG file, which is read by BrightStor VM:Backup during
initialization, allows you to define local operating standards for BrightStor
VM:Backup. You can define processing options by ending BrightStor VM:Backup,
editing the records in the VMBACKUP CONFIG file, and then starting BrightStor
VM:Backup again. You can also use the system administrator screens to define
many of the processing options dynamically.
This chapter explains how to interactively update processing options accessible
through Option 1, Manage configuration options, on the System Administrator
Main Menu. You can interactively update other configuration options through
Option 2, Manage authorizations and Option 3, Manage resource pools. For more
information about updating these configuration options, see Chapter 4,
“Managing Authorizations” and Chapter 5, “Managing Resource Pools.”
Before making any changes to the system configuration, see the chapter
“Customizing BrightStor VM:Backup” in the Systems Programmer Reference. There
are a number of operational and environmental requirements you must be aware
of before you can modify BrightStor VM:Backup to meet your system's
conventions. The Systems Programmer Reference also contains information about
configuring all processing options manually and explains the records that
correspond to the options discussed in this chapter and their default settings.
Configuration Options
Selecting Option 1, Manage configuration options displays the Manage
Configuration Options menu, which allows you to:
■
■
Define tape handling procedures, such as whether operators can override tape
expiration dates
Specify how long BrightStor VM:Backup should wait for a response to a
message and how frequently to issue a reminder message
Managing Configuration Options
3–1
Defining Tape Handling Procedures
■
■
Define job processing controls, such as the number of jobs BrightStor
VM:Backup can run concurrently and whether to process user restore requests
immediately or hold them for execution later
Identify SFS file pools to BrightStor VM:Backup
Defining Tape Handling Procedures
To define or revise the way BrightStor VM:Backup manages tapes at your data
center, select Option 1, Define tape handling options, from the Manage
Configuration Options menu. BrightStor VM:Backup displays the Define Tape
Handling Options screen.
Overriding Tape Expiration Dates
When a tape is mounted for use in a BrightStor VM:Backup backup or MPC job,
BrightStor VM:Backup verifies that the labels on the tape are valid, the tape is
either expired or new, and the tape can be used in the job.
If the tape can be used in the job, BrightStor VM:Backup rewrites the tape labels to
reflect the new information for this backup or MPC job. Included in this new
information is a new tape expiration date. However, only the tape labels are
updated now; the resource pool information is not updated until the end of the job.
If the job does not run to completion, the tape labels reflect that the tape is in use,
that is not expired, but the resource pool will indicate that the tape is either expired
or new.
BrightStor VM:Backup uses the resource pool information to select volumes to use
in backup or MPC jobs; BrightStor VM:Backup will select this tape for a future
backup or MPC job because the resource pool indicates that the tape is either
expired or new. When the tape is mounted, BrightStor VM:Backup will determine
from the tape labels that the tape is not expired.
To indicate how you want BrightStor VM:Backup to handle unexpired tapes that
are mounted during backup or MPC jobs, select either the Yes or No response to
the following question on the Define Tape Handling Options screen:
Can operators override expiration dates on tape volumes?
3–2
Administrator Guide
Defining Tape Handling Procedures
Yes
The tape operator is authorized to overwrite unexpired tapes. When an
unexpired tape is mounted during a backup or MPC job, BrightStor
VM:Backup issues messages to the tape operator requesting permission to
overwrite it.
No
BrightStor VM:Backup does not ask for permission to overwrite the
unexpired tape. Instead, BrightStor VM:Backup rejects the tape, selects
another volume to use in the job, and asks the tape operator to mount the
new volume. If BrightStor VM:Backup is configured to enable tape
chaining in tape trailer labels, before making the mount request, BrightStor
VM:Backup may ask the tape operator to mount the previously used
volume again so that it can update its trailer label to reflect the newly
selected volume.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the TAPEXPDT record in the Systems Programmer Reference. For
information about tape chaining, see Chapter 7, “Managing Tape and DASD
Resources, in the Systems Programmer Reference.
Overwriting Existing Data Sets
If BrightStor VM:Backup is interfaced with BrightStor® VM:Archiver®, this option
also determines whether BrightStor VM:Backup issues messages to the tape
operator requesting permission to overwrite existing incomplete data set.
BrightStor VM:Archiver tapes can contain multiple data sets. Each data set on the
tape contains its own tape header labels. A valid data set is any data set that
contains valid header labels. The following table describes the three ways in which
BrightStor VM:Archiver protects its tapes from being used inadvertently.
Method
Description
Tape
expiration
date
All BrightStor VM:Archiver tapes have an expiration date of
PERM (permanent), which means that they never expire. The
PERM designation protects them from becoming scratch tapes
and being reused by other users.
Ownership
All tapes created for BrightStor VM:Archiver jobs are owned by
the BrightStor VM:Archiver service virtual machine that
submitted the jobs. BrightStor VM:Backup makes sure the
requesting user is the owner of the tape before it uses the tape.
Data set
BrightStor VM:Archiver tells BrightStor VM:Backup which data
sets to write to so that BrightStor VM:Backup does not
inadvertently overwrite a BrightStor VM:Archiver data set.
Managing Configuration Options
3–3
Defining Tape Handling Procedures
When appending data sets to a tape, BrightStor VM:Archiver may provide
BrightStor VM:Backup with a starting volser for that job. BrightStor VM:Archiver
always asks BrightStor VM:Backup to write a specific data set. If the job is canceled
while BrightStor VM:Backup is processing it, part of the data set may have been
written to the BrightStor VM:Archiver tape volume; therefore, correct and valid
header labels may exist. When BrightStor VM:Archiver submits the next job, it asks
BrightStor VM:Backup to write the same data set that was specified in the canceled
job, but when BrightStor VM:Backup encounters the valid tape header labels, it
assumes that the entire data set exists.
If you select Yes in response to the question, Can operators override expiration
dates on tape volumes?, on the Define Tape Handling Options screen, the tape
operator is authorized to overwrite existing incomplete BrightStor VM:Archiver
data sets; BrightStor VM:Backup asks the tape operator for permission to
overwrite such data sets. If you select No in response to this question, BrightStor
VM:Backup selects another tape volume to use in the job.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the TAPEXPDT record in the Systems Programmer Reference.
Detaching Tape Drives Between Mounts
To indicate how BrightStor VM:Backup should handle releasing tape drives that
have been attached to the BrightStor VM:Backup service virtual machine, select
either the Yes or No response to the following question on the Define Tape
Handling Options screen:
Should VM:Backup detach tape drives between each mount?
Yes
Unloads the tape and detaches the tape drive after it finishes processing the
tape.
No
Unloads the tape but does not detach the tape drive until the job is
completed.
If your site uses automatic cartridge loaders (ACLs), you should select Yes for this
option. Detaching the tape drive allows the ACL to load the next tape in the unit.
If BrightStor VM:Backup is interfaced with BrightStor VM:Tape, this option is
ignored. BrightStor VM:Tape always attaches drives to BrightStor VM:Backup;
BrightStor VM:Backup always detaches the drives when the tapes are unloaded.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the TAPEDISP record in the Systems Programmer Reference.
3–4
Administrator Guide
Specifying Wait Times
Specifying OS Data Set Protection
If your data center allows expired BrightStor VM:Backup tapes to be reused by an
OS system, use this option to specify a tape data set security code to protect the
data sets against unauthorized access by the OS system. Select PASSWORD,
NOPSWD, or NOPWREAD in response to the following statement on the Define
Tape Handling screen:
Specify the type of OS data set protection on VM:Backup data sets:
PASSWORD
BrightStor VM:Backup tape data sets are password-protected
against all access.
NOPSWD
BrightStor VM:Backup tape data sets are not
password-protected against read or write access.
NOPWREAD
BrightStor VM:Backup tape data sets are password-protected
against write access only; read access is permitted without a
password.
This option is provided for other systems, such as OS/MVS, that honor tape
password protection. BrightStor VM:Backup ignores the tape data set security
code because its tapes are protected by expiration dates.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the TAPEPROT record in the Systems Programmer Reference.
Specifying Wait Times
To define or revise the amount of time you want BrightStor VM:Backup to wait for
a response to a tape- or disk-related request, or the frequency with which to issue
reminder messages, select Option 2, Define wait time options, from the Manage
Configuration Options menu. BrightStor VM:Backup displays the Define Wait
Time Options screen.
Use the Wait For field on the Define Wait Time Options screen to set how long
BrightStor VM:Backup is to wait for a user or operator to respond to a request.
Within that wait time, BrightStor VM:Backup sends reminder messages. Use the
Remind Every field on the screen to set how often reminder messages are sent.
Managing Configuration Options
3–5
Specifying Wait Times
Options on the Define Wait Time Options screen:
Wait For
Specify the total length of time, in minutes, BrightStor VM:Backup
should wait for a response. Enter a one- to four-digit whole number in
the acceptable range.
Remind
Every
Specify the length of time, in minutes, BrightStor VM:Backup should
wait between sending each reminder message. The Remind Every
time must be less than the Wait For time. Enter a one- to four-digit
whole number in the acceptable range.
The following table describes the wait times you can set, the acceptable values you
can enter in the Wait For and Remind Every fields, and the corresponding record
in the VMBACKUP CONFIG file. For more information about updating the
VMBACKUP CONFIG file to configure these options, see the Systems Programmer
Reference.
Wait Times on Define Wait Time Options Screen
Wait for ... BrightStor VM:Backup waits for a Range for
VMBACKUP
response ...
Wait For and CONFIG file
Remind
record
Every
1-9999
minutes
USERWAIT
A user to
A backup job has requested that the 1-9999
quiesce a
minidisk or file space be quiesced. minutes
minidisk or
file space
If the wait time expires and the user
has received the message but
ignored it, BrightStor VM:Backup
skips the minidisk or file space.
USERWAIT
A user to
detach a
disk
When BrightStor VM:Backup
cannot link to a needed minidisk
while processing a restore.
If the wait time expires and the user
has not detached the required
minidisk, BrightStor VM:Backup
cannot link to the minidisk and thus
cannot restore it.
If the wait time expires and the user
has not received the request,
BrightStor VM:Backup tries to back
up the minidisk or file space
3–6
Administrator Guide
Specifying Wait Times
Wait Times on Define Wait Time Options Screen
Wait for ... BrightStor VM:Backup waits for a Range for
VMBACKUP
response ...
Wait For and CONFIG file
Remind
record
Every
An
operator to
mount a
tape
When BrightStor VM:Backup has
1-9999
tape-related requests (for example, minutes
to mount a required tape volume to
override a tape expiration date),
during job processing.
TAPEWAIT
If the wait time expires and the
operator has not responded,
BrightStor VM:Backup puts the job
on hold.
If BrightStor VM:Backup is
interfaced with BrightStor
VM:Tape, the wait time for tape
mounts is controlled by BrightStor
VM:Tape. If the wait time expires,
BrightStor VM:Tape cancels the
mount request; this causes
BrightStor VM:Backup to place the
job on hold.
When a required DASD volume is 0-9999
An
operator to not mounted during job processing. minutes
mount a
disk
If the wait time expires and the
operator has not responded,
BrightStor VM:Backup continues
the job with the next DASD volume.
BrightStor VM:Backup does not
process minidisks defined on the
requested DASD volume. If the
DASD volume is part of a user
storage group, BrightStor
VM:Backup skips all file spaces in
that user storage group.
DISKWAIT
When you specify 0, BrightStor
VM:Backup does not issue messages
and skips all minidisks on the
DASD volume or all file spaces in
the user storage group.
Managing Configuration Options
3–7
Defining Job Processing Controls
Defining Job Processing Controls
To define or revise how BrightStor VM:Backup processes jobs and to determine the
number of jobs that can run concurrently, select Option 3, Define job processing
options, from the Manage Configuration Options menu. BrightStor VM:Backup
displays the Define Job Processing Options screen.
User ID to Receive Restore Tape Lists
To specify the user ID to receive the list of tapes required to satisfy each
CATSEARCH and VOLSER restore job, each MPC job, and each REINIT job, enter
the user ID after the following statement on the Define Job Processing Options
screen:
Additional userid to receive restore tape list:
By default, when you submit one of these type of jobs, BrightStor VM:Backup
creates the tape pull list and sends it to the virtual reader of the user ID you specify
on the Define Job Processing Options screen. If you submit a job using TPI, you can
use the REPORT PULLUSER template record to override this setting for specific
jobs.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the PULLUSER record in the Systems Programmer Reference. For more
information about the TPI record, REPORT PULLUSER, see the Template
Programming Interface Guide.
When to Process End-User Restore Requests
BrightStor VM:Backup can process end-user restore requests when they are
received or it can hold those requests to be processed later. If your users normally
submit many restore requests, you may want BrightStor VM:Backup to hold the
requests so that you can submit them during periods of low data center activity or
when the tape operators are available to mount the required tapes.
To specify when you want BrightStor VM:Backup to process end-user restore
requests, select either SUBMIT or HOLD in response to the following statement
on the Define Job Processing Options screen:
Hold restore requests or submit them immediately:
3–8
SUBMIT
BrightStor VM:Backup processes end-user restore requests
immediately.
HOLD
BrightStor VM:Backup holds end-user requests to be processed later.
Administrator Guide
Defining Job Processing Controls
Note: This option applies to end-user restore requests. Jobs received from
BrightStor VM:Archiver, BrightStor® VM:Migrate®, and administrative SFS
restores are always queued for immediate processing.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the RESTHOLD record in the Systems Programmer Reference.
Default Restore Time Period
For end-user restore requests, several screens specify default time periods for
BrightStor VM:Backup to use when listing data. Examples of some screens are:
■
■
■
The Novice User Main Menu displays a default date that is n days back from
the current day.
The Expert User Main Menu lets the user list minidisks or directories backed
up during a time period that is n days back from the current day.
The Select Files by Date Range or Filename screen shows the start and end
dates of a default time period that is n days long.
To specify the value n that is used on each of these screens, enter a response to the
following statement on the Define Job Processing Options screen:
Default restore selection period (in days):
You can enter either a number of days from 1 through 9999 or an asterisk to
indicate that BrightStor VM:Backup is to search from the earliest catalog through
the most recent backup.
WARNING! Make sure the value you enter results in a default time period that includes
the entire backup cycle, including the last full backup. For file restores, BrightStor
VM:Backup lists only data that was backed up within the specified time period.
When an end-user requests BrightStor VM:Backup to display a list of files available
to restore, BrightStor VM:Backup cannot display the list if the number of files
available to restore exceeds the value on the MAXFILES configuration file record.
To reduce the possibility of reaching this limit, specify a short default time period
on this screen.
For information about updating the VMBACKUP CONFIG file to configure the
default time period option, see the LISTPD record in the Systems Programmer
Reference. For information about the MAXFILES configuration record, see the
MAXFILES record in the Systems Programmer Reference.
Managing Configuration Options
3–9
Defining Job Processing Controls
User to Receive Dumps for System Abends
When a system abend occurs, BrightStor VM:Backup generates a VM dump
automatically. To specify the user ID to receive these dumps, enter a user ID after
the following statement on the Define Job Processing Options screen:
Userid to receive dump if system abends:
BrightStor VM:Backup will send the dumps to the user's virtual reader.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the DUMP record in the Systems Programmer Reference.
Number of Jobs that Can Run Concurrently
BrightStor VM:Backup can execute up to 15 jobs at the same time. To set the
maximum number of jobs and the maximum number of each type of job you want
BrightStor VM:Backup to be able to run simultaneously, specify the number of jobs
in each of the following fields on the Define Job Processing Options screen:
Use this field
To set the maximum number Enter a whole number from
of ...
...
Jobs
Jobs (backup, restore, MPC,
and REINIT) that BrightStor
VM:Backup can process at the
same time
Backup jobs
Backup jobs that can run at the 0 - 2
same time
This number cannot exceed the
number entered in the
Maximum number of
concurrent jobs field.
MPC jobs
MPC jobs that can run at the
same time
REINIT jobs
3–10
Administrator Guide
0 - 15
0-2
This number cannot exceed the
number entered in the
Maximum number of
concurrent jobs field.
REINIT jobs that can run at the 0 - 1
same time
This number cannot exceed the
number entered in the
Maximum number of
concurrent jobs field.
Identifying SFS File Pools
Use this field
To set the maximum number Enter a whole number from
of ...
...
Restore jobs
Both job template file and
end-user restore jobs that can
run at the same time
Template
restores
Job template file restore jobs
that can run at the same time
User restores
End-user restores that can run
at the same time
0 - 15
This number cannot exceed the
number entered in the
Maximum number of
concurrent jobs field.
0 - 15
This number cannot exceed the
number entered in the restore
jobs field.
0 - 15
This number cannot exceed the
number entered in the restore
jobs field.
WARNING! If the combination of jobs requires more than 75 tape drives, BrightStor
VM:Backup terminates abnormally with abend code MNT012.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the MULT record in the Systems Programmer Reference.
Identifying SFS File Pools
You must identify all SFS file pools to BrightStor VM:Backup before you can
include them in backup or restore jobs. If BrightStor VM:Backup is interfaced with
other products, such as, BrightStor VM:Archiver or BrightStor VM:Migrate, you
must identify the file pools that BrightStor VM:Backup must access on behalf of
these products. For example, you must identify all file pools from which BrightStor
VM:Archiver users can archive data and to which users can restore data.
To identify SFS file pools to BrightStor VM:Backup, select Option 4, Identify SFS
file pools, from the Manage Configuration Options menu. BrightStor VM:Backup
displays the Identify SFS File Pools screen. On this screen, enter the names of the
file pools. A file pool name:
■
Must start with a letter (A-Z)
■
Can contain up to eight alphanumeric characters (A-Z, 0-9)
■
Cannot be ALLOW, ANY, or SYSTEM
Managing Configuration Options
3–11
Identifying SFS File Pools
When you identify file pools through this screen, BrightStor VM:Backup
recognizes them immediately; you do not have to reinitialize BrightStor
VM:Backup for the new definitions to take effect.
For information about updating the VMBACKUP CONFIG file to configure this
option, see the FILEPOOL record in the Systems Programmer Reference.
3–12
Administrator Guide
Chapter
4
Managing Authorizations
In BrightStor VM:Backup, you can authorize certain user IDs to do the following:
■
■
Perform system administrator, operator, or end user functions
Receive disk mount requests, tape mount requests, or messages about system
activity from BrightStor VM:Backup
This chapter explains how to assign these authorizations through Option 2,
Manage authorizations, on the System Administrator Main Menu.
Authorization Information
When you select Option 2, Manage authorizations, BrightStor VM:Backup
displays the Manage Authorizations screen. This screen lists user IDs that have
previously been identified to BrightStor VM:Backup and shows whether each is
authorized to perform system administrator, operator, or end-user functions. In
addition, it shows whether each user ID is to receive requests or messages from
BrightStor VM:Backup.
You can use PF8 (Forward) and PF7 (Backward) to scroll through the user ID list.
Managing Authorizations
4–1
Authorizing User IDs
Authorizing User IDs
To allow a user ID to access BrightStor VM:Backup, you must specify that user ID
on the Manage Authorizations screen and assign it one or more of the following
authorizations.
Authorization Allows the user to perform ...
SysAdmin
System administrator functions, such as configuring BrightStor
VM:Backup, managing tapes and catalogs, creating backup and
restore job templates, starting special SFS/BFS restore jobs, and
restoring BFS directories. In addition, this authorization allows
the user to perform operator and user functions.
Operator
Operator functions, such as managing system activity, starting
system backups, and ending or suspending BrightStor
VM:Backup job processing. In addition, this authorization
allows the user to perform user functions.
User
End-user functions, such as restoring CMS and BFS files,
minidisks, and SFS directories, and responding to BrightStor
VM:Backup messages.
This section explains how to add, delete, and update authorizations. For more
information about updating the VMBACKUP CONFIG file to authorize user IDs
to perform different functions, see the AUTHORIZ record in the Systems
Programmer Reference.
Adding Authorizations
To authorize one or more users to perform certain functions, follow these steps:
4–2
1.
Select Option 2, Manage authorizations; BrightStor VM:Backup displays the
Manage Authorizations screen.
2.
Move the cursor to the user ID above which you want to add the new user ID
and press PF5 (Insert).
3.
Type the new user ID in the Userid field. You can use pattern matching. To
grant all users a particular authorization level, enter an asterisk in the Userid
field.
4.
Type x in the SysAdmin field to authorize system administrator functions, the
Operator field to authorize operator functions, or the User field to authorize
user functions. You can select any or all levels of authorizations.
Administrator Guide
Specifying Message Routing Controls
Deleting Authorizations
To remove a user's privileges, move the cursor to the user ID you want to delete
and press PF6 (Delete). The entire record for that user is removed.
Updating Authorizations
To modify a user's privileges, move the cursor in the appropriate authorization
field corresponding to that user's user ID and either add or delete the X
accordingly.
Specifying Message Routing Controls
BrightStor VM:Backup produces the following three types of messages:
System
Error and informational messages about BrightStor VM:Backup
processing
Tape
Tape-related requests
Disk
Disk mount requests
You can control which user IDs are allowed to receive and respond to each of these
types of messages. BrightStor VM:Backup issues messages of a particular type to
all user IDs authorized to receive that type of message. If a reply is required, any
authorized user ID can enter a response. If no user IDs are authorized to receive a
certain type of message, those messages are routed to the VM operator console.
To authorize a user ID to receive and respond to messages, follow these steps:
1.
Type the user ID in the Userid field. You cannot use pattern matching.
2.
Type x in the System field to authorize the user ID to receive and respond to
system messages, the Tape field to authorize the user ID to receive and
respond to tape-related requests, or the Disk field to authorize the user ID to
receive and respond to disk mount requests. You can select any or all types of
messages.
If you do not want to grant the user ID the authority to perform other functions,
leave the SysAdmin, Operator, and User fields blank.
For more information about updating the VMBACKUP CONFIG file to specify
user IDs to receive these messages, see the SYSOPER, TAPEOPER, and DISKOPER
records in the Systems Programmer Reference.
Managing Authorizations
4–3
Chapter
5
Managing Resource Pools
A resource pool is a collection of tapes that BrightStor VM:Backup can use during
backup or MPC job processing. Resource pools allow you to predefine a set of
tapes for use in particular backup or MPC jobs instead of specifying a tape each
time BrightStor VM:Backup requires one.
The tapes defined to a particular resource pool must have the same physical
characteristics. As a job runs, BrightStor VM:Backup automatically uses the next
tape defined in the pool. When the last tape in the resource pool is used, you can
have BrightStor VM:Backup prompt the tape operator to provide additional tapes,
which can be added permanently to the pool.
A superpool is a collection of DASDtape resource pools that are referenced and used
as if they were a single entity. During a backup or MPC job, if a DASDtape
minidisk that is part of the referenced superpool runs out of space, or if the last
tape in a resource pool is used, BrightStor VM:Backup uses the next pool defined
in the superpool to continue the job. When the last tape in the last resource pool is
used, BrightStor VM:Backup can hold the backup or ask the operator for the volser
of an available tape.
This chapter explains how to create, modify the attributes of, update, and discard
resource pools and superpools through Option 3, Manage resource pools, on the
System Administrator Main Menu. You can apply any of the functions described
in this chapter to resource pools and superpools for any authorized client, such as
BrightStor VM:Archiver and BrightStor VM:Migrate, as well as BrightStor
VM:Backup resource pools and superpools.
Managing Resource Pools
5–1
Suspending BrightStor VM:Backup Before Updating Resource Pools
Suspending BrightStor VM:Backup Before Updating Resource
Pools
Before you can update resource pool and superpool information, you must
temporarily suspend BrightStor VM:Backup.
Suspending BrightStor VM:Backup
To suspend BrightStor VM:Backup, perform one of the following actions:
■
■
■
From the System Administrator Main Menu, select Option 8, Perform
operator functions. From the Perform Operator Functions screen, select
Option 4, End, suspend, or resume processing.
From CMS, enter the BrightStor VM:Backup SUSPEND command.
On the command line of a BrightStor VM:Backup screen, enter the command
smsg vmbackup suspend.
Resuming BrightStor VM:Backup
When you have completed your task, perform one of the following tasks to resume
BrightStor VM:Backup job processing:
■
■
■
5–2
Administrator Guide
From the System Administrator Main Menu, select Option 8, Perform
operator functions. From the Perform Operator Functions screen, select
Option 4, End, suspend, or resume processing.
From CMS, enter the BrightStor VM:Backup RESUME command.
On the command line of a BrightStor VM:Backup screen, enter the command
smsg vmbackup resume.
Resource Pool Information
Resource Pool Information
When you select Option 3, Manage resource pools, BrightStor VM:Backup
displays the Manage Resource Pool screen. This screen displays the following
information about existing resource pools:
■
Name of the pool
■
Medium and density of the tapes in the pool
■
Number of tapes in the pool
■
Action BrightStor VM:Backup is to take if the pool runs out of tapes
■
Type of pool for tapes mounted by BrightStor VM:Tape, either pool for tapes
from a specific resource pool or scratch for a general scratch pool
For the last item, pool means that BrightStor VM:Tape allocates tapes from a
specific scratch pool with the same name as the BrightStor VM:Backup pool, and
scratch means that BrightStor VM:Tape allocates tapes according to BrightStor
VM:Tape pool assignment rules.
You can use PF8 (Forward) and PF7 (Backward) to scroll through the resource pool
list.
Superpools
Because the attributes of the pools in a superpool can vary, this screen displays
only the name of the superpool and the word SUPER. You can view information
about the pools that are part of a superpool on the Manage Resource Pool screen.
Use the UPDATE command to determine which pools are in the superpool. For
more information about the UPDATE command, see Screen Commands on
page 5-4.
For information about updating the VMBACKUP CONFIG FILE to define a
resource pool to BrightStor VM:Backup, see the TAPEPOOL record in the Systems
Programmer Reference.
Managing Resource Pools
5–3
Screen Commands
Screen Commands
The commands listed in the following table are available on the Manage Resource
Pools screen. To work with an existing resource pool, enter the appropriate
command in the Command column next to the resource pool. To create a resource
pool, enter the appropriate command on the command line.
Screen Commands on Manage Resource Pools Screen
Command
Where to Enter Use this command to ...
BROWSE 1
Command
column
CREATE/poolname
Command line Create the resource pool, poolname.
If BrightStor VM:Backup is interfaced
with BrightStor VM:Tape, poolname
corresponds to a BrightStor VM:Tape
resource pool of the same name. The
resource pool name can be 1-16
characters in length. You must update
the TAPEPOOL record in the
VMBACKUP CONFIG file to specify a
resource pool name with more than
eight characters.
If BrightStor VM:Backup is not
interfaced with BrightStor VM:Tape,
poolname corresponds to a CMS
filename; it must be unique, 1-8
characters in length, and follow CMS
file-naming conventions.
DISCARD
Command
column
1
5–4
Administrator Guide
View detailed information about a
resource pool.
BrightStor VM:Backup displays the
Tape List for Resource Pool screen,
which describes the tape attributes,
lists the volsers contained in the pool,
and provides status information (for
example, that a tape has been used in
a backup).
Delete a resource pool that is no
longer needed.
To prevent you from inadvertently
discarding a pool that still contains
tapes, BrightStor VM:Backup asks you
to verify that you want to discard the
pool.
You do not have to suspend BrightStor VM:Backup to use this command.
Screen Commands
Screen Commands on Manage Resource Pools Screen
Command
Where to Enter Use this command to ...
OPTIONS
Command
column
Change physical attributes (such as
tape density and medium), or
processing characteristics (for
example, the action BrightStor
VM:Backup should take if a pool runs
out of tapes) of a resource pool.
BrightStor VM:Backup displays the
Modify Resource Pool screen.
PRINT
Command
column
Send a copy of the resource pool
definition to your virtual printer.
This report lists the general attributes
of the resource pool and contains a list
of the volsers defined to the pool,
along with information about the
status of the tapes in the pool (for
example, if they were used in a
backup).
The PRINT command prints
information about the entire resource
pool; with PF11 (Print), you can print
the resource pool definition screens
one screen at a time.
RENAME/poolname
Command
column
Rename an existing pool; poolname is
the new name of the resource pool.
You can only use this command if the
new pool name is 1-8 characters in
length.
SCREATE/poolname
Command line Create the superpool, poolname.
The name of the superpool, poolname,
corresponds to a CMS filename; it
must be unique, 1-8 characters in
length, and follow CMS file-naming
conventions.
UPDATE
1
Command
column
Allow you to modify an existing
resource pool; for example, to add or
delete tapes, move a tape from one
pool to another, or add or delete
resource pools in a superpool.
You do not have to suspend BrightStor VM:Backup to use this command.
Managing Resource Pools
5–5
Creating Resource Pools
Creating Resource Pools
To create a resource pool from the Manage Resource Pools screen, use the
CREATE/poolname command.
On the Manage Resource Pools screen, enter create/poolname on the command
line, where poolname is the name of the pool you want to create. BrightStor
VM:Backup displays the Modify Resource Pool poolname screen. Use this screen to
describe the tapes contained in the pool and how BrightStor VM:Backup (or
BrightStor VM:Tape, if BrightStor VM:Backup is interfaced with BrightStor
VM:Tape) should select tapes for use in backup jobs.
Enhanced Device Support
When running BrightStor VM:Backup in a mixed tape device environment,
Enhanced Device Recognition (EDR) support in BrightStor VM:Backup enables
you to manage these devices by specifically identifying each one, and the media
types it can use. You can support not only different media types, but different
recording formats within a media type. Additionally, the media's format at any
point depends on the tape device that last initialized the media.
For detailed information on EDRSUP and NOEDRSUP, see the section Enhanced
Device Recognition Support in the chapter “Managing Tape and DASD
Resources” in the Systems Programmer Reference.
Device and Media Settings
Several records require you to specify the media type and density of tapes to use
for input or output. For a list of device, media, and density names for NOEDRSUP
and EDRSUP, see the section Enhanced Device Recognition Support in the chapter
“Managing Tape and DASD Resources” in the Systems Programmer Reference.
5–6
Administrator Guide
Enhanced Device Support
Defining DASDtape Characteristics
When you create a DASDtape resource pool, fill in the following fields on the
Modify Resource Pool poolname screen to identify the virtual address of the
DASDtape minidisk and length of the DASDtape.
Tapedisk
Address
This field identifies the virtual address of the DASDtape minidisk
on which the backed-up data is to be stored. This virtual address
must correspond to the address of an existing DASDtape
minidisk. Multiple resource pools can access the same DASDtape
minidisk, but no more than one DASDtape minidisk can be
specified for each resource pool.
To define a DASDtape minidisk by updating the VMBACKUP
CONFIG file, see the TAPEDISK record in the Systems Programmer
Reference.
Tape Length This field determines the size, in feet, of a physical tape that the
DASDtape is to approximate. This value can range from 300
through 3600; the default is 2400.
Specifying Empty Pool Action
When all tapes in a resource pool are used and additional tapes are required to
complete a backup or MPC job, BrightStor VM:Backup must take some action to
complete the job. Set the action BrightStor VM:Backup is to take on the Modify
Resource Pool poolname screen.
Empty Pool Action for Superpools
If a backup or MPC job references a superpool, when a particular DASDtape
resource pool in the superpool runs out of available tapes, BrightStor VM:Backup
ignores the specified empty pool action for that resource pool and uses a tape from
the next resource pool in the superpool pool list. When BrightStor VM:Backup has
used the last volser in the last resource pool in the list, BrightStor VM:Backup takes
the empty pool action for that resource pool. Set the action BrightStor VM:Backup
is to take for each DASDtape resource pool in the superpool on the Modify
Resource Pool poolname screen.
Managing Resource Pools
5–7
Enhanced Device Support
To specify the action BrightStor VM:Backup is to take if a resource pool runs out of
available tapes during a backup job, select one of the following options on the
Modify Resource Pool poolname screen:
Hold the job
BrightStor VM:Backup places the job on hold.
Ask for a volser
BrightStor VM:Backup asks the tape operator for the volser of
a tape to be used to complete the job; the volser is not added to
the resource pool.
This option cannot be used for DASDtape resource pools.
Try not to use this option unless it is absolutely necessary.
Ask, adding to the (Default) BrightStor VM:Backup asks the tape operator for the
pool
volser of a tape to be used to complete the job. When the
backup or MPC job completes, BrightStor VM:Backup adds the
volser to the resource pool. If the job references a superpool,
BrightStor VM:Backup adds the volser to the last DASDtape
resource pool defined to the superpool.
BrightStor VM:Backup adds the volsers of all tapes obtained
from the tape operator under the control of this option to the
resource pool whether the tape was actually used during the
backup or MPC job or not. This situation can arise if an error in
backing up a minidisk causes the tape to be completely
rewound.This is the default action.
Note: If your data center uses BrightStor VM:Tape, BrightStor VM:Backup ignores
these options for all resource pools other than DASDtape resource pools. When a
BrightStor VM:Tape resource pool runs out of tapes, more tapes must be added
through BrightStor VM:Tape facilities
Using the BrightStor VM:Tape Interface
The BrightStor VM:Backup-BrightStor VM:Tape interface provides a single point
of reference for defining the tapes to be used in backup and MPC jobs. Although
BrightStor VM:Backup still manages resource pools for DASDtapes, BrightStor
VM:Tape assumes complete control over the maintenance of resource pools for
reel and cartridge media.
When BrightStor VM:Backup is interfaced with BrightStor VM:Tape, specify how
BrightStor VM:Backup is to ask BrightStor VM:Tape for scratch tapes. You can set
up the resource pool to allow BrightStor VM:Tape to select the pool from which it
is to request scratch tapes or have BrightStor VM:Backup specify the pool name
from which BrightStor VM:Tape should request scratch tapes.
5–8
Administrator Guide
Modifying Resource Pool Attributes
Allowing BrightStor VM:Tape to Select a Pool
To allow BrightStor VM:Tape to select the pool from which to request scratch
tapes, select Use VM:Tape scratch volumes on the Modify Resource Pool poolname
screen. When you select this option, BrightStor VM:Backup does not pass
BrightStor VM:Tape a specific name of a resource pool. If the BrightStor VM:Tape
Tape Management Catalog (TMC) is set up as one large pool of scratch tapes
(general scratch pool), BrightStor VM:Tape requests an available tape defined in the
TMC. If scratch pools are defined to BrightStor VM:Tape, BrightStor VM:Tape
selects a pool using pool assignment rules and requests that a scratch tape be
mounted from that pool.
Specifying a Specific Pool Name
To have BrightStor VM:Tape request tapes from a specific scratch pool do not select
the Use VM:Tape scratch volumes option on the Modify Resource Pool poolname
screen. If this is not selected, BrightStor VM:Backup will request that BrightStor
VM:Tape select tapes from the specific resource pool, poolname.
When BrightStor VM:Backup is interfaced with BrightStor VM:Tape, resource pool
names can contain 1-16 characters. BrightStor VM:Backup passes the specified
pool name to BrightStor VM:Tape. When BrightStor VM:Backup is not interfaced
with BrightStor VM:Tape, resource pool names can contain only 1-8 characters.
Note: For more information about how to use BrightStor VM:Tape's scratch pool
facility, see the BrightStor VM:Tape System Administrator's Guide. For complete
information about using BrightStor VM:Backup with BrightStor VM:Tape, see the
CA VM:Manager® Component Interface Guide.
Modifying Resource Pool Attributes
To change any of the attributes defined for an existing resource pool, use the
OPTIONS command on the Manage Resource Pools screen. Enter options in the
Command column next to the resource pool you want to modify. BrightStor
VM:Backup displays the Modify Resource Pool poolname screen for the selected
resource pool.
Managing Resource Pools
5–9
Updating Resource Pools
Updating Resource Pools
To add tape volumes to or delete tape volumes from a resource pool, or to move
tape volumes from one resource pool to another, use the UPDATE command on
the Manage Resource Pools screen. Enter update in the Command column next to
the resource pool whose tape volumes you want to work with. BrightStor
VM:Backup displays the Tape List for Resource Pool poolname screen, where
poolname is the name of the pool you are updating. The tape list shows the
following information about each tape volume in the resource pool:
■
Volser
■
Backup date and time
■
Job template file name
■
Dumpjob number
■
Expiration date
■
Owner (if used by an authorized client)
BrightStor VM:Backup only displays a user ID in the Owner column for tapes used
by an authorized client, such as BrightStor VM:Archiver or BrightStor
VM:Migrate. The Owner field contains the user ID that used the tape; for example,
if a tape is used by BrightStor VM:Archiver, the Owner field contains the user ID
of the BrightStor VM:Archiver service virtual machine. The expiration date PERM,
which means the tapes never expire, and the owner's user ID protect tapes from
being used by other jobs.
For tape volumes used in a backup or MPC job that was canceled, the only
information displayed on the Tape List for Resource Pool poolname screen is the
message *Released from canceled job, the volser, and the expiration date.
You can use PF7 (Backward) and PF8 (Forward) to move through the list of volsers.
Enter the TOP and BOTTOM commands on the command line to view the
beginning and end of the tape list.
Adding Individual Tape Volumes
To add tape volumes to the resource pool, use the ADD/volsers command. Enter
add/volsers on the command line, where volsers are the unique volume serial
numbers of the tapes you want to add to the pool. The format for volsers is as
follows:
■
■
■
5–10
Administrator Guide
Volsers must be from one to six characters in length.
Volsers can contain only alphanumeric characters (A-Z, 0-9), and these special
characters: at sign (@), pound sign (#), dollar sign ($), and dash(-).
Duplicate volsers are not allowed within a pool or across pools; as you enter
volsers, BrightStor VM:Backup checks each to ensure it is unique.
Updating Resource Pools
You can add multiple tape volumes at one time by listing the appropriate volsers
on the ADD command. Enter a blank between volsers. You cannot use
pattern-matching characters.
Adding a Series of Tape Volumes
To add a range of tape volumes to the resource pool without having to specify
them individually, use the SERIES/number startvolser command. Enter
series/number startvolser on the command line, where number indicates the total
number of tape volumes in the series, and startvolser is the first volser in the range.
For example, to add 50 consecutively numbered tape volumes to a pool, ranging
from BN0000 to BN0049, from the command line enter:
series/50 bn0000
Note: The number of leading and trailing zeros and the number of digits in the
volser is significant. If you specify a starting volser that has five digits, you will
receive a range of five-digit volsers.
Discarding Tape Volumes
To remove tape volumes from the resource pool, use the DISCARD command.
Enter discard next to the volser of each tape volume you want to remove. If you
accidentally discard a tape volume, press PF3 (End) to exit the Tape List for
Resource Pool poolname screen without saving any changes you have made.
WARNING! Do not discard tapes owned by authorized clients such as BrightStor
VM:Archiver or BrightStor VM:Migrate; authorized clients perform tape management for
the tapes they own.
Moving Tape Volumes to Another Pool
To move tape volumes from one resource pool to another resource pool, use the
MOVE/poolname command. Enter move/poolname next to each tape volume you
want to move to another pool, where poolname is the name of the target resource
pool to which to move the tape volume. This name must be a unique resource pool
name containing a maximum of eight characters. If you try to move a tape volume
to a pool that contains tapes of a different medium or density, BrightStor
VM:Backup displays a message indicating that all tapes in a particular resource
pool must have the same physical attributes.
Managing Resource Pools
5–11
Creating Superpools
Creating Superpools
Before you create a superpool, make sure that the DASDtape resource pools you
want to include in the superpool exist. All resource pools defined to a superpool
must exist before the superpool is created.
To create a superpool, use the SCREATE/poolname command on the Manage
Resource Pools screen. Enter screate/poolname on the command line, where
poolname is the name of the superpool you want to create. BrightStor VM:Backup
displays the Resource Pool List for Superpool poolname screen. Use this screen to
identify the DASDtape resource pools you want to include in the superpool.
Adding DASDtape Resource Pools to a New Superpool
On the Resource Pool List for Superpool poolname screen, press PF5 (Insert). A data
entry field appears under the Resource Pool Name column. Enter the name of an
existing DASDtape resource pool. When you add pools to a superpool, consider
the following:
■
A single resource pool can belong to only one superpool.
■
A superpool record can be multi-line.
■
■
■
5–12
Administrator Guide
The medium defined for all resource pools within a superpool must be
DASDtape.
You can still use a resource pool that has been defined to a superpool on its
own, independent of the superpool.
In a superpool, when a particular resource pool runs out of available tapes,
BrightStor VM:Backup ignores the specified empty pool action for that
resource pool and uses a tape from the next resource pool in the superpool
pool list. When BrightStor VM:Backup has used the last volser in the last
resource pool in the list, BrightStor VM:Backup takes the empty pool action for
that resource pool.
Updating Superpools
Updating Superpools
To add DASDtape resource pools to or delete DASDtape resource pools from a
superpool, use the UPDATE command on the Manage Resource Pools screen.
Enter update in the Command column next to the superpool whose resource pools
you want to work with. BrightStor VM:Backup displays the Resource Pool List for
Superpool poolname screen for the selected superpool.
Discarding Resource Pools and Superpools
To delete a resource pool or superpool, use the DISCARD command on the
Manage Resource Pools screen. Enter discard in the Command column next to the
resource pool or superpool you want to delete.
As a safeguard against discarding a pool that still has tapes defined, BrightStor
VM:Backup displays the Discard a Resource Pool screen. This screen displays
information about the resource pool and gives you a second chance to review the
contents of the pool before discarding it.
If you still want to discard the displayed resource pool, enter yes on the command
line.
When you discard a superpool, the superpool is dissolved, but the individual
resource pools belonging to the superpool still exist. You cannot discard a resource
pool that belongs to a superpool until you either discard the superpool itself or you
delete the resource pool name from the list of pools defined to the superpool.
Note: When you discard a resource pool, make sure that you update any job
template files that reference the resource pool to specify a resource pool that still
exists.
Managing Resource Pools
5–13
Chapter
6
Managing Backup Job Template
Files
Backup job template files identify the data a particular job is to back up and how
the job is to process that data. This chapter explains how to create and maintain
BrightStor VM:Backup backup job template files through Option 4, Manage job
templates, on the System Administrator Main Menu.
Job Template File Information
When you select Option 4, Manage job templates, BrightStor VM:Backup displays
the Manage Job Templates screen. This screen provides the following information
about existing job template files:
■
Name of the job template file
■
Type of job template (always backup for a backup job)
■
Descriptive comments given to the job
The job template files listed on this screen include those created by BrightStor
VM:Archiver and BrightStor VM:Migrate which are identified by the descriptive
comment. These files are listed for information only; you cannot work with them.
You can use PF7 (Backward) and PF8 (Forward) to move through the list of job
template files. Enter the TOP and BOTTOM commands on the command line to
view the beginning and end of the job template file list.
Managing Backup Job Template Files
6–1
Job Template File Commands
Job Template File Commands
The commands listed in following table are available on the Manage Job Templates
screen. To work with an existing file, enter the appropriate command in the
Command column next to the file. To create a file, enter the appropriate command
on the command line.
Screen Commands to Manage Backup Templates
Command
Where to
Enter
Use this command to ...
BCREATE/template
Command
line
Create a new backup job template file
named template. The name, template,
corresponds to a CMS filename and must
be a unique job template file name
containing 1-8 characters.
COPY/template
Command
column
Create a new job template file by copying
an existing definition; template is the name
of the new job template file.
For example, you may want to copy a full
backup job template file to create an
incremental backup job template file that
will back up the same data specified in
the full backup job template file.
DISCARD
Command
column
Delete a job template file.
PRINT
Command
column
Send a report to your virtual printer that
describes the job according to the
definitions you specify on the job
template file. If an exception or exclusion
file is specified on the job template file,
the report also lists any exceptions or
exclusions defined for the job.
The PRINT command prints information
about the entire job; PF11 (Print) prints
the job template file definition screens on
screen at a time.
RENAME/template
6–2
Administrator Guide
Command
column
Rename an existing job template file;
template is the new name of the job
template file.
Creating or Updating Backup Job Template Files
Screen Commands to Manage Backup Templates
Command
Where to
Enter
Use this command to ...
TEST
Command
column
Tell BrightStor VM:Backup to send a
report to your virtual printer that
describes the job according to the
definitions you specify on the job
template file. This test report also
specifically identifies each minidisk or file
space to be included in the job.
If an exception file is specified, the report
indicates the options that are specified in
that exception file. If an exclusion file is
specified, the report does not show the
minidisks, file spaces, or user IDs that
were excluded.
UPDATE
Command
column
Modify an existing job template file.
Creating or Updating Backup Job Template Files
To create a backup job template file, use the BCREATE/template command on the
Manage Job Templates screen. Enter bcreate/template on the command line,
where template is the name of the backup job template file you want to create.
To update an existing backup job template file, use the UPDATE command on the
Manage Job Templates screen. Enter update in the Command column next to the
backup job template file you want to update.
In response to either command, BrightStor VM:Backup displays the first of the
Work with Backup Template template screens. Use these screens to specify the
following:
■
Descriptive comment
■
Type of backup job
■
Catalog guidelines
■
Output guidelines
■
How to detect changes from one backup to the next
■
Report guidelines
■
Select guidelines
Managing Backup Job Template Files
6–3
Creating or Updating Backup Job Template Files
■
Tape guidelines
■
Input guidelines
Describing the Backup Job
You can type up to 50 characters in the Descriptive Comments field in the backup
job template file. BrightStor VM:Backup displays the first 32 characters of this
comment on the Manage Job Templates screen.
Specifying the Backup Job Type
In the Type of Backup section of the Work with Backup Template template screen,
specify the following:
■
Type of backup you want BrightStor VM:Backup to perform
■
Backup level of detail
■
Backup job template files on which to base an incremental backup (for
incremental backup jobs)
Type of Backup
Select one of the following types of backups:
6–4
Full
BrightStor VM:Backup backs up each minidisk or file space
completely. This is the default.
Incremental
BrightStor VM:Backup backs up only those minidisks or file spaces
that have changed since a previous (full or incremental) backup.
When you define an incremental backup job, you must specify
whether the entire minidisk or file space should be backed up or
just the changed portions. You must also enter the names of the job
template files on which the incremental job is based.
Administrator Guide
Creating or Updating Backup Job Template Files
Detail Level
If the backup type is incremental, you must set the detail level of the incremental
backup job. Select one of the following detail levels:
■
File/Track/Block. BrightStor VM:Backup backs up only those portions of the
minidisk or file space that have changed since the previous backup. The
following describes what BrightStor VM:Backup backs depending on the type
of domain being processed.
Domain
BrightStor VM:Backup backs up each changed ...
CMS minidisk
File
CKD minidisk
Track
(Count-key-data)
FBA minidisk
(Fixed-blockarchitecture)
Group of blocks
One group comprises 32 blocks of 512 bytes; a change to
any block in a group causes the entire group to be backed
up.
BFS file space
File and its links, permissions, and ownership information
SFS file space
File and its authorizations
BrightStor VM:Backup also backs up an alias if its name
has changed or if the name of the base file to which it
points has changed.
A file-level base catalog is required to perform an incremental backup with
file-level detail. If the base catalog was not created with file-level detail,
BrightStor VM:Backup backs up the entire minidisk or file space if any portion
has changed. With only a domain-level catalog, BrightStor VM:Backup has no
base data against which file, track, or block changes can be compared.
■
Domain. BrightStor VM:Backup backs up the entire minidisk or file space if
any portion of the minidisk or file space has changed since the previous
backup. This is the default.
Based On
If the backup type is incremental, you must specify one or more base job template
files in the Based On field to identify the catalogs BrightStor VM:Backup is to use
to determine what data to back up. When you list more than one job template file
in the Based On field, BrightStor VM:Backup bases the incremental backup on the
most recently created catalog from any of the listed job template files.
Managing Backup Job Template Files
6–5
Creating or Updating Backup Job Template Files
In determining the data that needs to be backed up (that is, files, tracks, or blocks),
BrightStor VM:Backup compares the current minidisk or file space against the
most recent catalog to determine whether any changes have occurred. For
example, if you specify the job templates MONTHLY, WEEKLY, and DAILY in the
Based On field, BrightStor VM:Backup determines which of these three jobs was
run most recently and bases the incremental job on the catalog created during this
backup.
Enter the names of the job template files to be used as the base for the incremental
backup. You can use pattern matching to specify similar job template file names.
You can specify a maximum of 12 job template file names on this screen. If no
catalogs exist for the specified base backup job template files, BrightStor
VM:Backup performs a full backup.
If you want to specify more than 12 base backup job template files, you must use
the job template file BASE TEMPLATES record through TPI instead of the system
administrator screens. For information about this record and about TPI, see the
Template Programming Interface Guide.
Specifying Catalog Guidelines
A BrightStor VM:Backup catalog is a set of CMS files created and maintained by
BrightStor VM:Backup to store information about backed-up data. Although
BrightStor VM:Backup catalogs are optional, BrightStor VM:Backup uses a catalog
to determine what data has changed since a previous backup. Therefore, catalogs
are required for incremental backups. Catalogs are kept online and quickly provide
BrightStor VM:Backup with the information needed to locate data to restore.
In the Catalog Guidelines section of the Work with Backup Template template
screen, you specify the following:
■
Whether BrightStor VM:Backup should create a catalog or not
■
Catalog level of detail
■
Auto-discard period for the catalog
■
Auto-condense period for the catalog
Create a Catalog
To specify whether BrightStor VM:Backup is to create a catalog for the data it backs
up, select Yes or No in the Create a Catalog field.
6–6
Yes
BrightStor VM:Backup creates a catalog. This is the default.
No
BrightStor VM:Backup does not create a catalog.
Administrator Guide
Creating or Updating Backup Job Template Files
Detail Level
To specify the level of catalog detail, select one of the following in the Detail Level
field of the Catalog Guidelines section:
File/Track/Block BrightStor VM:Backup creates a catalog that contains
information about each file, alias, CKD track, or FBA block
backed up from each minidisk and file space.
Domain
BrightStor VM:Backup contains general entries for each
minidisk and file space backed up. This is the default.
Auto-Discard Period
In the Auto-Discard Period field, you specify the number of days you want
BrightStor VM:Backup to retain the catalog after the backup is run. BrightStor
VM:Backup automatically discards the catalog when the time period you specify
elapses and the automatic discard process is run. Any catalogs based on this
catalog are also discarded. For more information about when BrightStor
VM:Backup runs the automatic discard process, see the AUTOCAT configuration
file record in the Systems Programmer Reference.
To specify the number of days to retain the catalog, enter a whole number from 0
through 9999 in the Auto-Discard Period field. The number of days you specify
must be greater than or equal to the number of days you specify in the
Auto-Condense Period field. Zero (0) indicates that the catalog is to be discarded
the next time the automatic discard process is run. The default auto-discard period
is 30 days.
If you decide you need to retain the catalog longer, you can extend the retention
period by specifying a new auto-discard date on the Manage Existing Catalogs
screen. For details on updating the auto-discard period, see Updating Catalogs on
page 9-6.
Auto-Condense Period
Condensing catalogs refers to converting file-level detail catalogs to domain-level
detail catalogs. In the Auto-Condense Period field, you specify the number of days
you want BrightStor VM:Backup to retain file-level detail in the catalog after the
backup is run. BrightStor VM:Backup automatically condenses the catalog when
the time period you specify elapses and the automatic condense process is run.
Any catalogs based on this catalog are also condensed. For more information about
when BrightStor VM:Backup runs the automatic condense process, see the
AUTOCAT configuration file record in the Systems Programmer Reference.
Managing Backup Job Template Files
6–7
Creating or Updating Backup Job Template Files
To specify the number of days to retain file-level detail in the catalog, enter a whole
number from 0 through 9999 in the Auto-Condense Period field. The number of
days you specify must be less than or equal to the number of days you specify in
the Auto-Discard Period field. Zero (0) indicates that the catalog is to be
condensed the next time the automatic condense process is run. The default
auto-condense period is 15 days.
If you decide you need to retain the file-level information longer, you can extend
the retention period by specifying a new auto-condense date on the Manage
Existing Catalogs screen. For details on updating the auto-condense period, see
Updating Catalogs on page Updating Catalogs on page 9-6.
Specifying Output Guidelines
In the Output Guidelines section of the Work with Backup Template template
screen, you specify the following:
■
Format for backing up minidisks
■
Whether BrightStor VM:Backup is to back up changing minidisks physically
■
■
■
Whether BrightStor VM:Backup is to check for changes during file space
backups
Whether BrightStor VM:Backup is to pack data as it backs the data up
Whether BrightStor VM:Backup is to remount tapes already written to in the
currently running backup job
Backup Type
Use the Backup Type field to select one of the four backup formats: Logical, CMS,
CMSALLOC, or Physical.
Note: BrightStor VM:Backup always backs up SFS file spaces in SFS format,
regardless of what you specify in this field.
■
6–8
Administrator Guide
Logical. BrightStor VM:Backup determines the best way to back up data based
on the type of domain being backed up. This is the default.
Type of Domain
Backup Format
CMS minidisk
CMS format
BFS file space
BFS format
Non-CMS minidisk
Physical format
Creating or Updating Backup Job Template Files
Type of Domain
Backup Format
Recomputed minidisk
CMS format--CMS area
Physical format--Recomputed area
A recomputed (recomped) CMS minidisk is a
minidisk that has been formatted with the
RECOMP option of the CMS FORMAT command.
Reserved minidisk
Physical format
A reserved CMS minidisk is a minidisk that has
been formatted with the CMS RESERVE
command.
SFS file space
■
■
■
SFS format
CMS. BrightStor VM:Backup backs up all CMS minidisks in the same manner
as a logical backup described above. Non-CMS are not backed up at all. For
reserved minidisks, BrightStor VM:Backup performs a physical backup of the
entire minidisk.
CMSALLOC. BrightStor VM:Backup reads the block allocation map on CMS
minidisks to identify which blocks are free or active, and physically backs up
only those that are active. Non-CMS minidisks are backed up physically. If
you specify CMSALLOC in a full or incremental backup, BrightStor
VM:Backup automatically performs a full backup.
Physical. BrightStor VM:Backup determines the disk type of the minidisk,
then performs a physical backup accordingly. CKD minidisks are backed up
by track, and FBA minidisks are backed up in groups of 32 blocks of 512 bytes.
CMS Switch to Physical
During a backup job, BrightStor VM:Backup sometimes encounters a minidisk to
which changes are being made. For a CMS or CMSALLOC backup, you can specify
whether BrightStor VM:Backup should switch to a physical backup or skip the
minidisk if it is unable to back up the minidisk in the requested format. BrightStor
VM:Backup attempts to back up the minidisk in the requested format the number
of times you specify. Use the CMS Switch to Physical? field to set these options:
Yes
BrightStor VM:Backup switches to a physical backup of the minidisk
if the minidisk continues to change after the specified number of tries.
This is the default.
Managing Backup Job Template Files
6–9
Creating or Updating Backup Job Template Files
No
BrightStor VM:Backup skips the minidisk if the minidisk continues to
change after the specified number of tries.
Attempts BrightStor VM:Backup attempts this number of tries to back up the
minidisk in the requested format. Specify a whole number from one
through nine. By default, BrightStor VM:Backup tries to back up a
changing minidisk three times before either switching to a physical
backup or skipping the changing minidisk.
Number of Tries for Consistent View of File Space
By default, BrightStor VM:Backup does not check for changes in a file space during
a backup. This setting is suitable for most sites because SFS guarantees a consistent
view of individual files. However, if your site runs applications that require files to
be maintained at the same commit level, that is, in sync with each other, you
should have BrightStor VM:Backup make one or more attempts to obtain a
consistent view. You can specify the maximum number of times you want it to
check for changes (up to 9) in the Number of Tries for a Consistent View of File
Space field.
If, after the maximum number of checks, BrightStor VM:Backup still cannot obtain
a consistent view of the file space, BrightStor VM:Backup backs it up and writes a
message in the job output report stating a consistent view was not obtained.
BrightStor VM:Backup cannot detect changes made to update-in-place files. All
BFS files are update-in-place files. To ensure that you obtain a consistent
point-in-time view of BFS file spaces and SFS file spaces that contain
update-in-place files, you must quiesce these file spaces during backups.
Pack
To have BrightStor VM:Backup pack data as it backs it up, select Yes in the
Compression field. When you select Yes, BrightStor VM:Backup uses a general
purpose packing algorithm that eliminates repeating characters (for example,
blanks) in a data file by replacing them with a three-byte field. By default,
BrightStor VM:Backup does not pack data as it backs it up.
If hardware compression is available to you through IDRC-capable tape drives,
you can still have BrightStor VM:Backup pack the data; however, the job run time
and the number of tapes needed for the job may increase. Experiment with a
variety of jobs to see which settings give you the right balance between job run
times and number of tapes produced.
6–10
Administrator Guide
Creating or Updating Backup Job Template Files
Remounts
Use the Remounts field to specify whether BrightStor VM:Backup is to remount
tapes already written to in the currently running backup job, as follows:
Conserve Tapes,
Allow Tape Remounts
Allows BrightStor VM:Backup to remount tapes, thus
minimizing the number of tapes needed for the
backup job. This is the default.
Save Time,
Reduce Tape Remounts
Prevents BrightStor VM:Backup from remounting
tapes in most situations. This can make backup jobs
run more quickly.
If your data center uses automatic cartridge loaders
(ACLs), you may want to select this option.
Depending on the control setting for your ACL, it may
not be able to remount a tape that has already been
mounted in the currently running job. This is true if
the control setting on the ACL is set to AUTOMATIC.
This may also be true if the control setting is set to
SYSTEM and the software you use to mount tapes
cannot handle this situation.
For more information about tape remounts, see the
chapter “Managing Tape and DASD Resources” in the
Systems Programmer Reference.
Specifying Change Detection for a Backup
Use the Change Detection section of the Work with Backup Template template
screen to indicate how BrightStor VM:Backup is to identify when data changes
between backups. Depending on whether this is a full or incremental backup job,
BrightStor VM:Backup will react differently to what you specify for change
detection.
■
■
For a full backup, BrightStor VM:Backup uses the change detection selection
to determine what to save in the catalog to use for comparison during an
incremental backup to detect whether data has changed.
In incremental backups, BrightStor VM:Backup uses the change detection
selection to determine what values should be compared with the values stored
in the catalog to determine whether data has changed.
Managing Backup Job Template Files
6–11
Creating or Updating Backup Job Template Files
Storing Change Detection Information
The following describes what change detection information BrightStor
VM:Backup stores in the catalog for each backup format.
CMS Backups
Date
BrightStor VM:Backup stores file and minidisk date information in the
catalog.
Date is the default option for CMS backups.
Hash BrightStor VM:Backup uses a hash value to determine whether the
contents of a file or minidisk have changed.
If BrightStor VM:Backup is creating file-level catalogs, BrightStor
VM:Backup computes a hash value of the contents of each file backed up
and stores the values in the catalog.
If BrightStor VM:Backup is creating domain-level catalogs, BrightStor
VM:Backup computes a hash value of the contents of each minidisk
backed up and stores the values in the catalog.
Select this option if you have applications that use non-CMS access
methods that do not update file status table (FST) information when
modifying files or minidisks.
6–12
Administrator Guide
Creating or Updating Backup Job Template Files
Physical Backups
Hash
BrightStor VM:Backup uses a hash value to determine whether the
contents of a minidisk have changed.
If BrightStor VM:Backup is creating file-level catalogs, BrightStor
VM:Backup computes a hash value of the contents of each CKD track or
FBA group of blocks backed up and stores the values in the catalog.
If BrightStor VM:Backup is creating domain-level catalogs, BrightStor
VM:Backup computes a hash value of the contents of each minidisk
backed up and stores the values in the catalog.
Hash is the default option for physical backups.
None
BrightStor VM:Backup does not save hash values for change detection.
When you select None, BrightStor VM:Backup cannot detect changes;
incremental backup jobs will perform a full backup of these minidisks.
You may decide against saving hash values for physical backups if a
minidisk changes or is restored frequently. Not saving hash values
reduces the number of CPU cycles BrightStor VM:Backup uses and may
result in improved backup performance.
SFS and BFS Backups
When backing up SFS and BFS data, BrightStor VM:Backup always computes a
special hash value to detect changes in a file space, regardless of what you enter in
this field.
Detecting Changes During Incremental Backups
To allow BrightStor VM:Backup to detect changes, you must specify the same type
of change detection in the full backup and incremental backup templates. When
you specify different types of change detection for the full and incremental
backups, BrightStor VM:Backup is unable to detect changes when the incremental
backup is submitted. For example, in a CMS backup, when you select Date for a
full backup, BrightStor VM:Backup does not compute and store hash values for
data. When you select Hash for the incremental backup, BrightStor VM:Backup
cannot determine whether data has changed because there are no hash values in
the catalog created by the full backup. When BrightStor VM:Backup is unable to
detect changes for a domain in an incremental backup, a full backup is taken of that
domain. If you specify CMSALLOC as the backup format in an incremental
backup job template, BrightStor VM:Backup automatically performs a full backup
regardless of specifications in the template for detecting changes.
Managing Backup Job Template Files
6–13
Creating or Updating Backup Job Template Files
When you select Date change detection, BrightStor VM:Backup compares the date
stored in the catalog with the current date of the file or minidisk to be backed up
to determine whether the contents of the file or minidisk have changed.
When you select Hash change detection, BrightStor VM:Backup recomputes the
hash value for each file, CKD track, FBA group of blocks, or minidisk and
compares this value with the value stored in the catalog to determine whether the
contents of the file or minidisk have changed.
When you select None for an incremental backup, BrightStor VM:Backup does not
detect changes; BrightStor VM:Backup performs a full backup.
Specifying Report Guidelines
In the Report Guidelines section of the Work with Backup Template template
screen, you specify the following:
■
Detail level of reports produced by backup jobs (including keyword data
reports)
■
Where BrightStor VM:Backup is to route the reports
■
Whether BrightStor VM:Backup is to create a keyword data report
For a complete description of keyword data reports and other reports, output
listings, and notes BrightStor VM:Backup generates when processing backup jobs,
see the Systems Programmer Reference.
Detail Level
In the Report Guidelines section, select either File or Domain in the Detail Level
field to set the level of detail BrightStor VM:Backup should include in the reports
produced by backup jobs.
File
BrightStor VM:Backup produces a report that contains detailed
information about the files backed up. For backups of minidisks and
SFS file spaces, the report lists file attributes in a format similar to that
provided by the CMS LISTFILE command with the DATE option. For
backups of BFS file spaces, the report lists file attributes similar to that
provided by the CMS OPENVM LISTFILE command with the
ATTRIBUTES option.
Domain BrightStor VM:Backup produces a report that contains general
information about the minidisks or file spaces backed up. This is the
default.
6–14
Administrator Guide
Creating or Updating Backup Job Template Files
Route to
Use the Route Control fields to specify where BrightStor VM:Backup is to route
reports produced by the backup job. Fill in the Detail fields to identify where
BrightStor VM:Backup is to route the job detail report; fill in the Errors fields to
identify where BrightStor VM:Backup is to route the job error report. For each
report, specify the following information:
Use these fields to identify where BrightStor VM:Backup is to send
the reports. By default, BrightStor VM:Backup sends the reports to
At (node) the virtual reader of the user ID that created the job template file in
the local system (destination node).
Userid
To send the report to another user ID, type over the default user ID.
To send the report to another destination node, specify the
destination node. If the user ID you specify does not exist, or you
specify SYSTEM for the user ID, BrightStor VM:Backup sends all
output to the virtual reader of the BrightStor VM:Backup service
virtual machine.
Class
BrightStor VM:Backup can also send this report in a designated
virtual printer spool class. The default printer spool class is the class
of the first virtual printer indicated in the response BrightStor
VM:Backup receives from the CP QUERY VIRTUAL UR command at
system initialization. If a printer class is not defined, BrightStor
VM:Backup uses the default class A.
To override the default report class, specify the desired class.
Note: This routing specification does not include keyword data reports; you must
use the GETRPT command to obtain a keyword data report. For more information,
see the GETRPT command in the Systems Programmer Reference.
Keyword Data Reports
A keyword data report is a CMS file produced by a BrightStor VM:Backup job that
contains records describing the results of that job. These reports are designed for
use by programs that process information about BrightStor VM:Backup jobs. To
indicate whether you want BrightStor VM:Backup to create a keyword data report
for the job, select either Yes or No in the Keyword Report field.
Yes
BrightStor VM:Backup produces a keyword data report.
No
BrightStor VM:Backup does not produce a keyword data report. This is the
default.
Managing Backup Job Template Files
6–15
Creating or Updating Backup Job Template Files
BrightStor VM:Backup does not create a keyword data report for jobs that back up
the BrightStor VM:Backup service virtual machine even if a keyword data report
is requested. BrightStor VM:Backup cannot write to the report minidisk at the
same time it is trying to back up the minidisk.
Specifying Select Guidelines
In the Select Guidelines section of the Work with Backup Template template
screen, you can specify the following:
■
■
An exclusion file that specifies minidisks, account numbers, access control
interface (ACI) security groups, or file spaces that are not to be backed up
An exception file that specifies special processing for minidisks, account
numbers, ACI security groups, or file spaces
You can use the same exception or exclusion file with any number of job template
files, but you can specify only one exception file and one exclusion file in a single
job template file. If the same data is referenced in both types of files, the exclusion
file takes precedence and BrightStor VM:Backup excludes the data from the job.
Note: If the exception file for an incremental backup differs from the exception file
for the previous full backup, BrightStor VM:Backup will perform a full backup
instead of an incremental backup on those minidisks or file spaces affected by the
exception file.
For information about exception and exclusion files, see Managing Exception and
Exclusion Files on page 8-1.
Specifying Tape Guidelines
In the Tape Guidelines section of the Work with Backup Template template screen,
specify the resource pools from which BrightStor VM:Backup is to select tapes
during the backup. Depending on the options you choose, you can have BrightStor
VM:Backup write to tapes in different resource pools, create several copies of each
tape, and record unique retention periods and data set names on each tape copy
you create. All tapes are written with standard labels.
Number of Tape Streams
In the Number of Tape Streams field specify the number of tape streams to be
used in the backup. When using tape streams, BrightStor VM:Backup divides the
minidisks and file spaces among two or more streams, allowing data to be backed
up from several minidisks and file spaces at the same time. The data being backed
up is written to each stream independently and concurrently. BrightStor
VM:Backup can manage a maximum of 15 streams in one job. One stream is the
default.
6–16
Administrator Guide
Creating or Updating Backup Job Template Files
Resource Pool Name and Tape Copies
In the Resource Pool column, specify the name of the resource pool or superpool
from which tapes are to be chosen for use in the backup. If you want to create tape
copies, specify the resource pool from which each tape copy is to be obtained. You
can specify the same pool name for all tape copies. You can create up to four tape
copies in addition to the primary tape.
Except for the tape label and header information, tape copies are duplicate tapes
created at the same time on different drives.
Retention Period
In the Retention Period column, specify the number of days from the date the
backup is run that BrightStor VM:Backup is to retain the tapes created. BrightStor
VM:Backup writes the expiration date in the label of each tape used in the job. You
can specify different retention periods for the primary tape and each tape copy.
The number of days must be a number from 0 through 9999; 30 is the default.
Data Set Name
In the Data set Name column, you can specify data set names for the tape files
created during the backup, giving different names to the primary tape and each
tape copy. By default, BrightStor VM:Backup creates data set names based on tape
copy number (for example, VMBACKUP.PRIMARY and VMBACKUP.COPY1).
Use the following characters for data set names:
■
Alphanumeric characters (A-Z, 0-9)
■
Special characters: period (.), at sign (@), pound sign (#), and dollar sign ($)
The data set name can contain up to 44 characters. However, to conform to OS
standard tape label support, only the last 17 characters of the data set name are
written to the tape label. If you use BrightStor VM:Tape, the full data set name (up
to 44 characters) will be cataloged in the BrightStor VM:Tape TMC, but the tape
label will still contain only the last 17 characters.
Specifying Input Guidelines
In the Input Guidelines fields, specify the data BrightStor VM:Backup is to
process during the backup. You can define the backup broadly (for example, if you
want to back up all of the DASD volumes in your data center), or you can restrict
the backup to specific minidisks, file spaces, user IDs, account numbers, or ACI
security groups.
Managing Backup Job Template Files
6–17
Creating or Updating Backup Job Template Files
You can further limit the backup job by defining an exclusion file. For more
information about excluding data from a backup, see Creating or Updating an
Exclusion File on page 8-13.
Including Data
You cannot leave both the Include DASD and Include File Pools fields blank;
specify at least one DASD volser or file pool name.
Backing Up DASD Volumes
By default (indicated by the asterisk in the Include DASD field), BrightStor
VM:Backup backs up all of the minidisks on every DASD volume referenced in the
CP directory. To back up minidisks from certain DASD volumes, type the DASD
volsers in the fields provided. You can enter up to 12 individual volsers; you can
also use pattern matching to back up several volumes with similar volsers.
If you want to specify more than 12 DASD volumes, you must use the job template
file INCLUDE record through TPI instead of the system administrator screens. For
information about this record and about TPI, see the Template Programming
Interface Guide.
Backing Up File Pools
By default (as indicated by the asterisk in the Include File Pools field), BrightStor
VM:Backup backs up all of the file spaces (both SFS and BFS) in every local file pool
that you have identified to BrightStor VM:Backup. BrightStor VM:Backup cannot
back up data in remote file pools, that is file pools that are located on a different
system from the BrightStor VM:Backup service virtual machine. For more
information, see Identifying SFS File Pools on page 3-11.
To back up file spaces from specified file pools, type the file pool names in the
fields provided. You can enter up to 12 individual file pool names; you can also use
pattern matching to back up several file pools with similar names.
If you need to specify, view, or manage a job template file with more than 12 file
pools, you must use the job template file INCLUDE record through TPI instead of
the system administrator screens. For information about this record and about TPI,
see the Template Programming Interface Guide.
6–18
Administrator Guide
Creating or Updating Backup Job Template Files
Restricting the Backup
You can limit the backup by specifying that BrightStor VM:Backup back up only
certain user IDs, minidisks, account numbers, or ACI groups from the specified
DASD volumes, or that BrightStor VM:Backup back up only certain file spaces
from the specified file pools.
By default, (as indicated by USERID * * and FSPACE *:* in the Restricted to
records field), BrightStor VM:Backup backs up all minidisks and file spaces on the
specified DASD volumes and in the specified file pools. If you change these values,
specify at least one of the following record types and values; this field cannot be
left blank.
Record Type
Value
USErid
userid vaddr
ACCount
number
ACIgroup
name
FSPace
filepoolid:userid
(for an SFS or BFS file space)
Use pattern matching to back up file spaces with similar names or groups of
minidisks with similar user IDs, account numbers, or ACI security group names.
If the same user is included in more than one record type, that user's data will only
be backed up once.
FSPACE records identify both BFS and SFS file spaces. For example, if you accept
the default, *:*, BrightStor VM:Backup backs up all file spaces (both BFS and SFS)
in all file pools identified to BrightStor VM:Backup.
Example
Based on the Input Guidelines shown in Work with Backup Template Screen on
page 6-20, BrightStor VM:Backup will back up data belonging to these users:
■
Userid JOHN's 191 minidisk
■
All minidisks belonging to account number AB123
■
■
■
All minidisks belonging to user IDs whose ACI group name has six characters
starting with PROG
All minidisks belonging to userid MARY
All SFS and BFS file spaces in file pools whose file pool names start with SF and
whose user IDuser IDs start with J
Managing Backup Job Template Files
6–19
Creating or Updating Backup Job Template Files
WBTMABC4 (4 of 7) Work with Backup Template BIGDUMP VM:Backup
-------------------------------------------------------------------------------Input Guidelines:
Include DASD: * ______ ______ ______ ______ ______
______ ______ ______ ______ ______ ______
Include File
Pools:
Restricted to
records:
SFSPRD__ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
Type
userid
account_
acigroup
userid
fspace__
________
Value
john 191
ab123____________
prog%%___________
mary *___________
sf*:j*___________
_________________
Type
________
________
________
________
________
Value
_________________
_________________
_________________
_________________
_________________
-------------------------------------------------------------------------------PF: 1 Help
PF: 7 ...
===>
2 ...
8 ...
3 End
9 ...
Work with Backup Template Screen
6–20
Administrator Guide
4 Return
10 ...
5 ...
11 Print
6 ...
12 Cursor
Chapter
7
Managing Restore Job Template
Files
Restore job template files identify the data to be restored in a specific job and how
it is to be processed. For example, you may want to define restore job template files
to handle large restore requests. Restore job template files enable you to restore full
DASD volumes or groups of minidisks for several user IDs, account numbers, or
ACI security groups.
You may have tapes with no corresponding catalogs. Using a restore job template
file, you can restore data from a tape set by specifying the first volser from the tape
set.
This chapter explains how to create and maintain restore job template files through
Option 4, Manage job templates, on the System Administrator Main Menu. You
cannot create restore job template files that restore SFS or BFS file spaces, user
storage groups, or file pools through this option; you must use either Option 7,
Submit special SFS/BFS restores, or TPI instead. For more information about
restoring SFS or BFS data using TPI, see Starting Special SFS and BFS Restores on
page 10-1 in this book or to the Template Programming Interface Guide.
Job Template File Information
When you select Option 4, Manage job templates, BrightStor VM:Backup displays
the Manage Job Templates screen. This screen provides the following information
about existing job template files:
■
Name of the job template file
■
Type of job template (always restore for restore jobs)
■
Comments about the job
The job template files listed on this screen include those created by BrightStor
VM:Archiver and BrightStor VM:Migrate which are identified by the descriptive
comment. These files are listed for information only; you cannot work with them.
Managing Restore Job Template Files
7–1
Job Template File Commands
You can use PF7 (Backward) and PF8 (Forward) to move through the list of job
template files. Enter the TOP and BOTTOM commands on the command line to
view the beginning and end of the job template file list.
Job Template File Commands
The commands listed in the following table are available on the Manage Job
Templates screen. To work with an existing file, enter the appropriate command in
the Command column next to the file. To create a file, enter the appropriate
command on the command line.
Screen Commands to Manage Restore Templates
Tip: Command
Tip: Where to
Enter
Tip: Use this command to ...
COPY/template
Command
column
Create a new job template file by copying
an existing definition; template is the name
of the new job template file. Copying a job
template file is useful when there are only
minor processing variations between
different jobs.
DISCARD
Command
column
Delete a job template file.
PRINT
Command
column
Send a report to your virtual printer that
describes the job according to the
definitions you specify on the job template
file If an exception or exclusion file is
specified on the job template file, the
report also lists any exceptions or
exclusions defined for the job.
The PRINT command prints information
about the entire job; PF11 (Print) prints the
job template file definition screens one
screen at a time.
RCREATE/template Command line Create a new restore job template file;
template is the job template file name. This
name, which corresponds to a CMS
filename, must be a unique job template
file name with a maximum of eight
characters.
7–2
Administrator Guide
Creating or Updating Restore Job Template Files
Screen Commands to Manage Restore Templates
Tip: Command
Tip: Where to
Enter
Tip: Use this command to ...
RENAME/template
Command
column
Rename an existing job template file;
template is the new name of the job
template file.
TEST
Command
column
Tell BrightStor VM:Backup to send a
report to your virtual printer that
describes the job according to the
definitions you specify on the job template
file. This test report also specifically
identifies each minidisk to be included in
the job.
If you specify an exception file, the report
indicates the options that are specified in
that exception file. If you specify an
exclusion file, the report will not show the
minidisks or user IDs that were excluded.
UPDATE
Command
column
Modify an existing job template file.
Creating or Updating Restore Job Template Files
To create a restore job template file, use the RCREATE/template command on the
Manage Job Templates screen. Enter rcreate/template, where template is the name
of the restore job template file you want to create.
To update an existing restore job template file, use the UPDATE command on the
Manage Job Templates screen. Enter update in the Command column next to the
restore job template file you want to update.
In response to either command, BrightStor VM:Backup displays the first Work
with Restore Template template screen. Use the Work with Restore Template
template screens to specify the following:
■
Descriptive comment
■
Type of restore job
■
Search time period
■
Input tapes for VOLSEARCH restore jobs
■
Report guidelines
■
Select guidelines
Managing Restore Job Template Files
7–3
Creating or Updating Restore Job Template Files
■
Restore target
■
Link option
■
Formatting options
Describing the Restore Job
You can type up to 50 characters in the Descriptive Comments field in the restore
job template file. BrightStor VM:Backup displays the first 32 characters of this
comment on the Manage Job Templates screen.
Specifying the Restore Job Type
Use the Restore Data field to select either Using Catalogs or Scanning Tapes to
specify the type of restore job you want BrightStor VM:Backup to perform.
Using Catalogs
This option tells BrightStor VM:Backup that you have catalogs
available and want to perform a CATSEARCH restore job. In
CATSEARCH jobs, BrightStor VM:Backup searches the catalogs
for the data to restore until it meets the limits of the specified
time period or finds a full backup, whichever occurs first. You
can use CATSEARCH jobs to restore files when a catalog is
available. This is the default.
Scanning Tapes This option tells BrightStor VM:Backup that you do not have
catalogs available and want to perform a VOLSEARCH restore
job. In VOLSEARCH jobs, BrightStor VM:Backup searches the
tape volumes and restores data as it is encountered on the tapes.
Use VOLSEARCH jobs when the tapes that contain the backup
data are available but the catalogs are not available.
Specifying the Search Time Period
For a CATSEARCH restore job, BrightStor VM:Backup searches catalogs created
during a specified time period. When it finds the data to restore, BrightStor
VM:Backup restores the version of the data that was backed up most recently
within this time period. If the version of the data selected is from an incremental
backup, BrightStor VM:Backup uses all previous incremental backups and the full
backup on which they are based to perform the restore.
For a VOLSEARCH restore job, BrightStor VM:Backup makes sure the starting
input tape was created within the specified time period. If it was not, BrightStor
VM:Backup does not run the job. If the tape was created within the specified time
period, the job continues. If the specified tape is from an incremental backup,
7–4
Administrator Guide
Creating or Updating Restore Job Template Files
BrightStor VM:Backup uses all previous incremental backups and the full backup
on which they are based to perform the restore.
The To Limit Restore, Specify Search Range section of the screen shows the
default start date and time 01/01/1942 00:00:00 and the default end date and time
12/31/2041 23:59:59. You can type over these dates and times to specify a different
time period. Use the date format mm/dd/yyyy for the dates, and a 24-hour format
for the times.
To perform an incremental only restore of a minidisk, you must create a TPI job
and include the CUTOFF record. The CUTOFF record can prevent BrightStor
VM:Backup from going back to the full backup. For more information about this
record, see the Template Programming Interface Guide.
Specifying Starting Input Tape for VOLSEARCH Restore Jobs
If the catalog created during a backup no longer exists, or if the catalog was never
created, BrightStor VM:Backup can still locate and restore required data if the
tapes created during the backup are available. Volsers for the next and previous
tapes used in the backup are kept in the tape labels unless BrightStor VM:Backup
has been configured otherwise; see the TAPECHAIN configuration record in the
Systems Programmer Reference. All tapes created during all backup jobs from which
BrightStor VM:Backup is restoring must be available to restore without a catalog.
Use the If Scanning Tapes section of the Work with Restore Template template
screen to specify the starting input tape for VOLSEARCH restore jobs.
Tape Volser and DSSN
To specify the tape and data set from which data is to be restored, fill in the
following fields:
Tape Volser Type the volser of the tape from which data is to be restored.
DSSN
Type the data set sequence number of the data set from which data
is to be restored. DSSN must be 1 for all BrightStor VM:Backup jobs.
The specified tape must be the first tape written in any stream of the most recent
backup that you want to restore.
Managing Restore Job Template Files
7–5
Creating or Updating Restore Job Template Files
Media and Density
Indicate the media and density of the backup tape you specified in the Tape Volser
field by selecting one media from the Media field and one density from the
Density field. This is required so BrightStor VM:Backup can issue the correct
mount request. To determine the proper settings, see the section Enhanced Device
Recognition Support in the chapter “Managing Tape and DASD Resources” in the
Systems Programmer Reference.
Specifying Report Guidelines
In the Report Guidelines section of the Work with Restore Template template
screen, you specify the following:
■
Detail level of reports produced by restore jobs (including keyword data
reports)
■
Where BrightStor VM:Backup is to route the reports
■
Whether BrightStor VM:Backup is to create a keyword data report
For a complete description of keyword data reports and other reports, output
listings, and notes BrightStor VM:Backup generates when processing restore jobs,
see the Systems Programmer Reference.
Detail Level
Select one of the following fields in the Detail Level field to set the level of report
detail:
7–6
File
BrightStor VM:Backup produces a report that contains detailed
information about each file restored. The report lists file attributes in
a format similar to that provided by the CMS LISTFILE command
with the DATE option.
Minidisk
BrightStor VM:Backup produces a report containing general
information about the minidisks restored. This is the default.
Administrator Guide
Creating or Updating Restore Job Template Files
Route to
Specify the following information in the Route to field to specify where BrightStor
VM:Backup is to route the report produced by the restore job:
Userid
Use these fields to identify where BrightStor VM:Backup is to send
At (node) the report. By default, BrightStor VM:Backup sends the restore job
report to the virtual reader of the user ID that created the job template
file in the local system (destination node).
To send the report to another user ID, type over the default user ID.
To send the report to another destination node, specify the
destination node. If the user ID you specify does not exist, or you
specify SYSTEM for the user ID, BrightStor VM:Backup sends all
output to the virtual reader of the BrightStor VM:Backup service
virtual machine.
Class
BrightStor VM:Backup can send this report in a designated virtual
printer spool class. The default printer spool class is the class of the
first virtual printer indicated in the response BrightStor VM:Backup
receives from the CP QUERY VIRTUAL UR command at system
initialization. If a printer class is not defined, BrightStor VM:Backup
uses the default class A.
To override the default report class, specify the desired class.
Data restored to a virtual reader is always sent with spool class A.
Note: This routing specification does not include keyword data reports; you must
use the GETRPT command to obtain a keyword data report. For more information,
see the GETRPT command in the Systems Programmer Reference.
Keyword Data Reports
A keyword data report is a CMS file produced by a BrightStor VM:Backup job that
contains records describing the results of that job. These reports are designed for
use by programs that process information about BrightStor VM:Backup jobs. To
indicate whether you want BrightStor VM:Backup to create a keyword data report
for the job, select either Yes or No in the Keyword Report field.
Yes
BrightStor VM:Backup produces a keyword data report.
No
BrightStor VM:Backup does not produce a keyword data report. This is the
default.
Managing Restore Job Template Files
7–7
Creating or Updating Restore Job Template Files
Specifying Select Guidelines
In the Select Guidelines section of the Work with Restore Template template
screen, you can specify the following:
■
■
An exclusion file that specifies minidisks, account numbers, or ACI security
groups that are not to be restored
An exception file that specifies special processing for minidisks, account
numbers, or ACI security groups
You can use the same exception or exclusion file with any number of job template
files, but you can specify only one exception file and one exclusion file in a single
job template file. If the same data is referenced in both types of files, the exclusion
file takes precedence and BrightStor VM:Backup excludes the data from the job.
For information about exception and exclusion files, see Managing Exception and
Exclusion Files on page 8-1.
Specifying the Restore Target
In the Restore Data to field, you can select one of the following to specify where
BrightStor VM:Backup is to restore data:
Original
Minidisk
BrightStor VM:Backup restores data to the minidisks from which
data was backed up. Data backed up in CMS format can be restored
to a minidisk; data backed up in physical format must be restored to
a minidisk.
Reader
BrightStor VM:Backup restores data to the virtual reader of the user
ID owning the original minidisk. Only data backed up in CMS format
can be restored to a virtual reader.
Specify this option only when working with a template for a
CATSEARCH restore job.
7–8
Administrator Guide
Creating or Updating Restore Job Template Files
Alternate
Volume
BrightStor VM:Backup restores data to a DASD volume other than its
original source volume.
BrightStor VM:Backup creates an image of all or portions of another
volume on this alternate volume. The alternate volume will be
attached to BrightStor VM:Backup and minidisk images will be
overlaid by obtaining the location and size of the original minidisk
from the CP directory entry. You do not have to define any minidisks
on the alternate volume. BrightStor VM:Backup will restore
minidisks defined on the original source volume currently in the CP
directory to the same physical locations on the target volume.
When you start the restore, make sure the target volume is online and
not attached to any user ID (including BrightStor VM:Backup).
If you are restoring a CKD device, the target volume must be the
same device class and type as the source volume; for example, you
must restore a 3380 device to a 3380 device. If you are restoring an
FBA device, the target volume must be an FBA device.
Specifying the Link Option
If you are restoring data to the original minidisk, you must indicate the type of link
BrightStor VM:Backup is to obtain and the action BrightStor VM:Backup is to take
if the target is linked by another user.
Link to Obtain
In the Link to Users' Disks Using field, select the type of link BrightStor
VM:Backup is to obtain, as follows:
Write This option specifies that BrightStor VM:Backup is to obtain a write link
Link to the target minidisk only if no other user ID is linked to the minidisk in
either read or write access mode. If another user ID is linked, no link is
established for BrightStor VM:Backup and detach minidisk messages are
issued to all user IDs linked to the minidisk. This is the default.
Mult
Link
This option specifies that BrightStor VM:Backup is to obtain a write link
to the target minidisk even if another user ID is linked in read-only mode,
unless another user ID already has write access. BrightStor VM:Backup
requires write access to restore data to a minidisk.
Managing Restore Job Template Files
7–9
Creating or Updating Restore Job Template Files
Wait for Users to Detach Disks
During restore processing, BrightStor VM:Backup may try to link a user's minidisk
but not be able to get write access (that is, a Write or Mult link) because other users
are linked to that target minidisk. BrightStor VM:Backup sends detach messages
to users (and message 797I to the tape operator and local console) and stops restore
processing for this job until the minidisk is successfully linked. BrightStor
VM:Backup cannot continue processing this job until one of the following occurs:
■
■
■
All linked users detach the minidisk.
A user cancels the detach request, which tells BrightStor VM:Backup to not
restore the minidisk.
The wait time specified in the USERWAIT configuration file record expires.
In the Wait for Users to Detach Disks field, select whether you want BrightStor
VM:Backup to wait for users to detach linked minidisks or to skip restoring data
from linked minidisks, as follows:
Yes
When BrightStor VM:Backup encounters a target minidisk to which it
cannot obtain write access, BrightStor VM:Backup waits for users to detach
that minidisk.
No
When BrightStor VM:Backup encounters a target minidisk to which it
cannot obtain write access, BrightStor VM:Backup skips restoring data
from that particular backup of that minidisk and goes on to the next
minidisk. BrightStor VM:Backup records this information in the restore job
summary report.
Specifying Formatting Options
If you are restoring data from CMS and logical backups to the original minidisks
or to an alternate volume, you must indicate whether BrightStor VM:Backup is to
format the minidisk.
7–10
Administrator Guide
Creating or Updating Restore Job Template Files
If Formatting
If you are restoring to a minidisk that is not formatted, select one of the following
formatting options or use the CMS FORMAT command to format the minidisk
before running the restore. When a minidisk is formatted, all currently existing
files are erased and the minidisk is returned to the same blocksize it had when it
was backed up.
Format Only This option specifies that BrightStor VM:Backup is to perform the
equivalent of the CMS FORMAT command to format the minidisk
if Files to
Restore
before restoring data to it only if there is data to be restored. When
the data is restored, the minidisk appears exactly as it did when
the backup was performed.
Format Even This option specifies that BrightStor VM:Backup is to perform the
if No Files to equivalent of the CMS FORMAT command to format the minidisk
Restore
even if there is no data to restore.
If Not Formatting
If you do not format the minidisk, you must select one of the following options to
indicate how the data is to be restored.
Newfile
This option specifies that BrightStor VM:Backup should restore only
those files that do not already exist on the minidisk. This is the default.
Replace
This option specifies that BrightStor VM:Backup should restore all files
from the backed-up minidisk. If a file exists that has the same name as
a file to restore, the job should write the data to a work file, erase the
existing file from the minidisk, and rename the work file to the original
filename. If the restore job does not complete successfully, the existing
file is left intact and the work file is erased.
When you select Replace, make sure that there is sufficient free space
on the minidisk for BrightStor VM:Backup to create a copy of each file
before it erases the existing versions.
Erase
This option specifies that the job should restore all files from the
backed-up minidisk. If a file exists that has the same name as a file to
restore, the job should delete the existing file before restoring the
backed-up version. If you specify Erase, and the restore job does not
complete successfully, both the existing file and the file being restored
may be lost.
Managing Restore Job Template Files
7–11
Creating or Updating Restore Job Template Files
Specifying Source DASD Volumes or Source/Target DASD Volumes
BrightStor VM:Backup displays one of two Select Guidelines sections based on
the target you selected in the Restore Data to field:
Restore Data to:
BrightStor VM:Backup displays this section:
Original Minidisk
Source DASD Volumes
Reader
Source DASD Volumes
Alternate Volume
Source/Target DASD Volumes for Alternate-Volume
Restore
Source DASD Volumes
In Select Guidelines-Source DASD Volumes section, specify the data you want
the job to restore. By default, BrightStor VM:Backup restores all of the minidisks
on every DASD volume referenced in the CP directory. If you specify particular
volumes, BrightStor VM:Backup restores every minidisk on the specified DASD
volumes. You can enter up to 24 individual volsers or use pattern matching to
restore multiple volumes with similar volsers.
This screen must list at least one DASD volume. If you want to specify more than
24 DASD volumes, you must use the job template file INCLUDE record through
TPI instead of the system administrator screens. For information about this record
and about TPI, see the Template Programming Interface Guide.
WARNING! On a restore job, BrightStor VM:Backup cannot determine whether a
particular minidisk is part of the Shared File System. If you are doing a full volume restore,
and the specified DASD volume contains minidisks from a file pool, unexpected results
may occur to the file pool. To prevent this, create an exclusion file to exclude these minidisks
from the restore job.
7–12
Administrator Guide
Creating or Updating Restore Job Template Files
Source/Target DASD Volumes for Alternate-Volume Restore
In the Select Guidelines-Source/ Target DASD Volumes for Alternate-Volume
Restore section, fill in the following fields to specify the volumes you want the job
to restore and the alternate target volume on which you want the job to overlay
minidisks from the source volume. If you are restoring a CKD device, the target
volume must be the same device and class type as the source volume; for example,
you must restore a 3380 device to a 3380 device. If you are restoring an FBA device,
the target volume must be an FBA device. You cannot use pattern matching in
these fields.
Source Volser
Specify the volser of the source volume (the volume to restore).
Target Volser
Specify the target volume (the volume to which to restore the
source volume).
This volume must be online and must not be attached to a user ID,
BrightStor VM:Backup, or SYSTEM; BrightStor VM:Backup
attaches this target volume during the restore job. When the
restore is complete, BrightStor VM:Backup detaches the target
volume; you can attach it to the system.
Target Raddr
Specify the real address of the target alternate volume. Enter a
four-digit address.
Note: When restoring to an alternate volume, BrightStor VM:Backup cannot
restore to a minidisk that is defined with the END keyword in the CP directory
because BrightStor VM:Backup cannot determine the current size of the minidisk.
BrightStor VM:Backup skips the minidisk.
Restricted To
Whether you selected Original Minidisk, Reader, or Alternate Volume in the
Restore Data to field, BrightStor VM:Backup displays the Select
Guidelines-Restricted To section.
By default (as indicated by USERID * *), BrightStor VM:Backup restores all
minidisks belonging to all user IDs on the specified DASD volumes. You can
override this default to restrict the job to restoring only specific user IDs,
minidisks, account numbers, or ACI security groups.
Managing Restore Job Template Files
7–13
Creating or Updating Restore Job Template Files
If you change the default values, specify at least one of the following in the Record
Type and Value fields; these fields cannot be left blank.
Record Type
Value
USErid
userid vaddr
ACCount
number
ACIgroup
name
Use pattern matching to restore groups of minidisks with similar user IDs, account
numbers, or ACI security group names. If the same user is included in more than
one record type, BrightStor VM:Backup restores that user's data only once.
You can further limit the restore job by defining an exclusion file. For more
information about excluding data from a restore job, see Creating or Updating an
Exclusion File on page 8-13.
Example
You want to restore the following data:
■
All of userid MARY's minidisks
■
All minidisks belonging to accounts with 5-digit numbers ending in 123
Enter this information on the Select Guidelines-Restricted To section of the Work
with Restore Template template screen. The following screen shows a sample
screen with the example information entered.
WRSTABC4 (4 of 7) Work with Restore Template SMALLJOB VM:Backup
-------------------------------------------------------------------------------Select Guidelines - Restricted to:
Record
Type
userid
account_
________
________
________
________
________
________
________
________
________
Value
mary
* __
%%123________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
Record
Type
________
________
________
________
________
________
________
________
________
________
________
Value
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
_____________
-------------------------------------------------------------------------------5 ...
6 ...
PF: 1 Help
2 ...
3 End
4 Return
PF: 7 ...
8 ...
9 ...
10 ...
11 Print
12 Cursor
===>
7–14
Administrator Guide
Sample Restore Jobs
Sample Restore Jobs
This section presents sample CATSEARCH and VOLSEARCH restore jobs.
Sample CATSEARCH Restore Job
Full backups were taken on January 1 and an incremental backup was taken each
day from January 2 through 5 for a total of four incremental backups. You want to
restore a user's 191 minidisk to the state it was in on January 5, and catalogs are
available. To perform this task, follow these steps, starting at the System
Administrator Main Menu:
1.
Select Option 4, Manage job templates. BrightStor VM:Backup displays the
Manage Job Templates screen.
2.
Enter rcreate/sales96 on the command line to create a new restore template.
BrightStor VM:Backup displays the first Work with Restore Template screen
for that file.
3.
Tab to the Using Catalogs field and type x. Make sure that the Scanning
Tapes field is blank.
4.
Enter the appropriate restore criteria on the remaining screens for the job. In
this example, the default dates displayed include the dates of the full backup
and all of the incremental backups.
5.
Press PF9 (File) to enter the changes.
6.
Press PF4 (Return) until you exit BrightStor VM:Backup.
7.
Submit the CATSEARCH restore job by entering the following command from
CMS:
vmbackup submit sales96
BrightStor VM:Backup reads the catalog to determine which files exist on which
tapes. BrightStor VM:Backup asks for tapes that contain data for the user's 191
minidisk. BrightStor VM:Backup mounts the tapes containing the full backups,
followed by the tapes containing the incremental backups (oldest to most recent)
to restore the data.
Managing Restore Job Template Files
7–15
Sample Restore Jobs
Sample Restore Jobs
This section presents sample CATSEARCH and VOLSEARCH restore jobs.
Sample CATSEARCH Restore Job
Full backups were taken on January 1 and an incremental backup was taken each
day from January 2 through 5 for a total of four incremental backups. You want to
restore a user's 191 minidisk to the state it was in on January 5, and catalogs are
available. To perform this task, follow these steps, starting at the System
Administrator Main Menu:
1.
Select Option 4, Manage job templates. BrightStor VM:Backup displays the
Manage Job Templates screen.
2.
Enter rcreate/sales96 on the command line to create a new restore template.
BrightStor VM:Backup displays the first Work with Restore Template screen
for that file.
3.
Tab to the Using Catalogs field and type x. Make sure that the Scanning
Tapes field is blank.
4.
Enter the appropriate restore criteria on the remaining screens for the job. In
this example, the default dates displayed include the dates of the full backup
and all of the incremental backups.
5.
Press PF9 (File) to enter the changes.
6.
Press PF4 (Return) until you exit BrightStor VM:Backup.
7.
Submit the CATSEARCH restore job by entering the following command from
CMS:
vmbackup submit sales96
BrightStor VM:Backup reads the catalog to determine which files exist on which
tapes. BrightStor VM:Backup asks for tapes that contain data for the user's 191
minidisk. BrightStor VM:Backup mounts the tapes containing the full backups,
followed by the tapes containing the incremental backups (oldest to most recent)
to restore the data.
Note: If you had specified NEWFILE, BrightStor VM:Backup would mount the
tapes in the reverse order.
After BrightStor VM:Backup mounts the tapes from the last incremental backup
and restores the data, the job ends. The user's 191 minidisk is restored to the state
it was in on January 5.
When it has restored the user's 191 minidisk, BrightStor VM:Backup ends the job
and sends you the BrightStor VM:Backup restore job detail report and a message
saying that the job completed successfully.
7–16
Administrator Guide
Sample Restore Jobs
Sample VOLSEARCH Restore Job
Full backups were taken on January 1 and an incremental backup was taken each
day from January 2 through 5 for a total of four incremental backups. You want to
restore a user's 191 minidisk to the state it existed in on January 5, and catalogs are
not available. You know that the most recent backup was the incremental job run
on January 5, and that the first tape in the tape set is B00428. To perform this task,
follow these steps, starting at the System Administrator Main Menu:
1.
Select Option 4, Manage job templates. BrightStor VM:Backup displays the
Manage Job Templates screen.
2.
Enter rcreate/finan96 on the command line to create a new restore template.
BrightStor VM:Backup displays the first Work with Restore Template screen
for that file.
3.
Tab to the Scanning Tapes field and type x. Make sure that the Using Catalogs
field is blank.
4.
Tab to the If Scanning Tapes: Tape Volser field and type the volser of the
most recent incremental backup, which is B00428. Then type 1 in the DSSN
field.
5.
Enter the appropriate restore criteria on the remaining screens for the job. To
have BrightStor VM:Backup confirm that this tape was created on January 5,
set the date range to 01/05/2004 00:00 to 01/05/2004 23:59. Specify the
NEWFILE option so that BrightStor VM:Backup will not restore files that
already exist on the minidisk.
6.
Press PF9 (File) to enter the changes.
7.
Press PF4 (Return) until you exit BrightStor VM:Backup.
8.
Submit the VOLSEARCH restore job by entering the following command from
CMS:
vmbackup submit finan96
BrightStor VM:Backup mounts tape B00428 and continues to mount the first tape
of each preceding incremental backup until it reaches the first tape in the full
backup, which is B00425. Then, BrightStor VM:Backup processes the incremental
tapes from the newest to the oldest, and restores the data as it finds it.
Note: If you had specified the REPLACE or CLEAR option, BrightStor VM:Backup
would process the tapes from oldest to newest.
When it has restored the user's 191 minidisk, BrightStor VM:Backup ends the job
and sends you the BrightStor VM:Backup restore job detail report and a message
saying that the job completed successfully.
Managing Restore Job Template Files
7–17
Chapter
8
Managing Exception and
Exclusion Files
Exception files let you process selected user IDs, minidisks, account numbers, ACI
security groups, SFS file spaces, or BFS file spaces differently from other data
included in the job template file. For example, to back up a single minidisk
physically when all other minidisks are backed up in CMS format, specify the user
ID and virtual address of the minidisk to be processed physically in an exception
file. You can also use an exception file to specify exactly which files, tracks, or
blocks from some or all minidisks, account numbers, ACI security groups, or SFS
file spaces are to be included in or excluded from the job.
Exclusion files let you remove certain user IDs, minidisks, account numbers, ACI
security groups, SFS file spaces, or BFS file spaces from being processed in a job.
For example, to restore data for all but one user ID in an account, specify the
account number in the restore job template file and the user ID to be excluded in
an exclusion file.
This chapter explains how to create and maintain exception and exclusion files
through Option 5, Manage exception/exclusion files, on the System
Administrator Main Menu.
Exception and Exclusion File Information
When you select Option 5, Manage exception/exclusion files, BrightStor
VM:Backup displays the Manage Exception/Exclusion Files screen. This screen
provides the following information about existing exception and exclusion files:
■
Name of the exception or exclusion file
■
Exception or exclusion file type (XCEPT or XCLUDE, respectively)
■
Comments about the file
The exception files listed on this screen include those created by BrightStor
VM:Archiver and BrightStor VM:Migrate, which are identified by the descriptive
comment. These files are listed for information only; you cannot work with them.
Managing Exception and Exclusion Files
8–1
Exception and Exclusion File Commands
You can use PF7 (Backward) and PF8 (Forward) to move through the list of job
template files. Enter the TOP and BOTTOM commands on the command line to
view the beginning and end of the exception and exclusion file list.
Exception and Exclusion File Commands
The commands listed in the following table are available on the Manage
Exception/Exclusion Files screen. To work with an existing file, enter the
appropriate command in the Command column next to the file. To create a new
file, enter the appropriate command on the command line.
Commands to Manage Exception and Exclusion Files
Command
Where to
Enter
Use this command to ...
COPY/filename
Command
column
Create a new exception or exclusion file
by copying an existing definition;
filename is the name of the new file.
DISCARD
Command
column
Delete an existing exception or exclusion
file.
PRINT
Command
column
Send a report to your virtual printer that
describes the exceptions or exclusions
you have defined.
The PRINT command prints information
about the entire exception or exclusion
file; PF11 (Print) prints the exception or
exclusion file definition screens one
screen at a time.
RENAME/filename
8–2
Administrator Guide
Command
column
Rename an existing exception or
exclusion file; filename is the new name of
the file.
Creating or Updating an Exception File
Commands to Manage Exception and Exclusion Files
Command
Where to
Enter
Use this command to ...
UPDATE
Command
column
Modify an existing exception or
exclusion file.
WARNING! Update exception files only
before running a full backup; do not update
an exception file before running an
incremental backup. If the exception file for
an incremental backup job differs from the
exception file for the previous backup on
which the incremental job is based,
BrightStor VM:Backup will perform a full
backup of those minidisks or file spaces
affected instead of an incremental backup.
XCEPTION/filename
Command line Creates a new exception file; filename is
the name of the new file. This name,
which corresponds to a CMS filename,
must be a unique exception file name
containing one through eight characters.
XCLUSION/filename
Command line Create a new exclusion file; filename is the
name of the new file. This name, which
corresponds to a CMS filename, must be
a unique exclusion file name containing
one through eight characters.
Creating or Updating an Exception File
To create an exception file, enter the XCEPTION/filename command on the
Manage Exception/Exclusion Files screen. Enter xception/filename on the
command line, where filename is the name of the exception file you want to create.
To update an existing exception file, use the UPDATE command on the Manage
Exception/Exclusion Files screen. Enter update in the Command column next to
the exception file you want to update.
In response to either command, BrightStor VM:Backup displays the Work with
Exception File filename screen. Use this screen to identify data to be specially
processed by BrightStor VM:Backup.
Managing Exception and Exclusion Files
8–3
Creating or Updating an Exception File
Describing the Exception File
You can type up to 50 characters in the Descriptive Comment field in the
exception file. BrightStor VM:Backup displays the first 41 characters of this
comment on the Manage Exception/Exclusion File screen.
Record Type and Value
To indicate which user IDs, account numbers, ACI security groups, or file spaces
are to receive special processing, press PF5 (Insert). BrightStor VM:Backup
displays a blank data entry line.
Fill in the Record Type and Value fields with entries that are referenced in job
template files. The entry in the exception file must have an identical record type;
however, the value can be different as long as it is referenced in the job template
file. For example, if you specify USERID SAW * in the job template file, you can
specify USERID SAW 191 in the exception file. The following describes the format
for these fields:
Record Type
Value
USErid
userid vaddr
ACCount
number
ACIgroup
name
FSPace
filepoolid:userid (for SFS and BFS file spaces)
You can use pattern matching to specify file spaces with similar names or groups
of minidisks with similar user IDs, account numbers, or ACI security group names.
FSPACE records identify both BFS and SFS file spaces. For example, if you specify,
SYS01:*, the exceptions apply to file spaces (both BFS and SFS) in the SYS01 file
pool.
Ordering Records
The record order is critical to the outcome of the job. To determine what data is to
be included, excluded, or specially processed, BrightStor VM:Backup examines the
entries in the order that you list them in the exception file. If BrightStor VM:Backup
encounters the same user in multiple record types, it uses the first entry specified.
8–4
Administrator Guide
Creating or Updating an Exception File
Inserting and Deleting Records
To insert another record below the first entry, move the cursor down to the next
line and press PF5 (Insert). To insert a record above the first entry, leave the cursor
on the same line and press PF5 (Insert). To delete a record, place the cursor on the
same line and press PF6 (Delete).
Include/Exclude List
An Include/Exclude List allows you to specify the exact CMS or SFS files, CKD
tracks, or FBA blocks to include in or exclude from the job. By default, all data on
the specified minidisk (or SFS file space, for backup jobs) is included.
When you define an include list, BrightStor VM:Backup backs up or restores only
the specified CMS or SFS files, tracks, or blocks for the indicated minidisks or SFS
file spaces. A partial restore of a physically backed-up CKD or FBA minidisk
requires that the target minidisk for the restore be the same disk-type and size as
the original minidisk. For example, if a minidisk was backed up as a physical
minidisk existing from cylinders 0-49, and you need to restore cylinders 10 and 11,
you must allocate a minidisk of the same disk-type and size (50 cylinders) even
though you are restoring only two cylinders.
When you define an exclude list, BrightStor VM:Backup does not back up or
restore any of the specified CMS or SFS files, tracks, or blocks. BrightStor
VM:Backup processes all other files, tracks, or blocks on the indicated minidisks
and file spaces according to the specified job processing options.
When no include or exclude list exists, BrightStor VM:Backup displays No list is
defined in the Include/Exclude List column on the Work with Exception File
filename screen. If you define a list, BrightStor VM:Backup updates this column to
identify the type of list created.
Note: You cannot specify a list of BFS files to be included or excluded from a BFS
file space. If BrightStor VM:Backup encounters a BFS file space for which the
exception file contains a list of SFS files to include or exclude, BrightStor
VM:Backup ignores the list of files.
Managing Exception and Exclusion Files
8–5
Creating or Updating an Exception File
Screen Commands
To define an include or exclude list, enter one of the commands listed in the
following table, according to the type of data being processed. When you enter one
of these commands in the Command column next to a record type, BrightStor
VM:Backup displays an In/Exclude screen. On the In/Exclude screen, select either
Include or Exclude to identify whether you want to include or exclude data from
processing. Then, list the specific files, tracks, or blocks to include or exclude.
Creating In/Exclude Lists for Exception Files
Command
Valid for ...
To specify the In/Exclude list, enter ...
CKDLIST
CKD minidisk
The range of cylinders and tracks to be
(CMS or non-CMS) included or excluded when the minidisk is
processed
Specify the first (or only) cylinder and track
to be included or excluded in the From
field. In the CYL field, enter the starting
cylinder number; you must specify a
number within the bounds of the minidisk.
In the TRK field, enter the starting track
number; you must specify a supported
value for the disk type.
If more than one cylinder and track is being
included or excluded, specify in the To field
the ending cylinder and track numbers. The
ending cylinder or track numbers cannot
precede the starting cylinder and track
numbers.
CMSLIST
CMS minidisk
The filenames and filetypes of the specific
files to be included or excluded when the
minidisk is processed
You can use pattern matching.
8–6
Administrator Guide
Creating or Updating an Exception File
Creating In/Exclude Lists for Exception Files
Command
Valid for ...
To specify the In/Exclude list, enter ...
FBALIST
The range of blocks to be included or
FBA minidisk
(CMS or non-CMS) excluded when the minidisk is processed.
Specify the first (or only) block to be
included or excluded in the From Block
field; this number must be within the
boundaries of the minidisk.
If more than one block is being included or
excluded, use the To Block field to specify
the ending block number. The ending block
cannot precede the starting block number.
SFSLIST
SFS file space
The filenames and filetypes of the specific
files to be included or excluded when the
file space is processed
You can use pattern matching.
Specifying Special Processing Options
When you redefine options for an item on the Work with Exception File filename
screen, BrightStor VM:Backup displays Yes in the Options Modified column. If
you do not redefine options, BrightStor VM:Backup displays No in the Options
Modified column.
To have user IDs, account numbers, ACI security groups, or file spaces processed
differently from other data included in the job, enter options in the Command
column of the Work with Exception File filename screen next to the appropriate
record type. BrightStor VM:Backup displays the Specify Options for RecordType
Value screen.
This screen lists several processing options that you can set. To set all but the Pack,
Quiesce, or Number of Tries for Consistent View of File Space option, type x
next to that option. For example, if the job template file specifies backup type CMS
and you want to specify backup type physical for a certain user ID, type x next to
the Physical option in the Backup Type field. To set the Pack or Quiesce option,
type y or n (for yes or no) to set the option. For the Number of Tries for Consistent
View of File Space option, enter the number of times you want BrightStor
VM:Backup to check for a consistent view of the file space.
Managing Exception and Exclusion Files
8–7
Creating or Updating an Exception File
The following sections describe the Quiesce and Security Key options; you can
only specify these options in an exception file. For information about all other
backup job processing options, see Screen Commands to Manage Backup
Templates on page 6-2. For information about all other restore job processing
options, see Screen Commands to Manage Restore Templates on page 7-2.
Quiesce Option
If you are backing up very active minidisks (for example, other CA VM:Manager
components), file spaces containing files that must be at the same commit level, or
file spaces that contain update-in-place files such as BFS files, you should suspend
all activity on the minidisk or file space before BrightStor VM:Backup attempts the
backup. Quiescing a minidisk or file space ensures that it does not change while
BrightStor VM:Backup is writing its contents to tape.
If you do not want BrightStor VM:Backup to quiesce a minidisk or file space, type
n in the Quiesce field. BrightStor VM:Backup does not issue requests to have the
minidisks or file spaces quiesced before backing them up. This is the default.
If you want BrightStor VM:Backup to quiesce a minidisk or file space, type y in the
Quiesce field. BrightStor VM:Backup checks whether the quiesce user exit
(VMBEXIT2) exists. If a user exit has been created, BrightStor VM:Backup invokes
the user exit to allow the user exit the opportunity to send a quiesce request to the
user ID being backed up. If a user exit does not exist, BrightStor VM:Backup issues
a CP SMSG userid QUIESCE to ask the user ID to quiesce the minidisk or file space.
If the user ID is not receiving SMSG, BrightStor VM:Backup waits until the time
specified for the user wait period elapses, and then assumes that the minidisk or
file space is quiesced and continues the job. If the user ID receives the CP SMSG
userid QUIESCE command and does not respond within the allowed user wait
time. BrightStor VM:Backup assumes that the quiesce request is rejected and skips
the minidisk or file space. The user wait time is defined by the USERWAIT record
in the VMBACKUP CONFIG file.
For more information about quiescing minidisks and file spaces, see the Systems
Programmer Reference.
Security Key
If you want BrightStor VM:Backup to encrypt the specified data as it is backed up
to tape, or if you are restoring from an encrypted backup, type the security key in
the Security Key field. If you leave this field blank, BrightStor VM:Backup does
not encrypt data during a backup job or cannot decrypt data during a restore job.
8–8
Administrator Guide
Creating or Updating an Exception File
The security key uses the National Institute of Standards and Technology's
(formerly the National Bureau of Standards) Data Encryption Standard (DES).
Because of federal regulations, some international customers will receive another
encryption/decryption algorithm, RC2. The algorithms are functionally
equivalent, but you must use the same algorithm to decrypt data that you use to
encrypt it.
Type the two 8-digit hexadecimal values in the fields provided. The DES
encryption algorithm requires that each byte of the security key be of odd parity.
For exact security key formatting requirements for DES, see the National Institute
of Standards and Technology's Federal Information Processing Standards
Publications (FIPS PUB) 46, 15 January 1977.
The exception file used to restore the data must specify the same security key used
to encrypt the backup, and the exception file is the only place where the security
key is recorded. Therefore, if you change the security key after the job has run, you
are responsible for recording the key to be able to decrypt the data when restoring.
Example
To create an exception file named EXCEPT2, that tells BrightStor VM:Backup to
back up:
■
Only files with the filetype EXEC from the minidisk MARY 0192
■
All minidisks belonging to account number 67890 in physical format
■
All other minidisks included in the job according to the job processing options
specified in the job template file
Perform the following steps:
1.
On the Manage Exception/Exclusion Files screen, enter xception/except2 on
the command line. BrightStor VM:Backup displays the Work with Exception
File EXCEPT2 screen.
2.
Type a descriptive comment, then press PF5 (Insert) to add a blank data entry
field.
Managing Exception and Exclusion Files
8–9
Creating or Updating an Exception File
3.
Type userid in the Record Type field and mary 192 in the Value field. Type
cmslist in the Command column to create an Include List. The following is a
Work with Exception File EXCEPT2 screen with these entries filled in.
Sample Work with Exception File Screen
4.
8–10
Administrator Guide
Press ENTER. BrightStor VM:Backup displays the Include/Exclude CMS Files
for USERID MARY 0192 screen.
Creating or Updating an Exception File
5.
To create the Include List, accept the default by leaving the X in the Include
field. Type * in the Filename field and exec in the Filetype field to specify that
BrightStor VM:Backup should process only the EXEC files on the minidisk
MARY 0192. Note the filled-in Include/Exclude CMS Files for USERID MARY
0192 on the following screen.
Sample Include/Exclude CMS Files Screen
6.
Press PF9 (File) to save the Include List. BrightStor VM:Backup displays the
Work with Exception File EXCEPT2 screen again.
7.
Move the cursor below the entry for MARY 0192 and press PF5 (Insert). A
blank data entry line appears.
Managing Exception and Exclusion Files
8–11
Creating or Updating an Exception File
8.
Type account in the Record Type field and 67890 in the Value field. Type
options in the Command column to define job processing options for this
account. The following Work with Exception File EXCEPT2 screen shows
these values filled in.
Sample Work with Exception File Screen
If userid MARY is part of account group 67890, MARY's EXEC files will still be
the only files backed up because the USERID record type precedes ACCOUNT
in the list. If MARY were listed under ACCOUNT 67890, the account
processing options would take precedence, and MARY's 192 minidisk would
be backed up physically with all others in the account.
9.
8–12
Administrator Guide
Press ENTER. BrightStor VM:Backup displays the Specify Options for
ACCOUNT 67890 screen.
Creating or Updating an Exclusion File
10. Type x next to Physical in the Backup Type field to indicate that BrightStor
VM:Backup should back up all minidisks ownedphysically by account group
67890 . The filled-in Specify Options for ACCOUNT 67890 screen follows.
Sample Specify Options Screen
11. Press PF9 (File) to save the processing options. BrightStor VM:Backup
returns you to the Work with Exception File EXCEPT2 screen. Press PF9 (File)
to save the EXCEPT2 exception file.
Creating or Updating an Exclusion File
To create an exclusion file, use the XCLUSION/filename command on the Manage
Exception/Exclusion Files screen. Enter xclusion/filename on the command line,
where filename is the name of the exclusion file you want to create.
To update an existing exclusion file, use the UPDATE command on the Manage
Exception/Exclusion Files screen. Enter update in the Command column next to
the exclusion file you want to update.
In response to either command, BrightStor VM:Backup displays the Work with
Exclusion File filename screen. Use this screen to identify the data BrightStor
VM:Backup is to exclude from processing.
Managing Exception and Exclusion Files
8–13
Creating or Updating an Exclusion File
Describing the Exclusion File
You can type up to 50 characters in the Comments field in the exclusion file.
BrightStor VM:Backup displays the first 41 characters of this comment on the
Manage Exception/Exclusion File screen.
Exclude DASD
Type the volsers of the DASD volumes that BrightStor VM:Backup is to exclude
from processing. You can specify up to 12 individual volumes; you can also use
pattern matching to exclude multiple volumes with similar volsers. BrightStor
VM:Backup will not back up or restore any of the minidisks on the specified
volumes.
If you want to specify more than 12 DASD volumes, you must use the exclusion
file EXCLUDE record through TPI instead of the system administrator screens. For
information about this record and about TPI, see the Template Programming
Interface Guide.
WARNING! On a restore job, BrightStor VM:Backup cannot determine whether a
particular minidisk is part of the Shared File System. If you are doing a full volume restore
and the specified DASD volume contains minidisks from a file pool, unexpected results
may occur to the file pool. To prevent this, create an exclusion file to exclude these minidisks
from the restore job.
Exclude File Pools
Enter the names of the SFS file pools BrightStor VM:Backup is to exclude from
processing. You can specify up to 12 individual file pools or use pattern matching
to exclude multiple file pools that have similar names. BrightStor VM:Backup will
not back up any of the file spaces in the specified file pools. You cannot create an
exclusion file that excludes file spaces for a restore job by using this screen; if you
want to exclude file spaces, you must use TPI.
If you want to specify more than 12 file pools, you must use the exclusion file
EXCLUDE record through TPI instead of the system administrator screens. For
information about this record and about TPI, see the Template Programming
Interface Guide.
8–14
Administrator Guide
Creating or Updating an Exclusion File
Exclude Records
If you want to exclude certain user IDs, minidisks, account numbers, ACI security
groups, or file spaces from processing, specify them in the Record Type and Value
fields.
Fill in the Record Type and Value fields with entries that are identical to those
specified in job template files. The following describes the format for the format for
these fields:
Record Type
Value
USErid
userid vaddr
ACCount
number
ACIgroup
name
FSPace
filepoolid:userid (for SFS and BFS file spaces)
Use pattern matching to specify file spaces with similar names (for a backup job),
or groups of minidisks with similar user IDs, account numbers, and ACI security
group names (for backup and restore jobs).
FSPACE records identify both BFS and SFS file spaces. For example, if you specify,
SYS01:*, BrightStor VM:Backup excludes all file spaces (both BFS and SFS) in the
SYS01 file pool.
Managing Exception and Exclusion Files
8–15
Chapter
9
Managing Existing Catalogs
This chapter explains how to review or manage BrightStor VM:Backup catalog
files through Option 6, Manage existing catalogs, on the System Administrator
Main Menu.
WARNING! BrightStor VM:Backup catalog files and the pointers between them are
created and maintained by BrightStor VM:Backup. Never modify a catalog file manually.
Catalog File Information
When you select Option 6, Manage existing catalogs, BrightStor VM:Backup
displays the Manage Existing Catalogs screen. This screen provides the following
information about existing catalog files:
■
Date and time of the backup that created the catalog
■
Name of the job template file from which the catalog was created
■
Whether a catalog has been condensed
■
■
Dumpjob file number assigned by BrightStor VM:Backup when the catalog
was created
Dumpjob file number of the base catalog on which an incremental backup is
based
■
Date the catalog is scheduled to be automatically condensed
■
Date the catalog is scheduled to be automatically discarded
You can use PF7 (Backward) and PF8 (Forward) to move through the list of catalog
files. Enter the TOP and BOTTOM commands on the command line to view the
beginning and end of the catalog file list.
Managing Existing Catalogs
9–1
Screen Commands
Screen Commands
The commands listed in the following table are available on the Manage Existing
Catalogs screen. To work with a catalog, enter the appropriate command in the
Command column next to the catalog.
Screen Commands to Manage Catalog Files
Command
Use this command to ...
CHECK
Examine the structure of the catalog to identify any problems and
display the number of errors found
CONDENSE Convert a file-level detail catalog to a domain-level detail catalog
DISCARD
Delete a catalog
PRINT
Check the structure of the catalog and send a report to your virtual
printer that shows which minidisks and file spaces were backed
up, which tapes are included in the catalog, and the number of
errors found
This command is the same as the line-mode CHECK command
with the PRINT and DOMAINS options specified. For more
information about the CHECK command, see the Systems
Programmer Reference.
The PRINT command prints information about the entire catalog;
PF11 (Print) prints the catalog screens one screen at a time.
UPDATE
Modify the date a catalog was scheduled to be automatically
condensed or discarded
When you extend the retention period for a catalog, you must also
extend the retention period specified for the tapes used during the
backup to prevent the tapes from expiring before the catalogs.
When the tapes expire, BrightStor VM:Backup will reuse them
whether the catalog has not expired or not.
9–2
Administrator Guide
Checking Catalog Structures
Checking Catalog Structures
Use the CHECK command to examine the file structure of the specified BrightStor
VM:Backup catalog, identify any problems, and display the number of errors
found. When you use the CHECK command on a catalog, no BrightStor
VM:Backup jobs can be running.
To check the structure of a catalog, enter check in the Command column of the
Manage Existing Catalogs screen next to the catalog you want to examine.
BrightStor VM:Backup issues a message indicating the total number of errors
found. For example, if no errors were found, BrightStor VM:Backup responds with
this message:
THERE ARE 0 ERRORS IN THIS CATALOG.
This screen command is similar to the line-mode CHECK command with the
ERRORS option specified.
Condensing Catalogs
When you condense a catalog, BrightStor VM:Backup removes all file, track, and
block information for every minidisk and file space and retains only the general
entries for the minidisks and file spaces. You can condense a catalog only once. No
jobs can be running when BrightStor VM:Backup is condensing catalogs.
BrightStor VM:Backup marks condensed catalogs on the Manage Existing
Catalogs screen by preceding the dumpjob number with an asterisk, for example,
*00002009.
To condense a catalog, enter condense in the Command column of the Manage
Existing Catalogs screen next to the catalog you want to condense. BrightStor
VM:Backup displays the Condense Catalogs screen. This screen lists the catalog
you selected and all other catalogs based on this catalog.
Condense All Associated Catalogs
When you condense a catalog created during a full or incremental backup,
BrightStor VM:Backup will also condense any catalog from an incremental backup
based on that catalog, regardless of the individual auto-condense dates defined for
those catalogs. When you condense a catalog created during a backup that has no
other backup based on it, only that catalog is condensed.
To condense all the catalogs listed on the Condense Catalogs screen, enter yes on
the command line.
Managing Existing Catalogs
9–3
Discarding Catalogs
Backup Schedule Considerations
If you run incremental backups on a daily basis and full backups once a week, you
may want to run all backups using file/track/block-level detail and convert
catalogs older than a certain age to domain-level detail.
Restore Considerations
Depending on your data center's restore needs and how long you need the catalogs
to be available, it may be more useful to retain condensed catalogs instead of
discarding them. A domain-level catalog allows BrightStor VM:Backup to process
only those tapes containing data for the minidisk or file space being restored,
whereas the lack of a catalog requires BrightStor VM:Backup to scan all the tapes
from a particular backup while searching for the requested data.
Processing Guidelines
When you specify auto-condensing for a catalog, consider the following:
■
■
■
Specifying an auto-condense period does not protect that catalog from being
condensed manually (through the CONDENSE command) or from being
condensed because its base catalog was condensed.
If you try to condense the catalog for a domain-level backup, the resulting
catalog is the same as it was before you entered the CONDENSE command.
If an error occurs while a catalog is being condensed, BrightStor VM:Backup
does not condense that catalog.
Discarding Catalogs
To discard a catalog, enter discard in the Command column of the Manage
Existing Catalogs screen next to the catalog you want to delete. BrightStor
VM:Backup displays the Discard Catalogs screen. This screen lists the catalog you
selected as well as all other catalogs based on that catalog. No jobs can be running
when BrightStor VM:Backup is discarding a catalog.
9–4
Administrator Guide
Printing the Catalog Report
Discard All Associated Catalogs
When you discard a catalog created during a full or incremental backup,
BrightStor VM:Backup will also discard any catalog from an incremental backup
based on that catalog, regardless of the auto-discard period defined for those
catalogs. When you discard a catalog created during a backup that has no other
backup based on it, BrightStor VM:Backup discards only that catalog.
To discard all of the catalogs listed on the Discard Catalogs screen, enter yes on the
command line.
Processing Guidelines
When you specify auto-discarding for a catalog, consider the following:
■
■
Specifying an auto-discard period does not protect that catalog from being
discarded manually (through the DISCARD command) or from being
discarded because its base catalog was discarded.
If an error occurs while a catalog is being discarded, BrightStor VM:Backup
does not discard that catalog.
Printing the Catalog Report
Use the PRINT command to examine the structure of the specified BrightStor
VM:Backup catalog and send a report on the catalog files to your virtual printer.
The report lists:
■
Minidisks and file spaces backed up
■
Volsers of the tapes to which data was backed up
■
Total number of errors found
No BrightStor VM:Backup jobs can run while the catalog is being examined.
This command is the similar to the line-mode CHECK command with the PRINT
and DOMAINS options specified. For more information about the CHECK
command, see the Systems Programmer Reference.
To produce a detailed report on the catalog file structure, enter print in the
Command column of the Manage Existing Catalogs screen next to the catalog you
want to examine.
Managing Existing Catalogs
9–5
Updating Catalogs
Updating Catalogs
When the auto-condense and auto-discard process runs or whenever you enter the
AUTOCAT command, BrightStor VM:Backup checks the auto-condense and
auto-discard dates for each catalog to determine whether it should condense or
discard the catalog. Use the UPDATE command to modify the dates on which a
catalog is scheduled to be automatically condensed or discarded.
Overriding the Auto-Condense or Auto-Discard Date
To specify a new auto-condense or auto-discard date, follow these steps:
1.
Type update in the Command column of the Manage Existing Catalogs screen
next to the catalog you want to update.
2.
If you want to update the auto-condense date, move the cursor to the
Auto-Condense column, and type a new date over the displayed date. If you
want to update the auto-discard date, move the cursor to the Auto-Discard
column, and type a new date over the displayed date.
Type the dates in the format mm/dd/yy. You can enter one or two digits when
specifying mm, dd, or yy. Use the following conventions when specifying yy:
–
Type 42 through 99 for the years 1942 through 1999
–
Type 00 through 41 for the years 2000 through 2041.
For example, to specify November 15, 1997, type 11/15/97; to specify March 17,
2005, type 3/17/05.
If you enter a date that is earlier than or the same as the current date, BrightStor
VM:Backup displays a warning message.
3.
9–6
Administrator Guide
Press ENTER.
Chapter
10
Starting Special SFS and BFS
Restores
This chapter describes how to define and submit jobs to restore SFS and BFS data
by using:
■
■
Option 7, Submit special SFS/BFS restores, on the System Administrator
Main Menu to restore:
–
SFS and BFS file spaces
–
User storage groups
–
File pools
Option 9, Perform user functions, on the System Administrator Main Menu to
restore BFS directories for yourself or another user.
When you restore data using these screens, make sure a catalog is available. If no
catalog is available, you can use TPI to restore SFS and BFS data.
Note: When you specify the name of a file pool on any of the SFS/BFS restore
screens, make sure that the specified file pool is available. The BrightStor
VM:Backup service virtual machine must be enrolled as an administrator for any
file pool to which you are restoring. You can identify file pool names to BrightStor
VM:Backup on the Identify SFS File Pools screen or on a FILEPOOL configuration
file record in the VMBACKUP CONFIG file. For more information, see Identifying
SFS File Pools on page 3-11 or the FILEPOOL record in the Systems Programmer
Reference.
Restoring a File Space
To restore an entire SFS or BFS file space, either to the original file pool or to
another, select Option 1, Restore a file space, from the Submit Special SFS/BFS
Restores menu. BrightStor VM:Backup displays the Restore a File Space screen. Fill
in the fields as described below; then press ENTER to submit the restore request.
Starting Special SFS and BFS Restores
10–1
Restoring a User Storage Group
Source File Space
In the File space to be restored field, type the complete name of the source file
space that you want to restore. You cannot use pattern matching.
Target File Space
To restore the file space to a file space with a different name, or to a file space in a
different file pool, type the target file space name in the Target file space field. If
you leave this field blank, BrightStor VM:Backup uses the source file space name
as the target file space. The target file space must exist in the target file pool.
You can restore an SFS file space only to a target SFS file space. You can restore a
BFS file space only to a target BFS file space.
Backup Version
By default, BrightStor VM:Backup restores the most recently backed-up version of
the source file space within the specified time period (or search range). To restore
a version other than the most recent, change the To date to an earlier date. For
example, if today is 1/7/05 and you want to restore a version of the file space from
before 1/2/05, change the To date to 1/1/05 and the time to 23:59. To control how
far back BrightStor VM:Backup searches when looking for data to restore, you can
change the From date. BrightStor VM:Backup will restore a file space only if it was
backed up at least once during the date range. BrightStor VM:Backup will go back
to the full backup even if it was performed before the start date.
Restoring a User Storage Group
To restore a single user storage group, select Option 2, Restore a user storage
group, from the Submit Special SFS/BFS Restores menu. BrightStor VM:Backup
displays the Restore a User Storage Group screen. You can restore the user storage
group to itself, to a different user storage group in the same file pool, or to a
different file pool. Fill in the fields as described below; then press ENTER to submit
the restore request.
Source User Storage Group
In the User storage group to be restored section of the screen, identify the source
user storage group. Type the name of the file pool to which the storage group
belongs in the File Pool field and the storage group number (2 through 32767) of
the specific storage group you want to restore in the User Storage Group Number
field.
10–2
Administrator Guide
Restoring a User Storage Group
Target User Storage Group
To restore the file spaces in the source user storage group to a different file pool or
to a different user storage group in the same pool, identify the target user storage
group in the Target user storage group section of the screen. Type the name of the
file pool in the File Pool field and the storage group number of a target storage
group in the User Storage Group Number field. If you leave these fields blank,
BrightStor VM:Backup uses the source user storage group as the target.
Make sure the minidisks that make up the target user storage groups are formatted
using FILESERV GENERATE. The minidisks can differ in number, size, and device
type from those that originally contained the data. You must also make sure that
the user storage group is defined in the target file pool. The source file spaces do
not need to exist in the target user storage group.
Restoring File Spaces
To indicate which BFS and SFS file spaces BrightStor VM:Backup is to restore,
select All or Skip in response to the following question on the Restore a User
Storage Group screen:
Restore all file spaces or skip those for existing userids?
All
This option tells BrightStor VM:Backup to restore all file spaces whether
or not they already exist in the target user storage group. BrightStor
VM:Backup enrolls, deletes, or replaces file spaces during the restore. This
is the default.
■
■
■
Skip
If a file space exists in the backed-up file pool but not in the target file
pool, BrightStor VM:Backup enrolls the file space in the target file
pool using the backup enrollment information.
If a file space exists in the target file pool but not in the backed-up file
pool, BrightStor VM:Backup leaves the file space untouched in the
target file pool.
If a file space exists in both the target and backed-up file pools,
BrightStor VM:Backup replaces the file space in the target file pool
with the file space from the backed-up file pool but does not modify
the enrollment information.
This option tells BrightStor VM:Backup to restore only file spaces that
exist in the backup version and not in the target user storage group.
BrightStor VM:Backup creates file spaces for those that were backed up
and no longer exist, but it does not replace or erase existing file spaces
during the restore. All file spaces that already exist remain untouched.
Starting Special SFS and BFS Restores
10–3
Restoring a User Storage Group
■
■
■
If a file space exists in the backed-up file pool but not in the target file
pool, BrightStor VM:Backup enrolls the file space in the target file
pool using the backed-up enrollment information.
If a file space exists in the target file pool but not in the backed-up file
pool, BrightStor VM:Backup leaves the file space in the target file pool
untouched.
If a file space exists in both the target and backed-up file pool,
BrightStor VM:Backup leaves the file space in the target file pool
untouched.
Note: If you want to remove file spaces that exist in the target but not in
the back up, that is, you want the restored user storage group to look just
like the backed-up version, you must manually clear the user storage
group before running the restore
Backup Version
By default, BrightStor VM:Backup restores the most recently backed-up version of
the file spaces in the source user storage group within the specified time period (or
search range). By cchanging the To date, you can restore a version other than the
most recent. For example, if today is 1/7/05 and you want to restore a version of
the file space from before 1/2/05, change the To date to 1/1/05 and the time to
23:59.
Because of the way BrightStor VM:Backup stores file pool information in the
catalogs, you should specify a From date when restoring a user storage group. The
From date will prevent BrightStor VM:Backup from restoring more data than you
intended. For example, suppose you want to restore a user storage group from
which you deleted many file spaces on 12/01/04. You do not want BrightStor
VM:Backup to restore the deleted file spaces. To make sure BrightStor VM:Backup
does not restore the deleted file spaces, specify a From date that is later than
12/01/04, but early enough to contain the data you want to restore. If you do not
specify a From date, BrightStor VM:Backup uses the default From date
(01/01/1942) and continues searching for and restoring file spaces back to that
date.
10–4
Administrator Guide
Restoring a File Pool
Restoring a File Pool
To restore either an entire file pool or one or more user storage groups in a file pool,
select Option 3, Restore a file pool or user storage groups in a file pool, from the
Submit Special SFS/BFS Restores menu. BrightStor VM:Backup displays the
Restore a File Pool screen. Fill in the fields as described below; then press ENTER
to submit the restore request.
Source File Pool
In the File pool to be restored field, type the name of the file pool that contains the
user storage groups you want to restore. You cannot use pattern matching.
Target File Pool
To restore to a different file pool, type the name of that file pool in the Target file
pool field. If you leave this field blank, BrightStor VM:Backup uses the source file
pool as the target.
Make sure the minidisks that make up the target user storage groups being
restored are formatted using FILESERV GENERATE. The minidisks can differ in
number, size, and device type from those that originally contained the data. You
must also make sure that the user storage groups are defined in the target file pool.
The source file spaces do not need to exist in the target user storage group.
Restoring User Storage Groups
The following statement appears on the Restore a File Pool screen:
If restoring only certain user storage groups in the file pool, identify those user
storage groups by number.
If you do not specify any storage group numbers, BrightStor VM:Backup restores
all user storage groups in the source file pool to the target file pool. To restore
specific user storage groups, type their storage group numbers (the numbers can
range from 2 through 32767). Separate each storage group number by at least one
blank space.
Starting Special SFS and BFS Restores
10–5
Restoring a File Pool
Restoring File Spaces
To indicate which BFS and SFS file spaces BrightStor VM:Backup is to restore,
select All or Skip in response to the following question on the Restore a File Pool
screen:
Restore all file spaces or skip those for existing userids?
This option tells BrightStor VM:Backup to restore all file spaces whether
or not they already exist in the target user storage group. BrightStor
VM:Backup enrolls, deletes, or replaces file spaces during the restore.
This is the default.
All
■
■
■
Skip
If a file space exists in the backed-up file pool but not in the target file
pool, BrightStor VM:Backup enrolls the file space in the target file
pool using the backup enrollment information.
If a file space exists in the target file pool but not in the backed-up file
pool, BrightStor VM:Backup leaves the file space untouched in the
target file pool.
If a file space exists in both the target and backed-up file pools,
BrightStor VM:Backup replaces the file space in the target file pool
with the file space from the backed-up file pool but does not modify
the enrollment information.
This option tells BrightStor VM:Backup to restore only file spaces that
exist in the backup version and not in the target user storage group.
BrightStor VM:Backup creates file spaces for those that were backed up
and no longer exist, but it does not replace or erase existing file spaces
during the restore. All file spaces that already exist remain untouched.
■
■
■
If a file space exists in the backed-up file pool but not in the target file
pool, BrightStor VM:Backup enrolls the file space in the target file
pool using the backed-up enrollment information.
If a file space exists in the target file pool but not in the backed-up file
pool, BrightStor VM:Backup leaves the file space in the target file pool
untouched.
If a file space exists in both the target and backed-up file pool,
BrightStor VM:Backup leaves the file space in the target file pool
untouched.
Note: If you want to remove file spaces that exist in the target but not in the
back up, that is, you want the restored file pool or user storage groups to look
just like the backed-up versions, you must specify manually clear the user
storage group before running the restore.
10–6
Administrator Guide
Restoring a File Pool
Backup Version
By default, BrightStor VM:Backup restores the most recently backed-up version of
the file spaces in the specified file pool or user storage groups within the specified
time period (or search range). By changing the To date, you can restore a version
other than the most recent. For example, if today is 1/7/05 and you want to restore
a version of the file space from before 1/2/05, change the To date to 1/1/05 and
the time to 23:59.
Because of the way BrightStor VM:Backup stores file pool information in the
catalogs, you should specify a From date when restoring a file pool or user storage
groups. The From date will prevent BrightStor VM:Backup from restoring more
data than you intended. For example, suppose you want to restore a file pool from
which you deleted many file spaces on 12/01/04. You do not want BrightStor
VM:Backup to restore the deleted file spaces. To make sure BrightStor VM:Backup
does not restore the deleted file spaces, specify a From date that is later than
12/01/04, but early enough to contain the data you want to restore. If you do not
specify a From date, BrightStor VM:Backup uses the default From date
(01/01/1942) and continues searching for and restoring file spaces back to that
date.
Enroll Public
The following question appears on the Restore a File Pool screen:
Enroll Public in target file pool (Yes/No)?
Yes This response tells BrightStor VM:Backup to issue the CMS command
ENROLL PUBLIC for the file pool.
No
This response tells BrightStor VM:Backup not to issue the ENROLL
PUBLIC command for the file pool. This is the default.
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 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. For detailed information
on the ENROLL PUBLIC command, see the IBM SFS and CRR Planning,
Administration, and Operation publication.
Starting Special SFS and BFS Restores
10–7
Restoring BFS Directories
Restoring BFS Directories
You must have system administrator authorization to restore an entire BFS
directory. You can restore a BFS directory that you own or that another user owns.
You must restore a BFS directory to an existing BFS directory.
This section describes the following:
■
Naming conventions for BFS objects
■
Instructions for restoring BFS directories
■
Permissions required to restore to target BFS directories
Ownership and permissions assigned to BFS directories that BrightStor
VM:Backup creates
■
BFS Naming Conventions
When restoring BFS objects using BrightStor VM:Backup full screens, you need to
specify names for the different parts of a BFS object. BrightStor VM:Backup
identifies a BFS file by its file space, directories, and file name. The following
shows the naming conventions used in this section for BFS files, directories, and
file spaces.
Directory
/../VMBFS:BFSSERV:SALES/sales_goals/1st_quarter/numbers.txt
File space
Full directory pathname
File name component
The following describes a BFS object based on a CMS user's experience with the
SFS file system and a BFS object based on a user's understanding of POSIX.
10–8
Administrator Guide
Restoring BFS Directories
CMS Users
POSIX Users
BFS
Tells VM this is a
BFS file space
/../VMBFS
Identifies the file space
name
BFSSERV:SALES
Equivalent to the
root directory or a
mount point in a file
system
sales_goals
Directories
Directories
1st_quarter
Files
bonuses.txt
incentives.txt
Files
numbers.txt
Instructions for Restoring a BFS Directory
To restore a directory, perform the following steps:
1.
From the System Administrator Main Menu, select Option 9, Perform user
functions, on the System Administrator Main Menu.
BrightStor VM:Backup displays the Perform User Functions menu.
2.
Specify the file space from which you want to restore in the Restore BFS files
from file space field. BrightStor VM:Backup displays data backed up from
only the file space you specify.
3.
Type an asterisk (*) for the user ID in the Restore BFS files from file space for
userid field. When you restore a directory, specify an asterisk, which indicates
you want to restore files owned by any user ID.
4.
Select Option 3, Select directories from which to restore.
BrightStor VM:Backup displays the Select Directories from Which to Restore
screen.
Starting Special SFS and BFS Restores
10–9
Restoring BFS Directories
The Directory Name column contains directory names. If the data was backed
up from the root directory, a slash appears in column one. If the data was
backed up from a subdirectory, the name is indented according to the position
the subdirectory occupies in the directory tree (three characters for each
subdirectory level). If a directory name is not visible on the screen due to
indentation, BrightStor VM:Backup displays the string, ==>, on the right side
of the line to indicate that output exists on that line.
If a directory name is too long to display on the screen, use PF6 (Right) and
PF5 (Left) to scroll right and left to view the complete directory name. Each
time you press PF6 (Right) or PF5 (Left), BrightStor VM:Backup shifts the
display three characters in the appropriate direction to the next directory level.
As you scroll left and right, the Indent level field is updated to indicate what
level you are viewing. If the beginning portion of a directory name is not
visible, BrightStor VM:Backup precedes the name with an ellipsis. If the
ending portion of a directory name is not visible, BrightStor VM:Backup
appends the name with an ellipsis.
To view the full directory pathname for a directory, move the cursor to the Req
column next to the appropriate directory name and press PF10 (Seename).
BrightStor VM:Backup displays the full directory pathname at the top of the
screen. If the full directory pathname is too long to display on one line, press
PF6 (Right) and PF5 (Left) to scroll right and left to view the complete full
directory pathname. If the beginning portion of the full directory pathname is
not visible, BrightStor VM:Backup precedes the pathname with an ellipsis. If
the ending portion of the full directory pathname is not visible, BrightStor
VM:Backup appends the pathname with an ellipsis. While a full directory
pathname is displayed, PF6 (Right) and PF5 (Left) affect only the line
displaying the full directory pathname. Press ENTER or any PF key besides
PF6 (Right) and PF5 (Left) to remove the full directory pathname.
5.
Accept the default (YES) or enter no in response to the question:
Restore the latest version?
Respond yes if you want to restore the latest backed-up version of the
directory. Respond no if you want BrightStor VM:Backup to display
information about several backed-up versions of the directory you want to
restore.
6.
Type r in the Req column next to the directory you want to restore and press
PF9 (Submit) to submit your request. You can select only one directory.
BrightStor VM:Backup displays a screen based on your response to the
question Restore or view only the latest version?:
10–10
Administrator Guide
Response BrightStor VM:Backup displays:
Continue with:
NO
Select Version of Directory to Restore screen
Step 7.
YES
Specify Restore Directory Options screen
Step 8.
Restoring BFS Directories
7.
Type r in the Req column next to the version of the directory you want to
restore and press PF9 (Submit) to submit your request.
BrightStor VM:Backup displays the Specify Restore Directory Options screen.
By default, BrightStor VM:Backup displays the full directory pathname of the
source directory in the Directory field and the name of the source file space in
the Target BFS file space field.
8.
Type the full directory pathname of the directory to which you want to restore
in the Directory field and the name of the file space in which the target
directory exists in the Target BFS file space field. You must specify an
absolute pathname, that is, the full directory pathname must begin with a
slash (/). You can restore to only one directory in a single request.
WARNING! BrightStor VM:Backup does not require any specific permissions in the
target directory or its parent directories.
9.
Accept the default (NO) or enter yes in response to the following question to
specify whether you want the directory cleared before BrightStor VM:Backup
restores it:
Clear the directory before restoring?
If you respond no, the directory is not cleared before your files are restored. If
you respond yes, BrightStor VM:Backup erases all files in the target directory.
10. If you responded no to the Clear the directory before restoring? question, you
must accept the default (YES) or enter no in response to the following
question:
Restore files with the same names as existing files?
If you respond yes, BrightStor VM:Backup restores all the files backed up from
the source directory. If a file in the source directory has the same name as a file
in the target directory, BrightStor VM:Backup replaces the version in the target
directory with the version backed up from the source directory. If you respond
no, BrightStor VM:Backup restores only those files backed up from the source
directory whose names do not match any currently existing files.
11. If you responded yes to the Clear the directory before restoring? question,
you must accept the default (YES) or enter no in response to the following
question:
Restore directory ownerships and permissions?
If you respond yes, the restored data will have the ownerships and
permissions that exist in the backup.
If you respond no, the restored data will have the ownerships and permissions
that existed in the target directory before the restore.
12. Press PF9 (Submit) to submit the restore to BrightStor VM:Backup.
Starting Special SFS and BFS Restores
10–11
Chapter
11
Performing Operator and User
Functions
As the system administrator for BrightStor VM:Backup, your user ID is
automatically authorized to perform operator functions and end user restore
functions.
This chapter describes the operator and end user functions you can perform
through system administrator screens. For more information about operator
functions, see the Operator Guide. For more information about end user functions,
see the User Guide.
Performing Operator and User Functions
11–1
Performing Operator Functions
Performing Operator Functions
When you select Option 8, Perform operator functions, on the System
Administrator Main Menu, BrightStor VM:Backup displays the Perform Operator
Functions menu.
The following table lists the operator functions you can perform from this screen.
Operator Functions
Option
Use this option to ...
1 Manage system activity
■
■
■
Monitor the status of pending and active jobs
List the tapes required to fulfill a restore, MPC,
or REINIT request
■
Cancel jobs
■
Hold jobs
■
Display the contents of jobs
■
Release jobs, including end-user restore
requests, that are on hold
2 Respond to VM:Backup
requests
View or respond to messages sent from BrightStor
VM:Backup to an operator
3 Submit backup jobs
Select and submit a backup job from a list of job
template files
4 End, resume, or suspend
processing
11–2
View outstanding messages from BrightStor
VM:Backup
Administrator Guide
■
End processing
■
Temporarily suspend job execution
■
Resume processing
Performing User Functions
Performing User Functions
When you select Option 9, Perform user functions, on the System Administrator
Main Menu, BrightStor VM:Backup displays the Perform User Functions menu.
The following table lists the functions you can perform from this screen. Unless
otherwise noted, see the User Guide for information about any of these tasks.
User Functions
Task
Option
Use this option to ...
Restore
CMS/SFS
data
1 Select minidisk or
directories from
which to restore
data
Select specific minidisks and SFS
directories from which to restore. You can
restore CMS files, minidisks, and SFS
directories using procedures similar to
those used to perform the equivalent expert
user function.
2 Select files to
restore by date
range or file
name
Specify selection criteria for the CMS files
you want to restore. You can:
Select files by time period or file name
■
■
Specify whether all backup versions or
only the most recent should be
displayed
Indicate whether you want to limit the
search to certain minidisks and
directories
The procedures used to perform these tasks
are similar to those used in the equivalent
expert user function.
3 Select directories Select specific BFS directories from which
from which to
to restore. You can restore BFS files using
restore
procedures similar to those used to perform
the equivalent expert user functions. You
can restore entire BFS directories using the
procedures described in Restoring BFS
Directories on page 10-8.
Performing Operator and User Functions
11–3
Performing User Functions
User Functions
Task
Option
Use this option to ...
Restore BFS
data
4 Select files to
restore by date
range or file
name
Specify selection criteria for the BFS files
you want to restore. You can:
■
■
■
Select files by time period or file name
Specify whether all backup versions or
only the most recent should be
displayed
Indicate whether you want to limit the
search to certain BFS directories
The procedures used to perform these tasks
are similar to those used in the equivalent
expert user function.
5 Review restore
requests
Communicate 6 Respond to
with
VM:Backup
VM:Backup
11–4
Administrator Guide
Review the status of end user restore
requests or cancel an end user request
before BrightStor VM:Backup starts
processing it. This function is identical to
the equivalent function on the User Main
Menu, except that you can view and cancel
restores for other users.
View and respond to outstanding messages
from BrightStor VM:Backup. This function
is identical to the equivalent function on the
User Main Menu.
Performing User Functions
The following table describes how to perform the above tasks for yourself or
another user:
Performing User Tasks for Yourself or Others
To perform
this task:
For yourself
For others
Restore
CMS/SFS
data
Accept the default (your
user ID) displayed in
Restore CMS/SFS files for
userid field.
Type the user ID of another user in
the Restore CMS/SFS files for
userid field. You cannot type an
asterisk to restore data for more
than one user at a time.
Restore BFS
data
Type the name of the file
space from which you want
to restore. Then, accept the
default (the user ID
determined by using your
UID) displayed in the
Restore BFS files from file
space for userid field.
Note: To restore a BFS
directory, you must specify
an asterisk in the Restore
BFS files from file space for
userid field.
Type the name of the file space
from which you want to restore.
Then, type the user ID of another
user or an asterisk in the Restore
BFS files from file space for
userid field. If you specify an
asterisk, BrightStor VM:Backup
displays information owned by all
users.
Note: To restore a BFS directory,
you must specify an asterisk in the
Restore BFS files from file space
for userid field.
Accept the default (your
View or
cancel restore user ID) displayed in the
requests
Communicate on behalf of
userid field.
Type the user ID of another user or
an asterisk in the Communicate on
behalf of userid field. If you
specify an asterisk, BrightStor
VM:Backup displays information
about all end user restore requests.
You can only respond to BrightStor VM:Backup messages for your own user ID;
you cannot respond to BrightStor VM:Backup messages for another user.
Performing Operator and User Functions
11–5
Index
Symbols
alias files, backing up, 6-5, 6-9
ALL option, restoring file spaces, 10-3
# sign command delimiter, 2-7
alternate minidisk, restoring to, 7-9, 7-13
% pattern-matching character, 2-8
asking for volser, empty pool action, 5-8
* pattern-matching character, 2-8
AUTHORIZ configuration file record, 4-2
A
abend
maximum number of tape drives, 3-11
specifying user ID to receive dump, 3-10
access control interface (ACI) security groups
backing up, 6-17
restoring, 7-14
accessing VM:Backup, 2-2
ACI (access control interface) security groups
backing up, 6-17
restoring, 7-14
ACLs (automatic cartridge loaders), 6-11
ADD command, 5-10
adding
resource pools to superpool, 5-12
series of tapes to resource pool, 5-11
tape for current backup, 5-8
tape to resource pool, 5-8
address, tape disk, 5-7
algorithms, encryption
DES, 8-9
RC2, 8-9
authorizations, SFS, backing up, 6-5, 6-9
authorizations, VM:Backup
deleting, 4-3
for all user IDs, 11-3
hierarchy, 4-2
levels, 4-2
message routing, 4-3
operator, 4-3, 11-2
setting for all user IDs, 4-2
system administrator, 2-2, 2-5, 4-2
user, 4-2
auto-condensing catalogs
default time period, 6-8
definition, 6-7
processing guidelines, 9-4
resetting date, 9-6
setting time period, 6-7
auto-discarding catalogs
default time period, 6-7
definition, 6-7
processing guidelines, 9-5
resetting date, 9-6
setting time period, 6-7
Index–1
AUTOCAT
command, 9-6
configuration file record, 6-7
automatic cartridge loaders (ACLs), 6-11
B
backing up
alias files, 6-5, 6-9
DASD volumes, 6-18
file pools, 6-18
file spaces, 6-19
minidisks, 6-19
SFS authorizations, 6-5, 6-9
user IDs, 6-19
backup job templates
backup types, 6-4
catalog guidelines, 6-6
commands, 6-2
copying, 6-2
creating, 6-2
defining incremental job, 6-4
definition, 6-1
detecting changes during processing, 6-11
discarding, 6-2
encrypting data, 8-8
Manage Job Template screen, 6-1
overriding backup options, 8-7
printing, 6-2
quiescing minidisks, 8-8
renaming, 6-2
specify backup type, 6-8
specify exception file, 6-16
specify exclusion file, 6-16
specify handling of changing minidisks, 6-8
specify where to send reports, 6-14
specifying output tapes, 6-16
specifying what to backup, 6-17
testing, 6-3
updating, 6-3
Index–2
Administrator Guide
backup jobs
backing up DASD volumes, 6-18
backup type, 6-8
CMS, 6-8, 6-9
CMSALLOC, 6-9
detail level, 6-5
detecting changes during processing, 6-11
domain-level, 6-5
encrypting data, 8-8
exception files, 8-1
exclusion files, 8-1
file-level, 6-5
full, 6-4
holding when resource pool empty, 5-8
incremental, 6-4
limiting what to back up, 6-19
logical, 6-8
monitoring tapes used, 5-10
packing data, 6-10
physical, 6-9
quiescing minidisks and file spaces, 8-8
report detail level, 6-14
schedule considerations, 9-4
SFS, 6-8
specify backup type, 6-8
specify handling of changing minidisks, 6-8
specify if tapes are to be remounted, 6-8
specify where to send reports, 6-14, 6-15
specifying what to backup, 6-17
tape selection guidelines, 6-16
templates, 6-1
types, 6-4
backup tapes, guidelines, 6-16
base catalogs, 6-5
base templates, 6-5
BASE TEMPLATES record, TPI, 6-6
BCREATE command, 6-2
BFS
naming conventions, 10-8
restoring directories, 10-8
restoring file spaces, 10-1
BOTTOM command, 5-10, 6-1
BROWSE command, 5-4
browsing resource pools, 5-4
Byte File System (BFS)
naming conventions, 10-8
restoring directories, 10-8
restoring file spaces, 10-1
C
canceling restore requests, 11-4
catalogs
auto-condensing, 6-7, 9-6
auto-discarding, 6-7, 9-6
base, 6-5
checking for errors, 9-3
commands, 9-2
condensing, 9-3
controlling storage space, 9-3
creating, 6-6
discarding, 9-4
guidelines for backups, 6-6
guidelines for condensing, 9-4
guidelines for discarding, 9-5
limiting search period, 7-5
managing, 9-1
printing reports, 9-5
restore considerations, 9-4
restoring with, 7-5
restoring without, 7-5
setting detail level, 6-7
structure, 9-3
updating retention dates, 9-2, 9-6
warning, 9-1
CATSEARCH restore jobs
sample, 7-15, 7-16
submitting, 7-4
changes in backups, detecting
DATE option, 6-12
HASH option, 6-12
NONE option, 6-13
changing
restore dates, 10-4
tape expiration, 6-17
characters, pattern-matching, 2-8
CHECK command, 9-3
checking restore request status, 11-5
CKD (count-key-data) minidisks
backup detail level, 6-5
backup format, 6-9
CKDLIST command, 8-6
clearing BFS directories before restoring, 10-11
CMS backup
detail level, 6-5
format, 6-8, 6-9
CMS commands, entering, 2-6
CMS files, restoring, 7-9, 7-10
CMS HELP facility
exiting, 2-9
for commands, 2-8
for messages, 2-9
CMSALLOC backup, 6-9
CMSLIST command, 8-6
commands, general
entering from the VM:Backup console, 2-7
entering from VM:Backup screens, 2-7
entering VM:Backup commands from CMS, 2-6
entering VM:Backup commands from CP, 2-6
exception files, 8-2
exclusion files, 8-2
for backup job templates, 6-2
for catalogs, 9-2
for resource pools, 5-4
for restore job templates, 7-2
help, 2-8
commands, specific
ADD, 5-10
AUTOCAT, 9-6
BCREATE, 6-2
BOTTOM, 5-10
Index–3
BROWSE, 5-4
CHECK, 9-3
CKDLIST, 8-6
CMSLIST, 8-6
CONDENSE, 9-3
COPY, 6-2, 7-2, 8-2
CREATE, 5-4, 5-6
DISCARD, 5-11, 6-2, 9-4
FBALIST, 8-7
FORMAT, 7-11
GETRPT, 7-7
OPTIONS, 5-5, 5-9
PRINT, 5-5, 6-2, 9-5
RCREATE, 7-2
RENAME, 5-5, 6-2, 8-2
SCREATE, 5-5, 5-12
SERIES, 5-11
SFSLIST, 8-7
TEST, 6-3, 7-3
TOP, 5-10
UPDATE, 5-10, 6-3, 9-6
XCEPTION, 8-3
XCLUSION, 8-3
concurrent jobs, 3-10
Condense Catalogs screen, 9-3
CONDENSE command, 9-3
condensing catalogs
auto-condense period, 6-7, 9-6
description, 9-3
configuration file
for VM:Backup, 3-1
updating, 3-3
configuration file records
AUTHORIZ, 4-2
AUTOCAT, 6-7
DISKWAIT, 3-7
DUMP, 3-10
FILEPOOL, 3-12, 10-1
LISTPD, 3-9
MULT, 3-11
PULLUSER, 3-8
Index–4
Administrator Guide
RESTHOLD, 3-9
SYSOPER, 4-3
TAPEDISK, 5-7
TAPEDISP, 3-4
TAPEPOOL, 5-3
TAPEPROT, 3-5
TAPEWAIT, 3-7
TAPEXPDT, 3-3
USERWAIT, 3-6, 8-8
controlling
catalog storage space, 9-3
message routing, 4-3
conventions, examples, 1-2
COPY command, 6-2, 7-2, 8-2
copying
backup job templates, 6-2
exception files, 8-2
exclusion files, 8-2
restore job templates, 7-2
copyright screen, controlling the display of, 2-3
count-key-data (CKD) minidisks
backing up, 6-9
backup detail level, 6-5
CP commands
how to enter, 2-6
SMSG, 2-6, 2-7, 8-8
CP SMSG command, 8-8
CREATE command, 5-4, 5-6
creating
backup job templates, 6-2
catalogs, 6-6
exception files, 8-2, 8-3
exclusion files, 8-2, 8-3
include/exclude list, 8-5
resource pools, 5-4, 5-6
restore job templates, 7-2
superpools, 5-5, 5-12
tape copies, 6-17
customizing VM:Backup, 3-1
D
deleting authorizations, 4-3
densities, tape, 5-6
DASD
backing up DASD volumes, 6-18
excluding volumes from job, 8-14
restoring to alternate volume, 7-9
DASDtape
creating resource pools, 5-7
empty resource pool action, 5-7
length, 5-7
tape disk address, 5-7
data packing
description, 6-10
when using IDRC, 6-10
data set protection
NOPSWD option, 3-5
NOPWREAD option, 3-5
PASSWORD option, 3-5
Resource Access Control Facility (RACF), 3-5
security code, 3-5
data set sequence number (DSSN), 7-5
data sets
name format, 6-17
VM:Archiver, 3-3
default time period
auto-condense, 6-8
auto-discard, 6-7
restore selection, 3-9, 7-4
default values used in VM:Backup
BFS directory version displayed, 10-10
Define Job Processing Options screen, 3-8
Define Tape Handling Options screen, 3-2
Define Wait Time Options screen, 3-5
defining
file pools, 3-11
job processing, 3-8
local operating standards, 3-1
tape handling, 3-2
wait times, 3-5
DES encryption algorithm, 8-9
detaching
minidisks, 3-6
tape drives between mounts, 3-4
detail level
backup, 6-5
catalog, 6-7
report, 6-14, 7-6
detecting changes in backups
DATE option, 6-12
HASH option, 6-12
NONE option, 6-13
directories, BFS
clearing before restoring, 10-11
naming conventions, 10-8
restoring, 10-8
restoring entire directory, 10-9
root directory, 10-10
subdirectory, 10-10
viewing full directory pathname, 10-10
Discard a Resource Pool screen, 5-13
Discard Catalogs screen, 9-4
DISCARD command
deleting resource pools, 5-13
discarding catalogs, 9-4
discarding tapes in resource pool, 5-11
Manage Exception/Exclusion Files screen, 8-2
Manage Job Templates screen, 6-2, 7-2
discarding
backup job templates, 6-2
catalogs, 6-7, 9-4
exception files, 8-2
exclusion files, 8-2
resource pools, 5-4, 5-13
resource pools in superpool, 5-13
restore job templates, 7-2
superpools, 5-13
tapes in resource pool, 5-11
Index–5
disk mount requests, 3-7, 4-3
DISKWAIT configuration file record, 3-7
domain-level
backup, 6-5
catalog, 6-7
DSSN (data set sequence number), 7-5
DUMP configuration file record, 3-10
dump, specifying user ID to receive, 3-10
E
EDRSUP,, see also Enhanced Drive Recognition
embedded underscores, 2-4
encrypting backups, 8-8
encryption algorithms
DES, 8-9
RC2, 8-9
end user functions, 11-3
creating, 8-2, 8-3
definition, 8-1
discarding, 8-2
entering records, 8-4
example, 8-9
in backup template, 6-16
in restore template, 7-8
include/exclude list, 8-5
managing, 8-1
printing, 8-2
processing hierarchy, 8-12
record type hierarchy, 8-4
renaming, 8-2
specifying backup and restore options, 8-7
specifying records and values, 8-4
updating, 8-3
working with, 8-4, 8-14
exclude list
creating, 8-5
Enhanced Drive Recognition support overview, 5-6
EXCLUDE record
TPI, 8-14
Enroll Public option of Restore a File Pool screen,
10-7
EXCLUDE record, TPI, 8-14
entering commands
CMS, 2-6
CP, 2-6
VM:Backup, 2-6
ERASE option, restoring files, 7-11
erasing files during restore, 7-11
error checking, catalog structure, 9-3
error reports for
backups, 6-15
restores, 7-7
examples
conventions, 1-2
system responses and prompts, 1-2
user entries, 1-2
exception files
commands, 8-2
copying, 8-2
Index–6
Administrator Guide
excluding minidisks from job, 8-15
exclusion files
commands, 8-2
copying, 8-2
creating, 8-2, 8-3
definition, 8-1
discarding, 8-2
in backup template, 6-16
in restore template, 7-8
include/exclude list, 8-5
managing, 8-1
printing, 8-2
renaming, 8-2
updating, 8-3
working with, 8-13
exiting VM:Backup, 2-2
expiration dates for tapes, 3-2, 6-17
F
full directory pathname, 10-8
logical backup, 6-8
physical backup, 6-9
security key, 8-9
volser, 5-10
FBA (fixed-block-architecture) minidisks
backup detail level, 6-5
backup format, 6-9
FBALIST command, 8-7
FORMAT command, 7-11
file name component, naming convention, 10-8
formats, command, 2-6
file pools
automatically issuing ENROLL PUBLIC
command for, 10-7
backing up, 6-18
excluding from backup, 8-14
identifying, 3-11
restoring, 10-5
formatting minidisks, 7-11
file space, BFS
excluding, 8-15
not restoring ones that already exist, 10-3
restoring, 10-1, 10-3
skipping, 10-3
file space, SFS
excluding, 8-15
not restoring ones that already exist, 10-3
restoring, 10-1, 10-3
skipping, 10-3
file spaces
change detection during backups, 6-10
quiescing, 3-6
file-level
backup, 6-5
catalog, 6-7
FILEPOOL configuration file record, 3-12, 10-1
fixed-block-architecture (FBA) minidisks
backing up, 6-9
backup detail level, 6-5
format
CMS backup, 6-9
CMSALLOC backup, 6-9
data set name, 6-17
file name component, 10-8
file pool name, 3-11
full backup
defining backup job templates, 6-4
full directory pathname, 10-10
functions
operator, 11-2
user, 11-3
G
GETRPT command, 7-7
guidelines
backup tape select, 6-16
catalog for backups, 6-6
input for backups, 6-17
input for restores, 7-13
output for backups, 6-8
output for restores, 7-8
processing for auto-condensing catalogs, 9-4
processing for auto-discarding catalogs, 9-5
report for restores, 7-6
reports for backups, 6-14
select for backups, 6-16
select for restores, 7-8
H
hardware compression, 6-10
hardware requirements, 2-2
HASH option
detecting changes in backups, 6-12
header labels for tapes, 3-3
Index–7
help
for commands, 2-8
for messages, 2-9
for screens and menus, 2-5
holding
backup job, 5-8
restore request, 3-8
I
L
leading underscores, 2-4
leaving VM:Backup, 2-2
limiting
backup, 6-19
catalog search period, 7-5
restore, 7-14
linking to target minidisk, 7-9
Identify SFS File Pools screen, 3-11
list of tapes for restores, 3-8
IDRC (Improved Data Recording Capability)
feature, 6-10
listing
all backed-up versions of BFS directories, 10-10
latest backed-up versions of BFS directories,
10-10
In/Exclude screen, 8-6
INCLUDE record
TPI, 6-18, 7-12
INCLUDE record, TPI, 6-18
listings
output for backups, 6-14
output for restores, 7-6
Include/Exclude CMS Files screen, 8-11
LISTPD configuration file record, 3-9
include/exclude list, creating, 8-5
local operating standards, defining, 3-1
incremental backup
base templates, 6-5
definition, 6-4
options for detecting changes, 6-11
logical backup, 6-8
input guidelines
backups, 6-17
restores, 7-13
Manage Authorizations screen, 4-1
intervals, reminder messages, 3-5
J
M
Manage Configuration Options menu, 3-1
Manage Exception/Exclusion Files screen, 8-1, 8-9
Manage Existing Catalogs screen, 6-7, 9-1
Manage Job Templates screen, 6-1, 7-1
Manage Resource Pools screen, 5-1, 5-3
job processing
options, 3-8
suspending, 5-2
media for tapes, 5-6
K
menus
Manage Configuration Options, 3-1
Perform Operator Functions, 11-2
Perform User Functions, 11-3
Start Special SFS/BFS Restores, 10-1
System Administrator Main Menu, 2-5, 3-1
keyword data reports, obtaining, 7-7
messages
authorizing users to receive, 4-3
jobs
number that can run concurrently, 3-10
Index–8
Administrator Guide
detach minidisk requests, 3-6
help for, 2-9
requests to mount disks, 3-7
responding to, 4-3, 11-4
routing authorization, 4-3
tape mount requests, 3-7
to remind user to respond to VM:Backup, 3-5
types, 4-3
use IDs to receive tape-related messages, 4-3
user IDs to receive disk mount requests, 4-3
user IDs to receive system messages, 4-3
viewing operator messages, 11-2
viewing user messages, 11-4
minidisks
backing up, 6-4
backing up non-CMS minidisks, 6-9
detaching, 3-6
excluding, 8-15
formatting during restores, 7-11
if linked by other users during restores, 7-9
linking to, 7-9
quiescing, 3-6, 8-8
restoring to, 7-9, 7-10
specifying which to restore, 7-13
Modify Resource Pool screen, 5-6
NEWFILE option
restoring files, 7-11
non-CMS minidisk backup format, 6-8
NONE option
not detecting changes in backups, 6-13
NOPSWD option
OS data set protection, 3-5
NOPWREAD option
OS data set protection, 3-5
notations
examples, 1-2
O
operator
authorization level, 4-2, 4-3
functions, 11-2
messages, 3-7, 4-3, 11-2
Perform Operator Functions menu, 11-2
privileges, 4-3
wait times, 3-7
OPTIONS command, 5-5, 5-9
options for resource pools, 5-5, 5-9
mount requests
disks, 3-7
tape, 3-7
options, configuration
defining local operating standards, 3-1
job processing, 3-8
tape handling, 3-2
wait times, 3-5
moving tapes to another resource pool, 5-11
OS data set protection, 3-5
MULT
configuration file record, 3-11
link, 7-9
output guidelines
backups, 6-8
restores, 7-8
N
output listings
backups, 6-14
restores, 7-6
name format
data set, 6-17
file name component, 10-8
file pool, 3-11
full directory pathname, 10-8
overriding
auto-condense date, 9-6
auto-discard date, 9-6
tape expiration dates, 3-2
monitoring tapes used in backups, 5-10
Index–9
overwriting existing VM:Archiver data sets, 3-3
P
packing data
description, 6-10
when using IDRC, 6-10
PASSWORD option
OS data set protection, 3-5
producing tape pull lists, 3-8
protecting data
backup jobs, 8-9
restore jobs, 8-9
security key, 8-9
using encryption, 8-8
PULLUSER configuration file record, 3-8
Q
passwords for data sets, 3-5
pattern-matching characters, 2-8
quiesce user exit, 8-8
Perform Operator Functions menu, 11-2
quiescing file spaces, 3-6
function, 8-8
using exception file, 8-8
VMBEXIT2 user exit, 8-8
Perform User Functions menu, 10-9, 11-3
PF keys
PF1 (Help), 2-5
PF3 (End), 2-5
PF7 (Backward), 2-5
PF8 (Forward), 2-5
physical backup, format, 6-9
quiescing minidisks, 3-6
function, 8-8
using exception file, 8-8
VMBEXIT2 user exit, 8-8
pools
backing up, 6-18
excluding from backup, 8-14
identifying, 3-11
restoring, 10-5
R
pound (#) sign, command delimiter, 2-7
RCREATE command, 7-2
preventing copyright screen from appearing, 2-3
recomputed CMS minidisk backup, 6-9
PRINT command, 5-5, 6-2, 9-5
recording densities, 5-6
printing
backup job templates, 6-2
catalog reports, 9-5
exception files, 8-2
exclusion files, 8-2
resource pool reports, 5-5
restore job templates, 7-2
reducing tape remounts, 6-11
privileges
operator, 4-3
system administrator, 4-2, 11-3
user, 4-2
processing user restore requests, 3-9
Index–10
Administrator Guide
RACF (Resource Access Control Facility) security
system, 3-5
RC2 encryption algorithm, 8-9
reminder messages, intervals of, 3-5
remounts, allowing or reducing, 6-11
RENAME command
renaming exception or exclusion files, 8-2
renaming job template files, 6-2, 7-3
renaming resource pools, 5-5
renaming
backup job templates, 6-2
exception files, 8-2
exclusion files, 8-2
resource pools, 5-5
restore job templates, 7-3
REPLACE option
restoring files, 7-11
replacing files during restores, 7-11
report detail level
backups, 6-14
restores, 7-6
report guidelines
backups, 6-14
restores, 7-6
reports
error report for backup job, 6-15
for restore jobs, 7-6
job detail for backup job, 6-14
keyword data, 6-15
reports, printing
catalog, 9-5
error report, 6-15
resource pool, 5-5
specify where to send reports from backups, 6-15
requests
end user, 11-5
VM:Backup, 3-6, 3-7, 4-3
requirements, hardware, 2-2
reserved CMS minidisk backup, 6-9
resetting date
auto-condense, 9-6
auto-discard, 9-6
Resource Access Control Facility (RACF) security
system, 3-5
Resource Pool List for Superpool screen, 5-12, 5-13
resource pools
action when all tapes used, 5-7
adding tapes, 5-10
ask for a volser if empty pool, 5-8
ask for tapes to add to empty pool, 5-8
browsing, 5-4
changing attributes, 5-9
commands, 5-4
creating, 5-4, 5-6
creating superpools, 5-12
DASDtape characteristics, 5-7
definition, 5-1
discarding, 5-4, 5-13
discarding tapes, 5-11
hold job if empty pool, 5-8
in backups, 6-16
information about tapes, 5-10
listing order in a superpool, 5-12
Manage Resource Pools screen, 5-1
modifying, 5-10
moving tapes to another, 5-11
name format, 5-9
options, 5-5, 5-9
printing reports, 5-5
renaming, 5-5
superpools, 5-1, 5-5
suspending VM:Backup, 5-2
tape guidelines, 6-16
Tape List for Resource Pool screen, 5-10
updating, 5-5, 5-10
viewing without suspending job processing, 5-4
volser format, 5-10
responding to VM:Backup messages
operator, 3-7, 4-3, 11-2
user, 3-6, 11-4
responses, 1-2
RESTHOLD configuration file record, 3-9
Restore a File Space screen, 10-1
restore job templates
CATSEARCH jobs, 7-4
commands, 7-2
considerations, 7-1
copying, 7-2
creating, 7-2
definition, 7-1
discarding, 7-2
Manage Job Templates screen, 7-1
overriding restore options for specific domains,
8-7
Index–11
only files from incremental backup, 7-5
producing tape pull list, 3-8
replacing files, 7-11
restoring CMS files, 7-9, 7-10
restricting, 7-14
reviewing requests, 11-4
routing restored data, 7-8
selection period, 3-9, 7-4
special SFS and BFS, 10-1
specify what to restore, 7-13
specify where to restore, 7-8
to alternate volume, 7-9, 7-13
to original minidisk, 7-8
user storage groups, 10-2
with catalog, 7-5
without catalog, 7-5
printing, 7-2
renaming, 7-3
restoring encrypted data, 8-8
specify exception file, 7-8
specify exclusion file, 7-8
specify what to restore, 7-13
specify where to restore, 7-8
specify where to send report, 7-6
testing, 7-3
updating, 7-3
VOLSEARCH jobs, 7-4
with catalog, 7-5
without catalog, 7-5
restore jobs
tape media, 5-6
tapes, 5-6
restore requests
any user ID, 11-5
canceling, 11-4
holding, 3-8
Perform User Functions menu, 11-5
processing, 3-9
review, 11-4
selecting files, 11-3
your user ID, 11-5
restoring
all file spaces in storage group, 10-3
BFS directory, 10-9
catalog considerations, 7-5, 9-4
CMS minidisks to disk, 7-9, 7-10
earlier BFS directory version, 10-10
encrypted data, 8-8
erasing files, 7-11
error reports, 7-7
file pools, 10-5
file spaces, 10-1
for any user, 11-3
format minidisk before restore, 7-11
from encrypted backup, 8-9
holding end-user requests, 3-8
link to target minidisk, 7-9
new files only, 7-11
Index–12
Administrator Guide
restricting
backup, 6-19
catalog search period, 7-5
restore, 7-14
retention period for tapes, 6-17
reusing expired tapes, 3-2
reviewing restore requests, 11-4
root directory, BFS, 10-10
routing
dumps to specific user, 3-10
error reports, 6-15, 7-7
messages to user IDs, 4-3
reports from backup jobs, 6-15
restored data, 7-8
S
sample session
creating CATSEARCH job, 7-15, 7-16
creating VOLSEARCH job, 7-17
SCREATE command, 5-5, 5-12
screens, general
help, 2-5
underscores in values, 2-4
screens, specific
Condense Catalogs, 9-3
copyright, 2-3
Define Job Processing Options, 3-8
Define Tape Handling Options, 3-2
Define Wait Time Options, 3-5
Discard a Resource Pool, 5-13
Discard Catalogs, 9-4
Identify SFS File Pools, 3-11
In/Exclude, 8-6
Include/Exclude CMS Files, 8-11
Main Menu, 2-5
Manage Authorizations, 4-1
Manage Exception/Exclusion Files, 8-1, 8-9
Manage Existing Catalogs, 6-7, 9-1
Manage Job Templates, 6-1, 7-1
Manage Resource Pools, 5-1, 5-3
Modify Resource Pool, 5-6
Perform User Functions, 10-9
Resource Pool List for Superpool, 5-12, 5-13
Select Directories from Which to Restore, 10-9
Select Guidelines-Restricted To, 7-14
Select Guidelines-Source DASD Volumes, 7-12
Select Guidelines-Source/Target, 7-13
Select Version of Directory to Restore, 10-10
Specify Options, 8-7, 8-13
Specify Restore Directory Options, 10-10
Work with Backup Template, 6-2, 6-19
Work with Exception File, 8-3, 8-10, 8-14
Work with Exclusion File, 8-13
security codes for data sets, 3-5
security key
encrypted backup, 8-8
format, 8-9
recording in exception file, 8-9
restoring from encrypted backup, 8-8, 8-9
Select Guidelines-Restricted To screen, 7-14
Select Guidelines-Source DASD Volumes screen,
7-12
Select Guidelines-Source/Target screen, 7-13
Select Version of Directory to Restore screen, 10-10
selecting
files to restore, 11-3
tapes for backup jobs, 6-17
selection period for restores, 3-9
SERIES command, 5-11
setting wait times, 3-5
SFS file pools
automatically issuing ENROLL PUBLIC
command for, 10-7
SFS file spaces
change detection during backups, 6-10
SFSLIST command, 8-7
Shared File System (SFS)
alias files, 6-5, 6-9
authorization, 6-5, 6-9
backup format, 6-9
BFS directories, restoring, 10-9
detecting changes in incremental backups, 6-13
file pools, 3-11
include/exclude list, 8-7
issuing ENROLL PUBLIC command for file
pools during restores, 10-7
Perform User Functions screen, 11-3
restoring BFS directories, 10-9
restoring file spaces, 10-1
restoring SFS and BFS data, 10-1
SFSLIST command, 8-7
SKIP option, 10-3
skipping file spaces, 10-3
Select Directories from Which to Restore screen,
10-9
SMSG command, 8-8
select guidelines
backups, 6-16
restores, 7-8
Specify Restore Directory Options screen, 10-10
Specify Options screen, 8-7, 8-13
starting special SFS/BFS restore
file pools, 10-5
Index–13
identifying file pool names, 3-11
managing authorizations, 4-2
managing backup job templates, 6-1
managing configuration options, 3-1
managing exception and exclusion files, 8-1
managing existing catalogs, 9-1
managing resource pools, 5-1
managing restore job templates, 7-1
performing end-user functions, 11-3
submitting special SFS/BFS restores, 10-1
file spaces, 10-1
user storage groups, 10-2
starting VM:Backup, 2-2
storage groups
restoring more than one, 10-5
restoring single storage group, 10-2
streams, tapes
specifying number, 6-16
subdirectories, BFS, 10-10
Submit Special SFS/BFS Restores menu, 10-1
system messages, 4-3
submitting
CATSEARCH restore jobs, 7-4
incremental-only restore jobs, 7-5
VOLSEARCH restore jobs, 7-4
system responses and prompts, 1-2
superpools
adding resource pools, 5-12
characteristics, 5-12
creating, 5-5, 5-12
definition, 5-1
discarding, 5-13
discarding resource pools, 5-13
listing order of resource pools, 5-12
requirements, 5-12
updating, 5-13
viewing, 5-3
tape densities
definitions, 5-6
suspending
job processing, 5-2
VM: Backup, 5-2
VM:Backup, 5-2
tape streams
specifying number, 6-16
SYSOPER configuration file record, 4-3
system abend
specifying user ID to receive dump, 3-10
system administrator
authorization, 2-2
authorization level, 4-2
authorizing user IDs, 4-2
functions, 2-5
System Administrator Main Menu
defining job processing options, 3-8
defining wait time options, 3-5
Index–14
Administrator Guide
T
tape drives
detaching between mounts, 3-4
tape list
of tapes in resource pool, 5-10
Tape List for Resource Pool screen, 5-10
tape mount requests, 3-7
tape pull list, 3-8
tape retention period, 6-17
TAPEDISK configuration file record, 5-7
TAPEDISP configuration file record, 3-4
TAPEPOOL configuration file record, 5-3
TAPEPROT configuration file record, 3-5
tapes
adding individual to resource pools, 5-10
adding series of tapes to resource pools, 5-11
conserving, 6-11
creating copies, 6-17
data set security code, 3-5
densities, 5-6
discarding in resource pool, 5-11
empty resource pool options, 5-7
expiration date, 3-2, 6-17
guidelines for backups, 6-16
handling options, 3-2
header labels, 3-2, 3-3
length of DASDtapes, 5-7
media, 5-6
messages, 4-3
moving to another resource pool, 5-11
predefining, 5-1
reducing remounts, 6-11
specify output tapes for backup jobs, 6-16
tape disk address for DASDtapes, 5-7
valid VM:Archiver header labels, 3-3
TAPEWAIT configuration file record, 3-7
TAPEXPDT configuration file record, 3-3
template, base, 6-5
TEST command, 6-3, 7-3
testing
backup job templates, 6-3
restore job templates, 7-3
TOP command, 5-10, 6-1
TPI (template programming interface)
excluding DASD volumes, 8-14
excluding file pools, 8-14
restoring SFS data through, 7-1
specifying base job template files, 6-6
specifying DASD volumes to back up, 6-18
specifying DASD volumes to restore, 7-12
specifying file pools to back up, 6-18
trailer labels for tapes, 3-2
trailing underscores, 2-4
U
underscores in values, 2-4
unloading tapes between mounts, 3-4
UPDATE command
adding resource pools to superpool, 5-13
description, 5-5
Manage Exception/Exclusion Files screen, 8-3
Manage Job Templates screen, 6-3, 7-3
modifying auto-condense date, 9-6
modifying auto-discard date, 9-6
modifying resource pools, 5-10
viewing pools in superpool, 5-3
updating
backup job templates, 6-3
catalog retention dates, 9-2, 9-6
exception files, 8-3
exclusion files, 8-3
resource pools, 5-10
restore job templates, 7-3
superpools, 5-13
updating configuration file
file pool names, 3-11
job processing options, 3-8
tape handling options, 3-2
wait time options, 3-5
user
authorization level, 4-2
functions, 11-3
restore requests, 3-9, 11-3
user entries, 1-2
user IDs, authorizing all, 4-2
user storage groups
restoring more than one, 10-5
restoring single storage group, 10-2
USERWAIT configuration file record, 3-6, 8-8
V
viewing
all backed-up versions of BFS directories, 10-10
full directory pathname, 10-10
latest backed-up versions of BFS directories,
10-10
messages, 11-2, 11-4
pools in superpool, 5-3
resource pools without suspending job
processing, 5-4
Index–15
for users to quiesce file spaces, 3-6
options, 3-5
overriding current settings, 3-5
reminder, 3-5
setting, 3-5
restore requests, 11-4
superpools, 5-3
tapes in resource pools, 5-10
VM:Archiver data sets, 3-3
VM:Backup
accessing, 2-2
customizing configuration, 3-1
entering commands from CMS, 2-6
entering commands with SMSG, 2-6
exiting, 2-2
overview, 2-1
VM:Backup-VM:Tape interface
data set name, 6-17
empty resource pool action, 5-7
operator response wait time, 3-7
resource pool management, 5-8
VM:Tape
resource pool names, 5-9
VMBACKUP CONFIG file, 3-1
VMBEXIT2 user exit, 8-8
VOLSEARCH restore jobs
sample, 7-17
submitting, 7-4
volume serial number (volser)
definition, 5-10
format, 5-10
volumes, DASD
backing up, 6-18
excluding from restore, 8-14
restoring entire DASD volume, 7-14
restoring to alternate, 7-9
W
wait time
actions when time expires, 3-6
for operators to mount disks, 3-7
for operators to mount tapes, 3-7
for users quiesce minidisks, 3-6
for users to detach minidisks, 3-6
Index–16
Administrator Guide
wild card characters, 2-8
Work with Backup Template screen, 6-2, 6-19
Work with Exception File screen
describing the exception file, 8-4
describing the exclusion file, 8-14
example creating an exception file, 8-10
specifying options, 8-12
Work with Exclusion File screen, 8-13
X
XCEPTION command, 8-3
XCLUSION command, 8-3
Download PDF
Similar pages