Page History

Software

ChemIT: OS, the cluster's software "stack", and core applications.
Researchers: Their applications, configurations, scripts, sharing, etc.
Maintenance and updates, including scheduling.

See Roles and responsibilities for clusters managed by ChemIT.

Backup

EZ-Backup service
Local, on head node: Copies and/ or sync'ed
Local, off head node: : Copies and/ or sync'ed
Using SFS, which itself has versioning. And price included backups with EZ-Backup.

Not No all options are mutually exclusive.
If Options vary in what they protect against and their start-up and on-going costs.
Options vary in restores times and end-user vs. mediated restores.
Rule of thumb: The faster you pull unique data off quickly, investing in backup diminishes, the less you have to invest in backups.

Head nodes and compute nodes

Ensure contemporary head node, taking into account it's age, warranty, and ease of replacement with a compute node (unique attributes, including hard drive bays).

Data storage

Storage required for headnode and computational use (short term), including job store and user accounts.
Longer term storage needs, in which a file server may meet needs better. Examples include the SFS service (NFS is an option there).

Storing large amounts of data make restores harder, riskier, and more time-consuming. Storing large amounts of data needing backups will cost more than smaller amounts of data.