Considerations and restrictions for the save-while-active function

 

The save-while-active function affects important aspects of your system such as performance, auxiliary storage, and commitment control. The pages that follow contain considerations and restrictions in regard to these aspects of your system.

The pages that apply to you depend on whether you are reducing or eliminating your save-outage time.

Use dynamic device allocation to allocate tape drives more efficiently.

• Performance considerations for save-while-active
  While you can run save-while-active operations any time, save-while-active operations will affect the performance of other applications you are running.

• Storage considerations for save-while-active
  The save-while-active function uses more disk storage than normal save operations.

• Save-while-active restrictions
  

• Save-while-active object locking rules
  The object locking rules that the system uses for save-while-active requests are less restrictive than the rules it uses for other save operations.

• Restrictions for commitment control with save-while-active
  Restrictions for commitment control with save-while-active consist of object-level resource restrictions and application programming interface (API) resource restrictions.

• Saving to multiple devices to reduce your save window
  Use these save methods to decrease your save window by saving to multiple devices.

 

Parent topic:

Save-while-active and your backup and recovery strategy