Backing out of the Runbook
When an STP with a Backout needs to be in place - this can be cloned from an existing STP or created from scratch. If creating a new STP, remember to tick the Backout checkbox (see below) on the Create STP - Details screen. A Backout can also be added at alater stage via the Edit mode and adding Backout Stages.
Create STP with Backout Plan
Backing Out an STP
For an STP to be backed-out it must first of all be in an Active state.
Only an ICEFLO Deployment Manager can back out an Active STP. Backing Out state is achieved by invoking the Backout button.
When invoking the Backout button you will be asked to raise an Issue as to why you are invoking the Backout.
List Issues
The Issue raised as a result of Backing out the STP can be viewed by invoking the List Issues menu option.
Progressing The Backout
As with the Implementation Phase of an STP, the tasks should be started and stopped to reflect progress through the Backout.
STP - Backed Out
Once all Implementation Phase tasks in the Backout are complete, the STP will progress to a state of either Backed Out (as highlighted above in the RTUP by the red arrow with the red bar) or will progress to a state of Backout Closed if there are no Post-Implementation Phase Backout Tasks. The example above shows there is a post-implementation Backout task to "Reschedule implementation".
STP - Backout Closed
Once all post-imp tasks are complete, the STP progresses to Backout Closed (filing cabinet icon with red outline).
Suspending a Backout Plan
An active Backout plan can also be suspended the same way in which an STP would be suspended by invoking the Suspend button.
The Issue raised as a result of suspending the Backout can be seen in the list issues screen.