<?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 for Integrated Data Storage</title>
	<atom:link href="http://www.integrateddatastorage.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.integrateddatastorage.com</link>
	<description>Your complete data storage solutions provider.</description>
	<lastBuildDate>Tue, 21 Feb 2012 02:35:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Tape Sucks: Avamar 6.0 Version #tapesucksmoveon by mradamk</title>
		<link>http://www.integrateddatastorage.com/blog/2011/04/28/tape-sucks-avamar-6-0-version-tapesucksmoveon/#comment-5451</link>
		<dc:creator>mradamk</dc:creator>
		<pubDate>Tue, 21 Feb 2012 02:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=1978#comment-5451</guid>
		<description>Don&#039;t be so hard on the staging approach, there are customers using ATO who are achieving the equivilant of 15TB/24 hours all the way to tape using x2 staging servers and with 8 TB&#039;s of staging disk. This gives them file level recovery directly from tape in an almost buisness as usual manner and with no direct dependencies on Avamar itself when recovering from tape.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t be so hard on the staging approach, there are customers using ATO who are achieving the equivilant of 15TB/24 hours all the way to tape using x2 staging servers and with 8 TB&#8217;s of staging disk. This gives them file level recovery directly from tape in an almost buisness as usual manner and with no direct dependencies on Avamar itself when recovering from tape.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on To Snapshot Or Not To Snapshot? That Is The Question When Leveraging VNX Unified File Systems by Eric Hagstrom</title>
		<link>http://www.integrateddatastorage.com/blog/2012/01/10/snapshot-or-not-to-snapshot-that-is-the-question-when-leveraging-vnx-unified-file-systems/#comment-5321</link>
		<dc:creator>Eric Hagstrom</dc:creator>
		<pubDate>Tue, 14 Feb 2012 15:10:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=4096#comment-5321</guid>
		<description>I think as a first line of restore for user file data, snapshots are a great tool to have in your bag. But remember, that a snapshot relies on the original source data to be  useful. The only way to truly protect a file, database, or volume is to create a point in time copy to an independent device. From &quot;Using Snapsure&quot; manual, A checkpoint is not intended to be a mirror, disaster recovery, or high-availability tool. It is partially derived from realtime PFS data. A checkpoint might become inaccessible or unreadable if the associated PFS is inaccessible. Only a PFS and its checkpoints saved to a tape or an alternate storage location can be used for disaster recovery.&quot; I agree with you that snapshots should be a part of your strategy for data protection, but only a portion.</description>
		<content:encoded><![CDATA[<p>I think as a first line of restore for user file data, snapshots are a great tool to have in your bag. But remember, that a snapshot relies on the original source data to be  useful. The only way to truly protect a file, database, or volume is to create a point in time copy to an independent device. From &#8220;Using Snapsure&#8221; manual, A checkpoint is not intended to be a mirror, disaster recovery, or high-availability tool. It is partially derived from realtime PFS data. A checkpoint might become inaccessible or unreadable if the associated PFS is inaccessible. Only a PFS and its checkpoints saved to a tape or an alternate storage location can be used for disaster recovery.&#8221; I agree with you that snapshots should be a part of your strategy for data protection, but only a portion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cisco UCS: On Trial in the Court of Public Opinion (and the Verdict Is?) by Michael</title>
		<link>http://www.integrateddatastorage.com/blog/2011/06/27/cisco-ucs-on-trial-in-the-court-of-public-opinion-and-the-verdict-is/#comment-5272</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 13 Feb 2012 12:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=2541#comment-5272</guid>
		<description>Unified Fabric, Service Profiles, Extended Memory technology, a virtual chassis architecture, very extensive networking features and an XML. </description>
		<content:encoded><![CDATA[<p>Unified Fabric, Service Profiles, Extended Memory technology, a virtual chassis architecture, very extensive networking features and an XML.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cisco UCS: On Trial in the Court of Public Opinion (and the Verdict Is?) by David Langley</title>
		<link>http://www.integrateddatastorage.com/blog/2011/06/27/cisco-ucs-on-trial-in-the-court-of-public-opinion-and-the-verdict-is/#comment-4915</link>
		<dc:creator>David Langley</dc:creator>
		<pubDate>Wed, 25 Jan 2012 17:24:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=2541#comment-4915</guid>
		<description>Adam – thanks for the rebuttal.

I guess when I say unified I mean unified in management, not unified in faceplates. HP has many different interfaces to manage the contents of a single blade chassis – let alone any storage that falls underneath it. HP blades are just servers. HP switches are just switches. The fact that they are in the same chassis is coincidental and simply a matter of location, not management or functionality. In the case of the UCS, the fabric interconnect houses the management console as well as the profile of the server, and the server blade hardware interacts with the management logic in the switch to acquire it’s outwardly facing properties such as MAC address and BIOS settings. If a particular blade is removed, it’s replacement takes on the identity of the prior blade all the way down to those properties normally associated with the hardware itself. This is increasingly important as virtual environments have increasingly complex network structures where standardization is key.

From this, I see the UCS memory, CPU, and network unify into a dynamic, centrally managed entity. I would extend this paradigm identification to the chassis servers as well that integrate into the UCS framework to be centrally managed with the blades. I fully suspect that Dell and HP could do the same thing but the fact is they haven’t and they treat their blade systems as if they were typical server/switch facilities, just in a smaller package.

In terms of workloads, yes, UCS is aimed at the x86 market for sure. I guess Cisco just has a bad habit of developing to what the market is asking for. While I have nothing but respect for the robust nature of UNIX, iSeries, Mainframe etc. the market is generally moving away (dated but makes my point: http://www.computerworld.com/s/article/9177445/Unix_server_sales_sink_IDC_cites_a_perfect_storm). X86 hardware augmented by improved platforms such as VMware provide excellent reliability for all but the most highly availability demanding workloads at a fraction of the costs. So, no, the UCS is not a replacement for a mainframe, but the UCS is not trying to be.

In terms of oversubscription, yes, they can be oversubscribed, but the 10G converged networking platform is a major boon to virtual environments that have historically had to dedicate 4 to 7 connections to get the job done and even then the links were not balanced to ensure they actually benefitted fully from all that connectivity. New backplanes in the Nexus line are evolving very quickly which again, could certainly be oversubscribed, but what an evolution. Beyond the bandwidth we must also recognize the flexibility that the virtual interface card (VIC) has brought as well, where a single controller card can emulate over a hundred different cards to provide logical traffic isolation. Yes, great companies like Xsigo do this and more with switching and cards but Cisco has integrated this technology into the UCS as a whole, into the single management interface, and into the concept of the server profile.

Ah yes, margins.

I get the sense you believe Cisco sells at list price. Uhhhh, no…

I have to concede that the UCS sale has a lower margin than a Catalyst 6500 sale. However, the switching market has long been commoditized and servers are the very icon of IT commoditization. Speaking from experience I have seen many true HP blade diehards admit that they see a benefit in the UCS management capabilities and have made the switch. If you purchase a UCS, you are purchasing the fabric interconnects and also the fabric extenders, so when Cisco sells servers, they sell two other major elements of their portfolio and therefore increases the revenue to the company from a “server” purchase. I will happily also concede the per sale margin on the UCS may be lower than other larger Cisco product sales, but the net is that UCS is bringing Cisco a bigger footprint in the data center and they are not losing money doing it. To continue to grow as a company with such immense market penetration in the route switch space they can either innovate their products are or widen the offering and between Nexus and UCS. Cisco is doing both.

No cost? It’s true, somewhere there is a cost. But I did get my cell phone for free if someone else was going to give me the same contract at the same price without a phone? So if Cisco gives me a great management interface with the UCS at the same price for another manufacturer’s blade center that does not (or cannot) provide said interface, I’ll call it free.

I assure you, I do not believe that the UCS is the silver bullet for server/network integration, but I really like where Cisco went with it – especially for the virtualization workspace. If the UCS spurs the likes of HP and Dell to innovate and unify their products, then all the better. But I strongly believe that the UCS is different than anything else in the server/switching space, and it is helping Cisco continue to grow and thrive as a company.

- David</description>
		<content:encoded><![CDATA[<p>Adam – thanks for the rebuttal.</p>
<p>I guess when I say unified I mean unified in management, not unified in faceplates. HP has many different interfaces to manage the contents of a single blade chassis – let alone any storage that falls underneath it. HP blades are just servers. HP switches are just switches. The fact that they are in the same chassis is coincidental and simply a matter of location, not management or functionality. In the case of the UCS, the fabric interconnect houses the management console as well as the profile of the server, and the server blade hardware interacts with the management logic in the switch to acquire it’s outwardly facing properties such as MAC address and BIOS settings. If a particular blade is removed, it’s replacement takes on the identity of the prior blade all the way down to those properties normally associated with the hardware itself. This is increasingly important as virtual environments have increasingly complex network structures where standardization is key.</p>
<p>From this, I see the UCS memory, CPU, and network unify into a dynamic, centrally managed entity. I would extend this paradigm identification to the chassis servers as well that integrate into the UCS framework to be centrally managed with the blades. I fully suspect that Dell and HP could do the same thing but the fact is they haven’t and they treat their blade systems as if they were typical server/switch facilities, just in a smaller package.</p>
<p>In terms of workloads, yes, UCS is aimed at the x86 market for sure. I guess Cisco just has a bad habit of developing to what the market is asking for. While I have nothing but respect for the robust nature of UNIX, iSeries, Mainframe etc. the market is generally moving away (dated but makes my point: <a href="http://www.computerworld.com/s/article/9177445/Unix_server_sales_sink_IDC_cites_a_perfect_storm" rel="nofollow">http://www.computerworld.com/s/article/9177445/Unix_server_sales_sink_IDC_cites_a_perfect_storm</a>). X86 hardware augmented by improved platforms such as VMware provide excellent reliability for all but the most highly availability demanding workloads at a fraction of the costs. So, no, the UCS is not a replacement for a mainframe, but the UCS is not trying to be.</p>
<p>In terms of oversubscription, yes, they can be oversubscribed, but the 10G converged networking platform is a major boon to virtual environments that have historically had to dedicate 4 to 7 connections to get the job done and even then the links were not balanced to ensure they actually benefitted fully from all that connectivity. New backplanes in the Nexus line are evolving very quickly which again, could certainly be oversubscribed, but what an evolution. Beyond the bandwidth we must also recognize the flexibility that the virtual interface card (VIC) has brought as well, where a single controller card can emulate over a hundred different cards to provide logical traffic isolation. Yes, great companies like Xsigo do this and more with switching and cards but Cisco has integrated this technology into the UCS as a whole, into the single management interface, and into the concept of the server profile.</p>
<p>Ah yes, margins.</p>
<p>I get the sense you believe Cisco sells at list price. Uhhhh, no…</p>
<p>I have to concede that the UCS sale has a lower margin than a Catalyst 6500 sale. However, the switching market has long been commoditized and servers are the very icon of IT commoditization. Speaking from experience I have seen many true HP blade diehards admit that they see a benefit in the UCS management capabilities and have made the switch. If you purchase a UCS, you are purchasing the fabric interconnects and also the fabric extenders, so when Cisco sells servers, they sell two other major elements of their portfolio and therefore increases the revenue to the company from a “server” purchase. I will happily also concede the per sale margin on the UCS may be lower than other larger Cisco product sales, but the net is that UCS is bringing Cisco a bigger footprint in the data center and they are not losing money doing it. To continue to grow as a company with such immense market penetration in the route switch space they can either innovate their products are or widen the offering and between Nexus and UCS. Cisco is doing both.</p>
<p>No cost? It’s true, somewhere there is a cost. But I did get my cell phone for free if someone else was going to give me the same contract at the same price without a phone? So if Cisco gives me a great management interface with the UCS at the same price for another manufacturer’s blade center that does not (or cannot) provide said interface, I’ll call it free.</p>
<p>I assure you, I do not believe that the UCS is the silver bullet for server/network integration, but I really like where Cisco went with it – especially for the virtualization workspace. If the UCS spurs the likes of HP and Dell to innovate and unify their products, then all the better. But I strongly believe that the UCS is different than anything else in the server/switching space, and it is helping Cisco continue to grow and thrive as a company.</p>
<p>- David</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Shifting IT Workforce Paradigm: From Sys Admin to Capacity Planners by CIO Talk Radio</title>
		<link>http://www.integrateddatastorage.com/blog/2011/11/29/the-shifting-it-workforce-paradigm-from-sys-admin-to-capacity-planners/#comment-4804</link>
		<dc:creator>CIO Talk Radio</dc:creator>
		<pubDate>Mon, 09 Jan 2012 23:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=3848#comment-4804</guid>
		<description>Hi Charles,

Great article, you bring up a lot of different points that must be addressed in the IT workforce. 

CIO Talk Radio has a show coming up on January 25th at 9AM Central, 10AM Eastern, 7AM Pacific called &quot;IT Workforce Skills, Competency, and Engagement: The Road Ahead&quot; with guests Pablo A. Vegas, VP and Chief Information Officer at American Electric Power (AEP), Maurice Tayeh – SVP and CIO at the Shaw Group Inc. and Art Lofton, CIO and VP of IT Solutions at Northrop Grumman Aerospace Systems.

It would be great for you to listen in and see if this show can answer any of your questions about what is needed in the IT workforce from the understanding of the key IT executives. Our website is www.ciotalkradio.com... I will follow up with you after the show on some of the key points if you are interested.</description>
		<content:encoded><![CDATA[<p>Hi Charles,</p>
<p>Great article, you bring up a lot of different points that must be addressed in the IT workforce. </p>
<p>CIO Talk Radio has a show coming up on January 25th at 9AM Central, 10AM Eastern, 7AM Pacific called &#8220;IT Workforce Skills, Competency, and Engagement: The Road Ahead&#8221; with guests Pablo A. Vegas, VP and Chief Information Officer at American Electric Power (AEP), Maurice Tayeh – SVP and CIO at the Shaw Group Inc. and Art Lofton, CIO and VP of IT Solutions at Northrop Grumman Aerospace Systems.</p>
<p>It would be great for you to listen in and see if this show can answer any of your questions about what is needed in the IT workforce from the understanding of the key IT executives. Our website is <a href="http://www.ciotalkradio.com.." rel="nofollow">http://www.ciotalkradio.com..</a>. I will follow up with you after the show on some of the key points if you are interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Cisco UCS Command Line: Creating &#8220;Server&#8221; &amp; &#8220;Uplink&#8221; Ports From Your Command Center by Mark</title>
		<link>http://www.integrateddatastorage.com/blog/2011/08/12/the-cisco-ucs-command-line-creating-server-uplink-ports-from-your-command-center/#comment-4121</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 27 Oct 2011 17:25:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=3133#comment-4121</guid>
		<description>Looking at the picture in step 5... what does &quot;No Operational Members&quot; mean?</description>
		<content:encoded><![CDATA[<p>Looking at the picture in step 5&#8230; what does &#8220;No Operational Members&#8221; mean?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cisco UCS: On Trial in the Court of Public Opinion (and the Verdict Is?) by Adam</title>
		<link>http://www.integrateddatastorage.com/blog/2011/06/27/cisco-ucs-on-trial-in-the-court-of-public-opinion-and-the-verdict-is/#comment-2882</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Thu, 18 Aug 2011 03:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=2541#comment-2882</guid>
		<description>I could not disagree more with everything in this post. 

Does Cisco UCS differentiate itself in the market place? 

No, the same virtual fabric interconnect of servers and FoE storage is being provided by HP and, after the acquisition of BNT, IBM. Either of these providers are better suited to discuss &quot;unified computing&quot; as they own storage sub-systems (which Cisco does not, EMC partner) and system management and provision tools (which Cisco does not, BMC partner). Cisco is a switch provider which has white-boxed some x86 servers. Even Dell, the laggard of the industry, will be able to duplicate this architecture with Force 10. 

Also, UCS is only unified if all your workloads are x86, not realistic in large companies with mission critical Unix, mainframe, etc. Even if you had all x86 workloads, you can easily oversubscribe those switches. In a real world scenario of 4:1 Network oversubscription, (2) 6140&#039;s and (1) UCS Manager would be required per rack.

UCS will increase Cisco&#039;s margins? 

How in the world do you think UCS will raise Cisco&#039;s margins? They are accustomed to having little, if any, competition in the switching space which has allowed them to charge ludicrous 60% gross margins on their commodity switches. Even if Cisco retains their networking customers, they will retain them at much lower margins as HP and Juniper are offering the same performance and QoS at 50% the TCO or less. Cisco took on the rest of the IT industry, with the exception of EMC and BMC, when they released UCS. This will turn networking margins into x86 server margins. Competition makes margins go down, not up. 

Cisco UCS Manager is a &quot;no cost&quot; option? 

Do you think you are getting your cell phone at &quot;no cost&quot; when you sign a two year contract? No, the price of the phone is baked into the service cost. The Cisco UCS Manager cost is baked into the switch and SmartNet costs. I assure you that BMC is not giving them the software for free and they are no giving it away at &quot;no cost&quot; because they like losing money. There is a difference between &quot;included in the price&quot; and &quot;no cost.&quot;</description>
		<content:encoded><![CDATA[<p>I could not disagree more with everything in this post. </p>
<p>Does Cisco UCS differentiate itself in the market place? </p>
<p>No, the same virtual fabric interconnect of servers and FoE storage is being provided by HP and, after the acquisition of BNT, IBM. Either of these providers are better suited to discuss &#8220;unified computing&#8221; as they own storage sub-systems (which Cisco does not, EMC partner) and system management and provision tools (which Cisco does not, BMC partner). Cisco is a switch provider which has white-boxed some x86 servers. Even Dell, the laggard of the industry, will be able to duplicate this architecture with Force 10. </p>
<p>Also, UCS is only unified if all your workloads are x86, not realistic in large companies with mission critical Unix, mainframe, etc. Even if you had all x86 workloads, you can easily oversubscribe those switches. In a real world scenario of 4:1 Network oversubscription, (2) 6140&#8242;s and (1) UCS Manager would be required per rack.</p>
<p>UCS will increase Cisco&#8217;s margins? </p>
<p>How in the world do you think UCS will raise Cisco&#8217;s margins? They are accustomed to having little, if any, competition in the switching space which has allowed them to charge ludicrous 60% gross margins on their commodity switches. Even if Cisco retains their networking customers, they will retain them at much lower margins as HP and Juniper are offering the same performance and QoS at 50% the TCO or less. Cisco took on the rest of the IT industry, with the exception of EMC and BMC, when they released UCS. This will turn networking margins into x86 server margins. Competition makes margins go down, not up. </p>
<p>Cisco UCS Manager is a &#8220;no cost&#8221; option? </p>
<p>Do you think you are getting your cell phone at &#8220;no cost&#8221; when you sign a two year contract? No, the price of the phone is baked into the service cost. The Cisco UCS Manager cost is baked into the switch and SmartNet costs. I assure you that BMC is not giving them the software for free and they are no giving it away at &#8220;no cost&#8221; because they like losing money. There is a difference between &#8220;included in the price&#8221; and &#8220;no cost.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tape Sucks: Avamar 6.0 Version #tapesucksmoveon by Jason Mills</title>
		<link>http://www.integrateddatastorage.com/blog/2011/04/28/tape-sucks-avamar-6-0-version-tapesucksmoveon/#comment-2393</link>
		<dc:creator>Jason Mills</dc:creator>
		<pubDate>Tue, 21 Jun 2011 04:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=1978#comment-2393</guid>
		<description>I agree with the tapeout weakness.  Re-hydrating to a staging server then writing out to tape, come on EMC get direct tape out into AVAMAR.</description>
		<content:encoded><![CDATA[<p>I agree with the tapeout weakness.  Re-hydrating to a staging server then writing out to tape, come on EMC get direct tape out into AVAMAR.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tape Sucks: Avamar 6.0 Version #tapesucksmoveon by Dan Dwyer</title>
		<link>http://www.integrateddatastorage.com/blog/2011/04/28/tape-sucks-avamar-6-0-version-tapesucksmoveon/#comment-2278</link>
		<dc:creator>Dan Dwyer</dc:creator>
		<pubDate>Thu, 16 Jun 2011 23:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=1978#comment-2278</guid>
		<description>Jason B,

Interested in what you may have found about tape out with Avamar. I am also looking at Data Domain and tape out options.


Thanks,
Dan Dwyer</description>
		<content:encoded><![CDATA[<p>Jason B,</p>
<p>Interested in what you may have found about tape out with Avamar. I am also looking at Data Domain and tape out options.</p>
<p>Thanks,<br />
Dan Dwyer</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on &#8220;You&#8217;re Fired!&#8221; Why Snapshots + Replication (Donald) Trump Your Old Backup Strategy by Rowan Gillson</title>
		<link>http://www.integrateddatastorage.com/blog/2011/05/17/youre-fired-why-snapshots-replication-donald-trump-your-old-backup-strategy/#comment-1787</link>
		<dc:creator>Rowan Gillson</dc:creator>
		<pubDate>Wed, 18 May 2011 03:16:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrateddatastorage.com/?p=2344#comment-1787</guid>
		<description>Great article Nick, though I might add that if anyone is reading this and experiencing the difficulties you mention with regards to backups cutting into business hours or a low backup success rate, maybe they need to look into data archiving also. This would certainly reduce the former issue and go a small way to resolving the latter.

Preston Deguise has a great article here - http://nsrd.info/blog/2011/05/07/there-is-no-such-thing-as-a-backup-failure/ - addressing the latter and the importance of resolving your backup issues as they represent an inability to recover your data. Perhaps it&#039;s worth mentioning?

We find most customers interested in array based snapshot backups are primarily focussed on improving their recovery times where traditionally this may have taken upwards of a day to recover a tape full of data and they can instead rely on the ability to mount the snapshot or revert their data to a known good state. I&#039;m a massive champion of snapshot technology and it&#039;s great to see others including David Chapa - http://www.navigatingthebarscene.com/2011/05/notorious-b-i-g-data-infamous-b-i-g-backup/ - giving us all a firm shove into it&#039;s adoption .</description>
		<content:encoded><![CDATA[<p>Great article Nick, though I might add that if anyone is reading this and experiencing the difficulties you mention with regards to backups cutting into business hours or a low backup success rate, maybe they need to look into data archiving also. This would certainly reduce the former issue and go a small way to resolving the latter.</p>
<p>Preston Deguise has a great article here &#8211; <a href="http://nsrd.info/blog/2011/05/07/there-is-no-such-thing-as-a-backup-failure/" rel="nofollow">http://nsrd.info/blog/2011/05/07/there-is-no-such-thing-as-a-backup-failure/</a> &#8211; addressing the latter and the importance of resolving your backup issues as they represent an inability to recover your data. Perhaps it&#8217;s worth mentioning?</p>
<p>We find most customers interested in array based snapshot backups are primarily focussed on improving their recovery times where traditionally this may have taken upwards of a day to recover a tape full of data and they can instead rely on the ability to mount the snapshot or revert their data to a known good state. I&#8217;m a massive champion of snapshot technology and it&#8217;s great to see others including David Chapa &#8211; <a href="http://www.navigatingthebarscene.com/2011/05/notorious-b-i-g-data-infamous-b-i-g-backup/" rel="nofollow">http://www.navigatingthebarscene.com/2011/05/notorious-b-i-g-data-infamous-b-i-g-backup/</a> &#8211; giving us all a firm shove into it&#8217;s adoption .</p>
]]></content:encoded>
	</item>
</channel>
</rss>

