ResearchStorage

From UABgrid Documentation
(Difference between revisions)
Jump to: navigation, search
(How to use it: fix bullet formatting)
(What about backups?: Improve the wording and formatting to highlight policy)
Line 33: Line 33:
 
== What about backups? ==
 
== What about backups? ==
  
There is no central back up process on the cluster. This rule includes the new Research Storage containers.
+
=== No Backups! ===
 +
There is no central back up process on the cluster. Each user is responsible for backing up their own data. If you are not managing a back up process for data on the cluster then you do not have any back ups.
  
Each user is responsible for backing up their own data!
+
''This rule includes the new Research Storage containers.''
 
+
If you are not managing a back up process for data on the cluster then you do not have any back ups.
+
  
 
Please understand we do not say this out of malice or a lack of concern for your data.  Central backup processes are inherently ignorant and must assume all files are important.  This is done at the very real expense of keeping multiple copies of data.  In the context of large scale data sets which are typical of our HPC environment, this would amount to 100's of terabytes of data.  Duplicating the footprint of data for which we are already busting at the seams to support a single copy.
 
Please understand we do not say this out of malice or a lack of concern for your data.  Central backup processes are inherently ignorant and must assume all files are important.  This is done at the very real expense of keeping multiple copies of data.  In the context of large scale data sets which are typical of our HPC environment, this would amount to 100's of terabytes of data.  Duplicating the footprint of data for which we are already busting at the seams to support a single copy.
Line 43: Line 42:
 
It is much better for individuals, teams, or labs and their technical support staff critical data and ensure it is backed up.
 
It is much better for individuals, teams, or labs and their technical support staff critical data and ensure it is backed up.
  
 +
=== How to Backup ===
 
We understand this process can be difficult, especially if you are your own technical support staff.
 
We understand this process can be difficult, especially if you are your own technical support staff.
  
 
To that end, we have a new backup service available that leverages CrashPlan, a popular commercial backup product that will help you easily back up your data on your laptop or in your lab.
 
To that end, we have a new backup service available that leverages CrashPlan, a popular commercial backup product that will help you easily back up your data on your laptop or in your lab.
  
Please contact us if you are interested in using CrashPlan to fulfill your responsibilities for backing up your data.
+
Please contact us if you are interested in using CrashPlan to fulfil your responsibilities for backing up your own data.

Revision as of 15:09, 16 April 2014

Research Storage provides versatile containers for your data sets. The containers include dedicated space available on the Cheaha HPC platform.

Contents

How to get it

Once you log in to Cheaha, you can access your default 1TB storage container here:

 cd /rstore/user/$USER/default

You can check to see how much storage you have used in your container with the command:

 df /rstore/user/$USER/default

How to use it

You can use this storage in any way that you find useful to assist you with your HPC work flows on Cheaha.

But, you should still follow good high performance compute work flow recommendations and stage data sets $USER_SCRATCH during your job runs, especially if those data sets are heavily accessed or modified as part of your job operations.

One near term use would be to safely preserve important data in your $USER_SCRATCH so that it is not destroyed by the upcoming scratch file system rebuild during the May 3-10 cluster service window.

Follow these steps:

  1. Remove any data from $USER_SCRATCH that you no longer use or want
  2. Copy your remaining important data to your default container:
  rsync -a --stats $USER_SCRATCH/ /rstore/user/$USER/default/scratch

In general, a good use this storage for keeping larger data sets on the cluster longer than the lifetime of your active computations and for stuff that is too big to fit in your home directory.

How to get more

You can buy any amount of additional storage at a rate of $0.38/Gigabyte/year. That's $395/Terabyte/year. All we need to know is how much storage you want, for how long, and an account number. UAB IT will bill you monthly for the storage you consume

What about backups?

No Backups!

There is no central back up process on the cluster. Each user is responsible for backing up their own data. If you are not managing a back up process for data on the cluster then you do not have any back ups.

This rule includes the new Research Storage containers.

Please understand we do not say this out of malice or a lack of concern for your data. Central backup processes are inherently ignorant and must assume all files are important. This is done at the very real expense of keeping multiple copies of data. In the context of large scale data sets which are typical of our HPC environment, this would amount to 100's of terabytes of data. Duplicating the footprint of data for which we are already busting at the seams to support a single copy.

It is much better for individuals, teams, or labs and their technical support staff critical data and ensure it is backed up.

How to Backup

We understand this process can be difficult, especially if you are your own technical support staff.

To that end, we have a new backup service available that leverages CrashPlan, a popular commercial backup product that will help you easily back up your data on your laptop or in your lab.

Please contact us if you are interested in using CrashPlan to fulfil your responsibilities for backing up your own data.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox