CA VM:Backup system administrators can also define exception files and exclusion files to associate with job template files. An exception file specifies special processing for certain minidisks, file spaces, or directories specified in the job template file. An exclusion file specifies that a job not process certain entities that are specified in the job template file. These entities can include DASD volumes, file pools, minidisks, file spaces, or directories.
System administrators can define exception and exclusion files through function screens or TPI. CA VM:Archiver defines exception files through TPI.
You can associate the same exception or exclusion file with any number of job template files. However, a given job template file cannot specify more than one exception and one exclusion file. If the exception file and the exclusion file for a job template file reference the same data, the exclusion file takes precedence. Then CA VM:Backup excludes the data from the job.
Again, TPI offers certain options for exception and exclusion files that are not available through the function screens. For example, you can only specify that CA VM:Backup restore data to a target other than the source in an exception file that TPI created.
Note: If you are using CA VM:Batch Release 1.4, exclude each of your CA VM:Batch worker virtual machines from your backup jobs. The 194 RR minidisk for each of your CA VM:Batch worker machines is on a non-existent DASD volume and cannot be backed up. The other minidisks for each of your CA VM:Batch worker machines are work minidisks that are formatted and populated at job initiation with information specific to the job being run. Therefore, there is no need to back up this data.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|