Storing Data in the Home Filesystems for NAS Compute Resources

All data stored in your home filesystem of any NAS compute system are automatically backed up daily under script control.

If you lose important data from a home filesystem and need to have it restored, please send a request to the NAS Control Room at support@nas.nasa.gov and provide the following information:

• System name
• Your username
• The directory and/or file name(s) that you wish to restore
• The date the data was last touched

Note: Disk space quota limits are imposed on the home filesystems for NAS compute resources. If your data exceeds your disk space quota limits, reduce your usage by deleting unneeded files, copying important files to Lou, or copying them to storage space at your local site and then removing them from your home filesystem to NAS compute resources.

Storing Data in NAS /nobackup Filesystems

Data in any /nobackup filesystem of any NAS system are not backed up by NAS. You are responsible for performing your own backups.

Note: Disk space and inode quota limits are imposed on the Lustre filesystems (/nobackuppX). If your data exceeds the soft quota limits, reduce your usage by removing some files and/or archiving any important data on Lou or on the storage space at your local site.

In addition, when the overall usage of a /nobackup filesystem is near its capacity, files can be deleted by system administrators. Normally, the few top users are sent emails and asked to clean up their disk space.

Using Shift to Copy Files to Lou

The NAS /nobackup filesystems (for example, /nobackup[17-19, 27-29]) are mounted on Lou. As a result, you can log into Lou and copy the files from your /nobackup filesystem to your home directory on Lou.

We recommend using the Shift tool (shiftc), which will automatically utilize the highest performing local file transport. You can also use shiftc if you need to initiate the transfer from a NAS compute front end, such as a PFE. If you need to encrypt the data, even within the NAS enclave, then use the shiftc --encrypt option.