Previous Topic: Backup ProcessNext Topic: Changing BFS File Spaces and Directories


Changing SFS File Spaces and Directories

By default, CA VM:Backup does not check for changes in a file space during a backup. This setting is suitable for most sites because SFS guarantees a consistent view of individual files; however, if your site runs applications that requires files to be maintained at the same commit level, that is, in sync with each other, you should have CA VM:Backup perform one or more consistency checks during backups.

You can specify the number of consistency checks (up to 9) on the system administrator Work With Backup Template screen or Work With Backup Exception screen, or on the OPTIONS SFSTRIES TPI record in the template or exception file.

If, after the requested number of attempts, CA VM:Backup still cannot obtain a consistent view of the file space, CA VM:Backup backs it up and writes a message in the job output report stating a consistent view was not obtained.

CA VM:Backup cannot detect changes made to update-in-place files. To ensure that you obtain a consistent point-in-time view of SFS file spaces that contain update-in-place files, you must quiesce these file spaces during backups.