The following are the principal concepts behind CA VM:Backup.
This section contains the following topics:
The CA VM:Backup system administrator creates and updates the job template files, which are the basis for the jobs you submit. There are job template files for the following jobs:
Backup jobs copy data on a minidisk or in a file space to tape. CA VM:Backup can perform two types of backups, full and incremental. Full backups copy all of the data on a minidisk or in a file space to tape. Incremental backups copy to tape only data that has changed since the previous backup of the minidisk or file space.
You can submit backup jobs that are based on job template file using the Submit System Backups screen or the SUBMIT command. Backup job template files specify which minidisks and file spaces CA VM:Backup is to back up and how CA VM:Backup is to process them.
Note: Unless otherwise specified, references in this book to backup jobs include those submitted by CA VM:Backup and by other applications, such as CA VM:Archiver.
Restore jobs write backed-up data to a virtual reader, minidisk, or SFS entity (file pool, user storage group, SFS file space, BFS file space, SFS directory, or BFS directory). CA VM:Backup system administrators can restore data backed up for individual users or from entire DASD volumes and file pools. CA VM:Backup users can restore data backed up from minidisks or SFS directories they own, and they can restore BFS files backed up from BFS file spaces they own.
You can submit restore jobs (including SFS and BFS restore jobs) that are based on job template files using the SUBMIT command. Restore job template files specify which minidisks or portions of minidisks CA VM:Backup is to restore and how CA VM:Backup is to process them.
Note: Unless otherwise specified, references in this book to restore jobs include those submitted by CA VM:Backup and by other applications, such as CA VM:Archiver.
Merge/purge/copy (MPC) jobs copy specified domains, CMS files, SFS files, and BFS files from named input tapes to output tapes. Only authorized clients, such as CA VM:Archiver, can submit MPC jobs.
REINIT jobs re initialize input tapes that have been processed by MPC jobs. Only authorized clients, such as CA VM:Archiver, can submit REINIT jobs.
AUTOCAT jobs condense and discard CA VM:Backup catalogs. The CA VM:Backup system administrator maintains one or more AUTOCAT job template files that specify job processing options. The system administrator can configure CA VM:Backup so that an AUTOCAT job runs automatically every day at a predefined time, or you can submit AUTOCAT jobs manually using the SUBMIT command.
Normally, CA VM:Backup processes jobs in the order they enter the job queue. The system administrator determines the total number of jobs and the number of each type of job CA VM:Backup can process concurrently.
You can change the order in which CA VM:Backup processes particular jobs, and you can have CA VM:Backup restrict processing to just one job. To change the order in which CA VM:Backup processes jobs, you can:
To have CA VM:Backup restrict processing to just one job, you can make that job exclusive using the EXCLUSIVE option on the SUBMIT command. CA VM:Backup will not start an exclusive job until previous jobs have completed and will not start other jobs until the exclusive job completes.
An AUTOCAT job can run automatically if the system administrator configures it to do so. With a scheduling system such as CA VM:Schedule, you can schedule other jobs to run at preset times as well.
The system administrator also establishes whether CA VM:Backup should process user restore requests immediately or hold them for execution during a period of low data center activity. As an operator, you can tell CA VM:Backup when to start processing requests that were put on hold.
The system administrator specifies how long CA VM:Backup is to wait for you to respond to a message, such as a request to mount a tape, and how frequently CA VM:Backup should issue a reminder message. If you do not respond within the time allowed, the job is put on hold.
The system administrator determines how a backup job is to be handled when an insufficient number of tapes has been allocated. If you do not use CA VM:Tape, CA VM:Backup may ask you to provide the volser of an available tape so that the job can continue.
If an abnormal system termination (abend) occurs (including external terminations), when the system is re initialized the CA VM:Backup restart recovery facility automatically restarts any jobs (including those jobs that were started by CA VM:Archiver) that were interrupted.
If a job is interrupted because of a permanent tape I/O error, a job rollback occurs, and CA VM:Backup immediately restarts the job automatically.
If a job encounters a recoverable error (other than a permanent I/O error) or a procedural error, CA VM:Backup does not restart the job but instead places the job on hold. A CA VM:Backup operator or system administrator must restart the job later with the RELEASE command. For example, CA VM:Backup will not automatically restart a job that failed because an operator ignored a tape mount request.
Unless the system administrator has specified otherwise, CA VM:Backup uses the CHECKDISK minidisk to collect checkpoint data during backup and restore job processing. For backup jobs, CA VM:Backup uses checkpoint data to restart interrupted backup jobs with the last completed domain (minidisk, file space, or directory) on the last completed tape volume for each tape stream. For restore jobs, CA VM:Backup uses checkpoint data to restart interrupted restore jobs with the last completed domain.
For either type of job, you are asked to remount some volumes so that CA VM:Backup can accurately reposition the tapes for restarting. CA VM:Backup restarts from the beginning those domains that were not completely restored when the job was interrupted. When restarted, all jobs continue as though they were never interrupted.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|