Jump to main content

# Understanding task persistence

Active Unisphere configuration tasks persist across a server shutdown and subsequent restart. Inactive configuration tasks do not persist.

When the SMAS server is restarted, it restores all persisted tasks in the task list (based on the user and the storage system).

The status of each restored task is determined by its status before the server shutdown, as detailed in the following table:

Table 1. Task status before and after server shutdown
Task status before server shutdown | Task status post server shutdown
--- | ---
Created
Aborted Validated Running Successfully Run has error Prepare has error Submit has error Define has error Validate has error Done Failed
Prepare in progress Abort in progress Submitted Prepared Defined Pending NA Acquiring lock Lock acquire failed Running During run During preview | Created
Commit in progress | Unknown
| NOTE: Configuration tasks that were in a Commit in progress state before the server shutdown are restored in an Unknown state. This behavior occurs because there is no way for the server to determine whether the task completed successfully. To ensure that you are not committing a duplicate task, you should attempt to determine whether the original task completed successfully, before recommitting it.