Several things can contribute to a long run time for backups. The following are some key items to look at:

  1. Does the tape drive support data compaction? If yes, then turn data compaction to Y and data compression to N on the Backup Set Definition panel.

  2. Do all libraries need object archive? If not, turn it off for the libraries that don't need it. This is done from the Items Saved within a Backup Set panel.

  3. Is the last change date for all objects (found on Object Archive Information panel for a specific object) necessary? Is it necessary to keep object archive information for the source members? If not, turn these off in the RBS900 panel.

    To access RBS900, go to a command line, and enter these commands: ADDLIBLE RBSPGMLIB and ADDLIBLE RBSDTALIB. Then CALL RBS900. Page down until the Object Archive Options appears. The 0 is off and 1 is on. Enter appropriate option. (Note: Check to make sure this value was not changed from 0 to 1 as the result of updating the Robot Save software.) The Retrieve last change date adds a lot of time to backup. Robot Save performs a RTVOBJD for each object to get that information.

  4. Reorganizing files during a save adds time to the backup. Save While Active is also slower.

  5. Perhaps there is a damaged or corrupted object in a library trying to be saved. Perform a reclaim storage (RCLSTG) on the system or reorganize the library.

  6. Check to see if Robot Save is backing up journal receivers. Remove them from the backup if possible.
    Use optimum blocking (available on RISC systems), if possible. Check the parameters on the save commands to see if this is available.

  7. Try turning off archiving at the system setup level if it is an *ALLUSR or *NONSYS save. The save will run faster, but it will not track objects that have not been saved during the backup.



Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: March 30, 2021