Always develop a pre-change (template should be developed) When did we last do a shut-down? A stop/start should be tested without changes Checkpoints need to be identified as problems arise stop or go? – E.g. no shutdown script stop? – Go live checklist Walkthrough all dependencies Ensure everything is tested with the current version of the operation system Test prior to installing into production (done in this case). Test the drivers supplied the correct release of the O/S test – every configuration parameter in advance Additional or spare hardware requirements? Create an outage for planned outage window - e.g. ‘timetable’ Sunday Flag go/no go Identify when to back out if necessary Create for every change - A duplicate environment is required (parallel to try out) need for all – applications - many development environments are not adequate - Communicate to senior management the importance of appropriate equipment need functionality not necessarily the exact same boxes (save – $$$) - IF vendor resources are required, check availability Is the support line adequately during ‘manned’ (weekends?) Pre-arrange contacts to handle’ the situation with ‘stick internal resources 24x7? Notify vendor (s) of any impending changes/outages to ensure we are on their radar if any issues arise e) Escalation process: - Clarify Technical and Mgmt stakeholders: - Contact lists available: cell-phone / wireless-phone / pager, all can be automated - Refer to policies as to who and how the go/no go decision is made – management?
Always develop a pre-change (template should be developed) When did we last do a shut-down? A stop/start should be tested without changes Checkpoints need to be identified as problems arise – stop or go? E.g. no shutdown script – stop? Go live checklist Walkthrough all dependencies Ensure everything is tested with the current version of the operation system Test prior to installing into production (done in this case). Test the drivers supplied the correct release of the O/S – test every configuration parameter in advance Additional or spare hardware requirements? Create an outage ‘timetable’ for planned outage window - e.g. Sunday Flag go/no go Identify when to back out if necessary Create for every change - A duplicate environment is required (parallel to try out) – need for all applications - many development environments are not adequate - Communicate to senior management the importance of appropriate equipment need functionality – not necessarily the exact same boxes (save $$$) - IF vendor resources are required, check availability Is the support line adequately ‘manned’ during (weekends?) Pre-arrange contacts to ‘stick handle’ the situation with internal resources 24x7? Notify vendor (s) of any impending changes/outages to ensure we are on their radar if any issues arise e) Escalation process: - Clarify Technical and Mgmt stakeholders: - Contact lists available: cell-phone / wireless-phone / pager, all can be automated - Refer to policies as to who and how the go/no go decision is made – management?