CA VM:Backup issues requests when it needs you to perform a particular task, such as mounting a tape or overriding a tape expiration date, before it can continue processing a backup or restore job.
Option 2, Respond to VM:Backup requests, on the Operator Main Menu lets you view and reply to messages from CA VM:Backup. Enter 2 on the command line of the Operator Main Menu to select this option. CA VM:Backup displays the Respond to CA VM:Backup Requests screen. This screen provides the following information about CA VM:Backup messages:
This column displays the reply identification number for the message.
This column displays the message text and the responses you can make. For example, if CA VM:Backup asks you to mount a tape, the message tells you which tape needs to be mounted and the virtual address at which a tape drive should be attached.
This column displays the time CA VM:Backup issued the message. If you do not respond when you first receive the message, CA VM:Backup resends it periodically. If you do not respond within the time limit set by the CA VM:Backup system administrator, CA VM:Backup puts the job on hold.
The following sections describe the replies you can make to CA VM:Backup messages on the Respond to CA VM:Backup Requests screen. When you reply to a message on this screen, CA VM:Backup displays its response to your reply under the message. For example, if you enter ok in the Command column next to a tape mount request, CA VM:Backup displays <REPLY OK HAS BEEN ACCEPTED> under the mount request.
CA VM:Backup automatically updates the information on the Respond to CA VM:Backup Requests screen every 10 seconds. To remove outdated information, press PF2 (Refresh).
When CA VM:Backup issues a tape mount request for a job (message 624R), you can use the HOLD reply to temporarily interrupt a job and place it on hold. You can put any job whose status is other than compile on hold. Enter hold in the Command column next to the tape mount request for the job you want to put on hold.
Use the RELEASE command to restart a held job. For information, see Releasing Held Jobs.
You can use the CANCEL reply to reject a CA VM:Backup disk mount request (message 151R) that you cannot comply with. Enter cancel in the Command column next to the disk mount request you want to reject or the tape mount request you want to refuse.
If you reject a disk mount request, CA VM:Backup continues the job but skips the data on the requested DASD volume. If the disk is part of an SFS user storage group, CA VM:Backup skips all of the file spaces in that user storage group.
When CA VM:Backup is interfaced with CA VM:Tape and you run a backup or MPC job, CA VM:Tape writes its own checkpoint files on the CA VM:Tape service virtual machine. When the job finishes processing, CA VM:Tape erases those files.
If CA VM:Tape becomes unavailable after the job completes but before CA VM:Tape has erased the checkpoint files, the job continues to be in running status and CA VM:Backup periodically checks the status of CA VM:Tape. Each time CA VM:Backup checks CA VM:Tape and finds it unavailable, CA VM:Backup sends you a message that tells you to start CA VM:Tape or enter the FINISH reply for the job.
If you restart CA VM:Tape, CA VM:Tape erases the checkpoint files and the job ends normally. If you enter finish in the Command column next to the message for the job, the job ends normally but the CA VM:Tape checkpoint files still exist on the CA VM:Tape service virtual machine.
If you do not either restart CA VM:Tape or enter the FINISH response, CA VM:Backup waits until CA VM:Tape becomes available.
You can use the OK response to let CA VM:Backup know that you have complied with a request or that CA VM:Backup can do what it asked permission to do. Enter ok in the Command column next to the request.
Depending on the options specified by the CA VM:Backup system administrator, CA VM:Backup may ask you for permission to override the expiration date on a tape volume or overwrite an existing CA VM:Archiver data set.
When a tape is mounted for use in a CA VM:Backup backup job, CA VM:Backup verifies that the tape's labels are valid, it is an expired or new tape, and the tape can be used in the job.
If the tape can be used in the job, CA VM:Backup rewrites the tape labels to reflect the new information for this backup 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 backup job. CA VM:Backup uses the resource pool information to select volumes to use in backup jobs.
If the tape expiration date previously written in the tape labels has not yet been reached and the system administrator has authorized you to override the tape expiration date, CA VM:Backup will ask you for permission to overwrite the tape.
If you have not been authorized to override the tape expiration date, CA VM:Backup will not ask for permission to overwrite the tape. Instead, CA VM:Backup rejects the tape, selects another volume to use in the job, and asks you to mount this new volume. If CA VM:Backup is configured to enable tape chaining in tape trailer labels, before making the mount request, CA 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.
CA 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. CA VM:Archiver protects its tapes from being used inadvertently in three ways:
All CA VM:Archiver tapes have an expiration date of PERM (permanent), which means that they never expire. The PERM designation protects them from being reused by other user IDs.
All tapes created for CA VM:Archiver jobs are owned by the CA VM:Archiver service virtual machine that submitted the jobs. CA VM:Backup makes sure that the requesting user is the owner of the tape before it uses the tape.
CA VM:Archiver tells CA VM:Backup which data sets to write to so that CA VM:Backup does not inadvertently overwrite a CA VM:Archiver data set.
When appending data sets to a tape, CA VM:Archiver may provide CA VM:Backup with a starting volser for that job. CA VM:Archiver always asks CA VM:Backup to write to a specific data set. If the job is canceled while CA VM:Backup is processing it, part of the data set may have been written to the CA VM:Archiver tape volume; therefore, correct and valid header labels may exist. When CA VM:Archiver submits the next job, it asks CA VM:Backup to write to the same data set that was specified in the canceled job, but when CA VM:Backup encounters the valid tape header labels, it assumes that the entire data set exists. If the system administrator has authorized you to overwrite existing data sets, CA VM:Backup will request permission to overwrite the existing CA VM:Archiver data set.
You can reply OK to this request if the CA VM:Archiver backup job still exists in the CA VM:Archiver job queue. Enter the CA VM:Archiver QUERY JOBS command to display the CA VM:Archiver job queue. The CA VM:Backup job name must match one of the CA VM:Archiver jobs listed in the CA VM:Archiver job queue; if no CA VM:Archiver job exists, do not allow CA VM:Backup to overwrite the data set. The job name will be the name of the job template file. For detailed information about the QUERY command, see the CA VM:Archiver Command Reference .
If you have not been authorized to overwrite existing data sets, CA VM:Backup puts the job on hold.
If you do not want CA VM:Backup to override a tape expiration date or overwrite a data set on a CA VM:Archiver tape, or if you cannot comply with a request (for example, if you cannot locate a required tape), you can use the REJECT reply. Enter reject in the Command column next to the request you want to reject.
Depending on the options specified by the CA VM:Backup system administrator, CA VM:Backup may ask you for permission to override the expiration date on a tape volume. If you reply REJECT to a request to override a tape expiration date, CA VM:Backup will not overwrite the data on the requested volume. If an alternate volume is available, CA VM:Backup will issue a request to have it mounted. If an alternate volume is not available, CA VM:Backup will place the job on hold.
If CA VM:Backup is interfaced with CA VM:Tape and CA VM:Backup asks for permission to override a tape expiration date, do not reply REJECT; if you do, CA VM:Backup will not be allowed to overwrite the tape.
Depending on the options specified by the CA VM:Backup system administrator, CA VM:Backup may ask you for permission to overwrite an existing data set on a tape owned by an authorized client. Tapes used during a CA VM:Archiver backup are protected by data sets, not expiration dates; CA VM:Archiver tapes are permanent. If you respond REJECT to a request to overwrite an existing data set, CA VM:Backup will not overwrite the data on the requested data set of the requested tape. Instead, it will select a scratch tape from the same resource pool and issue a mount request again. If a scratch tape is not available, CA VM:Backup puts the job on hold.
For restore jobs, if the data was backed up to a different medium and a tape copy is available, the REJECT reply causes CA VM:Backup to search for an alternate volume and issue a mount request again. If an alternate volume is not available, CA VM:Backup puts the job on hold.
When you have corrected a problem with the security system service virtual machine, you can use the RETRY reply to have CA VM:Backup try the Surrogate request again. For more information about responding to requests relating to the Surrogate facility, see the following topic, Suspending the Request.
If you are unable to fulfill a request when CA VM:Backup issues it, if the Surrogate facility is not available, or if a problem with the security service virtual machine cannot be readily corrected, you can use the WAIT reply to suspend the request. The WAIT reply causes CA VM:Backup to wait until either the problem is corrected or you end CA VM:Backup processing.
Enter wait in the Command column next to the request you want to suspend. CA VM:Backup ignores the wait time limit defined by the CA VM:Backup system administrator and waits indefinitely, sending reminder messages periodically until you respond to the request.
When the problem is corrected, use the RETRY reply to have CA VM:Backup try the Surrogate request again. If the request cannot be fulfilled within a reasonable period of time, you can enter the REJECT response. For information about this reply, see Rejecting a Request.
If a resource pool runs out of available tape volumes, CA VM:Backup may ask you for the volser of a tape that can be used. This request should appear only if CA VM:Backup is not interfaced with CA VM:Tape. To provide a tape, enter the volser of a standard label tape that can be used with the specified resource pool (one that is of the same medium and density), then press PF2 to refresh the Respond to CA VM:Backup Requests screen. Reenter the volser as a safeguard against specifying an incorrect volume, then press PF2 (Refresh) again to refresh the screen and receive the tape mount request from CA VM:Backup.
The way in which the CA VM:Backup system administrator has set up tape handling procedures determines whether the volser you specify is added to the resource pool.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|