Enterprise and Standard plans

1. Click Administration in the left menu and select the Backups tab. Click the Run backup button.

   

2. Click Run to run a manual backup.

   

3. When the backup starts, some features might not be available until the backup is completed.

   

4. After backup completion, a new backup entry in the list of backups appears as a Full (Manual) type. The new backup is in an available state.

   

Procedures and Usages

SAVE_BACKUP:

• The SAVE_BACKUP call is used to mark backups that need to be retained beyond the standard retention period. This call creates a duplicate entry in the table, where the retained backup is indicated by a 1 in the RETAIN column. Both the original and saved entries will appear on the list until the original backup reaches the end of its retention period and is deleted through the regular cleanup process, and only the saved backup will show on the list.

db2 "call SAVE_BACKUP(20240313215333);"

REMOVE_SAVED_BACKUP:

• The REMOVE_SAVED_BACKUP call is used to unmark a retained back so it can be deleted by the automated cleanup process.

If the original backup is no longer available and the saved copy is removed, that backup becomes unrecoverable and cannot be marked for retention again. Therefore, this call should only be used when the User is absolutely certain the backup is no longer needed.

db2 "call REMOVE_SAVED_BACKUP(20240313215333);"

LIST_BACKUP:

• The LIST_BACKUP functionality shows the complete list of backups along with the ones marked for retention, a sample output is shown below.

db2 "select * from table(LIST_BACKUPS());"

BACKUP         PARTS       RETAIN
-------------- ----------- -----------
20240229215327           6           0
20240303215333           6           0
20240304215356           6           0
20240305215330           6           0
20240306215327           6           0
20240307215329           6           0
20240308215332           6           0
20240309215331           6           0
20240310215328           6           0
20240311215329           6           0
20240312215333           6           0
20240313215333           6           0
20240314215324           6           0
20240315215328           6           0
20240316215327           6           0
20240317215328           6           0
20240318215334           6           0
20240303215333           6           1
20240312215333           6           1

The PARTS field shows how many parts a backup is composed of after running the procedure to save it beyond its retention period. In this example, the backup contains 6 parts. Since both the original and the saved backup entries appear in the list, users should ensure the parts count matches between them. This helps confirm that all parts of the backup were saved properly. If the parts count on the saved entry is lower than the original, the SAVE_BACKUP call should be run again until all parts are saved successfully.

A 1 in the Retain Column indicates that the backup is saved until it's marked for deletion.

Restrictions

Any backup which is within 24 hours of being removed (i.e. 1 day or less from exceeding the retention period) cannot use the SAVE_BACKUP process.

End-of-backup restore

Point-in-time restore

IBM Db2 SaaS added a point-in-time restore capability for systems in IBM Cloud Public. You can restore to an exact point in time from your backups.

The following are a selected example of screen captures of the point-in-time restore operation in the web console UI: