<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Monthly rather than weekly fulls using backup to disk</title>
	<atom:link href="http://nsrd.info/blog/2009/02/05/monthly-rather-than-weekly-fulls-using-backup-to-disk/feed/" rel="self" type="application/rss+xml" />
	<link>http://nsrd.info/blog/2009/02/05/monthly-rather-than-weekly-fulls-using-backup-to-disk/</link>
	<description>EMC NetWorker commentary from a long term backup consultant and theorist</description>
	<lastBuildDate>Mon, 14 May 2012 03:13:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Preston</title>
		<link>http://nsrd.info/blog/2009/02/05/monthly-rather-than-weekly-fulls-using-backup-to-disk/comment-page-1/#comment-56</link>
		<dc:creator>Preston</dc:creator>
		<pubDate>Fri, 08 May 2009 20:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=67#comment-56</guid>
		<description>This style of backup, where a full is done once a month, differentials once a week and incremental backups the remainder of the time is quite common, and quite sensible when backups are unlikely to not be always &quot;online&quot;. I.e., the schedule I&#039;d described was primarily for true disk backup - i.e., backup to ADV_FILE devices where all backups would be online on volumes currently mounted, which allows for massively parallel recoveries. While VTL is disk, because backups will be spread across disparate volumes and there&#039;ll only be a specific number of devices able to read from them, using a combination of full + differential + incremental will allow for a suitably efficient recovery, even though volume load times/etc will be near to nil.</description>
		<content:encoded><![CDATA[<p>This style of backup, where a full is done once a month, differentials once a week and incremental backups the remainder of the time is quite common, and quite sensible when backups are unlikely to not be always &#8220;online&#8221;. I.e., the schedule I&#8217;d described was primarily for true disk backup &#8211; i.e., backup to ADV_FILE devices where all backups would be online on volumes currently mounted, which allows for massively parallel recoveries. While VTL is disk, because backups will be spread across disparate volumes and there&#8217;ll only be a specific number of devices able to read from them, using a combination of full + differential + incremental will allow for a suitably efficient recovery, even though volume load times/etc will be near to nil.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ced</title>
		<link>http://nsrd.info/blog/2009/02/05/monthly-rather-than-weekly-fulls-using-backup-to-disk/comment-page-1/#comment-55</link>
		<dc:creator>ced</dc:creator>
		<pubDate>Fri, 08 May 2009 12:13:45 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=67#comment-55</guid>
		<description>Hi,

we have recently switched to a VTL and i&#039;m considering changing our policy with 1 full per week for one month to 1 full per month and replace the other fulls by differential backup.

So a the end, compared to the current situation, we add one step in the restore process. Restore full then differential then all incremental.

WOuld it make sense for you ?

I&#039;m more confident to do this now that i&#039;ve removed the risk of having corrupted tapes thanks to the raid5 protection of my VTL</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>we have recently switched to a VTL and i&#8217;m considering changing our policy with 1 full per week for one month to 1 full per month and replace the other fulls by differential backup.</p>
<p>So a the end, compared to the current situation, we add one step in the restore process. Restore full then differential then all incremental.</p>
<p>WOuld it make sense for you ?</p>
<p>I&#8217;m more confident to do this now that i&#8217;ve removed the risk of having corrupted tapes thanks to the raid5 protection of my VTL</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: basic

Served from: nsrd.info @ 2012-05-22 12:13:24 -->
