Weekend Maintenance project planning, execution, rollbacks
Published: Saturday, August 22, 2020 written by Andy Flagg
View Count: 91
Keywords: Weekend Maintenance, Preparation, Rollback, Planning
If anyone has ever done weekend schedule maintenance for IT you will know things don't always go as planned.
For me, the maintenance window for some clients starts at 4pm on a Friday, and for others, it is any day between midnight and 3am, it just depends on the business and their processing cycles.
For businesses that run 24/7/365, you are allowed 6 minutes to 6 hours per year for down hard maintenance. It most cases, if you need 5 9's, that 99.999% uptime, then you have redundancy in your IT assets. So even if you bring one system down, another system or more takes over and carry's the load. The N+1 approach is easy for most things. Your centralized SAN data is always needing to be protected and safe and intermediate assets with multi-nodal access need to be serviced and maintained throughout a planned maintenance.
What do you do if things go wrong? Troubleshoot till you figure it out, or rollback and reschedule? It depends. If you have vendor support and that is available, after 20 minutes of being stuck, reach out for assistance regardless and report to stakeholders appropriately.
I have been hands on with large scale planned maintenance projects and it can get dicey sometimes.
It can be fun in the operations center when maintenance is scheduled and executed and plan goes successfully!
more to come...
if you found this article helpful, consider contributing $10, 20 an Andrew Jackson or so..to the author. more authors coming soon
FYI we use paypal or patreon, patreon has 3x the transaction fees, so we don't, not yet.
© 2020 myBlog™ v1.1 All rights reserved. We count views as reads, so let's not over think it.