Backup Software, Static Configuration and Configuration Database

In order to backup DPOD's software, static configuration and configuration database, use /app/scripts/app_backup.sh.

The scripts parameters:

Parameter	Description
-t, --backup-type	full: Application files and configuration database (default) app: Application files db: configuration database
-d, --backup-directory	The destination output backup directory. The default is `/installs/system-backup/<backup type>-<current date and time>` For example: `/installs/system-backup/full-backup-2021-08-02_18-52-08`
-f, ---backup-file-name	The destination output backup file name. The default is `<backup type>-<current date and time>.tar.gz` For example: `full-backup-2021-08-02_18-52-08.tar.gz`

The output backup directory will be the location of the backup log as printed in the backup status message.

The free space required on the backup output directory could get up to ~500MB.

Restore Software, Static Configuration and Configuration Database

In order to restore DPOD's software, static configuration and configuration database, use /app/scripts/app_restore.sh.

The restore should be executed on a DPOD instance of the same version and load architecture that the backup was executed on.

Restoring a backup file from a different DPOD version or load architecture is not supported and may lead to unexpected results.

The scripts parameters:

Parameter	Purpose
-t, --restore-type	full: Application files and configuration database (default) app: Application files db: configuration database
-d, --backup-directory	The restore source backup directory. For example: `/installs/system-backup/full-backup-2021-08-02_18-52-08`
-f, ---backup-file-name	The source backup file in the backup directory. For example: `full-backup-2021-08-02_18-52-08.tar.gz`

It is not recommended to backup the big data store using regular backup software due to its size.