How 'more with less' puts your data at risk

FREE

Become An Insider

Sign up now and get free access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content from the best tech brands on the Internet: CIO, CITEworld, CSO, Computerworld, InfoWorld, ITworld and Network World. Learn more.

Hasty development and implementation schedules have sidelined such maintenance tasks as backup testing. How long can they stay there?

If I picked up the phone, called any IT administrator I know, and asked what technical part of their job they like the least, the answer would almost invariably be backups.

Nobody likes backups. In the complex world of mixed physical and virtual environments, it sometimes seems nearly impossible to build a backup regimen that just works every time. Instead, it's much more common to see a few resources fail to back up or to get some kind of ambiguous error that takes hours to properly diagnose and resolve.

[ Read Matt Prigge's High-Availability Virtualization Deep Dive Report. | Discover the key technologies to speed archival storage and get quick data recovery in InfoWorld's Archiving Deep Dive PDF special report. ]

Too often, the amount of effort required to yield even the appearance of a consistently successful backup rotation takes so many hours that it crowds out other crucial tasks -- such as testing.

Recently, I got my hands on a survey commissioned by Veeam, a developer of backup tools for virtualized VMware environments, that polled 500 CIOs of companies with more than 1,000 employees. Like many commissioned surveys, this one tilts toward being a sales tool for the sponsor, but it also reveals shocking findings that underline the troubles many organizations have with backups. Several results jumped out at me:

To continue reading, please begin the free registration process or sign in to your Insider account by entering your email address:
From CIO: 8 Free Online Courses to Grow Your Tech Skills
Join the discussion
Be the first to comment on this article. Our Commenting Policies