...
MedicineBow uses the Data (VAST) filesystem configured with a 3 petabytes NVMe system, including advanced block-based data deduplication which will give an expected 6 PB of overall capacity. The cluster has several storage locations available for users and allocated for specific purposes. These storage spaces are described below.
home - /home/<username> $USER/
Space for configuration files and software installations. This file space is intended to be small and always resides on SSDs. The /home file space is snapshotted to recover from accidental deletions.
alias:
$HOME
project - /project/project_name/<username>$USER/
Space to collaborate among project members. Data here is persistent and is exempt from purge policy. The /project file space is snapshotted to recover from accidental deletions.
gscratch - /gscratch/<username> $USER/
Space to perform computing for individual users. Data here is subject to a purge policy defined below. Warning emails will be sent when deletions are expected. No snapshots.
alias:
$SCRATCH
Global Filesystems
Directory Name | Quota (GB) | Snapshots | Backups | Purge Policy | Additional Info |
|---|---|---|---|---|---|
home | Yes | No | No | Always on SSD | |
project | Yes | No | No | Aging Data will move to HDD | |
gscratch | No | No | Yes | Aging Data will move to HDD |
Snapshots vs Backups
Snapshots are a point in time reference of a specific filesystem, that can be referenced after changes are made. The data stays on the same storage system. This data would not be recoverable if there is an issue with the storage system.
...