Page History

...

...

• Please do not store under the scratch folder data that you cannot recreate because this directory is not backed up and the oldest files on scratch may be deleted at any time to make space for data from new experiments.
• For file cleanup in scratch/  the  last access time will be used for removing old files  (Updated 2024-04).
  For files in results/ and calib/ the age is determined using last modification time of a file (not access time).
  For the xtc and hdf5 files the access time is used (see  xtc/hdf5 cleanup).
  
• The tape archive (xtc, hdf5, usrdaq) and the tape backup (results, home) are fundamentally different:
  • In the tape archive the folders are frozen after the end of the experiments and their contents are stored on tape once. 
  • In the tape backup, the system takes snapshots of the folders as appear at a given time. This implies that files which are deleted from disk are eventually, i.e. after a long enough time, also deleted from tape. 
• Files under xtc and hdf5 can be restored from tape using the file manager tab in the electronic logbook. Files under home can be restored by the user following the instructions below.  To restore data from results send an email to pcds-datamgt-l@slac.stanford.edu.
• For raw data the cleanup operations will affect all files, i.e. all streams and chunks, which make up one run, rather than individual files.
• After 2 years from the end of an experiment we'll remove the experiment from disk. At that point we'll take a snapshot of the results and calib folders and archive them to tape so that we can, upon request, restore an entire experiment back to disk.
• After 10 years we plan to remove the tapes with the archived raw data from the silos and store them in a safe environment.
• The new policy will apply to all experiments, i.e. it will be retroactive, and its deployment date will coincide with the start of Run 14 (August 10^th 2016).
• For questions regrading the data retention and data access send your question to: pcds-datamgt-l@slac.stanford.edu.

...

The purging thresholds might vary depending on the size of a file system and its usage but typically are 5% and 10% (minimum/maximum threshold).  Using these three rules we try to keep runs that are actively analysed analyzed for as long as possible on disk and providing sufficient disk space for the ongoing experiment.

...