Template Programming Interface Guide › Backup Job Exception Files

Backup Job Exception Files

This chapter describes the structure of backup job exception files created using TPI and shows an example file. It then explains each record TPI backup job exception files can include. The records are listed in alphabetical order. Unless stated otherwise, the records and parameters apply to both full and incremental backup jobs.

This section contains the following topics:

Backup Job Exception File Structure and Sample

Backup Job Exception File Structure and Sample

The following table outlines the structure of a backup job exception file. The table lists the records in the order you or an authorized client might use them in a file.

Record	Information Specified	Required	Quantity Allowed
COMMENT	Comment	No	1
*	Additional comments	No	Multiple
EXCEPT	Domains to process differently than specified in job template file	Yes	Multiple; at least 1
FROM	Domain that contains the data the backup job is to back up for an abstract domain	No	1 required for each EXCEPT ABSTRACT record
OPTIONS	Processing options for domains identified on EXCEPT record	No	Multiple
REPORT	Report options for domains identified on EXCEPT record	No	Multiple
INCLUDE	Files or minidisk extents to back up from domains identified on EXCEPT record	No	Multiple
EXCLUDE	Files or minidisk extents to not back up from domains identified on EXCEPT record	No	Multiple
USRRECORD	User record to include with data to back up	No	Multiple
CHECKSUM	Number that protects file from manual modification	No	1; last in file

Example Backup Exception File

The following example Backup Exception File shows an exception file for a backup job named WEEKLY $XCEPT. This file defines the following exceptions:

For all minidisks belonging to user ID SQL, quiesce them and back them up in physical format.
For all minidisks belonging to user ID SECURE, do not backup any file having a file name of SMITH.
For all user IDs, do not backup files that have a file type of NETLOG.

For all file spaces in all file pools, do not backup files that have a file type of NETLOG.

EXCEPT USERID SQL * 
OPTIONS QUIESCE YES
OPTIONS BKPTYPE PHYSICAL

EXCEPT USERID SECURE * 
EXCLUDE FILE SMITH *

EXCEPT USERID * *
EXCLUDE FILE * NETLOG

EXCEPT FILESPACE *:*
EXCLUDE FILE * NETLOG

* Record

OPTIONAL

Use the * record to add comments to exception files in addition to the comment specified on the COMMENT record. When you manage exception files through the CA VM:Backup screens, CA VM:Backup displays the comment on the COMMENT record on the screen; comments on * records are not displayed on the screen.

You can use * records with the COMMENT record or by themselves, and you can include as many as you need. You can place * records anywhere in the file; however, when the file is exported, CA VM:Backup places all * records in order after the COMMENT record or, if no COMMENT record exists, at the beginning of the file.

Note: This record is available only through TPI. Using this record will not prevent you from managing the exception file through the CA VM:Backup screens.

* [text]

Definitions

text: Can include up to 80 characters of comment text; any additional text is truncated. You must enter the asterisk (*) in column 1 of the record. You can use uppercase and lowercase letters; when you import or export the file, text case is preserved.

Example:

You added an EXCEPT USERID SHERYL 0191 followed by an INCLUDE FILE * SCRIPT to your exception file. You want to document in the exception file for the weekly backups that only files with the filetype SCRIPT are to be backed up for user ID SHERYL. Include the following * record in the exception file:

* Back up only script files for user ID SHERYL in weekly backup