Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Backup is not Archiving

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends


Report Excerpt

The ECM Suites Report 2008 looks at... ECM/Documentum 6 Web Content Management

"There are many advantages to storing content as native objects (several other CMS packages, like Zope and Ingeniux, dod this), but you should understand that this is the first of several places where you enter a kind of netherworld of Documentum-specific interfaces and query languages. For example, you access the Content Server using "DQL," short for Documentum Query Language. If Content Server is storing XML, you access it through "XDQL," rather than standard XML can openers like XPath and XQuery. "

(p. 158)

More about The ECM Suites Report 2008

 

TrendWatch Blog

Backup is not Archiving

29-Nov-2007

Question: What's the difference between a backup and an archive?

Answer: A backup is designed to manage short-term risk and provide some kind of facility for disaster recovery -- an important activity for sure. An archive on the other hand is designed to help manage long term risk, ensuring that historical data can be accessed and remains authentic either for the business user or (heaven forbid) an auditor or lawyer. Both involve storage media, and both involve a policy to be instituted and enacted. In the case of backup the policy might simply dictate backing up data overnight to tape, and rotating tapes once a week. An archive on the other hand will likely have a far more rigorous set of policies around media longevity, data authenticity, and security -- alongside detailed policies relating to retention periods and compliance requirements.

In other words: just copying everything to a storage medium on a regular basis (as one does a backup) is actually a thousand miles away from having a records and retention policy that drives a corporate archive.

2008 will see ECM vendors aggressively trying to move into the archiving sector. It's a move driven (as all meaningful market dynamics are) by buyer demand. At the moment, demand stems less from a full understanding of retention and archiving, and more from the need to shift ballooning volumes of e-mails (e-mails that may well become the focus of a laywer at some future date), that are swamping mail servers. And once the e-mail challenge has been tackled, the equally massive job of archiving corporate documents will start.

- Submitted by: Alan Pelz-Sharpe, Analyst

All ECM Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (customer service)

+1 617 763 5336 (int'l customer service)

Fax: +1 214 242 3048