IT Employment

General discussion

Gravatar
Locked

Set up strong change request procedures

By debate ·
Does your organization have defined change request procedures? Do you think this documentation is necessary? Do you agree with Mike Talon that the lack of such procedures can damage your disaster recovery plan? Share your comments about establishing strong change request procedures, as discussed in the Oct. 14 e-newsletter.

If you haven't subscribed to our free Disaster Recovery e-newsletter, sign up today!
http://nl.com.com/acct_mgmt.jsp?brand=techrepublic

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
+ Follow this Discussion ·
| Thread display: Collapse - | Expand +

All Comments

gravatar
Collapse -

maintenance vs. repair change control

by harlan.montague In reply to Set up strong change requ ...

Strong change control procedures are great, especially for organizations with multiple data centers. But they can only reasonable be required for planned changes (maintenance and upgrades) not for troubleshooting a production failure. In the case of an unplanned failure the primary concern is getting things running again and there will be no time for pre-approval. You'll have to rely on a post mortem discussion to let everyone know what changes were made after the fact.
This approach opens a loophole to subvert the system. I have seen cases where it was difficult to schedule a maintenance period so techs just wait for the next unplanned failure and do all their maintenance work as part of the repair, without having to get all the approvals.

Back to IT Employment Forum
1 total post (Page 1 of 1)  

Start or search

Related Discussions

Related Forums