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) |
-d, --backup-directory | The destination output backup parent directory. The default is |
|
-f, |
--backup-file-name | The destination output backup file name. The default is |
|
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.
| Note |
|---|
The restore should be executed on a DPOD instance of the same version and load architecture deployment profile that the backup was executed on. Restoring a backup file from a different DPOD version or load architecture deployment profile is not supported and may lead to unexpected results. |
The scripts parameters:
Parameter | Purpose |
-t, --restore-type | full: Application files and configuration database (default) |
-d, --backup-directory | The restore source backup directory. |
-f, -- |
backup-file-name | The source backup file in the backup directory. |
Backup the Store
It is not recommended to backup the big data store using regular backup software due to its sizeOnce the restore completes successfully, you may start the system using app-util.sh → Start all (option 1).