CA VM:Backup (or CA VM:Tape if it is used) issues tape mount requests as it processes jobs. The requests are sent to authorized operator consoles, to the CA VM:Backup console, and to the job detail report.
If your user ID has been authorized to receive and respond to tape-related messages, use the Respond to CA VM:Backup Requests screen to view the mount requests and enter replies to CA VM:Backup. For more information about this screen, see Responding to CA VM:Backup Requests.
If your system uses CA VM:Tape, tape mount requests are not displayed on the Respond to VM:Backup Requests screen. Your user ID must have tape operator authorization on the TAPEOPER configuration file record in the VMTAPE CONFIG file to receive and respond to tape-related messages.
If your user ID has been authorized to perform operator functions (such as starting system backups) but has not been authorized to respond to tape-related messages, use the REVIEW command on the Manage System Activity screen to view the outstanding tape mount requests. This function does not allow you to enter replies to CA VM:Backup. For more information about the REVIEW command, see Viewing Outstanding Messages from CA VM:Backup.
CA VM:Backup issues message 623I to ask you to mount a tape:
MOUNT medium volser AT vaddr (DENSITY densityname, RING [IN | OUT]) [WITHIN minutes MINUTES].
Identifies the tape medium to mount. For media types, see the section Enhanced Device Recognition Support in the chapter "Managing Tape and DASD Resources" in the System Programmer Reference Guide.
Identifies the volume serial number of the tape to mount.
Identifies the virtual address at which to mount the tape.
Identifies the recording density of the input tape. For density names, see the section Enhanced Device Recognition Support in the chapter "Managing Tape and DASD Resources" in the System Programmer Reference Guide.
Indicates whether a write ring is required (IN) or not required (OUT).
Indicates the time frame within which you must mount the tape. The [WITHIN minutes MINUTES] portion of the tape mount request appears only the first time CA VM:Backup issues the request.
Several table 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, see the section Enhanced Device Recognition Support in the chapter "Managing Tape and DASD Resources" in the System Programmer Reference.
The STREAMS option on the SUBMIT command lets you specify a different number of streams from the number listed in the job template file before you submit a backup job. For this job submission, the number you specify overrides the number displayed in the job template file. The job template file remains unchanged during processing. Use this option if a tape drive that you normally use is unavailable for a particular job, or if more drives become available for a job. For more information about the STREAMS option, see the SUBMIT Command.
You can restart a backup job and have it run with fewer streams than originally specified. Once a tape mount request for a stream has been satisfied, that stream will begin processing.
Note: You cannot use the STREAMS option on the SUBMIT command to change the number of streams after a job has been submitted.
You can restart a backup job with fewer streams if the job meets one of the following criteria:
To restart a job and run it with fewer streams than originally specified, follow these steps:
If CA VM:Backup is interfaced with CA VM:Tape, CA VM:Tape, not CA VM:Backup, requests the tapes to be mounted. Ignore the mount requests for the streams you no longer want to use.
Example
You are running a backup job with four streams. After the second tape of each stream has been mounted, you receive an I/O error on one of the drives and CA VM:Backup places the job on hold. Because you can no longer use one of the drives, you want to restart the job to run with three streams instead of four.
To reduce the number of streams, type release next to the job name in the Command column on the Manage System Activity screen and press ENTER. When CA VM:Backup issues the four tape mount requests, reply wait to any one of them. CA VM:Backup then begins backing up data (including data originally intended for the fourth stream) to the three active streams.
When all the data has been backed up, mount a tape for the inactive stream. Once a tape is mounted on any available drive, CA VM:Backup writes a trailer label to the tape to close the stream, and the job ends.
If you reject a tape mount request issued during a backup, CA VM:Backup (or CA VM:Tape) automatically allocates another tape and asks you to mount this tape instead. For more information about reviewing and replying to CA VM:Backup messages, see Responding to CA VM:Backup Requests.
Under certain circumstances, CA VM:Backup rewinds and unloads a tape and asks you to remount the previous tape. This is not an error. For example, if CA VM:Backup encounters an invalid file while backing up a minidisk in CMS format, CA VM:Backup must backspace to the point on the tape where the minidisk began and then back up the entire minidisk in physical format. If the backup of the minidisk started on a previous tape and the output configuration in the job template specifies to conserve tapes, the current tape is rewound and unloaded. You must remount the previous tape before CA VM:Backup can continue the job.
Remember that CA VM:Backup immediately returns the unloaded tape to the scratch pool; it may or may not reuse the tape in the job. Before sending tapes offsite, check the backup job detail report for the list of tapes actually used by the job.
If you attach the wrong device type during a backup, CA VM:Backup sends you an error message and then issues another tape mount request. You are given three chances to attach the correct device. If after three tries the correct device type is still not attached, CA VM:Backup issues another error message and places the backup job on hold.
Note: This situation does not occur if you use CA VM:Tape because CA VM:Tape automatically attaches the drive for CA VM:Backup.
If data was backed up to both DASD and physical tapes, CA VM:Backup first tries to restore from the DASDtape, regardless of whether it is the primary copy. If all copies of the DASDtape are unavailable, reused, or damaged, CA VM:Backup asks you to mount the physical tape.
If tape copies were created during a backup, the tape mount request includes the volsers of all tapes that have the same medium and density as the primary tape; you can use any copy in place of the primary tape. If you cannot mount any of the requested volsers, you can reject the mount request.
When you reject a tape mount request, CA VM:Backup searches for a copy that exists on a different medium. CA VM:Backup starts the search with the highest density medium. For the search order, see the Density Names column in the section Enhanced Device Recognition Support in the chapter "Managing Tape and DASD Resources" in the System Programmer Reference Guide. If a copy is available, CA VM:Backup reissues the mount request. If no other copies exist, the job is put on hold. If you are unable to mount any of the requested tapes, you must cancel the restore job. For information about reviewing and replying to CA VM:Backup messages, see Responding to CA VM:Backup Requests.
If you mount the wrong tape medium during a restore, CA VM:Backup issues an informational message stating that the medium mounted was not what was expected, and then continues the job. This situation can occur when a tape copy created on a different device type is mounted in place of the primary tape.
If you reject a tape mount request for an output tape issued during an MPC job, CA VM:Backup (or CA VM:Tape) automatically allocates another tape and asks you to mount this tape instead.
When you reject a tape mount request for an input tape issued during an MPC job, CA VM:Backup searches for a copy that exists on a different medium. CA VM:Backup starts the search with the highest density medium. For the search order, see the Density Name column in the section Enhanced Device Recognition Support in the chapter "Managing Tape and DASD Resources" in the System Programmer Reference Guide. If a copy is available, CA VM:Backup reissues the mount request. If no other copies exist, the job is put on hold. If you are unable to mount any of the requested tapes, you must cancel the restore job.
For information about reviewing and replying to CA VM:Backup messages, see Responding to CA VM:Backup Requests.
If you reject a tape mount request during a REINIT job, CA VM:Backup does not reinitialize the tape. CA VM:Backup does expire the tape in the CA VM:Backup resource pool or the CA VM:Tape TMC. CA VM:Backup continues the job with the next tape.
CA VM:Backup handles physical tape I/O errors differently for backup jobs and restore jobs.
If recoverable I/O errors occur while CA VM:Backup is processing a job, CA VM:Backup sends informational messages to describe the errors. To recover, CA VM:Backup repositions the tape to the last full block written and continues with the job.
If permanent I/O errors are encountered during CA VM:Backup backup jobs, CA VM:Backup tries to recover instead of terminating or abnormally ending the job. When recovering from the error, if the backup of the domain being backed up begins on the previous tape, and the output configuration in the job template specifies to conserve tapes, CA VM:Backup asks you to mount the previous tape again, then continues the job from the last completed domain on the tape. Next, CA VM:Backup asks you to mount a new volser to continue the job, skipping the tape with the error. CA VM:Backup reports all tape I/O errors through EREP.
If a restore job encounters a permanent tape I/O error, a job rollback occurs, and CA VM:Backup automatically resumes the job immediately.
If a restore job encounters an I/O error (other than a permanent I/O error) or a procedural error, CA VM:Backup does not restart the restore job but instead places the job on hold. You must restart the job later with the RELEASE command. For example, CA VM:Backup will not automatically restart a job that failed because you ignored a tape mount request.
If checkpoint data is not available, CA VM:Backup restarts interrupted restore jobs from the beginning. If checkpoint data is available, CA VM:Backup restarts interrupted restore jobs with the last completed domain. CA VM:Backup restarts from the beginning those domains that were not completely restored when the job was interrupted.
If recoverable I/O errors occur on an MPC output tape while CA VM:Backup is processing an MPC job, CA VM:Backup sends informational messages to describe the errors. To recover, CA VM:Backup repositions the tape to the last full block written and continues with the job.
If permanent I/O errors are encountered on an MPC output tape during an MPC job, CA VM:Backup tries to recover instead of terminating or abnormally ending the job. When recovering from the error, if the domain being written to the output tape begins on the previous tape, and the output configuration in the job template specifies to conserve tapes, CA VM:Backup asks you to mount the previous tape again, then continues the job from the last completed domain on the tape. Next, CA VM:Backup asks you to mount a new volser to continue the job, skipping the tape with the error. CA VM:Backup reports all tape I/O errors through EREP.
If permanent I/O errors are encountered on an MPC input tape, a job rollback occurs, and CA VM:Backup automatically resumes the job.
If an I/O error (other than a permanent I/O error) or a procedural error occurs on an MPC input tape, CA VM:Backup does not restart the job, but instead places the job on hold. You must restart the job later with the RELEASE command. For example, CA VM:Backup will not automatically restart a job that failed because you ignored a tape mount request.
If checkpoint data is not available, CA VM:Backup restarts the interrupted job from the beginning. If checkpoint data is available, CA VM:Backup restarts the interrupted MPC job with the last domain completely copied to an output tape.
If any I/O error or a procedural error occurs on a tape during a REINIT job, CA VM:Backup does not re initialize the tape. The tape is not expired in the CA VM:Backup resource pool or the CA VM:Tape TMC. CA VM:Backup continues the job with the next tape.
If CA VM:Backup encounters a DASDtape I/O error, CA VM:Backup places the backup or restore job on hold.
If you are unable to mount a particular tape, you must put the job on hold and correct the problem, or reject the request. For a list of commands you can enter to respond to a tape-related request, see Responding to CA VM:Backup Requests.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|