Save and restore processing for a distributed relational database

Saving the system on external media, such as tape, protects system programs and data from disasters, such as fire or flood. However, information can also be saved to a disk file called a save file. A save file is a disk-resident file used to store data until it is used in input and output operations or for transmission to another IBM® i operating system over communication lines. Using a save file allows unattended save operations because an operator does not need to load tapes. In a distributed relational database, save files can be sent to another system as a protection method.

When information is restored, the information is written from tape or a save file into auxiliary storage where it can be accessed by system users.

The IBM i operating system has a full set of commands to save and restore your database tables and SQL objects:

• The Save Library (SAVLIB) command saves one or more collections
• The Save Object (SAVOBJ) command saves one or more objects such as SQL tables, views and indexes
• The Save Changed Object (SAVCHGOBJ) command saves any objects that have changed since either the last time the collection was saved or from a specified date
• The Save Save File Data (SAVSAVFDTA) command saves the contents of a save file
• The Save System (SAVSYS) command saves the operating system, security information, device configurations, and system values
• The Restore Library (RSTLIB) command restores a collection
• The Restore Object (RSTOBJ) command restores one or more objects such as SQL tables, views and indexes
• The Restore User Profiles (RSTUSRPRF), Restore Authority (RSTAUT) and Restore Configuration (RSTCFG) commands restore user profiles, authorities, and configurations saved by a Save System (SAVSYS) command