System Programmer Reference › Backing Up Data › Backup Job Overview › Error Handling › During File Space Backups

During File Space Backups

If CA VM:Backup cannot obtain links to all of the minidisks in an SFS user storage group, file spaces in that user storage group are not backed up.

For SFS file spaces, if CA VM:Backup detects changes in a file space after performing the maximum number of consistency checks allowed, CA VM:Backup backs up the file space and writes a message to the job output report indicating that a consistent point-in-time view could not be obtained. In this case, the integrity of individual files in the file space is not guaranteed. If a consistent point-in-time view can be obtained, the files might be at different commit levels. This should not be important to most applications; however, if you are unsure, you should quiesce the file space.

CA VM:Backup cannot detect changes made to update-in-place files. To make sure that you obtain a consistent point-in-time view of an SFS file space that contains update-in-place files, you must quiesce the file space during backups.

For BFS file spaces, all files are update-in-place; therefore, CA VM:Backup cannot detect changes. To make sure that you obtain a consistent point-in-time view of a BFS file space, you must quiesce it during backups.

Errors or the inability to link are indicated in the output listing returned to the user specified under Report Guidelines or on the REPORT record in the backup job template file. For more information, see the chapter "Managing Backup Job Template Files" in the Administration Guide or the REPORT record for backup job template files in the Template Programming Interface Guide.