Reducing save-outage time: Overview

This information tells you what happens when you use the save-while-active function to reduce your save-outage time.

Reducing your save-outage time is the recommended way to use the save-while-active function. To reduce your save-outage time, you can end the applications that make changes to the objects you are saving. You can restart the applications when the server has established a checkpoint for application-dependent objects.

An application-dependent object is any object that applications use and update. By using the save-while-active to reduce your save-outage time, you will have to perform no additional recovery procedures when you restore the objects.

You can specify to have the server send you a message when it has completed checkpoint processing of the following:

For all objects within a particular library
For all libraries in the save request

You can start the applications again when all application-dependent objects have reached a checkpoint. The checkpoint images of the objects that you save then appear as if you performed a dedicated save during the time the applications were ended.

If you are saving objects from multiple libraries and a common application-dependency that spans the libraries exists, do not restart the applications right away. You should wait until checkpoint processing has completed for all the libraries in the save request. When the checkpoint processing has completed for all the libraries, you can then restart the applications.

This method can substantially reduce your save-outage time, even though it does not eliminate it.