<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>DCIGInc.com</title>
    <link rel="alternate" type="text/html" href="http://www.dciginc.com/" />
    <link rel="self" type="application/atom+xml" href="http://www.dciginc.com/atom.xml" />
    <id>tag:www.dciginc.com,2007-09-06://1</id>
    <updated>2008-05-15T17:00:56Z</updated>
    <subtitle>DCIG writes evaluations of products and services in the storage and electronically stored information (ESI) markets for consumers, public relations firms, business analysts and other interested companies. Our analysis is an informed inside look made possible through business blogging agreements.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>

<entry>
    <title>eDiscovery; Proactive Approach or Corporate Fire Drill</title>
    <link rel="alternate" type="text/html" href="http://kazeon.dciginc.com/2008/05/ediscovery-proactive-approach.html" />
    <id>tag:kazeon.dciginc.com,2008://26.280</id>

    <published>2008-05-16T13:38:00Z</published>
    <updated>2008-05-16T13:38:00Z</updated>

    <summary>If your company strategy toward Electronic Discovery (eDiscovery) process amounts to nothing more than a corporate fire drill, you are not alone; but the potential costs and risks associated with this reactive approach are staggering.

An eDiscovery process can touch many areas within your company, and meeting the obligations of the Federal Rules of Civil Procedure (FRCP) regarding eDiscovery processes can be a daunting task.  According to the National Law Journal over 90 percent of business documents today are created and stored electronically.  When you factor in the many avenues in which corporate data is created and stored, whether it is e-mail, spreadsheets, or electronic documents, the need for adopting a proactive eDiscovery process becomes apparent.
</summary>
    <author>
        <name>Howard Haile</name>
        
    </author>
    
    <category term="electronicdiscovery" label="Electronic Discovery" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://kazeon.dciginc.com/">
        <![CDATA[<p>If your company strategy toward Electronic Discovery (eDiscovery) process amounts to nothing more than a corporate fire drill, you are not alone; but the potential costs and risks associated with this reactive approach are staggering.</p>
<p>An eDiscovery process can touch many areas within your company, and meeting the obligations of the <a href="http://www.law.cornell.edu/rules/frcp/">Federal Rules of Civil Procedure</a> (FRCP) regarding eDiscovery processes can be a daunting task. According to the <a href="http://www.law.com/jsp/nlj/index.jsp">National Law Journal</a> over <a href="http://findarticles.com/p/articles/mi_m0EIN/is_2008_March_6/ai_n24376803">90 percent</a> of business documents today are created and stored electronically. When you factor in the many avenues in which corporate data is created and stored, whether it is e-mail, spreadsheets, or electronic documents, the need for adopting a proactive eDiscovery process becomes apparent.</p>
<p>It is well established that not having a formal process towards eDiscovery is a costly and risky strategy. Studies performed by <a href="http://www.dciginc.com/2008/01/kazeon-steve-dalencon-interview-pt1.html">DCIG </a>have shown that costs can approach $2000 per gigabyte of information for collecting and preserving electronic data. This does not include the costs associated with a legal review that a proactive approach to eDiscovery can help mitigate </p>
<p>Traditional reactive approaches to eDiscovery expose companies to skyrocketing costs as they try to wade through the processing and review of e-mail and documents which too often cause delays in determining which documents are subject to discovery. A proactive approach towards eDiscovery shortens the time it takes to identify, collect, process, and analyze electronically stored e-mail and documents thereby reducing costs and delays in responding to eDiscovery requests. </p>
<p>In developing a proactive approach to eDiscovery, there are several areas which a company needs to consider:</p>
<ul><i>
<p><strong>1. Is a company better served through outsourcing eDiscovery to a third party? Or is bringing up-front eDiscovery in house through the use of an eDiscovery tool such as <a href="http://www.kazeon.com/">Kazeon Systems'</a> <a href="http://www.kazeon.com/products2/information_server.php">IS1200</a> a more prudent option?</strong> </i>When making this decision companies need to consider all issues and risks and decide which model best fits their corporate strategy. Usually the decision is one based on cost and control. How can a company have the most control over its data and implement the eDiscovery process for the lowest cost? </p><b><i>
<p><strong>2. Does your company have a good understanding of the laws pertaining to eDiscovery?</strong> </b></i>The revised FRCP governs eDiscovery in legal proceedings. Ensuring there isn't any legal counsel confusion regarding eDiscovery is critical during these times since, in order to comply with FRCP, there are steps that companies need to take including:</p>
<ul>
<li>Verifying that electronically stored information (ESI) is accessible and discoverable</li>
<li>Faster, hassle-free information for 26(a) initial disclosures</li>
<li>Prepare for 26f meet and confer to define scope</li>
<li>Knowing the guidelines on when cost or effort is excessive and not justifiable in producing an e-document</li>
<li>The loss of evidence through routine e-mail purging</li></ul></ul><b><i>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p><strong>3. Developing an adequate records management program.</strong></b></i> If you do not have a good handle on your electronically stored information, then any eDiscovery request is going to be a costly and time consuming effort. Companies no longer have open-ended time frames in which to answer an eDiscovery request and there have been high profile examples in which civil penalties have been levied against companies for delays in responding to eDiscovery requests. One such example as reported by the New York Times was Morgan Stanley's $15 million agreed upon fine with the SEC for failing to produce e-mails in a timely manner.</p></blockquote>
<ul><i>
<p><strong>4. Finally, companies should develop policies and procedures to ensure they have a plan in place when eDiscovery occurs.</strong></i> This should be a combined effort between corporate management, corporate IT and legal counsel to ensure a good understanding of the challenges in responding to eDiscovery requests. A consistent approach to these types of requests will go a long way in making sure management, IT and legal are all on the same page when a company needs to perform an eDiscovery. </p></ul>
<p>Legal fire drills generate a lot of activity and sometimes solve the problem but they are no longer a viable substitute for a well managed and documented corporate eDiscovery process. Companies must understand that a reactive approach to eDiscovery results in unacceptable delays and could lead to critical omissions and/or revelations. These may damage the organization's reputation in the market while also increasing costs and taking up valuable time. By following the above suggestions your company can begin to implement a thoughtful and prudent pro-active eDiscovery infrastructure that will benefit not only your ongoing information management initiatives, but help you respond to reactive eDiscovery requests with unprecedented completeness and accuracy across your enterprise. </p>
<p>&nbsp;</p>]]>
        
    </content>
</entry>

<entry>
    <title>Quantum&apos;s DXi7500 Makes the Enterprise Jump</title>
    <link rel="alternate" type="text/html" href="http://quantum.dciginc.com/2008/05/quantums-dxi7500-makes-the-ent.html" />
    <id>tag:quantum.dciginc.com,2008://25.279</id>

    <published>2008-05-16T13:00:00Z</published>
    <updated>2008-05-16T13:00:00Z</updated>

    <summary>Quantum is aiming for the enterprise with its deduplication technology and looks to make a serious run at the enterprise datacenter with its DXi7500. Designed to anchor Quantum&apos;s deduplication strategy, companies can use the scalable DXi7500 when it is receiving replicated data from Quantum&apos;s DXi3500 or DXi5500 appliances in remote offices; replicating to disaster recovery site(s); or deduplicating terabytes of data during nightly backup jobs in the datacenter. To accomplish this, Quantum designed the DXi7500 to become the focal point for its DXi portfolio.
</summary>
    <author>
        <name>Howard Haile</name>
        
    </author>
    
    <category term="deduplication" label="Deduplication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="disasterrecovery" label="Disaster Recovery" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="replication" label="Replication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="tiereddatasystems" label="Tiered Data Systems" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://quantum.dciginc.com/">
        <![CDATA[<p><a href="http://www.quantum.com/">Quantum</a> is aiming for the enterprise with its deduplication technology and looks to make a serious run at the enterprise datacenter with its <a href="http://www.quantum.com/Products/Disk-BasedBackup/DXi7500/Index.aspx">DXi7500</a>. Designed to anchor Quantum's deduplication strategy, companies can use the scalable DXi7500 when it is receiving replicated data from Quantum's <a href="http://www.quantum.com/Products/Disk-BasedBackup/DXi3500/Index.aspx">DXi3500</a> or <a href="http://www.quantum.com/Products/Disk-BasedBackup/DXi5500/Index.aspx">DXi5500</a> appliances in remote offices; replicating to disaster recovery site(s); or deduplicating terabytes of data during nightly backup jobs in the datacenter. To accomplish this, Quantum designed the DXi7500 to become the focal point for its DXi portfolio.</p>
<p>Though Quantum announced the DXi7500 some time ago, today marks general availability of the DXi7500 that it views as meeting today's enterprise concerns. There are a number of features that Quantum includes within the DXi7500 to scale into the enterprise including:</p>
<ul>
<ul><font face="Symbol">
<li></font><font style="FONT-SIZE: 1em">Better performance for shorter backup and restore windows</font></li>
<li><font style="FONT-SIZE: 1em">Unique options for either policy-based adaptive&nbsp;or fully deferred deduplication</font></li>
<li><font style="FONT-SIZE: 1em">Replication for remote offices and disaster recovery</font></li>
<li><font style="FONT-SIZE: 1em">High availability and reliability</font></li></ul></ul>
<p>One of the more innovative features of the DXi7500 is its adaptive approach to deduplication. It appears that when Quantum was looking at how to best approach deduplication for the enterprise, it did not to take sides in the "inline" versus "post- processing" deduplication debate and instead gave the customer the flexibility to choose which approach best suits their needs.</p>
<p>This is particularly valuable to companies that have a mix of backup jobs with both low and high performance characteristics and that need more than one alternative when deduplicating backup data. Other products only offer one choice for deduplicating data - "inline" or "post-processing" - but not both. Using Quantum's adaptive deduplication approach, however, companies can match the form of deduplication to the characteristics of their backup job or even the nature of the data contained in the backup jobs. Configured this way, the DXi7500 can match the deduplication approach to the requirements of specific backup jobs. </p>
<p>Matching the deduplication approach to the type of backup job, or even data within the backup job, delivers faster ingest speeds during the backup window. However, because the DXi7500 also gives companies the option to create partitions and assign specific deduplication methods to these partitions, companies can designate which partitions use what specific type of deduplication. In those circumstances where companies expect moving backup data to tape immediately or backups contain a high percentage of new data, companies can take advantage of its "fully deferred" deduplication policy that postpones the deduplication until the backup is fully complete. </p>
<p>Quantum also looks to give companies a compelling reason to use the DXi7500 as the target for receiving replicating data from DXi3500s and DXi5500s as well as using the DXi7500 as a foundation in building a company's disaster recovery (DR) strategy. By deploying DXi3500s or DXi5500s at remote offices, companies can replicate data from these appliances back to a central DXi7500 in their primary data center. Once the data is replicated and centrally stored on the DXi7500, companies can then optionally place a DXi7500 at their disaster recovery site and then replicate data from the DXi7500 in their home office to this secondary site. </p>
<p>The DXi7500 also provides a mechanism to copy data to removable media (tape) for those companies that do not plan to replicate data to a remote site or have long term archiving or compliance requirements. The DXi7500 can either use its own software to copy data from disk on tape or companies can optionally use <a href="http://shop.symantecstore.com/store/symnasmb/en_US/DisplayProductDetailsSmbPage/productID.77818000/ThemeID.106400/pgm.13399900">Symantec's NetBackup 6.5</a> that recognizes the DXi7500 and can manage the migration of data from disk to tape. </p>
<p>Of course, a final prerequisite when positioning a storage system like the DXi7500 at the enterprise core is to address enterprise concerns about high availability and reliability. The DXi7500 provides dual RAID controllers, dual redundant power and cooling, and hot replaceable components. Dual-node DXi7500 systems eliminate all single points of failure by using dual DXi controllers, active-active failover for all hardware, and cluster-aware software components that fail-over as needed. </p>
<p>Quantum is one of the first deduplication vendors to make the jump from the midrange market with its DXi3500 and DXi5500 backup appliances into the enterprise space with its DXi7500. On the surface, Quantum appears to have put all of the features into the DXi7500 in order to succeed: a highly available and reliable system, careful navigation of the deduplication debate through adaptive and fully deferred duplication and the use of the same replication software across its midrange and enterprise appliances. </p>
<p>This should work in Quantum's favor near and long term. Despite the fact that the Quantum is somewhat late to market with an enterprise level deduplication system, deduplication is still just getting started, not tailing off. By introducing one of the first core-to-edge global deduplication and replication schemes in the market, Quantum should find ample opportunities for companies that are eagerly looking for a single vendor to meet all of their disk-based data protection and disaster recovery needs.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Did Xiotech Over-Engineer Its Emprise Storage System? Insights from Day 2 at Chicago Storage Decisions</title>
    <link rel="alternate" type="text/html" href="http://www.dciginc.com/2008/05/did-xiotech-overengineer-its-emprise-storage.html" />
    <id>tag:www.dciginc.com,2008://1.278</id>

    <published>2008-05-15T16:06:00Z</published>
    <updated>2008-05-15T16:06:00Z</updated>

    <summary>I started out the day with an hour-long briefing with Xiotech&apos;s CTO Stephen J Sicola and Storage Architect Peter Selin. Xiotech has been talking up a storm about the ground-shaking importance of its new Intelligent Storage Elements (ISE) ever since Xiotech announced it at Storage Networking World about a month ago. However Xiotech and I have not had a chance to connect for me to take a close look at its architecture so Stephen and Peter spent some time talking me through it.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="businesscontinuity" label="Business Continuity" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="disasterrecovery" label="Disaster Recovery" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="gridstorage" label="Grid Storage" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="physicaltape" label="Physical Tape" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="storagesystems" label="Storage Systems" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.dciginc.com/">
        <![CDATA[<font size="2">
<p>Yesterday I completed my quick road trip to Chicago to attend TechTarget's annual spring <a href="http://storagedecisions.techtarget.com/">Storage Decisions</a> conference returning home last night. Here are some the highlights from my day 2.</p>
<p>I started out the day with an hour-long briefing with Xiotech's CTO Stephen J Sicola and Storage Architect Peter Selin. <a href="http://www.xiotech.com/">Xiotech</a> has been talking up a storm about the ground-shaking importance of its new <a href="http://www.xiotech.com/Products-and-Services_ISE.aspx">Intelligent Storage Elements</a> (ISE) ever since Xiotech announced it at Storage Networking World about a month ago.&nbsp;However Xiotech and I have not had a chance to connect for me to take a close look at its architecture&nbsp;so&nbsp;Stephen and Peter spent some time talking me through it.</p>
<p>One of the factoids I found most intriguing was the history (at least as Steve tells it) why Xiotech (and Seagate behind the scenes) felt obligated to go back to the basics in designing the ISE that underlies its new <a href="http://www.xiotech.com/Products-and-Services_ISE_Emprise-7000.aspx">Emprise stroage system</a>. One of the more interesting aspects to the story was the history of placing disk drives into storage systems. Apparently when disk drives were first&nbsp;placed into storage systems, they were not designed them for vertical insertion - always horizontal. So when disk drives were placed vertically in storage systems to optimize rack space, they started failing more frequently.</p>
<p>Another key problem had to do with mounting and cooling the disk drives. Again, disk drives were designed for mounting in stable (non-vibrating) racks as standalone units with ample air flow for cooling. However, when putting tens or hundreds of disk drives into a rack, not only is air flow around the disk drives reduced, but the vibration of all of these spinning disk drives in the same rack is amplified leading to higher disk drive failure rates. So the disk storage systems have compensated over the years by making tweaks in their firmware and controllers to offset these variances and minimize the impact of failures.</p>
<p>Xiotech's Sicola felt it was time to go back to the drawing board and re-examine the design of everything from the disk drive firmware to how they were mounted in storage systems to the controllers managing them. He started this process nearly 6 years and the result is the ISE found in Xiotech's Emprise storage systems. Key changes it makes are more stable mounts for&nbsp;disk drive placement and&nbsp;replacing the disk drive's native firmware with its own firmware for more pro-active monitoring and the transmission of storage system reports to Xiotech. </p>
<p>Though there were many others, sending the activity reports to Xiotech caught my attention because Xiotech will now monitor activity on your systems and notify companies&nbsp;not just when drives fail, but warn&nbsp;them when it detects&nbsp;abnormal activity on their Emprise system that may contribute to&nbsp;degraded application&nbsp;performance. For instance, if a company places a high performance Oracle database on SATA disk drives, the reports sent back to Xiotech should detect this activity and Xiotech should in turn warn the company that not only should its Oracle database not reside on SATA disk drives, but that this level of activity&nbsp;could lead to&nbsp;degraded performance and SATA disk drives on the system failing prematurely.</p>
<p>So what do all these new features mean for users short and long term? Because Xiotech makes the Emprise more resilient, they have extended the warranties on their systems from 3 to 5 years while its upfront costs are comparable to other systems. This should allow companies to depreciate these systems out over five years rather than three. This can lower quarterly depreciation costs and, since the underlying disk drives are theoritically more reliable, there is a lower chance of disk drives failing and hence less risk to your applications.</p>
<p>The main question companies need to ask themselves about Emprise is not about its stability and reliability but did Xiotech over-engineer this system? Five years is a long time in the technology industry and can span as much as three generations of technology improvements (assuming new technology is introduced every 18 months). This can leave a company with book value on a 3 year old storage system should a need to upgrade it to more current technology. This could require the company taking a financial hit on the books even though the Emprise is still a viable storage system. Overall, though, Xiotech's Emprise should give companies pause about their current vendor's storage system and think more deeply about how their current storage&nbsp;systems are archtitected and if going from a 3 to a 5 year warrantly makes sense.</p>
<p>My next meeting was with Omneon's Director of Storage Marketing, Dave Frederick. <a href="http://www.omneon.com/">Omneon</a> is a 10-year old, $120 million storage company primarily dedicated to providing storage for the broadcasting industry so I inquired of Dave why his company's sudden interest in attending Storage Decisions. He said that more Fortune 500 and Fortune 1000 companies are now broadcasting video internally&nbsp; and this is creating a new demand for storage&nbsp;systems specifically designed for the broadcasting industry.</p>
<p>So I queried Dave further to understand further how high transaction environments differ from broadcasting since both call for near 100% availability. Dave explained that there are two fundamental differences between broadcasting and high transaction environments. Broadcasting accesses data sequentially while high transaction environments tend to access data randomly. However, the larger difference is that if there are pauses in high transaction environments (even milliseconds), the transaction can be resent. This is not so in broadcasting. It even one frame is missed (30 frames are sent every second), you don't get a second chance and those types of misses (called black spaces) result in missed SLAs and loss of revenue for broadcasting companies.</p>
<p>It is in this way that Omneon's <a href="http://www.omneon.com/products/index.html">MediaDeck Integrated Media Server</a> storage differentiates itself from competitive products. Though it uses a grid storage architecture, it also includes an out of band component that verifies each frame as it is encoded and decoded so that when a broadcast is sent out, it streams the video without a black spaces.</p>
<p>Finally, my other notable meeting for the day was lunch with representatives from the <a href="http://www.ultrium.com/About/default.php?section=3&amp;subsec=default">LTO consortium</a>: <a href="http://www.quantum.com/">Quantum</a>'s Product Marketing Manager, Tom Hammond; <a href="http://www.ibm.com/us/">IBM</a>'s Senior Program Manager, Bruce Master; and <a href="http://www.hp.com/">HP</a>'s Product Marketing Manager, Rick Sellers. Most of our conversation focused around how the use of tape is changing in environments and that while disk is becoming the primary target for backup, companies still need to exercise some caution about using disk exclusively for backup.&nbsp;All of us were aware of recent examples where companies had both their primary, secondary and, in one case, even a tertiary DR site affected by disasters that required the use of portable media in order to recover their environment at still another site.</p></font>]]>
        
    </content>
</entry>

<entry>
    <title>So what about the voicemail?</title>
    <link rel="alternate" type="text/html" href="http://autonomy.dciginc.com/2008/05/so-what-about-the-voicemail.html" />
    <id>tag:autonomy.dciginc.com,2008://27.277</id>

    <published>2008-05-15T00:42:34Z</published>
    <updated>2008-05-15T00:42:34Z</updated>

    <summary>The dreaded question plagues discovery vendors, IT and even industry experts shy away from tackling the costs and complexities created by emerging unified communications systems. Office Communications Server 2007 and other communication systems feed divergent media streams into enterprise archives,...</summary>
    <author>
        <name>Greg Buckles</name>
        <uri>http://www.dciginc.com/about/gregorybuckles</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://autonomy.dciginc.com/">
        <![CDATA[<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">The dreaded question plagues discovery vendors, IT and even industry experts shy away from tackling the costs and complexities created by emerging unified communications systems. Office Communications Server 2007 and other communication systems feed divergent media streams into enterprise archives, corporate legal hold repositories and litigation collections. This 'simplification' for the users actually poses serious challenges for search technologies that have traditionally focused exclusively on text. <o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">Finding key terms and phrases buried inside of mountains of recorded phone conversations, voice mails and IM chats can devour discovery budgets and send counsel crying 'undue burden' to the court. There seem to be two dominant speech analytics methods: phonetic indexing (first brought to eDiscovery by Nexidia) and transcription or speech-to-text (long dominated by Autonomy's engine which supports both methods). Phonetic search renders sound wave forms into simplified strings of phonemes that can be indexed and searched. This makes the technology effectively content agnostic, but makes it challenging to integrate with text based search. Speech-to-text has been the foundation for automated conceptual search and improvements in speaker recognition technologies have also increased the value in what was effectively raw dialogue. <o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">Knowing that one can search digitized conversations, the next question is can users effectively search everything within the enterprise system from unified federated search? There is little doubt that the archiving systems are aggressively pursuing acquisitions, partnerships and development to enable ingestion and indexing of every conceivable data stream. All of them started with email back in the late 1990's.<span style="mso-spacerun: yes">&nbsp;&nbsp; </span>For example, Symantec doesn't have audio, but jumped ahead with early products to handle IM, file shares, Sharepoint through merger and acquisition.<o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">Mergers inject complexity by requiring integration of technology, services and cultures. Having experienced the Symantec-Veritas integration first hand, it always surprises me to see pundits and bloggers jumping all over the expected personnel departures.<span style="mso-spacerun: yes">&nbsp; </span>Moreover, other restructurings that occur in the wake of big M&amp;A moves. Instead of looking at who departed, which products are End-of-Lifed and which partners jump ship, I think that we should look at who stays, fundamental IP integrations and new solution offerings to get a better idea of where the new joint entity is headed. <o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">As a former customer of Zantaz's Introspect, I watched press releases closely after the Autonomy acquisition last July. I was surprised to see how quickly all of Zantaz's products were integrated to the IDOL search architecture. A two to three month integration tells me that the business units got the resources and investment needed to make necessary changes under the hood. The back channel continues to be positive.<span style="mso-spacerun: yes">&nbsp; </span>For example, after speaking with two big Introspect customers at a conference last week, it was clear that Autonomy had greatly improved search speed and performance. The back end administration and database complexity still seems to be an issue with some customers, but systems that offer enterprise scale will require enterprise level investments in architecture, support and consistent project management to succeed. Perhaps that is at the root of the shift within the Zantaz channel to go up market and target larger sales? <o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">If we are going to demand that large public corporations make all of their communication data streams accessible and manageable to respond to the new FRCP requirements, then we have to expect further consolidation in the maze of different applications used today. Discovery, ILM, Retention Management, Enterprise Content Management and all the other flavors of alphabet soup are just ways of saying that companies are responsible for administrating their information assets, including formerly transient forms such as audio, IM, PIN-2-PIN, etc.<span style="mso-spacerun: yes">&nbsp;&nbsp; </span></font></font></font><o:p></o:p></p>]]>
        
    </content>
</entry>

<entry>
    <title>Email archiving, is it for the little guy?</title>
    <link rel="alternate" type="text/html" href="http://estorian.dciginc.com/2008/05/email-archiving-is-it-for-the.html" />
    <id>tag:estorian.dciginc.com,2008://23.276</id>

    <published>2008-05-14T16:30:16Z</published>
    <updated>2008-05-14T16:30:16Z</updated>

    <summary>In this age of rising eDiscovery costs, many small players seem to be getting left out in the cold. Implementation of a traditional full featured enterprise archive happens in response to combined IT and Legal pain that finally exceed the...</summary>
    <author>
        <name>Greg Buckles</name>
        <uri>http://www.dciginc.com/about/gregorybuckles</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://estorian.dciginc.com/">
        <![CDATA[<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">In this age of rising eDiscovery costs, many small players seem to be getting left out in the cold. Implementation of a traditional full featured enterprise archive happens in response to combined IT and Legal pain that finally exceed the threshold and cut lose the capitol budget to reign in bloated Exchange environments and service provider profits. But selecting the right solution for a large public company or governmental agency is an entirely different process from the immediate needs of the SMB market and smaller state or county entities. Recent changes in the dominant archive platforms seem to acknowledge this reality as some of them raise the minimum target sale and focus their channel on large enterprise sales. <o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font face="Calibri" color="#000000" size="3">So what is a smaller player to do? Well there are quite a few new </font><a href="http://www.dciginc.com/category/SaaS"><font face="Times New Roman" size="3">SaaS</font></a><font size="3"><font color="#000000"><font face="Calibri"> offerings to consider. The model makes sense for many smaller companies with 1-100 users, especially if they are a service company that wants to minimize overhead and infrastructure. If you have good access to bandwidth or your employees are geographically diverse, then chucking the entire messaging platform can be very attractive. <o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font size="3"><font color="#000000"><font face="Calibri">But outsourcing your informational assets may not be an option for regulated verticals or public agencies with FOIA requirements like the Florida Sunshine Laws. A <st1:State w:st="on"><st1:place w:st="on">Florida</st1:place></st1:State> school system must retain communications record and make them available upon proper request.<span style="mso-spacerun: yes">&nbsp; </span>More challenging than a FOIA request, many smaller companies face potential economic disaster from just one serious civil lawsuit. Large public corporations are required to carry excess umbrella insurance and reserves against risk. They can more easily absorb the typical $1 million deductible that may cap their loss for cases. A $1 million dollar deductible could cripple a small company, assuming that it has a properly structured insurance envelope. This puts small companies and under-budgeted state and local agencies into a unique place in the archiving market.<o:p></o:p></font></font></font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 10pt"><font face="Calibri" color="#000000" size="3">So the under-represented segment of the market needs an archiving and discovery solution with a low entry and implementation threshold. Moreover, it has to be easy to use and administrate as smaller entities may not have dedicated personnel with deep skills. Some of the archiving players seem to have focused on meeting these challenges. </font><a href="http://www.estorian.com/"><font face="Calibri" color="#800080" size="3">Estorian's Looking Glass</font></a><font size="3"><font color="#000000"><font face="Calibri"> Interactive Archive is sold on a subscription model with an entry point as low as $400 per month. The system leverages the Exchange's 'Receive As' functionality to intercept active traffic without using Journaling. This also enables them to scan the mailbox and attached PSTs via MAPI call to dynamically track the folder location and other user actions on the items in the mailbox. <span style="mso-spacerun: yes">&nbsp;</span>This makes it easier to roll outfor smaller companies, because journaling and stubbing are de-emphasized.<o:p></o:p></font></font></font></p>]]>
        
    </content>
</entry>

<entry>
    <title>Disk-Based Backup Does Not Equate to VTL; Insights from Day 1 at Storage Decisions in Chicago</title>
    <link rel="alternate" type="text/html" href="http://www.dciginc.com/2008/05/diskbased-backup-does-not-mean-vtl-insights-f.html" />
    <id>tag:www.dciginc.com,2008://1.275</id>

    <published>2008-05-14T16:25:00Z</published>
    <updated>2008-05-14T16:25:00Z</updated>

    <summary>Despite some of the rumors that were floating around that user attendance was down and not as many vendors were in attendance, I did not necessarily find that the case. I ran into Lindsay Mullen, TechTarget&apos;s event coordinator, in the exhibit hall. She said that about 550 end-users had registered for the event and that she still expected another small influx of end-users on Wednesday. Also, in talking to other analysts and TechTarget editors who were in attendance, they said that all of the break-out sessions were full. The number of vendors exhibiting did, however, seem to be down from years past but not as much as I anticipated. Off-hand, I am guessing that the number of vendors exhibiting was about two-thirds of past events.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="diskbasedbackup" label="Disk Based Backup" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="gridstorage" label="Grid Storage" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.dciginc.com/">
        <![CDATA[<font size="2">
<p>This week I was back on the road again for a short trip to Chicago (short for me anyway since I am from Omaha) to attend the annual spring <a href="http://storagedecisions.techtarget.com/">Storage Decisions</a> conference put on by <a href="http://www.techtarget.com/">TechTarget</a>.</p>
<p>Despite some of the rumors that were floating around that user attendance was down and not as many vendors were in attendance, I did not necessarily find that the case. I ran into Lindsay Mullen, TechTarget's event coordinator, in the exhibit hall. She said that about 550 end-users had registered for the event and that she still expected another small influx of end-users on Wednesday. Also, in talking to other analysts and TechTarget editors who were in attendance, they said that all of the break-out sessions were full. The number of vendors exhibiting did, however, seem to be down from years past but not as much as I anticipated. Off-hand, I am guessing that the number of vendors exhibiting was about two-thirds of past events.</p>
<p>For me, the first day had a decided <a href="http://www.necam.com/">NEC</a> flair to it. I arrived mid-afternoon on Tuesday and met first with NEC's Karen Dutch. Though I know Karen quite well and she and I speak often, there were a couple of salient points that came out of our briefing. The first was that as she speaks to end-users, she finds that there is a tendency among end-users to lump all disk-based backup products into the virtual tape library (VTL) category. Having been guilty of making that assumption myself in the past, it's easy for me to believe that other end-users are falling into the same trap. However, based upon my observations and trends I am seeing the market, I would venture to say that there is a definite trend away from VTLs and towards using disk-based appliances configured as NAS. Even vendors like <a href="http://www.overlandstorage.com/US/index.html">Overland Storage</a> who predominantly provide VTLs are examining the <a href="http://overlandstorage.dciginc.com/2008/05/overland-storages-rationale-fo.html">possibility of releasing a NAS-based interface</a>.</p>
<p>The other topic that Karen and I discussed at length was the willingness of enterprise users to accept the NEC HYDRAstor's disk-based NAS interface. NEC definitely has the enterprise in mind with the <a href="http://www.necam.com/Storage/GridStorage.cfm">HYDRAstor</a> but I have wondered if enterprises were ready to make the jump from VTL to a disk-based backup appliance configured as NAS. Karen said she had had that concern as well but so far that concern has not born out. Though NEC has a version of the HYDRAstor that is configured as a block-based VTL ready for testing, so far it has not found the need to bring&nbsp;a VTL-based version of the HYDRAstor&nbsp;to market.</p>
<p>Following my briefing with Karen, I stopped by the exhibit hall for a couple of hours to see who was exhibiting and catch up on the latest industry buzz. While grabbing a bite to eat, I ended up sitting with Greg Schulz from <a href="http://www.storageio.com/">Storage I/O</a>, We were sitting across from the HP booth so it naturally followed that we would talk about <a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9085019">HP's acquisition of EDS</a>. Having heard about the acquisition on Monday night, I already had a day to mull it over and thought the acquisition made sense. Greg concurred. He felt that HP had a solid insourcing model for those companies who wanted to keep most of their computer management in-house but still needed the more traditional break/fix support that HP current offers. By acquiring EDS, HP now gains access to an outsourcing model for those companies that want to outsource components of their IT infrastructure that are not strategic to their core business. These companies can now turn to HP for both of those functions, something they could not do in the past.</p>
<p>Next up was the evening event that was hosted by NEC (hence the NEC flair to my Day 1 on Storage Decisions). During this event, I was seated next to an end-user from Davenport, IA, and we got to talking about what I saw as the hottest thing in storage right now. I told him that the evolution of data protection software to data management software is probably the most encouraging trend going on. Whenever I speak to users of <a href="http://www.asigra.com/products/televaulting.php">Asigra Televaulting</a> or the <a href="http://www.commvault.com/products/">CommVault Simpana Suite</a>, these users are almost universally telling me that they have moved beyond the day-to-day fire drill of troubleshooting backups to focusing on data management and data recovery. That statement obviously struck a chord with this user. He&nbsp;uses Tivoli Storage Manager (TSM) and he said that he wished he was at that point with backup&nbsp;because he still spends a lot of time struggling with backup and recoveries. </p>
<p>Stay tuned for more insight and info on Storage Decisons Chicago in tomorrow's blog entry.</p></font>]]>
        
    </content>
</entry>

<entry>
    <title>Asigra Televaulting 8.0 Commits Itself to Information Recovery</title>
    <link rel="alternate" type="text/html" href="http://asigra.dciginc.com/2008/05/asigra-televaulting-80-commits.html" />
    <id>tag:asigra.dciginc.com,2008://17.274</id>

    <published>2008-05-13T13:05:00Z</published>
    <updated>2008-05-13T13:05:00Z</updated>

    <summary>In the face of these fundamental shifts among corporate data centers in server data protection and virtualization, data protection software needs to do more than just adapt. It needs to embrace backup-to-disk and server virtualization in order to transform data protection software into an information recovery platform. That is exactly what today&apos;s 8.0 release of Asigra Televaulting brings to the table in the following ways:</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="archiving" label="Archiving" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="dataprotection" label="Data Protection" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="deduplication" label="Deduplication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="diskbasedbackup" label="Disk Based Backup" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="replication" label="Replication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="virtualization" label="Virtualization" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://asigra.dciginc.com/">
        <![CDATA[<p>In the last few years, companies of all sizes have discovered the advantages of using disk as a target in the backup process. Driven by disk's dropping costs, larger capacities, end-user intolerance for failed backups and faster recovery speeds, companies are switching to disk as their primary target for backup and recovery in droves. </p>
<p>Virtualization is having the same type of revolutionary impact on corporate data centers that using disk as part of the data protection process has had. Though companies utilize virtualization in many ways, server virtualization is where its impact is most apparent. <a href="http://www.vmware.com/">VMware</a>, <a href="http://www.virtualiron.com/">Virtual Iron</a> and <a href="http://www.citrixxenserver.com/products/Pages/XenEnterprise.aspx">Xen</a> are contributing to server virtualization's current growth while <a href="http://www.microsoft.com/windowsserver2008/en/us/virtualization-consolidation.aspx">Hyper-V</a> in Microsoft's Windows Server 2008 is poised to join the virtualization fray this summer. </p>
<p>In the face of these fundamental shifts among corporate data centers in server data protection and virtualization, data protection software needs to do more than just adapt. It needs to embrace backup-to-disk and server virtualization in order to transform data protection software into an information recovery platform. That is exactly what today's 8.0 release of <a href="http://www.asigra.com/index.php">Asigra</a> Televaulting brings to the table in the following three ways:</p>
<p>First, Televaulting 8.0 introduces on-demand grid computing. Televaulting has used an agentless architecture since its inception. However its DS-Clients (its agentless backup servers) were configured as one-to-many. This architecture precluded a single DS-Client from helping other DS-Clients complete backup jobs in enterprise shops with large numbers of servers - physical or virtual. </p>
<p>Using Televaulting 8.0's new on-demand grid computing architecture, a parent DS-Client is now created that is aware of the other child DS-Clients residing on virtual or physical machines in the backup environment. As child DS-Clients complete backup jobs assigned to them, they notify the parent DS-Client that its jobs are completed and that it can help other child DS-Clients complete their assigned backup jobs. The parent DS-Client then re-distributes jobs from busy child DS-Clients to the idling child DS-Client so it can help in the backup process.</p>
<p>Second, as I go to storage conferences and speak to end-users, the wide-scale acceptance and adoption of wide area replication astounds me. The size of the company no longer matters. Whether they as small, medium or large, companies want this feature because they understand the age of recovering data anywhere, anytime, and anyplace is upon them.</p>
<p>Multi-directional Data Center Replication in Televaulting 8.0 addresses this growing enterprise need. Asigra Televaulting has for years deduplicated and then replicated data from remote sites back to its central site. However, enterprise companies may have multiple data centers with a need to replicate data between these sites. The Multi-directional Data Center Replication in Televaulting 8.0 capitalizes on the new on-demand grid computing architecture to create an "N+1" configuration. Using "N+1", DS-Systems (the parent Televaulting server into which child DS-Clients feed their data) are aware of each other, sending and receiving backup data to one another. A DS-System can also take over for a DS-System at another site should it fail or need to go off-line for maintenance.</p>
<p>Finally, Asigra Televaulting has always used disk as its primary target for backup but treated all files as the same and worked on the assumption that there was only one tier of disk. Televaulting 8.0 makes no such assumption. Instead, it leverage its knowledge about the files it is protecting (age, size, date last accessed, etc.) plus it now understands that multiple tiers of disk (Fibre channel, SATA, MAID) may exist. </p>
<p>By using this knowledge about the data and disk storage systems, Televaulting 8.0 introduces intelligent archiving as a feature set by placing a server's most active data on FC disk to improve performance during backups and recoveries. However it can store infrequently accessed data on SATA or <a href="http://en.wikipedia.org/wiki/Massive_array_of_idle_disks">MAID</a> disk storage systems to take advantage of their lower disk costs and higher capacities while minimizing power consumption.</p>
<p>Asigra recognizes that a fundamental shift is occurring in data protection and it is about more than just supporting or adapting to backup to disk or virtual machines - it is about embracing them. Televaulting 8.0 takes this next logical step in its product evolution by not just adapting to these technologies but&nbsp;making them core to its next generation of prodcut. The introduction of on-demand grid computing, multi-directional replication and intelligent archiving in the newest version of Televaulting 8.0&nbsp;demonstrate Asigra is&nbsp;committed to helping its clients usher in&nbsp;a new era of information recovery.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Scalable Grid Storage Architecture a Prerequisite for Enterprise Data Archiving</title>
    <link rel="alternate" type="text/html" href="http://permabit.dciginc.com/2008/05/scalable-grid-storage-architec.html" />
    <id>tag:permabit.dciginc.com,2008://29.273</id>

    <published>2008-05-12T10:00:00Z</published>
    <updated>2008-05-12T10:00:00Z</updated>

    <summary>One can hardly have a conversation about storage management these days without the topic of archiving surfacing. Part of the reason that archiving is commanding more attention is because as companies create and keep ever greater amounts of referential data on their production storage systems, it is creating a host of new problems</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="archiving" label="Archiving" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="dataretention" label="Data Retention" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="deduplication" label="Deduplication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="gridstorage" label="Grid Storage" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="networkedstorage" label="Networked Storage" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://permabit.dciginc.com/">
        <![CDATA[<p>One can hardly have a conversation about storage management these days without the topic of archiving surfacing. Part of the reason that archiving is commanding more attention is because as companies create and keep ever greater amounts of referential data on their production storage systems, it is creating a host of new problems.</p>
<p>Some of the problems are obvious. Retaining more data drives up storage costs across the board from extra capacity needed on production storage systems to the need for more capacity in backup. Though deduplication helps to take some of the sting out of disk-based storage costs and using disk as a backup target helps shorten the backup windows, this is only a short term reprieve in coping with existing corporate data and storage management problems, not the final solution.</p>
<p>Most companies fail to understand the financial, technical and legal liabilities that keeping this amount of data online presents to their companies. <a href="http://www.forrester.com/rb/analyst/andrew_reichman">Andrew Reichman</a>, a Senior Analyst with <a href="http://www.forrester.com/rb/research">Forrester Research</a>, conducted studies over the last couple of years that illustrates some of the risks that unmanaged data presents to companies. His findings with Forrester Research included:</p>
<ul>
<li>Storage budgets are flat or declining</li>
<li>The #1 reason companies are buying more storage capacity is because it is easier to throw more capacity at the problem than to understand and deal with the problem</li>
<li>Companies find it very difficult to find good storage people</li>
<li>Data&nbsp;is growing 60% year-over-year while storage costs are dropping only 20% year-over-year</li></ul>
<p>Actual experiences and&nbsp;expenditures&nbsp;will vary by company but these findings clearly identify/illustrate that companies are approaching a point where they&nbsp;must pro-actively manage their data and start to separate production data from stale or infrequently accessed data. Moving this data from primary storage to secondary reduces backup windows since less data is backed up during full backups. Companies can also reduce the amount of money they pay for secondary storage since, instead of procuring high cost Fibre Channel storage systems, they can purchase lower cost, higher capacity storage systems to house this type of data.</p>
<p>However before anyone runs down to <a href="http://www.compusa.com/">CompUSA</a> to start buying hard drives and servers, companies need to put some thought into the type of storage system that they are going to use to host archived data. Companies should also weigh the wisdom of using a product from their existing storage system vendor's portfolio of storage systems as their storage system for archived data. The challenge that most companies will find in this situation is that while most storage systems using off-the-shelf SATA disk drives&nbsp;will cost less than FC disk drives, companies cannot forget to factor in the technical challenges, legal liabilities and financial costs associated with long term data archiving and retention. </p>
<p>Selecting a system that has a scalable and flexible architecture and also satisfies external legal compliance issues by retaining data for the appropriate time without keeping it too long; thereby exposing companies to new risks is a separate issue. In the next blog entry, I'll take a closer look at:</p>
<ul>
<li>How <a href="http://www.permabit.com/products/enterprise-archive.asp">Permabit's Enterprise Archive</a> delivers on these specific concerns</li>
<li>What specific features it has; and</li>
<li>Partnerships that&nbsp;<a href="http://www.permabit.com/">Permabit</a> has&nbsp;in place to address corporate concerns around implementing and managing archived data short and long term</li></ul>]]>
        
    </content>
</entry>

<entry>
    <title>Compellent Users Get Virtualization; Day 2 of Compellent&apos;s Annual C-Drive User Conference</title>
    <link rel="alternate" type="text/html" href="http://www.dciginc.com/2008/05/compellent-users-get-virtualization-day-2-of.html" />
    <id>tag:www.dciginc.com,2008://1.272</id>

    <published>2008-05-09T14:45:00Z</published>
    <updated>2008-05-09T14:45:00Z</updated>

    <summary>One thing that struck me was that Compellent users really understand what a game-changing technology that virtualization is. I sat through 2 or 3 presentations during the two days of the conference (May 7 - 8) and also met with a fair number of users (~10) between sessions, over meals and at the evening events and all of them were pretty stoked about the capabilities that virtualization in general and Compellent specifically delivers.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="businesscontinuity" label="Business Continuity" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="disasterrecovery" label="Disaster Recovery" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="replication" label="Replication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="storagesystems" label="Storage Systems" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="tiereddatasystems" label="Tiered Data Systems" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.dciginc.com/">
        <![CDATA[<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">I just returned home after attending Compellent's <a href="http://www.compellent.com/CDrive.aspx">C-Drive</a> user conference and had some final thoughts and experiences to share after completing my stay at the conference.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">One thing that struck me was that&nbsp;<a href="http://www.compellent.com/">Compellent</a> (NYSE: <a href="http://finance.yahoo.com/q?s=CML">CML</a>) users really understand what a game-changing technology that virtualization is. I sat through 2 or 3 presentations during the two days of the conference (May 7 - 8) and also met with a fair number of users (~10) between sessions, over meals and at the evening events and all of them were pretty stoked about the capabilities that virtualization in general and Compellent specifically delivers.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">Compellent's <a href="http://www.compellent.com/Products/Software/Automated-Tiered-Storage.aspx">Data Progression</a> (automated tiered storage) was the virtualization feature that its users spoke most highly about. One user I spoke with over drinks who was from <st1:City w:st="on"><st1:place w:st="on">Palm Beach</st1:place></st1:City> said that he has been using the Data Progression feature for a couple of years. He actually described the experience as "fun" in watching the Compellent <st1:place w:st="on"><st1:PlaceName w:st="on">Storage</st1:PlaceName> <st1:PlaceType w:st="on">Center</st1:PlaceType></st1:place> migrate infrequently accessed blocks of data to lower cost tiers of disk. </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">Compellent's <a href="http://www.compellent.com/Products/Software/Thin-Provisioning.aspx">Dynamic Capacity</a> (thin provisioning) feature was given a lot of attention at the user conference but none of the users I spoke to seemed to be using it - or at least it never came up in conversations that I had with them. It might just be that they assumed I knew they were using it since the Dynamic Capacity feature is part of Compellent's <st1:place w:st="on"><st1:PlaceName w:st="on">Storage</st1:PlaceName> <st1:PlaceType w:st="on">Center</st1:PlaceType></st1:place> core software licensing and, hence, didn't feel obligated to bring it up.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">Replication was clearly on the mind of almost every user whether they were presenting at the show or merely talking with me privately. It seems a fair number of its users are taking advantage of Compellent's Storage Center replication functions, <a href="http://www.compellent.com/Products/Software/Remote-Replication.aspx">Remote Instant Replay</a> (asynchronous replication) and <a href="http://www.compellent.com/Products/Software/Continuous-Snapshots.aspx">Data Instant Replay</a> (snapshots), in some way even though these software features are add-on licenses to the core software. This trend confirms my suspicions that fast recoveries are becoming more important for companies and the end-users they support. </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">However not all of the news around replication was positive. Most users had no problems using Compellent to replicate data locally or remotely but when it came to providing consistent recoverable snapshots in conjunction with applications, the news was somewhat mixed. During one user panel, Bill Moss, IT Director for <a href="http://www.mosscm.com/">Moss Construction Managers</a> in <st1:place w:st="on"><st1:City w:st="on">Ft. Lauderdale</st1:City>, <st1:State w:st="on">FL</st1:State></st1:place>, described replicating and recovering Exchange data as a "nightmare". He had to work with Microsoft and come up with a two pages of procedures (some of&nbsp;this content&nbsp;apparently appears on Microsoft's website) to recover public folders within Exchange. In looking around the audience and gauging their reaction, it appeared that Moss's struggles with protecting and recovering Exchange is not unique.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">Also at the conference, I had the opportunity to meet with Bruce Kornfeld, Compellent's VP of Marketing, and Larry Aszmann, Compellent's CTO. The main item Bruce and I discussed was how Compellent licenses its software. What distinguishes Compellent from most of its competitors is that it licenses its software by spindle (per disk drive). Its core licensing includes Dynamic Capacity (thin provisioning), LUN security, boot from SAN, some base level reporting features and email home support. This licensing is based on a single controller with&nbsp;one shelf of 16 disk drives. As companies grow their Compellent system,&nbsp;Compellent sells disk drives and licensing in what it terms as "8-packs". Additional software features that users can optionally license with larger systems include its Data Progression, Data Instant Replay, Remote Instant Replay and <a href="http://www.compellent.com/Products/Software/FastTrack.aspx">Fast Track</a> features.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">In the&nbsp;brief meeting I had with Compellent's CTO Larry Aszmann just before I exited the conference, I gleaned&nbsp;&nbsp;two pieces of new information&nbsp;regarding Compellent's&nbsp; manufacturing process and its commitment to its VARs. In regards to manufacturing,&nbsp;Compellent primarily uses off-the-shelf components in the construction of its systems. This&nbsp;removes from Compellent&nbsp;many of the traditional manufacturing concerns that&nbsp;other storage system providers need to manage.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><o:p><font face="Times New Roman" color="#000000" size="3">&nbsp;</font></o:p></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" color="#000000" size="3">Aszmann also said that Compellent sells 100% of its products through the channel and has no plans to go direct. He has seen other storage systems vendors do that which has ultimately undermined the relationship with their VARs. Because&nbsp;Compellent does not sell direct, VARs are much more transparent with Compellent about their business dealings since they&nbsp;are less worried about Compellent cutting them out of deals later on. Aszmann says this level of transparency is helping&nbsp;it as a public traded company&nbsp;because it can remain very accurate (about 90% on target) with each quarter's sales forecasts.</font></p>]]>
        
    </content>
</entry>

<entry>
    <title>Anderson Center for Autism Drives Storage Costs Down to 70¢/GB Using the NEC HYDRAstor</title>
    <link rel="alternate" type="text/html" href="http://necam.dciginc.com/2008/05/anderson-center-for-autism-dri.html" />
    <id>tag:necam.dciginc.com,2008://10.271</id>

    <published>2008-05-08T17:44:52Z</published>
    <updated>2008-05-08T17:44:52Z</updated>

    <summary>Paulk revealed that he is now in full production with the production code loaded on the NEC HYDRAstor. However he is still using the same hardware configuration (two Accelerator Nodes and four Storage Nodes) that he started out using due to the high deduplication ratio that he is achieving with the HYDRAstor. Last fall he was achieving a 17:1 deduplication ratio and hoped to eventually achieve a 35:1 ratio. Six months later, his deduplication ratio is now approximately 39:1 which has mitigated his need to buy additional capacity and has driven his cost/GB down to approximately 70¢/GB. &quot;It&apos;s like getting 390 TB for the price of 10 TBs,&quot; says Paulk.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="archiving" label="Archiving" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="deduplication" label="Deduplication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="diskbasedbackup" label="Disk Based Backup" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="gridstorage" label="Grid Storage" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="recordsmanagement" label="Records Management" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://necam.dciginc.com/">
        <![CDATA[<p>One of DCIG's objectives in blogging is to document over time how companies are using different vendors' products, the ways in which they are using the product, successes they are having and specific challenges that they are beginning to face. Greg Paulk, the IT Director for the <a href="http://www.andersonschool.org/">Anderson Center for Autism</a>, represents the first individual that DCIG has had the opportunity to do this with.</p>
<p>I first met Mr. Paulk at the Fall 2007 <a href="http://storagedecisions.techtarget.com/">Storage Decisions</a> conference in New York City and interviewed him shortly thereafter for a <a href="http://necam.dciginc.com/2007/10/one-of-those-days.html">blog entry</a> that appeared back in October 2007. However six months have passed since that interview so I followed up with Mr. Paulk to get an update on how his installation of the <a href="http://www.necam.com/Storage/GridStorage.cfm">NEC HYDRAstor</a> was performing, since Paulk was still using a beta version of the NEC HYDRAstor software when we last spoke.</p>
<p>Paulk revealed that he is now in full production with the production code loaded on the NEC HYDRAstor. However he is still using the same hardware configuration (two Accelerator Nodes and four Storage Nodes) that he started out using due to the high deduplication ratio that he is achieving with the HYDRAstor. </p>
<p>Last fall he was achieving a 17:1 deduplication ratio and hoped to eventually achieve a 35:1 ratio. Six months later, his deduplication ratio is now approximately 39:1 which has mitigated his need to buy additional capacity and has driven his cost/GB down to approximately 70<font face="Arial" size="2">¢/GB</font>. "It's like getting 390 TB for the price of 10 TBs," says Paulk.</p>
<p>He also has not found it necessary to add more Accelerator Nodes into his HYDRAstor configuration. Though he has nearly doubled the number of servers he is backing up on a nightly basis (from 13 to 21 servers), he is achieving about 3 Gbps of throughput across his two Accelerator Nodes.</p>
<p>I then asked him, "What are the biggest benefits that you have experienced since you started using the HYDRAstor?" There were four benefits he cited:</p>
<ul>
<li><font style="FONT-SIZE: 1em">First, it worked as advertised. The installation was easy (it took 68 minutes), and it has done everything he has needed it to do.</font></li>
<li><font style="FONT-SIZE: 1em">Second, it requires very little management overhead. He has one individual assigned to manage the HYDRAstor and, since it functions as one logical configuration, it takes very little time to manage.</font></li>
<li><font style="FONT-SIZE: 1em">Third, no backups have failed since he introduced the HYDRAstor, and it works 90% faster than when he was using tape.</font></li>
<li><font style="FONT-SIZE: 1em">Fourth, he has found it has reduced his stress level. Aside from alleviating his backup concerns, the HYDRAstor provides him a solid foundation that he can use to build for the future. He no longer has the traditional worries of how he will manage, upgrade or migrate data to new storage systems, because the HYDRAstor accounts for all of these concerns with its grid storage architecture.</font></li></ul>
<p>In the next few months, Paulk plans to archive about one million documents to the HYDRAstor, which will consume about another 1.4 TBs of storage. What he is curious to discover is how this will impact his deduplication ratio. These one million documents are currently paper documents that need to be scanned so he is anxious to find out if he will achieve the same high deduplication ratio when archiving the paper documents that he is experiencing with his backup data. My plan is to catch up and speak with Mr. Paulk again this fall so DCIG can share some more of his story and experiences at that time.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Compellent Sees Green; Day 1 of Compellent&apos;s C-Drive Annual User Conference</title>
    <link rel="alternate" type="text/html" href="http://www.dciginc.com/2008/05/compellent-sees-green-day-1-of-compellents-cd.html" />
    <id>tag:www.dciginc.com,2008://1.270</id>

    <published>2008-05-07T17:45:00Z</published>
    <updated>2008-05-07T17:45:00Z</updated>

    <summary>Today and tomorrow I am putting on both my reporter and analyst hats. Living in Omaha, NE, I am only a hop, skip and jump away from Minneapolis, MN, so I took the opportunity to drive up here to attend Compellent&apos;s annual C-Drive user conference that runs from May 6 - May 8 and do some live, on-site blogging about my experiences while I am here.  Already a few notable items to report from last night&apos;s customer reception and this morning&apos;s opening presentation.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="archiving" label="Archiving" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="deduplication" label="Deduplication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="encryption" label="Encryption" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="storagesystems" label="Storage Systems" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.dciginc.com/">
        <![CDATA[<font size="2">
<p>Today and tomorrow I am putting on both my reporter and analyst hats. Living in Omaha, NE, I&nbsp;am only a hop, skip and jump away from Minneapolis, MN, so&nbsp;I took the opportunity to drive up here to attend <a href="http://www.compellent.com/">Compellent</a>'s annual <a href="http://www.compellent.com/CDrive.aspx">C-Drive</a> user conference that runs from May 6 - May 8 and do some live, on-site&nbsp;blogging about my experiences while I am here. </p>
<p>Already a few notable items to report from last night's&nbsp;customer reception and this morning's opening presentation.</p>
<p>At the&nbsp;customer reception at Brit's Pub in downtown Minneapolis, I ran into Scott Horst, Compellent's Director of Marketing, and had a chance to chat with him for a bit. He said that about 100 users were registered for the event which represents nearly 10% of their current customer base since Compellent forecasts hitting the 1000 customer mark&nbsp;yet this year.</p>
<p>Also at the customer reception I had the opportunity to meet Sonia St. Charles, the CEO of the <a href="http://www.davenportgroup.com/">Davenport Group</a>, a Minneapolis based VAR. What was noteworthy about this meeting was that she was one of the first VARs if not the first VAR I have&nbsp;met that has embraced Web 2.0 technologies and has redesigned Davenport Group's entire website with&nbsp;a focus on social networking. </p>
<p>She says her 19-year-old son was part of the motivation&nbsp;to push her company to&nbsp;adopt a Web 2.0 format. She finds that the next generation of storage administrators (35 and under) are not accustomed to being called on by sales reps or willing to wait. Instead they are spending a few hours searching the Internet and getting up to speed on technologies so they can make more informed buying decisons. She sees this as key to her company's future in helping her educate and inform current and potential Davenport Group clients.</p>
<p>This morning (May 7) Compellent kicked off the day with a presentation by its CEO Phil Soran and "Green" was a major part of the theme. The first "Green"&nbsp;was the&nbsp;color that&nbsp;Wall Street types like (as in greenbacks). Some highlights that he shared from Compellent's past year included:</p>
<ul>
<li>16% of revenue now comes from international sources even as its income has grown fourfold (last year only 6% came for international sources)</li>
<li>Did its IPO in October 2007 raising $93.1 million</li>
<li>107% year-over-year growth</li>
<li>53% of its revenue is coming from repeat orders from existing customers even as its number of new customers has doubled</li></ul>
<p>The more popular notion of "green" also appeared in two&nbsp;of&nbsp;the key trends that Soran sees for storage&nbsp;in the remainder of 2008 which include:</p>
<ul>
<li>Virtual data center</li>
<li>Green, green, green (literally)</li>
<li>IT and business are more closely aligning</li></ul>
<p>I guess up to this point I have been somewhat skeptical about the whole green initiative and still some skepticism remains.&nbsp;Based on&nbsp;Soran's&nbsp;follow-on comments, companies are going green&nbsp;not because they are having&nbsp;any sudden pangs of guilt about wasting too much power or having a carbon footprint that is too large.&nbsp;Rather, power costs are going through the roof and/or there is a real shortage of&nbsp;power.</p>
<p>Soran mentioned one Compellent customer, the <a href="http://www.uscapitolpolice.gov/home.php">US Capitol Police</a>, that had to virtualize their infrastructrure and go "green" because they couldn't get any more power. They used that as an incentive&nbsp;to virtualize their data center thereby making it more green and now actually have power to spare by more efficiently using their resources.</p>
<p>A question and answer period with the audience then followed and here were some of the responses that Soran and other members of the Compellent executive management team had to the audience's questions.</p>
<p>Q&amp;A</p>
<p><strong>When will TB drives be available? </strong>In<strong> </strong>final qualifications right now&nbsp;and Compellent&nbsp;expects them to be released in the next 6 weeks.</p>
<p><strong>Time line on availability of SAS drives?</strong> Been testing SAS for 2 years. The drives are fine but waiting until scalability is there. Currently&nbsp;there are limitations in how many drives can be in a loop. It is a technology&nbsp;Compellent will support but not in the immediate near-term (next 6 months).&nbsp;</p>
<p><strong>Solid State? </strong>Some customers have solid state in their boxes and Compellent supports&nbsp;solid state drives on a case-by-case basis.&nbsp; There are different kinds of solid state: some are slower than others; others you can only write to a certain number of times. Soran expects them to be adopted first in enterprises with $100 million applications but sees them as problematic to deploy&nbsp;now since customers are still unwilling to ante up for them. </p>
<p>(Side note - I sat in on a customer panel after Soran spoke and&nbsp;there might be some disconnect between Compellent and its customer base on this message. Both of the users on-stage were their highlighted speakers of the C-Drive conference - their pictures are plastered everywhere including Compellent's web site - and both of these presenters&nbsp;indicated they would pursue SSDs if Compellent made them available.)</p>
<p><strong>Encrypted drives?</strong> First initiative is to encrypt data stored to removable drives and later to encrypt other drives if demand arose. This is not a&nbsp;6 week time frame but near future.&nbsp;</p>
<p><strong>How much of user base has upgraded to 4.0?</strong> ~250 customers; performance benefits have been good with those users upgrading from earliers releases to 4.0 reporting substantial performance benefits.</p>
<p><strong>Dedupe?&nbsp;</strong>Nothing immediate. Thin provisioning&nbsp;and boot from&nbsp;SAN (one volume&nbsp;for all of your server boots) are technologies that Compellent is using now to address&nbsp;current customer concerns but are&nbsp;trying to figure out most logical fit for this technology. They see&nbsp;archive as the most likely fit for dedupe.</p>
<p><font style="FONT-SIZE: 0.8em">Editor Notes: Edits were made to this blog entry on 5/9/08 at 7:00 am CST to make for better reading and correct some grammatical mistakes.</font></p></font>]]>
        
    </content>
</entry>

<entry>
    <title>The decision to support Microsoft SharePoint Portal Server</title>
    <link rel="alternate" type="text/html" href="http://inmage.dciginc.com/2008/05/inmage-protects-sharepoint-pt3.html" />
    <id>tag:inmage.dciginc.com,2008://14.259</id>

    <published>2008-05-07T11:00:00Z</published>
    <updated>2008-05-07T11:00:00Z</updated>

    <summary>SharePoint Portal Sever was generally unprotected from 2003 through 2007 and couldn&apos;t be effectively supported in a disaster recovery/business continuity scenario.  Thankfully Microsoft resolved that issue in SharePoint Portal Server 2007 by releasing a VSS writer for Microsoft SharePoint Portal Server.  Earlier this year I explained what a VSS Writer did and how VSS works in a two part series Microsoft Volume Shadow Copy Service (VSS) for Continuous Data Protectio (Part 1) and Microsoft Volume Shadow Copy Service (VSS) for Continuous Data Protectio (Part 2).</summary>
    <author>
        <name>Joshua L. Konkle</name>
        <uri>http://www.dciginc.com/about/joshualkonkle</uri>
    </author>
    
    <category term="businesscontinuity" label="Business Continuity" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="continuousdataprotection" label="Continuous Data Protection" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="dataprotection" label="Data Protection" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="disasterrecovery" label="Disaster Recovery" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://inmage.dciginc.com/">
        <![CDATA[Continuation of our series on InMage's support of Microsoft SharePoint Portal Server.<br /><br />Part 1: <a href="http://inmage.dciginc.com/2008/04/inmage-protects-sharepoint-pt1.html">InMage DR-Scout protects Microsoft SharePoint Portal Server 2007, but document management is not new to InMage</a><br />Part 2: <a href="http://inmage.dciginc.com/2008/05/inmage-protects-sharepoint-pt2.html">InMage uses two agents to support the confluence in Document Management systems</a><br /><br />The decision to support Microsoft SharePoint Portal Server continuous data protection was very challenging in prior versions.&nbsp; Microsoft SharePoint Portal Server 2001 was a short lived document management/basic content services system based on Microsoft's Extensible Storage Engine (ESE) used by Microsoft Exchange.&nbsp; Microsoft SharePoint Portal Sever 2003 was a reworked version of the 2001 edition and required Microsoft SQL instead of ESE.&nbsp; The downside was that SharePoint Portal Server 2003 didn't support snapshots or any type of recovery other than whole system recovery.<br /><br />SharePoint Portal Sever was generally unprotected from 2003 through 2007 and couldn't be effectively supported in a disaster recovery/business continuity scenario.&nbsp; Thankfully Microsoft resolved that issue in SharePoint Portal Server 2007 by releasing a VSS writer for Microsoft SharePoint Portal Server.&nbsp; Earlier this year I explained what a VSS Writer did and how VSS works in a two part series <a href="http://inmage.dciginc.com/2008/01/microsoft-vss-inmage-pt1.html">Microsoft Volume Shadow Copy Service (VSS) for Continuous Data Protectio (Part 1)</a> and <a href="http://inmage.dciginc.com/2008/02/microsoft-vss-inmage-pt2.html">Microsoft Volume Shadow Copy Service (VSS) for Continuous Data Protectio (Part 2)</a>.<br /><br />From Part 1<br /><br />
<blockquote>
<blockquote>Microsoft's VSS works by using three pieces a requester, writer and provider.&nbsp; If you have heard about this, then skip to the last paragraph and wait for part 2 due later this week.&nbsp; The requester is your traditional backup solution.&nbsp; Requester's send collection inquiries to the application you want to protect.&nbsp; This application must understand the collection inquiry sent to it by the requester and needs a writer designed to support the application data and data types.&nbsp; The writer is written by the application developers, not the backup vendor, to ensure the most stable and consistent recoveries.<br /></blockquote></blockquote><br />InMage immediately supports the application because of the VSS writer included with Microsoft SharePoint Portal Server 2007.&nbsp; The VSS framework makes it very easy for a VSS requester to support virtually all new VSS writers without issue.&nbsp; InMage supports the requester framework.<br /><br />InMage, using the previous knowledge of document management, identified the confluence of VX Agent volume replication, FX Agent file replication, FX Agent scheduling and VSS requester/writer support to deliver a comprehensive Microsoft SharePoint Portal Server 2007 solution as of the third quarter of 2007.&nbsp; Rajeev Atluri, CTO of InMage, told me that the development and product management team moved from an internal Wiki to SharePoint Portal Server in an attempt to better understand the day to day underpinnings of SharePoint Portal Server.<br /><br />Such a great move for a great company to use the products they develop.<br /><br />]]>
        
    </content>
</entry>

<entry>
    <title>Traditional Technology Companies - &quot;They Know Nothing!&quot;</title>
    <link rel="alternate" type="text/html" href="http://asigra.dciginc.com/2008/05/traditional-technology-compani.html" />
    <id>tag:asigra.dciginc.com,2008://17.269</id>

    <published>2008-05-06T10:00:00Z</published>
    <updated>2008-05-06T10:00:00Z</updated>

    <summary>One of my favorite shows to watch is nightly reruns of Jim Cramer&apos;s Mad Money on CNBC. Aside from his crazy antics and &quot;They Know Nothing&quot; sound effect, he provides some good laughs just before I call it a night. Part of the reason that I find him so entertaining is that he is not necessarily in a position where he has to be politically correct - though some might argue he no longer has to be a good stock picker either, but that&apos;s a topic for another day.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="datamanagement" label="Data Management" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://asigra.dciginc.com/">
        <![CDATA[<p>One of my favorite shows to watch is nightly reruns of <a href="http://en.wikipedia.org/wiki/Jim_Cramer">Jim Cramer</a>'s <a href="http://www.cnbc.com/id/15838459">Mad Money</a> on <a href="http://www.cnbc.com/">CNBC</a>. Aside from his crazy antics and "They Know Nothing" sound effect, he provides some good laughs just before I call it a night. Part of the reason that I find him so entertaining is that he is not necessarily in a position where he has to be politically correct - though some might argue he no longer has to be a good stock picker either, but that's a topic for another day. </p>
<p>Anyway, what caught my interest on his May 1, 2008, broadcast was that he took on the Technology sector and he said that it is time to sell traditional technology stocks. At that point I began to listen more carefully because I have tended to disagree with his observations about technology in the past. Also, since my entire career is centered on covering technology in general and storage technologies specifically, I was curious about how in touch he was with this sector.</p>
<p>To summarize, Cramer feels that many technology companies in Silicon Valley have forgotten their engineering roots and are no longer providing game changing technologies. They now have become so focused on sales and have so many sales people running around trying to sell their products that their engineering departments have gotten lost in the shuffle. As a result, they are no longer focused on delivering products that solve today's immediate problems. Instead they are busy re-packaging yesterday's technology and re-branding it in such a way that it sounds like it solves today's problems.</p>
<p>Having worked as a storage engineer in a Fortune 500 and being involved in the day to day operations as well as having input into its storage buying decisions, I can certainly see his point of view. Sales representatives from traditional technology companies would constantly call on me selling products that did little or nothing to solve the problems that I was trying to solve at that time. </p>
<p>So in the last week I stopped by the place where I used to work just to see how things were going and little has changed except one thing: the people with whom I used to work. All of the people who bought into these 10+ year old technologies that solved yesterday's problems are pretty much gone. And by gone, I do not mean that they were promoted to better paying jobs or leadership roles within the organization. They were gone - as in laid off. Even more ironic, the current regime is now taking the same approach as the previous generation - trying to make old technologies solve today's problems. In that respect, my feelings echo that of Cramer's - "They know nothing!" </p>
<p>I say this not to disparage my co-workers or even traditional technology companies. But when I look at the type of problems that companies face today and how they are trying to fit square pegs (traditional technology) into round holes (today's problems), I have no doubt in my mind that a tsunami of change is gathering that will sooner or later&nbsp;sweep through enterprise organizations.</p>
<p>So do I agree with Cramer? Partially. He is right in the sense that traditional technology companies are behind the curve and that sales departments have overtaken engineering departments in too many of these companies. But I disagree with him that no innovation is occurring in technology - it's just from his vantage point he still can't see it. </p>
<p>I consider Cramer a good barometer of how close we are to a revolution of technology in general and data protection specifically. Cramer sees technology from a bird's eye view whereas I am up close and personal with it. So when I look at products like <a href="http://www.asigra.com/products/televaulting.php">Asigra Televaulting</a> and its Information Recovery Management platform, I know that this is one product that disproves Cramer's notion that no innovation is occurring in technology. Some of the cool, innovative features that Asigra is about to bring to market I will get into in a forthcoming blog entry.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Overland Storage&apos;s Rationale for Configuring Its REO Backup Appliance as a VTL</title>
    <link rel="alternate" type="text/html" href="http://overlandstorage.dciginc.com/2008/05/overland-storages-rationale-fo.html" />
    <id>tag:overlandstorage.dciginc.com,2008://28.268</id>

    <published>2008-05-05T10:00:00Z</published>
    <updated>2008-05-05T10:00:00Z</updated>

    <summary>Any time one looks at midrange backup appliances, the appliances are almost always NAS based. When configured this way, the backup appliance is attached to the local LAN it appears as a filer server to the backup server and files are backed up to a folder on that appliance. Though I initially called to speak to Overland Storage&apos;s Senior Product Manager, Jeff Graham, about REO&apos;s Dynamic Virtual Tape (DVT) technology, I first wanted to get some clarification on why Overland Storage&apos;s REO-series appliances are configured as Virtual Tape Libraries (VTLs) rather than as a NAS-based appliance.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="d2d2t" label="D2D2T" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="diskbasedbackup" label="Disk Based Backup" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="virtualtapelibraries" label="Virtual Tape Libraries" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="virtualization" label="Virtualization" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://overlandstorage.dciginc.com/">
        <![CDATA[<font size="2">
<p>Any time one looks at midrange backup appliances, the appliances are almost always NAS based. When configured this way, the backup appliance is attached to the local LAN, it appears as a filer server to the backup server and files are backed up to a folder on that appliance. Though I initially called to speak to Overland Storage's Senior Product Manager, Jeff Graham, about REO's <a href="http://www.overlandstorage.com/PDFs/REO_Family.pdf">Dynamic Virtual Tape</a> (DVT) technology, I first wanted to get some clarification on why Overland Storage's <a href="http://www.overlandstorage.com/US/products/backup_recovery.html">REO-series</a> appliances are configured as <a href="http://en.wikipedia.org/wiki/Virtual_Tape_Library">Virtual Tape Libraries</a> (VTLs) rather than as a NAS-based appliance.</p>
<p>Jeff provided a couple of reasons as to why <a href="http://www.overlandstorage.com/US/index.html">Overland Storage</a> currently configures its REO-series appliances as VTLs:</p>
<p>The first reason has to do with performance. Overland Storage has found that its VTLs consistently outperform NAS-based appliances. On NAS-based appliances you have to introduce a file system on the appliance which consumes some server overhead (processing and memory) that a block-based VTL does not consume. However, the larger benefit of using a REO is that it is optimized for storing the large sequential blocks of reads and writes found in backup traffic. Using a NAS, these blocks will fragment over time as the system distributes these blocks of data across the back end disk drives. Using a REO-series VTL, all of the blocks of data are kept together on a specific virtual tape cartridge that helps prevents this type of fragmenting from occurring.</p>
<p>The other reason is manageability. Using a NAS-based backup appliance, folders are created on the appliance's file system that is then used to store the backup data. The problem that can emerge in this scenario is that as if and when the folder fills up with data, the backup job can fail or hang. To allow the backup job to continue, administrators may need to increase the folder's size, manually direct the backup software to backup the data in another folder or manually give the OK to the backup software to overwrite older data in that folder. </p>
<p>Using a REO-series VTL, administrators have a couple of options within the backup software that minimize the likelihood of backup job failures. They can configure the backup software to migrate data from virtual tapes to physical tapes so as the REO VTL fills up, the backup software recognizes this and automatically moves the data from virtual tape to physical tape and then deletes the data on the virtual tape. Alternatively, companies can add more disk capacity to the REO and create more virtual tape cartridges for additional storage capacity. </p>
<p>Bottom-line, using a REO VTL companies do not need to change their backup structure. The backup software recognizes and treats the REO VTL like a physical tape library which minimizes the number of changes that companies need to make their backup infrastructure.</p>
<p>Now, having said all of this, Graham says that Overland Storage is investigating the possibility of adding a NAS option to their backup appliance. The rationale behind this move is that despite the fact VTLs are better suited for backup, there are still market forces at play. A NAS-based backup appliance is simpler for companies to understand since it does not require Overland Storage or its resellers to explain what a VTL is or how it. However, Graham did not indicate if Overland Storage actually plans to move in this direction or, if they are, when such an appliance might be released.</p>
<p>In a future blog entry, I'll delve more deeply into Overland Storage REO's DVT technology, how it works and what makes it unique in the market place.</p></font>]]>
        
    </content>
</entry>

<entry>
    <title>Replication and Global Deduplication Offered as Part of Quantum&apos;s DXi Architecture</title>
    <link rel="alternate" type="text/html" href="http://quantum.dciginc.com/2008/05/replication-and-global-dedupli.html" />
    <id>tag:quantum.dciginc.com,2008://25.267</id>

    <published>2008-05-02T10:00:00Z</published>
    <updated>2008-05-02T10:00:00Z</updated>

    <summary>Bringing backup data from remote and branch offices back to a home office is a particularly thorny problem that enterprises continue to face. Directly sending nightly full, incremental or differential backup jobs over a wide area network (WAN) connection back to the home office can saturate the WAN link and cause backups to exceed backup windows and result in failed backups. However the current procedure of backing up data to disk or tape at the remote site perpetuates the problem of how to most efficiently and securely transmit backup data back to the home office or disaster recovery site.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="deduplication" label="Deduplication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="diskbasedbackup" label="Disk Based Backup" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="replication" label="Replication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="tiereddatasystems" label="Tiered Data Systems" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://quantum.dciginc.com/">
        <![CDATA[<font size="2">
<p>Bringing backup data from remote and branch offices back to a home office is a particularly thorny problem that enterprises continue to face. Directly sending nightly full, incremental or differential backup jobs over a wide area network (WAN) connection back to the home office can saturate the WAN link and cause backups to exceed backup windows and result in failed backups. However the current procedure of backing up data to disk or tape at the remote site perpetuates the problem of how to most efficiently and securely transmit backup data back to the home office or disaster recovery site.</p>
<p>Placing disk-based backup appliances with data deduplication technology at the remote or branch office can be a good first step towards resolving this problem.&nbsp;Bt placing these appliances at the remote site companies keep backup traffic on their local LAN and off of the corporate WAN and&nbsp;backups complete more quickly and within the backup window. Further, the deduplication feature&nbsp;reduces the amount of backup data stored on the appliance so it can keep more data for longer periods of time. </p>
<p>Still, adding disk-based backup and deduplication to remote sites doesn't solve the challenge of consolidating business data within the core data center (home office) or ensuring all corporate data is secure for disaster recovery/business continuance purposes. In this case, one needs to ensure that the offering provides software that replicates data from the remote office back to the central office. </p>
<p>For companies with only one remote office or that just need to replicate data to a disaster recovery site, a number of appliances provide replication to like appliances at the remote site. Since the data is deduplicated before it is replicated, the amount of data that needs to be replicated from the remote office to the home office is minimized and only net new data needs to be replicated back to the target site. This also lessens the network bandwidth requirements and administrators can configure the replication to occur during periods of low network activity.</p>
<p>The difficulty that arises is when companies have multiple or global remote offices and each has a deduplicating backup appliance. If the deduplicating backup appliance only supports a one-to-one replication configuration, the company may need to purchase enough backup deduplicating appliances for the home office to match the number of deduplicating appliances that they have in the remote offices. This approach is very costly, consumes additional data center resources (power, cooling and floor space) and quickly becomes management intensive, especially in remote offices without adequate IT support.</p>
<p>Companies in these situations need to identify vendors that offer a data deduplication architecture that supports a many-to-one replication model and that can also globally deduplicate the data once it receives the data from the remote sites. By supporting a many-to-one configuration, companies only need one deduplicating backup appliance to receive the data from all of its remote sites. The global deduplication feature is needed since it can further reduce the amount of data that companies need to transmit and store on the deduplicating backup appliance at the home office.</p>
<p>This is the architecture that <a href="http://www.quantum.com/">Quantum</a> has adopted for its <a href="http://www.quantum.com/Products/Disk-BasedBackup/DXi3500/Index.aspx">DXi3500</a>&nbsp;and <a href="http://www.quantum.com/Products/Disk-BasedBackup/DXi5500/Index.aspx">DXi5500</a> appliances and its scalable <a href="http://www.quantum.com/Products/Disk-BasedBackup/DXi7500/Index.aspx">DXi7500</a> system to facilitate the deduplication, replication and optimal storage of backup data across an enterprise. In the next blog entry, I'll take a look at how Quantum's <a href="http://www.quantum.com/Products/Disk-BasedBackup/DXi-Series/Index.aspx">DXi-Series</a> supports this architecture and what configuration options this platform provides.</p></font>]]>
        
    </content>
</entry>

<entry>
    <title>InMage Uses Two Agents to Support the Confluence in Document Management Systems</title>
    <link rel="alternate" type="text/html" href="http://inmage.dciginc.com/2008/05/inmage-protects-sharepoint-pt2.html" />
    <id>tag:inmage.dciginc.com,2008://14.258</id>

    <published>2008-05-01T12:30:00Z</published>
    <updated>2008-05-01T12:30:00Z</updated>

    <summary>InMage addressed the challenge of system recovery through replication.  To do this they needed to be forward thinking about how they would replicate the data.  InMage DR-Scout uses two data protection agents.  The VX Agent manages volume/block based continuous data protection.  Their FX Agent manages file based continuous data protection and works as the scheduler within the InMage system.</summary>
    <author>
        <name>Joshua L. Konkle</name>
        <uri>http://www.dciginc.com/about/joshualkonkle</uri>
    </author>
    
    <category term="businesscontinuity" label="Business Continuity" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="continuousdataprotection" label="Continuous Data Protection" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="dataprotection" label="Data Protection" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="disasterrecovery" label="Disaster Recovery" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://inmage.dciginc.com/">
        <![CDATA[Continuation of our series on InMage's support of Microsoft SharePoint Portal Server.<br /><br />Part 1: <a href="http://inmage.dciginc.com/2008/04/inmage-protects-sharepoint-pt1.html">InMage DR-Scout protects Microsoft SharePoint Portal Server 2007, but document management is not new to InMage</a><br /><br /><a href="http://www.inmage.net/">InMage</a> goes one step further and allows you to group your servers so that you can recover them as a whole.&nbsp; To avoid mishaps and unintentional recovery, InMage configuration supports the grouping of systems to ensure recovery points occur across the correct servers.&nbsp; Supporting the grouped recovery of file and database data was somewhat challenging.&nbsp; <a href="http://www.inmage.net/management.html">Rajeev Atluri</a>, InMage CTO, says "We had to treat all three servers as a system, so my development team created a way to set consistency bookmarks across all three servers and manage it as a system."&nbsp; Atluri continued saying "the bookmarking was not the challenging part during development."&nbsp; According to Atluri, the challenging portion was determining the best way to support system recovery.<br /><br />InMage addressed the challenge of system recovery through replication.&nbsp; To do this they needed to be forward thinking about how they would replicate the data.&nbsp; InMage DR-Scout uses two data protection agents.&nbsp; The VX Agent manages volume/block based continuous data protection.&nbsp; Their FX Agent manages file based continuous data protection and works as the scheduler within the InMage system.<br /><br /><a href="http://www.inmage.net/how-it-works.html">InMage DR-Scout FX-Agent</a> manages the data recovery point bookmarking for consistent databases and consistency across servers in an n-tier group of supporting application servers.&nbsp; Most of the document management data protected by InMage is managed by their VX Agent, aka the host-off loaded block based continuous data protection agent.&nbsp; This leaves the FX-Agent free to manage bookmarks.&nbsp; However, the FX Agent handles the replication of files that are changed infrequently.<br /><br />Using the VX Agent on files that are rarely changed would be over kill.&nbsp; VX Agent replicates block level changes.&nbsp; Since template files in document management rarely change, or change infrequently, supporting them with VX Agent is unnecessary.&nbsp; The VX Agent provides the host-off loaded CDP.&nbsp; VX Agent is best used for files that are being created rapidly or changed regularly.<br /><br />VX Agent is what supports the <a href="http://www.dciginc.com/category/Continuous%20Data%20Protection">continuous data protection</a> for the Microsoft SQL server in a document management environment.&nbsp; The VX Agent replicates the database and the transaction log files using a block based replication method.&nbsp; It simply copies the blocks off the source system, leaving the target, or recovery system, to do all the reconstruction work.&nbsp; The recovery system has many free CPU cycles and memory to handle the management of the CDP recovery data.&nbsp; Therefore, off-loading the CDP heavy lifting allows the Microsoft SQL server being protected to work at maximum efficiency for its application requirements, such as Document Management.<br /><br />To provide the best system possible, the InMage development team supports the recovery point for document management using a combination of FX Agent and VX Agent.&nbsp; The FX Agent will manage the template files and recovery point bookmarking, while the VX Agent does all the hard work keeping up with the massive Microsoft SQL loads.&nbsp; InMage has been supporting this model since it first helped customers protect iManage and Livelink ECM - DOCS Open, several years ago.&nbsp; So supporting Microsoft SharePoint Portal Server as a document management system isn't new to InMage.<br /><br />Look for&nbsp;the final installment, Part 3: <a href="http://inmage.dciginc.com/2008/05/inmage-protects-sharepoint-pt3.html">The decision to support Microsoft SharePoint Portal Server</a>, later this month.<br />]]>
        
    </content>
</entry>

<entry>
    <title>NEC HYDRAstor Restores Focus on Optimized Data Management</title>
    <link rel="alternate" type="text/html" href="http://necam.dciginc.com/2008/04/nec-hydrastor-restores-focus-o.html" />
    <id>tag:necam.dciginc.com,2008://10.266</id>

    <published>2008-04-30T11:00:00Z</published>
    <updated>2008-04-30T11:00:00Z</updated>

    <summary>NEC&apos;s Vice President of Advanced Storage Products, Karen Dutch, recently brought out some salient points about storage management in her Spring 2008 SNW presentation, &quot;Defining Storage Solutions in the Data Center 2.0&quot;. Specifically, she described the features that new storage architectures should deliver in order to keep storage management manageable as storage growth in organizations continues. Of course, the not-so-subtle message is that NEC&apos;s HYDRAstor delivers on these new features.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="diskbasedbackup" label="Disk Based Backup" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="gridstorage" label="Grid Storage" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://necam.dciginc.com/">
        <![CDATA[<p>NEC's Vice President of Advanced Storage Products, Karen Dutch, recently brought out some salient points about storage management in her Spring 2008 SNW presentation, "<a href="http://www.snworlando.com/agendaS08/mon440c.html">Defining Storage Solutions in the Data Center 2.0</a>". Specifically, she described the features that new storage architectures should deliver in order to keep storage management manageable as storage growth in organizations continues. Of course, the not-so-subtle message is that NEC's <a href="http://www.hydrastor.com/">HYDRAstor</a> delivers on these new features. Here's how I see the HYDRAstor doing so.</p>
<ul>
<li><strong><em>Self managing.</em></strong> NEC's HYDRAstor architecture supports self-management through the dynamic addition of nodes (servers) that offer either more capacity or performance. As more <a href="http://www.necam.com/storage/HYDRAFAQ.cfm#2">Accelerator or Storage Nodes</a> are added to the HYDRAstor grid architecture, it non-disruptively redistributes data across old and new nodes to optimize performance and maximize data resiliency. This eliminates the normal processes of provisioning, sizing and data migrations that administrators have to perform, while alleviating the management overhead and costs associated with archive and backup processes. </li>
<li><strong><em>Data mobility. </em></strong>Data mobility comes more prominently into play when new Storage Nodes are added into the HYDRAstor grid storage architecture as well as during technology refreshes of Storage Nodes. As new Storage Nodes are added, the HYDRAstor re-balances data across existing and new Storage Nodes to simplify data management. As existing nodes are retired, data from an existing node is automatically migrated to a new node and, if companies have multiple sites, HYDRAstor supports the movement of data to alternative sites to create an enhanced level of data resiliency.</li>
<li><strong><em>Non-disruptive evolution. </em></strong>The HYDRAstor grid storage architecture addresses one of the most problematic aspects of storage management today: technology refreshes. As current storage systems age, usually the only option companies have is to purchase an entirely new storage system and then use either host or network based data migration tools to move to new storage controller architectures. Since HYDRAstor is based on a grid architecture, it can transparently evolve to newer technology simply through the introduction of new Accelerator or Storage Nodes based on the latest and greatest hardware technology. The HYDRAstor adds these new nodes into the grid while older nodes are marked for decommissioning and non-disruptively taken out of service.</li>
<li><strong><em>Scalability without trade-offs</em></strong>. A key problem with current storage system architectures is that you generally have to pick between performance, capacity and cost when scaling the architecture. Since HYDRAstor's Accelerator and Storage Nodes are based on industry-standard, off-the-shelf hardware, the typical hardware costs associated with proprietary storage hardware architectures are avoided. Since HYDRAstor also decouples performance (Accelerator Nodes) and capacity (Storage Nodes), users can scale one or both to accommodate whichever direction their storage environment grows.</li>
<li><strong><em>Enhanced, flexible resiliency.</em></strong> The HYDRAstor accounts for the growing possibility that today's RAID data protection architectures are insufficient when deduplication is used across 100s or 1000s of TBs of capacity. Administrators can define the level of data redundancy that is appropriate to their site and the HYDRAstor will dynamically distribute the data across the nodes to deliver the desired level of resiliency.</li>
<li><strong><em>Integrated data management services.</em></strong> The HYDRAstor comes with two sets of integrated data management services. The base level of services includes the automated management of the data, more efficient storage (deduplication) and enhanced data resiliency. Advanced services like replication, WORM, security, classification and search are other features that users can optionally license from NEC.</li>
<li><strong><em>Industry standard interface support.</em></strong> The HYDRAstor presents an industry-standard NFS and/or CIFS interface, so any Linux, Windows or UNIX server can archive data to it or, alternatively, any backup software can treat it as a disk cache and store data on it. </li></ul>The most compelling benefit of the NEC HYDRAstor grid storage architecture is that companies who adopt this architecture can start to take their focus off managing the storage infrastructure and focus more squarely on the data they are entrusted with protecting and managing. Today's businesses live and die by how well they manage their data and&nbsp;the management of data is still tied too closely to how well the hardware is managed. By meeting these new storage solution features of the Data Center 2.0, NEC HYDRAstor restores the focus of administrators back to optimal data management and protection. ]]>
        
    </content>
</entry>

<entry>
    <title>Blessing Hospital Finds the Magic in CommVault®&apos;s Simpana® SIS</title>
    <link rel="alternate" type="text/html" href="http://commvault.dciginc.com/2008/04/blessing-hospital-finds-the-ma.html" />
    <id>tag:commvault.dciginc.com,2008://22.265</id>

    <published>2008-04-29T12:35:00Z</published>
    <updated>2008-04-29T12:35:00Z</updated>

    <summary>One of the toughest aspects of being a storage administrator is finding reliable information that one can use to make decisions about competitive storage hardware or software products, especially when it comes to making decisions about newer technologies like Single Instance Storage (SIS). Even when data does become available, it is often too generic or not applicable to their situation so the individual is left in the position of either trusting the vendor&apos;s literature or doing some level of testing. In the case of Blessing Hospital&apos;s Technical Support Analyst II, Doug Barry, he opted for the latter.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="datamanagement" label="Data Management" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="datareduction" label="Data Reduction" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://commvault.dciginc.com/">
        <![CDATA[<p>One of the toughest aspects of being a storage administrator is finding reliable information that one can use to make decisions about competitive storage hardware or software products, especially when it comes to&nbsp;making decisions about&nbsp;newer technologies like <a href="http://www.commvault.com/products/advanced_features.asp?sid=10309">Single Instance Store</a> (SIS). Even when data does become available, it is often too generic or not applicable to their situation so the individual is left in the position of either trusting the vendor's literature or doing some level of testing. In the case of Blessing Hospital's Technical Support Analyst II, Doug Barry, he opted for the latter. </p>
<p>Barry was recently put in the situation where he began to doubt that his data protection software was providing the level of protection that <a href="http://www.blessinghospital.org/pages/default.asp?NavID=398">Blessing Hospital</a> needed in order to recover its data. So before anything seriously bad happened to its data, he felt that a change in data protection software was required. However as he started to evaluate contending enterprise data protection software products, he could not ascertain which one was best suited for Blessing Hospital so he decided to bring in each of the contending products and test them.</p>
<p>When testing the products, he essentially put them through what he described as a drag race. Each product was loaded on the same server hardware and had to back up the same amount of data to disk. However what made Blessing Hospital's data unique is that it used a PACS (<a href="http://en.wikipedia.org/wiki/Picture_archiving_and_communication_system">Picture Archiving and Communication System</a>) system to create and manage its imaging files. The PACS system creates a large number of files that only change infrequently but need to be kept online for ready access to meet specific HIPAA regulations.</p>
<p>A particular vexing problem he ran across when backing up files on the PACS system is that periodically the PACS management database would touch a large number of files. Though none of the content in any of the files would change, the PACS system would in some way change permissions on the files. What he discovered in his testing is that the different backup software packages would interpret these changed file permissions differently. Some products would conclude that the files had changed and needed to be backed up again. This would dramatically increase backup times and the amount of data backed up.</p>
<p>What Barry specifically found noteworthy was how much the different backup software products differed in how they performed the file scan. In most cases, the larger the server, the larger the file system it had; the larger the file system, the longer it took to scan. In this aspect, the CommVault® Simpana® software&nbsp;suite distanced itself from the competitors in his environment. "The scan up front is where the magic is," says Barry.</p>
<p>Barry came to understand that CommVault's Simpana software is so effective in scanning files&nbsp;during backups because of how its intelligent agents interact with CommVault's underlying Single Instance Store (SIS) database. Its intelligent agents don't just look at a file's permissions but at the file's make-up. As the agent scans the file, if it determines the file permissions have changed but the file has not, CommVault knows it does not need to backup the file again. This, says Barry, resulted in backup times that were about half of what he achieved using Symanctec's Backup Exec.</p>
<p>Barry said the choice eventually came down to EMC Networker and the CommVault Simpana Suite. Even though he considers Blessing Hospital an EMC shop and has a lot of respect for EMC, <a href="http://commvault.com/news_story.asp?id=378">he chose CommVault</a>. Since his implementation of CommVault software, he finds that he has reduced the total amount of storage he stores on the back-end as well as the time it takes to do backups.</p>
<p>Equally important is what Barry said as I was finishing up my call with him. While single instance stores and reduced backup times are great, data restoration is where the rubber meets the road. In this respect, he has seen restore times decrease from an hour to 15 - 20 minutes.</p>
<p>Barry's methodical approach to selecting the appropriate data protection product for Blessing Hospital deserves some accolades and not only because he choose the CommVault Simpana software. No matter how much is written about a product or how many case studies one reads, one never really knows for sure (even the vendor) until you put the product through the paces in your environment. As Barry found out, SIS was a feature that he&nbsp;may never&nbsp;have thought to look for in the literature or ask of the vendor,&nbsp;but through testing&nbsp;it&nbsp;ended up being the feature that&nbsp;separated the CommVault Simpana software from the pack.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Overland Storage Layers in Disk-Based Data Protection</title>
    <link rel="alternate" type="text/html" href="http://overlandstorage.dciginc.com/2008/04/overland-storage-layers-in-dis.html" />
    <id>tag:overlandstorage.dciginc.com,2008://28.264</id>

    <published>2008-04-28T13:00:00Z</published>
    <updated>2008-04-28T13:00:00Z</updated>

    <summary>In case no one has noticed lately, the number of ways in which companies can configure disk-based storage systems to protect their data has multiplied significantly. This fact was brought clearly into focus by a pre-recorded video lecture that I recently watched on Overland Storage&apos;s Tiered Data Protection (TDP) website.</summary>
    <author>
        <name>Jerome M. Wendt</name>
        <uri>http://www.dciginc.com/about/jeromemwendt</uri>
    </author>
    
    <category term="d2d2" label="D2D2" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="deduplication" label="Deduplication" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="diskbasedbackup" label="Disk Based Backup" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="tiereddatasystems" label="Tiered Data Systems" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://overlandstorage.dciginc.com/">
        <![CDATA[<font color="#000080" size="2"><font size="2">
<p>In case no one has noticed lately, the number of ways in which companies can configure disk-based storage systems to protect their data has multiplied significantly. This fact was brought clearly into focus by a pre-recorded <a href="http://www.overlandstorage.com/tdp/tdp101.htm">video lecture</a> that I recently watched on <a href="http://www.overlandstorage.com/US/index.html">Overland Storage</a>'s <a href="http://www.overlandstorage.com/tdp/">Tiered Data Protection</a> (TDP) website. Though I think most users are well aware that disk is now a viable target for backup, it didn't really hit me until I watched this video by Overland Storage's VP of Worldwide Sales, <a href="http://www.overlandstorage.com/US/aboutovrl/bios.htm">Bob Farkaly</a>, just how many configuration options are available when using disk as a backup target.</p>
<p>During the <a href="http://www.overlandstorage.com/tdp/tdp101.htm">presentation</a>, "Professor" Farkaly took the viewer (in this case, me) through the disk-based offerings that Overland Storage has for backup. These include:</p><b><font size="2">
<ul>
<li><strong>Disk-as-Disk: the <a href="http://www.overlandstorage.com/US/products/reo1500.html">REO 1500</a>, <a href="http://www.overlandstorage.com/US/products/reo4500.html">REO 4500</a> and <a href="http://www.overlandstorage.com/US/products/reo9100.html">REO 9100</a> products</strong>.</b> It seems that with the incessant noise one hears about deduplication every time you read or hear about something storage related, it's easy to forget about the fact that using disk-as-disk is not necessarily a bad thing. Deduplication may incur a write penalty when backing up data, a read penalty when retrieving data and, more than likely, an up-front financial penalty when purchasing and licensing the deduplication technology. Though Overland Storage offers a deduplicating backup appliance (which I'll get to in a second), these versions of the REO peel away some of the complexity and cost and give users options to present the systems as either disk or virtual tape libraries (VTLs) through iSCSI and FC interfaces.</li><font size="2">
<li><strong>Disk with Compression: The <a href="http://www.overlandstorage.com/US/products/reo4500.html">REO 4500C</a> and <a href="http://www.overlandstorage.com/US/products/reo9100.html">REO9100C</a>&nbsp;products. </strong>I have to admit this version of Overland Storage's disk family caught me a bit by surprise. While I am aware that most deduplicating disk appliances compress data after it is deduplicated, this is the first disk-based appliance that I can remember encountering that offers hardware based compression. Though I need to get some more details on how this feature works and its impacts on price and performance, this seems like an almost no-brainer upgrade if you are already leaning towards using disk-as-disk in your backup and archive plans. If my past experience serves me correctly, using hardware based compression incurs only a nominal read-and-write penalty and most users should be able to safely and confidently double the amount of data they store on these appliances.</li>
<li><b><font size="2">Disk with Deduplication: The <a href="http://www.overlandstorage.com/US/products/reo9500D.html">REO 9500D</a>. </b>Obviously Overland Storage isn't stupid and to compete in this marketplace, it needs to offer a disk-based storage system that supports deduplication. Yet what I found interesting in watching the video is that Farkaly did not actively promote using the REO 9500D as the initial backup target. While Farkaly did not preclude the 9500D as a possible target, the approach he recommended is what I privately have started to adopt: a "Backup to native disk first and then copy the data to a deduplicating appliance second". Why? Not because I think deduplication is bad. But when I was an end-user, a major concern of management on the daily 7:00 am operation calls is what caused last night's backups to fail. No one ever asked what the deduplication ratio was. While most deduplication appliances likely do an OK job the first 60, 90 and maybe even 120 days, I think companies still need to exercise caution about deploying deduplication too quickly in their production backup environments.</font></li></ul><font size="2"><font size="2">
<p>The videos on Overland Storage's TDP website are definitely worth the time to watch for those who are looking to learn more about tiered data protection as well as those who also want a better understanding of what is the best type of disk system to introduce into your backup process. What you read in the press can sometimes leave one with the impression that deduplicating all of your backup data is the only way to go. Longer term it probably is, but for now the journey of introducing disk into the backup process has just begun and Overland Storage's strategy of "Walk, then run" when introducing disk into the backup process is one&nbsp;worth following.</p></font></font></font></font></font></font>]]>
        
    </content>
</entry>

<entry>
    <title>Estorian LookingGlass indexing supports open archive for local, state and federal governments</title>
    <link rel="alternate" type="text/html" href="http://estorian.dciginc.com/2008/04/estorian-open-archive-for-government.html" />
    <id>tag:estorian.dciginc.com,2008://23.263</id>

    <published>2008-04-28T10:00:00Z</published>
    <updated>2008-04-28T10:00:00Z</updated>

    <summary>Accessing the history of any department within a branch of government can seem trying at times.  For example, the technology used by the Office of the President required end users to decide which emails were necessary for long term preservation, as opposed to storing all of the data, regardless of personal interpretation.  Therefore, accessing the unabridged version of the email records for the Republics highest office was hampered by user precision and recall, not technology.  Where precision represents the number of correct hits in a return set of specified length; recall represents the number of correct returns relative to the total number of possible correct returns.  Specifically, deciding which emails should and shouldn&apos;t be kept for long term retention is best left up to software and open records managers.</summary>
    <author>
        <name>Joshua L. Konkle</name>
        <uri>http://www.dciginc.com/about/joshualkonkle</uri>
    </author>
    
    <category term="electronicdiscovery" label="Electronic Discovery" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="emailarchive" label="eMail Archive" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="search" label="Search" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://estorian.dciginc.com/">
        <![CDATA[Government, specifically the US Federal, State and Local Government is challenged with a requirement to preserve information for the duration of the Republic.&nbsp; The duration of the Republic already spans hundreds of years.&nbsp; The first 175 years stored the Republics business on paper.&nbsp; However, since the 1950's new types of storage media have emerged.&nbsp; That media maintains the historical audio, video and text of the Republic.&nbsp; It is incumbent upon the US Government to make that history available, as needed, to the constituents of the United States of America.<br /><br />Accessing the history of any department within a branch of government can seem trying at times.&nbsp; For example, the technology used by the Office of the President required end users to decide which emails were necessary for long term preservation, as opposed to storing all of the data, regardless of personal interpretation.&nbsp; Therefore, accessing the unabridged version of the email records for the Republics highest office was hampered by <a href="http://www.dciginc.com/2008/03/david-baskin-recommind-pt1.html#precision-recall">user precision and recall</a>, not technology.&nbsp; Where precision represents the number of correct hits in a return set of specified length; recall represents the number of correct returns relative to the total number of possible correct returns.&nbsp; Specifically, deciding which emails should and shouldn't be kept for long term retention is best left up to software and open records managers.<br /><br />In order for a manager who is responding to a Federal Open Information Act (FOIA) request to find data, the data must be stored in an open format.&nbsp; Open formats are critical for all agencies within the Government, because they never know when data may be requested.&nbsp; If the data is proprietary and the request is 50 years from now, it's possible the developer or the data-type is long retired or deceased.&nbsp; Therefore, accessing the data may become impossible, unless a computer with the right software is under maintenance at <a href="http://www.si.edu/">The Smithsonian</a>.<br /><br />If you are using <a href="http://www.estorian.com/">Estorian LookingGlass</a> you can be assured that your data is accessible.&nbsp; Data accessibility is maintained by <a href="http://estorian.dciginc.com/2008/04/spherical-indexing-outside-olap-cube.html">LookingGlass Spherical Indexing</a> solution, which is based on open format SQL queries.&nbsp; LookingGlass takes a standard approach to storing the data within an open storage system, such as NetApp NAS or <a href="http://www.permabit.com/">Permabit Enterprise Archiving</a>.&nbsp; The standard data approach, used by most of the vendors supporting an archive, is to take the Microsoft MSG files and store them in collections of ZIP files.<br /><br />The Microsoft MSG files are the Message file data-type created by Microsoft Outlook.&nbsp; Granted, the data-type may have been created by Microsoft, but it has been in use for over 13 years.&nbsp; Specifically, Microsoft MSG files were introduced when Microsoft released Windows 95 Preview Program (April 1995).&nbsp; Since then, thousands of developers have been manipulating and managing MSG files, it is well known and can be considered a de facto standard.&nbsp; Individual MSG files are a suitable format for email and email meta-data, but billions of immutable MSG files create a performance and storage challenge for all systems.<br /><br />To address the issue of backing up millions of individual MSG files, LookingGlass incorporates standard zip file support in to the storing of its archived email.&nbsp; The ZIP file format, made popular by <a href="http://en.wikipedia.org/wiki/Phil_Katz">Phil Katz (d. 2000)</a> was released into the open format in 1989.&nbsp; Despite Mr. Katz death, the open format creates assurances the data type will continue to be supported within LookingGlass well in to the future.<br /><br />Look