{"id":142,"date":"2012-03-01T09:39:59","date_gmt":"2012-03-01T16:39:59","guid":{"rendered":"http:\/\/pln.lanecc.net\/webteam\/?page_id=142"},"modified":"2019-06-03T12:39:37","modified_gmt":"2019-06-03T19:39:37","slug":"server-maintenance-schedule","status":"publish","type":"page","link":"https:\/\/blogs.lanecc.edu\/webteam\/server-maintenance-schedule\/","title":{"rendered":"Maintenance Schedule"},"content":{"rendered":"

What to expect<\/strong><\/p>\n

During any maintenance windows you should expect 0 – 3 short service interruptions. Some updates require processes to be restarted, some require the server to be restarted, and some don’t require anything other than installation. Thus, there might not be any interruption at all, or there might be more than one. It all depends on the updates.<\/p>\n

To be clear, all interruptions should be short. No more than 15 minutes, and seldom more than 5 minutes.<\/p>\n

Since our services run on several different servers, we have to install updates on all those servers. Thus we cannot give an exact time when an interruption might occur. That’s why is a “window” and not a “time”.<\/p>\n

Why we interrupt you<\/h2>\n

Security and reliability. By keeping the software running the services up to date, we limit potential openings for malicious use. The updates also fix bugs that could cause our services to have problems. Basically, by having a few short interruptions during an expected time slot, we prevent future long, unexpected, interruptions. That makes all our lives easier.<\/p>\n

Affected services<\/h2>\n