How 'more with less' puts your data at risk

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

Become An Insider

Sign up now and get FREE access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content. Learn more.

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.

To continue reading this article register now

Notice to our Readers
We're now using social media to take your comments and feedback. Learn more about this here.