Contents

The CA VM:Backup/CA VM:Schedule interface enables you to use CA VM:Schedule to issue the CA VM:Backup SUBMIT command, specifying the template name and submit time desired.

How the Interface Works

CA VM:Schedule can be set up to run an EXEC that issues the CA VM:Backup SUBMIT command for the desired template. For example, at your site, full backups are run every Sunday afternoon, incremental backups are run Monday through Friday, and a monthly backup is run on the last Sunday of every month, in place of the regular Sunday backup. VMANAGER is the user ID that schedules the backup jobs. Template and EXEC names are as follows:

  • The name of the Sunday full backup template (and the name of the CA VM:Schedule EXEC that starts it) is BSUNDAY.
  • The name of the daily incremental backup template (and the name of the CA VM:Schedule EXEC that starts it) is BDAILY.
  • The name of the monthly full backup template (and the name of the CA VM:Schedule EXEC that starts it) is BMONTH.

Restrictions and Requirements

The EXEC created to issue the CA VM:Backup SUBMIT command runs on the CA VM:Schedule user ID. Executing the SUBMIT command can take several minutes for very large jobs. The CA VM:Schedule machine will be tied up while the SUBMIT command executes; other requests scheduled for the same time period may not execute. Therefore, you may want to use another method to submit the backup jobs if you need to initiate other requests while CA VM:Schedule executes the CA VM:Backup SUBMIT command. For example, you could create a special CA VM:Schedule user ID for submitting the backup jobs. Or, you could use the CP SMSG facility to enter the SUBMIT command; this allows CA VM:Schedule to continue working while CA VM:Backup processes the command. However, you will see no return codes.

Implementation

  1. Log on to VMSCHED.
  2. ENTER the END command to shut down VMSCHED.
  3. Create EXECs to submit the backup jobs.
    Following are three sample EXECs to run the backup jobs BSUNDAY, BDAILY, and BMONTH if you are interfacing CA VM:Schedule with CA VM:Backup:
    /*             BSUNDAY EXEC                             */
    /*EXEC to submit full backup run every Sunday           */
    'VMBACKUP SUBMIT BSUNDAY'
    saverc = rc
    If saverc = 0 Then
    'CP MSG OPERATOR Problems submitting backup job BSUNDAY'
    Exit saverc /*                    BDAILY EXEC                      */
    /*EXEC to submit daily backups run Monday thru Friday  */
    'VMBACKUP SUBMIT BDAILY'
    saverc = rc
    If saverc = 0 Then
       'CP MSG OPERATOR Problems submitting backup job BDAILY'
    Exit saverc /*             BMONTH EXEC                             */
    /* EXEC to submit monthly full backup run              */
    /* the last Sunday of every month.                     */
    'VMBACKUP SUBMIT BMONTH'
    saverc = rc
    If saverc = 0 Then 
    'CP MSG OPERATOR Problems submitting backup job BMONTH'
    Exit saverc
  4. Make sure there is an AUTHORIZ BSUNDAY VMANAGER record in the VMSCHED CONFIG file.
  5. This configuration file record allows VMANAGER to issue the CA VM:Schedule BSUNDAY EXEC.
  6. Make sure there is an AUTHORIZ BDAILY VMANAGER record in the VMSCHED CONFIG file. This configuration file record allows VMANAGER to issue the CA VM:Schedule BDAILY EXEC.
  7. Make sure there is an AUTHORIZ BMONTH VMANAGER record in the VMSCHED CONFIG file. This configuration file record allows VMANAGER to issue the CA VM:Schedule BMONTH EXEC.
  8. Enter the PROFILE command to restart VMSCHED.
  9. Enter the #CP DISCONN command to leave VMSCHED running disconnected.
  10. Log on to VMANAGER.
  11. Give CA VM:Schedule the authorizations necessary to run CA VM:Backup backup requests.
    1. Enter vmbackup. The CA VM:Backup System Administrator Main Menu displays.
    2. From the System Administrator Main Menu, select option 2. The Manage Authorizations screen displays.
    3. Press PF5 to insert a new line. Type vmsched in the Userid field. Type an x in the Operator field.
    4. Press PF9 to save your work. Press PF3 until you return to CMS.
  12. Enter the CA VM:Schedule EXEC command to schedule your backups. For example, to run the BDAILY backup, where daily is the CA VM:Schedule request name and BDAILY is the EXEC name:
    VMSCHED EXEC DAILY BDAILY (ON MON-FRI AT 20:00 WITHIN 1 AGAIN WEEKLY
    
  13. To run the BSUNDAY backup, where weekly is the CA VM:Schedule request name and BSUNDAY is the EXEC name:
    VMSCHED EXEC WEEKLY BSUNDAY (ON SUN AT 2:00 WITHIN 1 AGAIN WEEKLY
    
  14. To run the BMONTH backup, where monthly is the CA VM:Schedule request name and BMONTH is the EXEC name:
    VMSCHED EXEC MONTHLY BMONTH (ON SUN AT 2:00 WITHIN 1 FROM L SUN M AGAIN MONTHLY
    
    Note: For more information about using the CA VM:Schedule User's Guide.
  15. Log off VMANAGER.
    Note: If you are using the Surrogate Facility, the user ID that starts the job (in this case, VMSCHED) must be able to link to all minidisks to be backed up. For more information, see CA VM:Schedule/CA VM:Secure.