*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
| Excerpt |
|---|
Clusters and other high performance servers require maintenance. Documented procedures reduce surprises for both enabling scheduled maintenance and emergency work. |
Typical work done during maintenance
Update BIOS (and why it's done...)
Update OS
Update...
Test UPS
Test backups
Test...
Scheduled maintenance procedures
Emergency work procedures
Table of contents
| Table of Contents |
|---|
Scheduled maintenance and upgrades procedures
| Children Display | ||||||
|---|---|---|---|---|---|---|
|
Emergency work procedures
See also
Communication timeline
1) Something bad happens, which was not scheduled.
- Power outages have been the most frequent, recent reasons for downtime
- Please talk to us to discuss cost/ benefits options to reduce power outage impacts, if you haven't already done so. Thank you!
2) ChemIT learns of the emergency situation.
- This often happens by researchers confirming cluster is down, and then emailing ChemIT with evidence.
- ChemIT staff are available M-F, 9am-5 most days. Weekends, evenings, and holidays
3) ChemIT characterizes the problem and develops an initial prognosis.
4) ChemIT notifies group rep (users) of status and prognosis as soon as practicable.
A record (and notes) of Emergency Actions
Cluster or HPC Cluster name | Event date | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ChemIT (C4)Eldor |