Contents

The CA VM:Archiver/CA VM:Backup interface enables you to use an efficient, economical alternative to DASD storage: tape storage.

CA VM:Archiver uses the interface with CA VM:Backup to:

  • Move STAGE and ONLINE files to tape storage and to copy user minidisks and files from minidisks and directories to tape storage (archive).
  • Retrieve (recall) archived data on tape to minidisks, directories, and virtual readers.
  • Copy and merge unexpired and unpurged data on existing tape sets to new tape sets. (This is known as merge/purge/copy.) Merge/purge/copy has the effect of removing expired and purged data from a tape set.
  • Reinitialize tapes that the merge/purge/copy jobs have processed.

How the Interface Works

CA VM:Archiver uses the CA VM:Backup Template Programming Interface (TPI) to create a job that archives data to, or recalls data from, tape storage. CA VM:Archiver also uses the TPI to create merge/purge/copy and reinitialization jobs. CA VM:Archiver creates $TEMPLAT and $XCEPT files that define the files and domains to be archived and recalled.

When the $TEMPLAT and $XCEPT files have been created for a job, CA VM:Archiver issues the CA VM:Backup IMPORT command to copy the files to the CA VM:Backup service virtual machine and convert them to a CA VM:Backup internal format template. When the files have been successfully imported, CA VM:Archiver issues the CA VM:Backup SUBMIT command to start the processing of the job by CA VM:Backup.

While processing the job, CA VM:Backup writes job completion information in a keyword data report on the CA VM:Backup report minidisk. When CA VM:Backup finishes processing the job, it issues the CA VM:Archiver JOBEND command to notify CA VM:Archiver that the job has completed.

Upon job completion, CA VM:Archiver issues the CA VM:Backup GETRPT command to copy the keyword data report to a CA VM:Archiver minidisk. CA VM:Archiver uses the information in the keyword data report to update its database. For archive or recall jobs, CA VM:Archiver also uses this information to notify users of the outcome of their archive or recall requests.

In addition to creating the keyword data report described above, CA VM:Backup sends the CA VM:Backup Backup and Restore Job Detail reports to the user ID identified on the CA VM:Archiver Define CA VM:Backup Options screen.

Archiving Files and Minidisks

The CA VM:Archiver SUBMIT ARCHIVES command builds a TPI job that specifies files and domains to be copied to tape storage. CA VM:Archiver also specifies the names of the CA VM:Backup resource pools to be used for each archive tape copy being created. If CA VM:Backup is interfaced with CA VM:Tape and consequently is obtaining tape volumes through CA VM:Tape, your site can use scratch tapes.

When trying to copy data from a user's minidisk, CA VM:Backup obtains a read-only link to the minidisk; the user does not need to detach the minidisk. How CA VM:Backup proceeds depends on if it is attempting to back up a file or minidisk.

  • If CA VM:Backup is trying to back up a file - If the minidisk on which the file resides changes, CA VM:Backup tries again a specified number of times. (You set the number of times that CA VM:Backup tries on the CA VM:Archiver Define CA VM:Backup Options screen.) If the minidisk is still changing after the specified number of tries, CA VM:Backup skips the file and does not back it up.
  • If CA VM:Backup is trying to back up a minidisk - If the minidisk changes, CA VM:Backup tries again a specified number of times. (You set the number of times that CA VM:Backup tries on the CA VM:Archiver Define CA VM:Backup Options screen.) If the minidisk is still changing after the specified number of tries, CA VM:Backup instead makes a physical backup of the minidisk.

Recalling Files and Minidisks From Tape

The CA VM:Archiver SUBMIT RECALLS command builds a TPI job that specifies the files and domains to be retrieved from tape storage, and the location to which these files and minidisks are to be restored.

For the files and domains being recalled directly to a minidisk, CA VM:Backup tries to obtain a read/write link to the target minidisk. The user and anyone else who is linked read/write must detach this minidisk to enable CA VM:Backup to obtain the link. CA VM:Backup notifies CA VM:Archiver of the success or failure of the recall requests.

Submitting Jobs When CA VM Backup Is Not Available

If a job is submitted when CA VM:Backup is not running, CA VM:Archiver will have already created the TPI files and the job will be in BUILT status. This job can be resubmitted when CA VM:Backup becomes available.

Implementation

 

Configuring the Interface for CA VM Backup

 

  1. Log on to CA VM:Backup.
  2. Enter the END command to shut down CA VM:Backup.
  3. Use the XEDIT command to edit the VMBACKUP CONFIG file.
  4. Make sure that there is a PRODUCT VMARCHIVE VMARCH record present. This configuration file record provides CA VM:Backup with the CA VM:Archiver service virtual machine user ID. This record allows CA VM:Archiver to use CA VM:Backup to archive, recall, and merge/purge/copy files, and reinitialize tapes.
  5. If a REPORTDISK minidisk is not yet defined for CA VM:Backup, define one and add a REPORTDISK record. This configuration file record sets up the minidisk that enables CA VM:Backup to create keyword data reports. These reports list the outcome of jobs that CA VM:Archiver submits to CA VM:Backup.
  6. Enter the FILE command to save the changes to the VMBACKUP CONFIG file.
  7. You will probably need to increase the size of these CA VM:Backup minidisks:
    • 191 (local files)
    • 1E0 (system files)
    • 1D1 (restart recovery files)
    Contact CA Technical Support for assistance if necessary.
  8. Enter the PROFILE command to restart CA VM:Backup.
  9. Enter the #CP DISCONN command to leave CA VM:Backup running disconnected.
  10. Log on to VMANAGER.
  11. Enter vmbackup. The CA VM:Backup System Administrator Main Menu displays.
  12. Verify that the names of the Shared File System (SFS) file pools that users of CA VM:Archiver will have access to are identified to CA VM:Backup.
    1. From the System Administrator Main Menu, select option 1. The Manage Configuration Options menu displays.
    2. Select option 4; the Identify SFS File Pools screen displays. Verify that the names of the SFS file pools listed are those that CA VM:Archiver will access. If not, add the SFS file pool names that CA VM:Archiver will access to the list.
      Note: For more information about defining SFS file pools to CA VM:Backup, see the CA VM:Backup System Administrator's Guide.
    3. When finished, press PF9 to save your changes. Press PF3 to return to the Manage Configuration Options menu. Press PF3 again to return to the System Administrator Main Menu.
  13. Create the resource pools to be used for CA VM:Archiver jobs. (CA VM:Backup resource pools define the media, density, and other characteristics used during CA VM:Archiver jobs.)
    1. Before creating the CA VM:Archiver resource pool, you must first suspend CA VM:Backup. Select option 8 from the System Administrator Main Menu. The Perform Operator Functions menu displays. Select option 4. The End, Suspend, or Resume Processing screen displays. Select option 3 to suspend processing temporarily.
    2. Press PF3 until you return to the System Administrator Main Menu.
    3. From the System Administrator Main Menu, select option 3. The Manage Resource Pools screen displays.
      The default pool name used by CA VM:Archiver is VMARCHIV. If you are going to use the default CA VM:Archiver pool name, create a resource pool on this screen with the name VMARCHIV.
      If you are not using the default CA VM:Archiver pool name, create a resource pool for each pool to be used in CA VM:Archiver jobs. For more information about creating resource pools, refer to the CA VM:Backup System Administrator's Guide.
      When finished, press PF3 to return to the System Administrator Main Menu.
      Resume CA VM:Backup by selecting option 8 from the System Administrator Main Menu. The Perform Operator Functions menu displays. Select option 4. The End, Suspend, or Resume Processing screen displays. Select option 4 to resume suspended processing.
  14. Press PF3 until you return to CMS.
  15. For each file pool that you identified in Step 9, verify that the following record is in the DMSPARMS file of the corresponding SFS server to define the user ID of the CA VM:Backup service virtual machine as an administrator for that file pool:

    ADMIN VMBACKUP
    

Configuring the Interface for CA VM Archiver

 

  1. Make sure that CA VM:Archiver is initialized.
  2. Log on to VMANAGER.
  3. Enter the VMARCH CONFIG command. CA VM:Archiver displays the Manage Configuration Options menu.
  4. On the Manage Configuration Options menu, select option 2. CA VM:Archiver displays the Define Tape Controls screen.
  5. On the Define Tape Controls screen, the default pool name (VMARCHIV) and corresponding data set name display. If you are not using the default pool name, enter the names of the resource pools created in Step 10 during configuration of the CA VM:Backup interface, as well as the data set names to be used for each archive tape copy to be created. You can specify one primary tape and up to four copies.
  6. When finished, press PF9 to file your changes. CA VM:Archiver returns you to the Manage Configuration Options menu.
  7. On the Manage Configuration Options menu, select option 3. CA VM:Archiver displays the Define CA VM:Backup Options screen.
  8. The Define CA VM:Backup Options screen displays the names of the CA VM:Backup service virtual machines being used for each type of job. The default name is VMBACKUP. If the name of your CA VM:Backup service virtual machine is not VMBACKUP, enter the service virtual machine name being used for each type of job.
    Note: The name of the CA VM:Backup service virtual machine for ARCHIVE, MPC, and REINIT jobs must be the same.
  9. When finished, press PF9 to file your changes. CA VM:Archiver returns you to the Manage Configuration Options menu.
  10. Press PF3 to exit the Manage Configuration Options screen, then press PF3 again until you return to CMS.