There are several types of components in the DPOD appliance that should be backed up :
Backup software
...
For complete software and configuration backup directory /app
you can use the following command :
| Code Block | ||||
|---|---|---|---|---|
| ||||
tar zcvf DPOD-bck-full.tar.gz /app |
this command will produce archive file of about 1GB.
...
,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> |
-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
| Code Block | ||||
|---|---|---|---|---|
| ||||
tar zcvf DPOD-bck.tar.gz /app/elasticsearch_nodes /app/flume/aggregator_agents /app/flume/balancer_agent /app/flume/syslog_agents /app/flume/wsm_agents /app/hk_keepalive/MonTier-HK-SyslogKeepalive/webapps/MonTier.war /app/hk_keepalive/MonTier-HK-SyslogKeepalive/conf /app/hk_keepalive/MonTier-HK-WsmKeepalive/webapps/MonTier.war /app/hk_keepalive/MonTier-HK-WsmKeepalive/conf /app/hk_resources/MonTier-HK-WdpDeviceResources/webapps/MonTier.war /app/hk_resources/MonTier-HK-WdpDeviceResources/conf /app/hk_resources/MonTier-HK-WdpServiceResources/webapps/MonTier.war /app/hk_resources/MonTier-HK-WdpServiceResources/conf /app/hk_retention/MonTier-HK-ESRetention/webapps/MonTier.war /app/hk_retention/MonTier-HK-ESRetention/conf /app/reports/MonTier-Reports/webapps/MonTier.war /app/reports/MonTier-Reports/conf /app/ui/MonTier-UI/webapps/MonTier.war /app/ui/MonTier-UI/conf /app/scripts |
this command will produce archive file of about 200MB.
Backup user configuration data
...
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 ).
this command will produce archive file of about 200MB.
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 :
| Code Block | ||||
|---|---|---|---|---|
| ||||
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 :
| Code Block | ||||
|---|---|---|---|---|
| ||||
echo "CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE('/tmp/db_backup');" > /tmp/db_backup.txt ij /tmp/db_backup.txtapp_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. |
...