System Programmer Reference › Backing Up Data › Backup Types › Conditions that Force a Full Backup of a Minidisk or File Space

Conditions that Force a Full Backup of a Minidisk or File Space

CA VM:Backup performs a full backup of any minidisk or file space if one of the following conditions occurs during an incremental backup job:

• The catalog minidisk does not contain catalogs for the job template files on which the incremental job template file is based. (Job template file names may have been spelled incorrectly.) CA VM:Backup performs a full backup of all minidisks and file spaces specified in the job.
• A domain was not included in a previous backup in this catalog chain.
• The incremental backup job specifies that CA VM:Backup should back up the entire domain if any data has changed, and data has changed.
• The catalog for the previous backup contains domain-level detail, and the domain has changed.
• The catalog for the previous backup contains domain-level detail, and the incremental backup job requests file-level detail. CA VM:Backup performs a full backup even if no data has changed.
• The backup format specified in the incremental backup job is different from that used in the previous backup. For example, CMS is specified in the incremental backup job, and physical was used in the previous backup.
• The minidisk block size has changed since the previous backup. For example, the incremental backup detects that the minidisk was formatted at 1K-byte blocks, but the previous backup recorded the minidisk in 4K-byte blocks.
• The user storage group in which a file space resides or the maximum number of blocks allocated to a file space was changed. (A change to a file space's warning threshold value does not force a full backup of that file space.)
• For physical backups, if the device type of the minidisk has changed since the previous backup. For example, the incremental backup detects that the minidisk resided on a CKD device type, but the previous backup recorded the minidisk as residing on an FBA device type.
• For physical backups, if the size of the minidisk has changed since the previous backup.
• For CMS backups, if the incremental backup job specifies using HASH to detect changes and the previous backup used DATE, CA VM:Backup performs a full backup even if no files have changed. CA VM:Backup does not perform a full backup if HASH was specified for the previous backup and the incremental backup job specifies DATE. For information about the HASH and DATE options, see Change Detection for CMS Backups.
• For physical backups, if the previous backup specified that changes were not to be detected. CA VM:Backup performs a full backup, regardless of the change detection method specified by the incremental backup job.
• The backup method specified by the incremental backup job is CMSALLOC.
• The encryption key specified by the incremental backup job differs from that used in the previous backup.
• The exception file information associated with the domain differs from that used in the previous backup. For example, files are listed for inclusion in the incremental job's exception file that were not listed in the previous backup job's exception file.
• A CMS minidisk contained invalid files or was changing while CA VM:Backup attempted to back it up.
• The catalog for the previous backup job contains domain-level detail and the incremental backup job contains an Include/Exclude list of files for this minidisk or file space.