There are several types of components in the DPOD appliance that should be backed up :

Backup software ,Static configuration and User Configuration data (Internal DB)

In order to backup DPOD's software, static configuration and user configuration data (internal DB ) use the app_backup.sh script located in directory /app/scripts.

The scripts parameters :

Parameter	Purpose
-t, --backup-type	full (default) : application files and internal DB app : application files db : internal DB
-d, --backup-directory	The destination output backup directory . default is :/installs/system-backup/<backup type>-<current date and time> example for full backup : /installs/system-backup/full-backup-2017-11-02_18-52-08
-f, ---backup-file-name	The destination output backup file name. default is :<backup type>-<current date and time>.tar.gz example for full backup : full-backup-2017-11-02_18-52-08.tar.gz

Invoke the backup command

app_backup.sh
INFO : backup finished successfully. for more information see log file /installs/system-backup/full-backup-2017-09-11_17-17-59/full-backup-2017-09-11_17-17-59.log

The output backup directory will be the location of the backup log as printed in the backup status message (in the current example /installs/system-backup/full-backup-2017-09-11_17-17-59 ).

The free space required on the backup output directory could get up to 300MB (for DPOD version 1.0.6.0)

Restore software ,Static configuration and User Configuration data (Internal DB)

In order to restore DPOD's software, static configuration and user configuration data (internal DB ) use the app_restore.sh script located in directory /app/scripts.

The scripts parameters :

Parameter	Purpose
-t, --restore-type	full : application files and internal DB app : application files db : internal DB
-d, --backup-directory	The restore source backup directory. in the example /installs/system-backup/system-migration/full-backup-2017-09-13_22-38-56
-f, ---backup-file-name	The source backup file in the backup directory. in the example full-backup-2017-09-13_22-38-56.tar.gz

example for restoring internal DB :

app_restore.sh -t db -d /installs/system-backup/system-migration/full-backup-2017-09-13_22-38-56 -f full-backup-2017-09-13_22-38-56.tar.gz

stopping application ...
application stopped successfully.
starting restore process ...
restoring internal DB .....
system restore was successful
for more information see log file /installs/system-backup/db-restore-2017-09-17_15-04-19.log

example for restoring software, static configuration :

app_restore.sh -t app -d /installs/system-backup/system-migration/full-backup-2017-09-13_22-38-56 -f full-backup-2017-09-13_22-38-56.tar.gz

stopping application ...
application stopped successfully.
starting restore process ...
restoring system files ...
making sure files to restore exist in backup file
files to restore exist in backup file
system restore was successful
for more information see log file /installs/system-backup/app-restore-2017-09-17_15-04-19.log

Backup the Store

It is not recommended to backup the big data store using regular backup software due to its size . You should follow the instruction on how to create snapshot and export the data to HDFS.

Automatic Backup for monitored device before critical operations

DPOD creates a backup of the monitored device or create a checkpoint before some Web Console operations that changes the monitored device.

The list of this operations appears in this table

This backups can be located at /data/ui/WdpBackups

It is recommended that you should delete periodically these backups or move them to a secured location.

Browser not supported