Backing up a Db2 database online

You can simplify the recovery process by using a Single System View (SSV) backup for your Db2 database deployments. You can back up database partitions simultaneously and receive a single time-stamp for all partitions.

1. From a bash shell on the catalog node, switch to the database instance owner and create the directory to hold the backup images:

   su - db2inst1

   mkdir -p backup_dir/backup_nnn

   where backup_dir is the directory that you create to hold backup images and nnn is an incremental value that puts each backup in a separate subdirectory. The backups can be put into any directory on the cluster that is shared by the container nodes and has sufficient space to hold the backups. If you back up into a different directory, alter these commands as necessary.
2. Connect to the database.

   db2 connect to ${DBNAME}

3. From the node where the database service is deployed, run the online backup with the following command:

   db2 backup db ${DBNAME} on all dbpartitionnums online to backup_dir include logs without prompting

   Where backup_dir is the full path to the directory that you created in Step 1.

   The following is an example of a successful result:

   Part  Result
   ----  ------------------------------------------------------------------------
   0000  DB20000I  The BACKUP DATABASE command completed successfully.
   0001  DB20000I  The BACKUP DATABASE command completed successfully.
   0002  DB20000I  The BACKUP DATABASE command completed successfully.
   
   Backup successful. The timestamp for this backup image is : 20190523204048

   The database backup is complete.
4. Run the following command to copy over the two keystore files from the keystore directory into the backup directory.

   cp ${KEYSTORELOC}/keystore.p12 ${BACKUPDIR}
   cp ${KEYSTORELOC}/keystore.sth ${BACKUPDIR}
   

   When you restore from an encrypted backup, you will need the following two keystore files:

   • keystore.p12
   • keystore.sth