There are several types of components in the DPOD appliance that should be backed up :
...
Backup Software, Static Configuration and Configuration Database
In order to backup DPOD's software, static configuration and user configuration data (internal DB ) use the configuration database, use /app/scripts/app_backup.sh script located in directory /app/scripts.
The scripts parameters:
Parameter |
Description | |
-t, --backup-type | full: Application files and configuration database (default) |
|
Application files |
configuration database | |
-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 |
|
|
: |
|
|
Invoke the backup command
...
| language | bash |
|---|---|
| theme | RDark |
...
|
...
|
...
|
...
|
...
|
...
|
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)~500MB.
Restore
...
Software, Static
...
Configuration and
...
Configuration
...
Database
In order to restore DPOD's software, static configuration and user configuration data (internal DB ) use the configuration database, use /app/scripts/app_restore.sh script located in directory /app/scripts.
| Note |
|---|
The restore should be executed on a DPOD instance of the same version and deployment profile that the backup was executed on. Restoring a backup file from a different DPOD version or 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) |
Application files |
configuration database | |
-d, --backup-directory | The restore source backup directory. |
|
|
|
|
|
|
|
|
-f, -- |
backup-file-name | The source backup file in the backup directory |
. |
|
...
: |
...
| language | bash |
|---|---|
| theme | RDark |
...
|
...
|
...
|
...
|
...
|
...
example for restoring software, static configuration :
| Code Block | ||||
|---|---|---|---|---|
| ||||
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
| Note |
|---|
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
...
|
Once the restore completes successfully, you may start the system using app-util.sh → Start all (option 1).