<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.uabgrid.uab.edu/w/index.php?action=history&amp;feed=atom&amp;title=Template%3AClusterDataBackup</id>
	<title>Template:ClusterDataBackup - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://docs.uabgrid.uab.edu/w/index.php?action=history&amp;feed=atom&amp;title=Template%3AClusterDataBackup"/>
	<link rel="alternate" type="text/html" href="https://docs.uabgrid.uab.edu/w/index.php?title=Template:ClusterDataBackup&amp;action=history"/>
	<updated>2026-05-30T15:33:41Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.38.2</generator>
	<entry>
		<id>https://docs.uabgrid.uab.edu/w/index.php?title=Template:ClusterDataBackup&amp;diff=5936&amp;oldid=prev</id>
		<title>Jpr@uab.edu: Create template for data backup policy and guidance</title>
		<link rel="alternate" type="text/html" href="https://docs.uabgrid.uab.edu/w/index.php?title=Template:ClusterDataBackup&amp;diff=5936&amp;oldid=prev"/>
		<updated>2019-10-03T20:20:57Z</updated>

		<summary type="html">&lt;p&gt;Create template for data backup policy and guidance&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;There is no automatic back up of any user data on the cluster in home, data, or scratch.  At this time, all user data back up processes are defined and managed by each user and/or lab. Given that data backup demands vary widely between different users, groups, and research domains, this approach enables those who are most familiar with the data to make appropriate decisions based on their specific needs.&lt;br /&gt;
&lt;br /&gt;
For example, if a group is working with a large shared data set that is a local copy of a data set maintained authoritatively at a national data bank, maintaining a local backup is unlikely to be a productive use of limited storage resources, since this data could potentially be restored from the authoritative source.  If, however, you are maintaining a unique source of data of which yours is the only copy, then maintaining a backup is critical if you value that data set. It's worth noting that while this &amp;quot;uniqueness&amp;quot; criteria may not apply to the data you analyze, it may readily apply to the codes that define your analysis pipelines.&lt;br /&gt;
&lt;br /&gt;
An often recommended backup policy is the 3-2-1 rule: maintain three copies of data, on two different media, with one copy off-site. You can [https://www.backblaze.com/blog/the-3-2-1-backup-strategy/ read more about the 3-2-1 rule here]. In the case of your application codes, using revision control tools during development provides an easy way to maintain a second copy, makes for a good software development process, and can help achieve reproducible research goals.&lt;br /&gt;
&lt;br /&gt;
Please review the [https://www.uab.edu/it/home/data-storage data storage options provided by UAB IT] for maintaining copies of your data. In choosing among these options, you should also [https://www.uab.edu/it/home/data-classification be aware of UAB's data classification rules and requirements for security requirements for sensitive and restricted] data storage.  Given the importance of backup, Research Computing continues to explore options to facilitate data backup workflows from the cluster.  Please [mailto:support@listserv.uab.edu contact us] if you have questions or would like to discuss specific data backup scenarios.&lt;br /&gt;
&lt;br /&gt;
A good guide for thinking about your backup strategy might be: &amp;quot;If you aren't managing a data back up process, then you have no backup data.&amp;quot;&lt;/div&gt;</summary>
		<author><name>Jpr@uab.edu</name></author>
	</entry>
</feed>