-
Notifications
You must be signed in to change notification settings - Fork 4
UsagePolicies
robnagler edited this page Jun 8, 2016
·
2 revisions
We divide disk space into five usage categories in order of increasing volatility:
-
/home
- RAID, backed up nightly and archived permanently in two vaults -
/var/no-archive
- RAID, backed up nightly -
/var/no-backup
- RAID -
/var/tmp
- can be removed at any time -
/tmp
- cleared at boot
Our biggest constraint is on archived data. We compress the data, copy
it to 2.5" disks, and take them to two separate vaults. As of 6/8/16,
we are using 1TB disks, which is sufficient as long as people don't
store experimental data in /home
.
The general policy should be to run simulations in /var/no-archive
.
Our JupyterHub partition is backed up but not archived.
On dev
, don't use all the CPU. It's running production services like
ownCloud and Sirepo.