Common Change Control Rollback
BC Project: FY06-12
Date of Policy: 17 Apr 2006
Last Updated: 29 Sep 2021 (see Revision Log)
This policy defines a Change Control Rollback policy to be followed consistently across participating centers. This policy applies to scheduled system changes that impact the user experience. These scheduled system changes will include a recovery plan, outlined in advance of the change, in case the change is determined to be unsuccessful and rollback to a previous configuration is necessary.
- Each Center will have a Contingency/Recovery Plan for rollback to a previous configuration prior to making hardware or software changes.
- Each center will utilize any applicable Test and Development System or other non-production system to test changes prior to implementation. To the extent feasible, appropriate test methods that provide broad coverage of basic functionality should be used to enhance risk mitigation of adverse consequences of changes.
- HPC Help Desk staff will have access to a description of the scheduled system changes to facilitate identification of problems encountered by users following hardware/software changes.
| Date | Revision |
|---|---|
| 29 Sep 2021 | BC Team Audit - Edited item 2 |
| 12 Apr 2018 | BC Team Audit - Changed "Customer assistance" to "HPC Help Desk" |
| 12 May 2016 | BC Team Audit |
| 13 Mar 2014 | BC Team Audit |
| 23 Mar 2012 | BC Team Audit |
| 05 Nov 2009 | Logging Changes added to Announcing Changes |