IBM DataPower Operations Dashboard v1.0.8.5
Note: A more recent version of DPOD is available. See IBM DPOD Documentation for the latest documentation.
Backup Tasks Status Codes
Here are some common statuses for Backup task executions.
| Status Code | Description |
|---|---|
| WAITING_FOR_PRE_VALIDATION | The task was entered into the execution queue, it was not yet validated or checked, and eventually may not get executed |
| SKIPPED_APIC_DOMAIN | The task will not execute - cannot backup API Connect domain |
| SKIPPED_DEVICE_NOT_AVAILABLE | The task will not execute - the device was not available |
| SKIPPED_NO_DEVICES_MATCHING_PATTERN | The task will not execute - no devices were matching the device pattern requested in the activity |
| DEVICE_NOT_IN_DR_MODE | The task will not execute - Secure Backup requested, but the device was not in DR mode |
| NOT_ENOUGH_FREE_SPACE_ON_DEVICE | The task will not execute - There is not enough free space in the DataPower temp storage (see Configurable Parameters and Settings on how to change the check's threshold) |
| CERT_DOESNT_EXIST_ON_DEVICE | The task will not execute - The certificate specified for Secure Backup was not found on the device |
| SKIPPED_BECAUSE_ERROR_POLICY EXECUTION_CANCELED_BECAUSE_ERROR_POLICY | The task will not execute - Another task failed and specified Error Policy = Fail (See Maintenance Concepts to learn more about Error Policies) |
| PLAN_FAILED_PRE_SCRIPT | The task will not execute - the pre-plan script returned with a return code greater than 0 |
| EXECUTION_CANCELED_BECAUSE_A_DAY_PASSED | The task was not executed - it was automatically canceled because more than 24 hours passed since it started to wait for execution |
| EXECUTION_CANCELED_BECAUSE_MAINTENANCE_WINDOW | The task was not executed - the current time is not within the maintenance window (see Maintenance Concepts for more information about the maintenance window), the maintenance window is checked for all execution types - schedules, ad-hoc via the UI and via the REST API |
| READY_FOR_EXECUTION | Interim status - the task passed all validation, it is queued and will be executed in the next minute, or is waiting for other tasks to finish executing first. |
| SENT_TO_MDB EXECUTION_STARTED EXECUTION_PRE_CHECKS_STARTED | Interim status - the task is executing |
| EXECUTION_PRE_CHECKS_FOUND_QUIESCED_DOMAIN_IN_DEVICE | Task failed - quiesce deice requested (for Secure Backup or Export all domains) but found a domain that was already quiesced |
| EXECUTION_PRE_CHECKS_DOMAIN_IS_ALREADY_QUIESCED | Task failed - quiesce domain requested but the domain was already quiesced |
| EXECUTION_PRE_CHECKS_NFS_OUT_OF_SPACE | Task failed - The specified backup destination is out of space, see Configurable Parameters and Settings on how to check this check threshold |
| EXECUTION_PRE_CHECKS_NFS_DIRECTORY_NOT_FOUND | Task failed - The specified backup destination was not found, see Configurable Parameters and Settings on how to change the destination |
| EXECUTION_PRE_CHECKS_DEVICE_NOT_AVAILABLE | Task failed - the DataPower device was not available |
| EXECUTION_CHECK_MANIFEST_WAITING_FOR_ANOTHER_BACKUP | The task is waiting for another DPOD backup task to finish running on the device |
| EXECUTION_CHECK_MANIFEST_ANOTHER_SECURE_BACKUP_IS_RUNNING_CHECK_DEVICE | Task failed - this may happen if DPOD was restarted while a backup task was running, it seems that the backup task is still executing, but DPOD lost track of it, check the device manually. |
| EXECUTION_WAITING_FOR_PRE_SCRIPT | Waiting for the user pre script to execute |
| EXECUTION_PRE_SCRIPT_ERROR | Task failed - the user pre task script return code was larger than 0, the post task script will still be executed (if specified) |
| EXECUTION_QUIESCE_STARTED | Quiesce domain/device started |
| EXECUTION_QUIESCE_WAITING_FOR_QUIESCE | Waiting for the device or domain to quiesce |
| EXECUTION_QUIESCE_TIMEOUT_OCCURRED | A timeout occurred while waiting for the device or domain to quiesce, the timeout can be configured - see Configurable Parameters and Settings (DPOD will add 3 minutes to the specified timeout) |
| EXECUTION_EXPORT_DOMAIN_PERSISTED_STARTED EXECUTION_EXPORT_DOMAIN_NON_PERSISTED_STARTED | Export-Domain started |
| EXECUTION_EXPORT_DOMAIN_PERSISTED_SOMA_ERROR EXECUTION_EXPORT_DOMAIN_NON_PERSISTED_SOMA_ERROR | Error occurred in the Export-Domain process |
| EXECUTION_EXPORT_DOMAIN_PERSISTED_EMPTY_FILE EXECUTION_EXPORT_DOMAIN_NON_PERSISTED_EMPTY_FILE | The Export Domain process returned an empty file |
| EXECUTION_EXPORT_DOMAIN_PERSISTED_SAVEFILE_EXCEPTION EXECUTION_EXPORT_DOMAIN_NON_PERSISTED_SAVEFILE_EXCEPTION | An error occurred while saving the Export Domain zip file to DPOD |
| EXECUTION_EXPORT_DOMAIN_PERSISTED_DONE EXECUTION_EXPORT_DOMAIN_NON_PERSISTED_DONE | Export-Domain finished successfully |
| EXECUTION_SECURE_BACKUP_STARTED | Secure Backup started |
| EXECUTION_SECURE_BACKUP_UNSUCCESSFUL | Secure Backup returned an error |
| EXECUTION_SECURE_BACKUP_WRONG_FILE_HASH EXECUTION_SECURE_BACKUP_WRONG_FILE_SIZE EXECUTION_SECURE_BACKUP_EMPTY_FILE | Downloading the Secure Backup files from the DataPower temp folder to DPOD failed |
| EXECUTION_UNQUIESCE_STARTED EXECUTION_UNQUIESCE_ON_ERROR_STARTED | Unquiesce domain/device started |
| EXECUTION_UNQUIESCE_WAITING_FOR_UNQUIESCE EXECUTION_UNQUIESCE_ON_ERROR_WAITING_FOR_UNQUIESCE | Waiting for domain/device to unquiesce |
| EXECUTION_UNQUIESCE_TIMEOUT_OCCURRED EXECUTION_UNQUIESCE_ON_ERROR_TIMEOUT_OCCURRED | A timeout occurred while waiting for the device or domain to unquiesce, the timeout can be configured - see Configurable Parameters and Settings (DPOD will add 3 minutes to the specified timeout) |
| EXECUTION_FAILED_WITH_INTERNAL_EXCEPTION | Internal error occurred, see error message for details |
| EXECUTION_FAILED_LONG_RUNNING | The task was running for more than 60 minutes (see Configurable Parameters and Settings on how to change this duration) and was marked as finished, the task may still be executing, manual intervention may be required |
| FAILED_NO_FILES_DOWNLOADED | No errors occurred, but no files downloaded to DPOD - this may happen if DPOD was restarted during the backup process Try to run the backup again |
| SUCCESS | The backup finished successfully |