Linux/Admin/Regular Scheduled Maintainence
From Notes
Contents |
[edit]
TOPIC: Regular scheduled maintenence downtime
To schedule a regular maintenence time for possible downtime, or reboots. Possible time to reboot servers on a set schedule. Time will be negotiated with all users for 30 to 90 minutes on a particular day, or set annouced schedule.
(Regular schedule could be: Daily, Weekly, Monthly, Quarterly, Yearly ?)
[edit]
PROS
- A scheduled time to do maintaince/updates
- gives the system a chance to clean itself up.
- due orphaned process
- due to memory fragmentation/leaks
- Assures that recent patches, and security releases are correctly loaded.
- Good time to do Kernel updates and patches (via 'YaST/System Update')
- Assures that system can survive an un-scheduled downtime without sys admin intervention.
- Test functionality to make sure critical services are still functional as expected.
- Continuation with WWU Campus standards and practices.
- Closer to methodology that AdmCS and Technical services follows.
- (Note: Eventually they will be running and managing this server)
[edit]
CONS
- "Unnecessary" in some people's opinion.
- Services unavailabe during downtime.
[edit]
Resources and references
- Hydra Downtime, http://www.wwu.edu/depts/admcs/hydyrly.html
- WWU's scheduled downtime, http://www.wwu.edu/depts/admcs/machstat.html
- Down 5 hours a month. (1st Friday):
- Titan, WWIS, myWWU, Arinna, Helios, Balder, RA,
- MyWestern, myWWU,
- Lab Servers, Modem Pools
- Down, Thursdays 8:30 to 7:30am friday
- Hydra, Gecko
- Down, Wednesday mornings, mid - 6 am
- WUF system
- Down 5 hours a month. (1st Friday):
