Rollback
Discussion
Rollback is a recovery operation that reverses the effects of an identified change by restoring the affected subject to a previously valid state.
The affected subject may include:
-
An Image
-
A database
-
Another operational subject
The prior valid state may be identified through:
-
A prior Revision
-
A prior Baseline
-
A recorded configuration
-
A checkpoint
-
A snapshot
-
A prior Image
-
Another identified state representation
Rollback differs from recovery:
-
Rollback restores an identified prior valid state by reversing a change
-
Recovery restores an acceptable operational condition and may use rollback, repair, replacement, restoration, or another mechanism
Rollback differs from restoration:
-
Rollback reverses the effects of an identified change
-
Restoration reconstructs a subject or its information from a preserved representation
Rollback differs from redeployment:
-
Rollback restores an identified prior state
-
Redeployment performs a deployment operation again
Definition
recovery operation that reverses the effects of an identified change by restoring the affected subject to an identified prior valid state
Source
Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
Note
Rollback does not necessarily:
-
Restore external state
-
Restore information modified outside the controlled change
-
Reverse irreversible operations
-
Recover all dependent subjects
-
Occur automatically after a failure
Applicable requirements should identify:
-
The affected subject
-
The change being reversed
-
The prior valid state
-
The rollback initiation condition
-
The rollback result
-
State that cannot be reversed
-
Required Evidence
Example
After an unsuccessful configuration change, Crucible performs Rollback by restoring the affected Infrastructure Environment to the identified Infrastructure Configuration Revision used before the change.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.