<?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: On tape&#8230;</title>
	<atom:link href="http://blog.50micron.com/2009/10/23/on-tape/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.50micron.com/2009/10/23/on-tape/</link>
	<description>Ranting and raving about storage and technology</description>
	<lastBuildDate>Mon, 19 Dec 2011 15:36:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: SANDiety</title>
		<link>http://blog.50micron.com/2009/10/23/on-tape/comment-page-1/#comment-7294</link>
		<dc:creator>SANDiety</dc:creator>
		<pubDate>Thu, 05 Nov 2009 22:11:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.50micron.com/?p=564#comment-7294</guid>
		<description>In our backup environment, datadomain + lto-4 in a &#039;blended&#039; solution is working very well. For 90% of our hosts, backups that have a retention of  1 year go to disk. Just a quick look: our oracle data (rman fulls bi-weekly + more or less hourly archlogs on deduped-disk) = 
Total files: 29,176;  bytes/storage_used: 6.9
       Original Bytes:   47,634,887,009,428
  Globally Compressed:   27,944,163,293,266
   Locally Compressed:    6,768,282,021,668 (47T to compressed to 6.7T)
            

vmware (vmdk files/wintel os&#039;s)...
Total files: 5,361;  bytes/storage_used: 24.1
       Original Bytes:   19,759,665,225,250
  Globally Compressed:    1,625,616,555,655
   Locally Compressed:      816,176,984,187 (19T to 800GB)
           

We do have monthly full requirements that are greater than 5 years - so we simply put those to tape directly.

Some of the business &#039;sell&#039; for us was:
1) Tapes have a lower level of reliability for use as disaster recovery. Once ejected, they SHOULD work...but I&#039;m not betting on &#039;should&#039;. Have has too many go bad when needed over the years.
2) Any Oracle database can be recovered point in time going back 30 days, without having to wait for a tape recall. Huge for us. Also, ever notice how DBA&#039;s want/love their nightly fulls? Ever ask them why? Usually, the answer is tape related...if theres a problem with a tape that happens to be holding 2 day&#039;s of arch logs...the full is all they have. Disk changes that, or more specifically, redundant disks.
3) Effort. VTL or using a dedupe array is as simple as it gets. Backup runs, no tapes to rotate, no drives to clean, no tape loss worries, no bad tapes getting hung in the drive, no middle of the night robot gripper/hand failure...it&#039;s great.
4) Backup success rates are important. We regularly get 100% nightly backups (~12TB nightly). With failures usually related to client side issues .


Anyway - as for the annual maintenance point - I guess it depends on if the annual maintenance on a disk array is worth more to a company, than a higher rate of successful backups. When we were tape only, our policy effectively stated &quot;if we missed a night, we had to guarantee the next&quot;. While we still have this policy in place...I don&#039;t worry about the next night nearly as much.

just my 2 cents...</description>
		<content:encoded><![CDATA[<p>In our backup environment, datadomain + lto-4 in a &#8216;blended&#8217; solution is working very well. For 90% of our hosts, backups that have a retention of  1 year go to disk. Just a quick look: our oracle data (rman fulls bi-weekly + more or less hourly archlogs on deduped-disk) =<br />
Total files: 29,176;  bytes/storage_used: 6.9<br />
       Original Bytes:   47,634,887,009,428<br />
  Globally Compressed:   27,944,163,293,266<br />
   Locally Compressed:    6,768,282,021,668 (47T to compressed to 6.7T)</p>
<p>vmware (vmdk files/wintel os&#8217;s)&#8230;<br />
Total files: 5,361;  bytes/storage_used: 24.1<br />
       Original Bytes:   19,759,665,225,250<br />
  Globally Compressed:    1,625,616,555,655<br />
   Locally Compressed:      816,176,984,187 (19T to 800GB)</p>
<p>We do have monthly full requirements that are greater than 5 years &#8211; so we simply put those to tape directly.</p>
<p>Some of the business &#8216;sell&#8217; for us was:<br />
1) Tapes have a lower level of reliability for use as disaster recovery. Once ejected, they SHOULD work&#8230;but I&#8217;m not betting on &#8216;should&#8217;. Have has too many go bad when needed over the years.<br />
2) Any Oracle database can be recovered point in time going back 30 days, without having to wait for a tape recall. Huge for us. Also, ever notice how DBA&#8217;s want/love their nightly fulls? Ever ask them why? Usually, the answer is tape related&#8230;if theres a problem with a tape that happens to be holding 2 day&#8217;s of arch logs&#8230;the full is all they have. Disk changes that, or more specifically, redundant disks.<br />
3) Effort. VTL or using a dedupe array is as simple as it gets. Backup runs, no tapes to rotate, no drives to clean, no tape loss worries, no bad tapes getting hung in the drive, no middle of the night robot gripper/hand failure&#8230;it&#8217;s great.<br />
4) Backup success rates are important. We regularly get 100% nightly backups (~12TB nightly). With failures usually related to client side issues .</p>
<p>Anyway &#8211; as for the annual maintenance point &#8211; I guess it depends on if the annual maintenance on a disk array is worth more to a company, than a higher rate of successful backups. When we were tape only, our policy effectively stated &#8220;if we missed a night, we had to guarantee the next&#8221;. While we still have this policy in place&#8230;I don&#8217;t worry about the next night nearly as much.</p>
<p>just my 2 cents&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sto Rage</title>
		<link>http://blog.50micron.com/2009/10/23/on-tape/comment-page-1/#comment-7292</link>
		<dc:creator>Sto Rage</dc:creator>
		<pubDate>Thu, 05 Nov 2009 04:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.50micron.com/?p=564#comment-7292</guid>
		<description>Have you looked at COPAN Systems? They have a unique MAID system that scales well. We have been using it for all of our Archive/Nearline needs. We now have a few 100 TB on them. Great value. 
http://www.copansystems.com/</description>
		<content:encoded><![CDATA[<p>Have you looked at COPAN Systems? They have a unique MAID system that scales well. We have been using it for all of our Archive/Nearline needs. We now have a few 100 TB on them. Great value.<br />
<a href="http://www.copansystems.com/" rel="nofollow">http://www.copansystems.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://blog.50micron.com/2009/10/23/on-tape/comment-page-1/#comment-7290</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Thu, 05 Nov 2009 03:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.50micron.com/?p=564#comment-7290</guid>
		<description>He&#039;s using it as only-copy-production data.  Not my idea of a good time.  I would *NEVER* put only copy data in anything portable for the sole purpose that if it can be moved or carried it can be dropped, and tapes are just as vulnerable as disk to drop-faults.</description>
		<content:encoded><![CDATA[<p>He&#8217;s using it as only-copy-production data.  Not my idea of a good time.  I would *NEVER* put only copy data in anything portable for the sole purpose that if it can be moved or carried it can be dropped, and tapes are just as vulnerable as disk to drop-faults.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: william bishop</title>
		<link>http://blog.50micron.com/2009/10/23/on-tape/comment-page-1/#comment-7234</link>
		<dc:creator>william bishop</dc:creator>
		<pubDate>Mon, 26 Oct 2009 23:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.50micron.com/?p=564#comment-7234</guid>
		<description>I mean that I eat through that amount of storage per year. And in 4 years (at the outside), I&#039;m going to have to replace those nodes to keep up.

You don&#039;t need to have multiple tape silos...you add tape heads. It sounds like he paid WAY too much.

For nearline, yes, tape would not be adequate for some functions, I agree there....as I also said earlier, 1st target disk, second target tape.

If there is no penalty for latency on retrieval, tape might work nearline...I must have missed where you were telling us he was using it thusly.</description>
		<content:encoded><![CDATA[<p>I mean that I eat through that amount of storage per year. And in 4 years (at the outside), I&#8217;m going to have to replace those nodes to keep up.</p>
<p>You don&#8217;t need to have multiple tape silos&#8230;you add tape heads. It sounds like he paid WAY too much.</p>
<p>For nearline, yes, tape would not be adequate for some functions, I agree there&#8230;.as I also said earlier, 1st target disk, second target tape.</p>
<p>If there is no penalty for latency on retrieval, tape might work nearline&#8230;I must have missed where you were telling us he was using it thusly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://blog.50micron.com/2009/10/23/on-tape/comment-page-1/#comment-7226</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Mon, 26 Oct 2009 00:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.50micron.com/?p=564#comment-7226</guid>
		<description>Ok, a few points.

1. You&#039;re talking about backup, and I conceded the point that for backup purposes tape is the best way to go.  Highly portable, extremely cheap.

2. What I&#039;m talking about is using tape for &quot;nearline&quot; or &quot;online&quot; storage.  Files that are being recalled on a regular basis, that need to be done so in a timely fashion.  My customer just bought two more of those giant StorageTek libraries, you know, the ones bigger than my first apartment...for storage that is *NOT* backup.  This is archival storage, nearline.

Now the problem with this is, the $2,000 figure you quoted doesn&#039;t include the cost of the hardware, and when you start throwing multiple silos at a solution disk QUICKLY becomes a more viable alternative to tape.  These silos are at least a million a piece, not including maintenance.  I don&#039;t know the money end of it but I&#039;m pretty sure you can drop a Petabyte of CX4 storage on the floor for about that much, let alone cheaper Atmos or Centerra options.

Secondly, I want to know where you get the idea that Centerra storage is only good for a year - I&#039;ve got two running right now that have been going strong since 2004.

Now my quantum rep told me that a tape is good for about 5 years.  That means that even if you put a tape in a climate controlled environment after that point you run the risk of data loss if you don&#039;t read the tape and copy it to new media.  Start talking hundreds of terabytes to petabytes and you start requiring a seperate environment JUST to handle duplication of your data.

I stand by my original point.  Tape is WONDERFUL for backup.  For archival  and &quot;nearline&quot; storage it&#039;s just not up to the task.</description>
		<content:encoded><![CDATA[<p>Ok, a few points.</p>
<p>1. You&#8217;re talking about backup, and I conceded the point that for backup purposes tape is the best way to go.  Highly portable, extremely cheap.</p>
<p>2. What I&#8217;m talking about is using tape for &#8220;nearline&#8221; or &#8220;online&#8221; storage.  Files that are being recalled on a regular basis, that need to be done so in a timely fashion.  My customer just bought two more of those giant StorageTek libraries, you know, the ones bigger than my first apartment&#8230;for storage that is *NOT* backup.  This is archival storage, nearline.</p>
<p>Now the problem with this is, the $2,000 figure you quoted doesn&#8217;t include the cost of the hardware, and when you start throwing multiple silos at a solution disk QUICKLY becomes a more viable alternative to tape.  These silos are at least a million a piece, not including maintenance.  I don&#8217;t know the money end of it but I&#8217;m pretty sure you can drop a Petabyte of CX4 storage on the floor for about that much, let alone cheaper Atmos or Centerra options.</p>
<p>Secondly, I want to know where you get the idea that Centerra storage is only good for a year &#8211; I&#8217;ve got two running right now that have been going strong since 2004.</p>
<p>Now my quantum rep told me that a tape is good for about 5 years.  That means that even if you put a tape in a climate controlled environment after that point you run the risk of data loss if you don&#8217;t read the tape and copy it to new media.  Start talking hundreds of terabytes to petabytes and you start requiring a seperate environment JUST to handle duplication of your data.</p>
<p>I stand by my original point.  Tape is WONDERFUL for backup.  For archival  and &#8220;nearline&#8221; storage it&#8217;s just not up to the task.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: william bishop</title>
		<link>http://blog.50micron.com/2009/10/23/on-tape/comment-page-1/#comment-7225</link>
		<dc:creator>william bishop</dc:creator>
		<pubDate>Sun, 25 Oct 2009 18:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.50micron.com/?p=564#comment-7225</guid>
		<description>Additionally, does the tape cost me a FORTUNE in annual maitenance? Nope. When I pull the tape back scratch to move the data to a denser medium, does it have the same capital cost as buying newer denser nodes? Nope. I&#039;m failing to see where disk is even in the running. If I need a second copy for ultra reliability, yep, I&#039;ll keep that first centera. But honestly, tape would be my second target</description>
		<content:encoded><![CDATA[<p>Additionally, does the tape cost me a FORTUNE in annual maitenance? Nope. When I pull the tape back scratch to move the data to a denser medium, does it have the same capital cost as buying newer denser nodes? Nope. I&#8217;m failing to see where disk is even in the running. If I need a second copy for ultra reliability, yep, I&#8217;ll keep that first centera. But honestly, tape would be my second target</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: william bishop</title>
		<link>http://blog.50micron.com/2009/10/23/on-tape/comment-page-1/#comment-7224</link>
		<dc:creator>william bishop</dc:creator>
		<pubDate>Sun, 25 Oct 2009 18:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.50micron.com/?p=564#comment-7224</guid>
		<description>Again, I&#039;ll use a personal example. TSM does dedupe, so you&#039;ve no longer got that hanging for you. My tape library does 300meg a second, and put&#039;s 2 TB on a tape.

Now, let&#039;s think about this. The 20+T of centera I just bought costs approx 80,000 dollars and will last me 1 year. I can do the same on tape for 2,000 dollars. Can I put the centera in a car and move it someplace else for restoration? Nope. Does tape have a constant power draw? Nope. Does a tape lose nodes? Nope. Does it cost me an additional 80k to have another copy? Nope. If I already have copy one on spinning disk, then why, in the name of all that is holy, should I pay 40x the cost for a copy that can be done for far, far less? And can be restored on pretty much any compatible tape drive?</description>
		<content:encoded><![CDATA[<p>Again, I&#8217;ll use a personal example. TSM does dedupe, so you&#8217;ve no longer got that hanging for you. My tape library does 300meg a second, and put&#8217;s 2 TB on a tape.</p>
<p>Now, let&#8217;s think about this. The 20+T of centera I just bought costs approx 80,000 dollars and will last me 1 year. I can do the same on tape for 2,000 dollars. Can I put the centera in a car and move it someplace else for restoration? Nope. Does tape have a constant power draw? Nope. Does a tape lose nodes? Nope. Does it cost me an additional 80k to have another copy? Nope. If I already have copy one on spinning disk, then why, in the name of all that is holy, should I pay 40x the cost for a copy that can be done for far, far less? And can be restored on pretty much any compatible tape drive?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

