Modifying file access times (using "touch" or any other method) for the purpose of circumventing purge policies may result in the loss of access to the cluster.
Even with the policy in place, if the total usage of /scratch remains above 70%, the top /scratch users will be asked to reduce their /scratch usage.
Please do not directly use the linux cp command to copy data from /scratch to /archive on Prince login nodes. This would create heavy load on /archive. Please use the /share/apps/utils/rsync.sh shell script wrapper to copy data from /scratch to /archive. Inside this script, we limit "rsync" to a bandwidth of no more than 20MB/s, also enable the flag -a for archive mode. In some cases when source and destination are not on the same file systems, and the file systems have different block size settings, the directory sizes might look different. This is fine since rsync makes sure data transfers are successful by verifying checksum. The script wrapper usage is similar to the rsync command, e.g.:
Please only back up what you actually need to retain. Backup the minimum needed to reproduce your work.
If you see warnings about set_acl similar to the following example, please ignore them. /scratch file system is Luster with FACL enabled, /archive is ZFS NetApp file system. The FACL enabled for files in /scratch can not be kept when synchronize to /archive, that’s the warning information about. This also means when you copy the data back from /archive to /scratch, if you want to share with others, you’ll have to reset FACL properly.
rsync: set_acl: sys_acl_set_file(ConsumerSearch, ACL_TYPE_DEFAULT): Operation not supported (95)
sent 269 bytes received 16 bytes 570.00 bytes/sec
total size is 23280 speedup is 81.68
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]