Rollback Scenarios for Data Consistency

Rollback of failed configuration changes ensures data consistency.

Failure on Some Devices During Configuration

When a REST operation succeeds on one device but fails on another, configuration changes are rolled back for both devices. In the following example, the operation fails on one MCT node but succeeds on the other. The whole operation fails and an error message is returned as part of the REST response.

Click to expand in new window
Rollback for failure of one node
When configuration fails on REST request fails on a 2 Node MCT, all configuration changes are rolled back
Note

Note

This process for partial failures is the default. You can change the process to enable partial successes even when one node fails. For more information, see Administered Partial Success.

Failure on All Devices During Configuration

When a REST operation fails on all devices in the request, configuration changes are rolled back for all devices. In this example, the operation fails on both MCT nodes and an error message is returned as part of the REST response.

Click to expand in new window
Rollback for failure of both nodes
The REST operation fails on both MCT nodes

Failure During De-configuration

Rollback does not occur when a REST operation fails during a de-configuration request. The status of configuration items that were not rolled back changes to "delete-pending." You must manually verify and address the status of such items.