This page describes how DPOD prepares the execution flow of a backup plan (using tasks) and subsequently - how the tasks themselves are executed.
General execution flow for a backup plan:
After the backup tasks are created, they will start to execute. The following is the general execution flow for a backup task:
Backup tasks will start to execute in the order they were created, which corresponds to the order which the activities were defined. |
When all the plan's tasks completed execution, the post-plan script will be executed (if requested in the plan settings)
The backups will be downloaded and stored in the destination filesystem that was set by the user (see Configurable Parameters and Settings)
For secure backup, the destination path will be:
<user defined path> + /Device-Name/secure-backup/timestamp
E.g. /data/backup/store/QA-device1/secure-backup/2017-06-26-22-48-00-000
For export domain (specific domain), the destination path will be:
<user defined path> + /Device-Name/domain/domain-name/domain-export-timestamp-isPersisted
E.g. /data/backup/store/QA-device1/domain/Domain1/Domain1-export-2017-06-26-22-48-00-000-persisted.zip
For export domain (all domains), the destination path will be:
<user defined path> + /Device-Name/domain/all-domains/all-domains-export-timestamp-isPersisted
E.g. /data/backup/store/QA-device1/all-domains/all-domains-export-2017-06-26-22-48-00-000-nonpersisted.zip
The Plan Details page shows the 40 most recent plan execution results,
The table outlines the following details for each plan execution
| Column Name | Description |
|---|---|
| ID | The Plan Execution ID |
| Start Time | The time the plan entered the execution queue |
| Devices | Number of devices that were supposed to be backed-up. Both failed and successful backups are aggregated. |
| Domains | Number of domains that were supposed to be backed-up. Both failed and successful backups are aggregated. (Note: no domains are aggregated for secure backup and export all domains) |
| Status | The current status of the plan |
| Successful Tasks | Number of backup tasks that completed successfully for this plan execution |
| Failed Tasks | Number of backup tasks that failed for this plan execution |
| Skipped Tasks | Number of backup tasks that did not execute, e.g. because the device was not available |
| Error Message | Plan's Error message (If any) |
Click the status column to drill into the activities execution details page
| Column Name | Description |
|---|---|
| ID | The Activity Execution ID |
| Status Time | The last time the status of the activity changed |
| Device Pattern | The device name or pattern that was used for this backup activity |
| Domain Pattern | The domain name or pattern that was used for this backup activity |
| Action | SECURE_BACKUP or EXPORT_DOMAIN |
| Status | The current status of the activity |
| Successful Tasks | Number of backup tasks that completed successfully for this activity execution |
| Failed Tasks | Number of backup tasks that failed for this activity execution |
| Skipped Tasks | Number of backup tasks that were skipped for this activity execution |
Click the status column to drill into the task execution details page
| Column Name | Description |
|---|---|
| ID | The Task Execution ID |
| Status Time | The last time the status of the task changed |
| Device Name | The Device being backed-up |
| Domain Name | The Domain being backed-up or "all-domains" for Secure Backup/Export Domain for all domains |
| Files D/L | Number of files that were downloaded to the user's storage |
| D/L Errors | Number of download errors |
| Status | The current status of the task |
| Error Message | Task's Error message if any |
Click the status column to drill into the downloaded files details page
The downloaded files page displays information about the backup operation, such as the device firmware version, device type, device build, etc; and a list of all files that were downloaded to the user's storage