<?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: The 7 procedural obligations of backup administrators</title>
	<atom:link href="http://nsrd.info/blog/2009/09/16/7-procedural-obliations/feed/" rel="self" type="application/rss+xml" />
	<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/</link>
	<description>EMC NetWorker commentary from a long term backup consultant and theorist</description>
	<lastBuildDate>Tue, 22 May 2012 21:45:31 +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/09/16/7-procedural-obliations/comment-page-1/#comment-372</link>
		<dc:creator>Preston</dc:creator>
		<pubDate>Tue, 10 Nov 2009 08:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-372</guid>
		<description>I agree with your take, and would suggest that it&#039;s irresponsible of either management or other administrators (application, database, system) who don&#039;t get involved in recovery testing.

The job of a backup administrator should be to facilitate the backup and recovery process, of course, but that role should be one which ensures that the resources and configuration are correct so as to enable the sys/app/db administrators to perform their role.

As I suggest in my book, everyone in a company has a role to play in backup and recovery. While there is a certain amount of familiarity that should be expected of backup administrators with all the backup/recovery operations, the core aspects should be tested and (where possible) handled by the people with the primary responsibility in these areas.</description>
		<content:encoded><![CDATA[<p>I agree with your take, and would suggest that it&#8217;s irresponsible of either management or other administrators (application, database, system) who don&#8217;t get involved in recovery testing.</p>
<p>The job of a backup administrator should be to facilitate the backup and recovery process, of course, but that role should be one which ensures that the resources and configuration are correct so as to enable the sys/app/db administrators to perform their role.</p>
<p>As I suggest in my book, everyone in a company has a role to play in backup and recovery. While there is a certain amount of familiarity that should be expected of backup administrators with all the backup/recovery operations, the core aspects should be tested and (where possible) handled by the people with the primary responsibility in these areas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ced</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-371</link>
		<dc:creator>ced</dc:creator>
		<pubDate>Tue, 10 Nov 2009 04:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-371</guid>
		<description>Hi,

I&#039;ve had an intense discussion with my management today about the responsabilities of my job (being responsible for the backup service)

Do yo consider that a restore test is a task to be perfomed/initiated by a backup administrator or to be initiated by an application owner.

My point of view was that restoring data alone is meaningless. This is not the goal of a restore and as a backup admin, i can&#039;t do more. Only the application owner is able to restore all elements of its application and ensure that the system is restorable from the backup.

What do you think ?

 I ask you the same question when specific modules have been deployed to ensure the consistency like NMM for MOSS. Who is responsible of performing the restore/consistency check ? The backup admin or the moss admin ?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;ve had an intense discussion with my management today about the responsabilities of my job (being responsible for the backup service)</p>
<p>Do yo consider that a restore test is a task to be perfomed/initiated by a backup administrator or to be initiated by an application owner.</p>
<p>My point of view was that restoring data alone is meaningless. This is not the goal of a restore and as a backup admin, i can&#8217;t do more. Only the application owner is able to restore all elements of its application and ensure that the system is restorable from the backup.</p>
<p>What do you think ?</p>
<p> I ask you the same question when specific modules have been deployed to ensure the consistency like NMM for MOSS. Who is responsible of performing the restore/consistency check ? The backup admin or the moss admin ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The 5 Golden Rules of Recovery &#171; NetWorker Blog</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-370</link>
		<dc:creator>The 5 Golden Rules of Recovery &#171; NetWorker Blog</dc:creator>
		<pubDate>Mon, 09 Nov 2009 18:36:10 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-370</guid>
		<description>[...] by Preston    You might think, given that I wrote an article awhile ago about the Procedural Obligations of Backup Administrators that it wouldn&#8217;t be necessary to explicitly spell out any recovery rules – but this [...]</description>
		<content:encoded><![CDATA[<p>[...] by Preston    You might think, given that I wrote an article awhile ago about the Procedural Obligations of Backup Administrators that it wouldn&#8217;t be necessary to explicitly spell out any recovery rules – but this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Backup Obligations : BeginnerPC</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-369</link>
		<dc:creator>Backup Obligations : BeginnerPC</dc:creator>
		<pubDate>Tue, 13 Oct 2009 08:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-369</guid>
		<description>[...] The NetWorker Blog has a great article discussing the 7 Procedural Obligations of a Backup Administrator. [...]</description>
		<content:encoded><![CDATA[<p>[...] The NetWorker Blog has a great article discussing the 7 Procedural Obligations of a Backup Administrator. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Obligations were popular in September &#171; NetWorker Blog</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-368</link>
		<dc:creator>Obligations were popular in September &#171; NetWorker Blog</dc:creator>
		<pubDate>Fri, 02 Oct 2009 12:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-368</guid>
		<description>[...] by Preston    Looking back over September, the most read/visited article was &#8220;The 7 Procedural Obligations of Backup Administrators&#8220;. The goal of the article was to outline what functions should be at the absolute core of any [...]</description>
		<content:encoded><![CDATA[<p>[...] by Preston    Looking back over September, the most read/visited article was &#8220;The 7 Procedural Obligations of Backup Administrators&#8220;. The goal of the article was to outline what functions should be at the absolute core of any [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trickle recoveries aren&#8217;t recoveries &#171; NetWorker Blog</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-367</link>
		<dc:creator>Trickle recoveries aren&#8217;t recoveries &#171; NetWorker Blog</dc:creator>
		<pubDate>Thu, 24 Sep 2009 18:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-367</guid>
		<description>[...] my definition of recoverable in The 7 Procedural Obligations of Backup Administrators, I&#8217;d like to suggest that for most situations, there&#8217;s no such thing as a trickle [...]</description>
		<content:encoded><![CDATA[<p>[...] my definition of recoverable in The 7 Procedural Obligations of Backup Administrators, I&#8217;d like to suggest that for most situations, there&#8217;s no such thing as a trickle [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Backup Obligations &#124; TuxWire : The Linux Blog</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-366</link>
		<dc:creator>Backup Obligations &#124; TuxWire : The Linux Blog</dc:creator>
		<pubDate>Tue, 22 Sep 2009 14:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-366</guid>
		<description>[...] The NetWorker Blog has a great article discussing the 7 Procedural Obligations of a Backup Administrator. [...]</description>
		<content:encoded><![CDATA[<p>[...] The NetWorker Blog has a great article discussing the 7 Procedural Obligations of a Backup Administrator. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preston</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-365</link>
		<dc:creator>Preston</dc:creator>
		<pubDate>Thu, 17 Sep 2009 18:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-365</guid>
		<description>What I&#039;m referring to is the need to have an understanding of both the current capacity forecasts and what sort of growth factors lead into them. This allows a better reaction to changing circumstances. E.g., if you ask the average backup admin, they&#039;ll probably say that yearly data growth is X% - let&#039;s say for the example, 30%. But where does that 30% come from? Is 70% of that from filesystem data growth, 20% from database growth, with a remaining 10% to handle miscellaneous. Having an idea of the breakdown of the growth areas allows a better understanding of the impact of growth spikes - e.g., when other departments are added to the backup environment, or new projects start up that require additional storage.

It also ties in with the budget and purchase cycles, both for CapEx and OpEx for the company. I.e., you need to be across the capacity management such that you can slot in CapEx requests and make OpEx expenditure in a planned, logical way that fits into the fiscal operations of the company. Of course, there&#039;s always the chance to have exceptions, but the goal should be to keep the process as smooth and straight forward as possible.</description>
		<content:encoded><![CDATA[<p>What I&#8217;m referring to is the need to have an understanding of both the current capacity forecasts and what sort of growth factors lead into them. This allows a better reaction to changing circumstances. E.g., if you ask the average backup admin, they&#8217;ll probably say that yearly data growth is X% &#8211; let&#8217;s say for the example, 30%. But where does that 30% come from? Is 70% of that from filesystem data growth, 20% from database growth, with a remaining 10% to handle miscellaneous. Having an idea of the breakdown of the growth areas allows a better understanding of the impact of growth spikes &#8211; e.g., when other departments are added to the backup environment, or new projects start up that require additional storage.</p>
<p>It also ties in with the budget and purchase cycles, both for CapEx and OpEx for the company. I.e., you need to be across the capacity management such that you can slot in CapEx requests and make OpEx expenditure in a planned, logical way that fits into the fiscal operations of the company. Of course, there&#8217;s always the chance to have exceptions, but the goal should be to keep the process as smooth and straight forward as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saint Aardvark</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-364</link>
		<dc:creator>Saint Aardvark</dc:creator>
		<pubDate>Thu, 17 Sep 2009 15:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-364</guid>
		<description>I&#039;m sorry, but I don&#039;t understand what &quot;To be across ongoing capacity management and forecasting requirements&quot;.  I understand (and agree with) the explanation that follows, but I can&#039;t parse the original sentence.  What am I missing?</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry, but I don&#8217;t understand what &#8220;To be across ongoing capacity management and forecasting requirements&#8221;.  I understand (and agree with) the explanation that follows, but I can&#8217;t parse the original sentence.  What am I missing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Backup Obligations &#124; Standalone Sysadmin</title>
		<link>http://nsrd.info/blog/2009/09/16/7-procedural-obliations/comment-page-1/#comment-363</link>
		<dc:creator>Backup Obligations &#124; Standalone Sysadmin</dc:creator>
		<pubDate>Thu, 17 Sep 2009 04:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://nsrd.wordpress.com/?p=803#comment-363</guid>
		<description>[...] The NetWorker Blog has a great article discussing the 7 Procedural Obligations of a Backup Administrator. [...]</description>
		<content:encoded><![CDATA[<p>[...] The NetWorker Blog has a great article discussing the 7 Procedural Obligations of a Backup Administrator. [...]</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-23 10:41:11 -->
