MCPMag.com

Sign up for our newsletter.

I agree to this site's Privacy Policy.

Weekly quickTIP

Hooray for Transactional Integrity!

Image-level backup consolidates that server's state into one nice and tidy bundle.

Image-level backups are a great benefit gained when an IT environment moves to virtualization. These single-file backups allow the state of an entire server to be restored without all the thousand-file nastiness required in a traditional backup. Lose one key file with old-school backups and you're staring down a road of rebuilding instead of a restore. Conversely, an image-level backup consolidates that server's state into one nice and tidy bundle.

All this sounds fine and well until you start to dig a little deeper into the processes whereby image-level backups go about quiescing that server prior to a backup. You see, pretty much every hypervisor-based virtualization solution has the capability to quiesce the server prior to starting the backup. This "snapshotting" mechanism ensures that the restored file has file system integrity.

But there's always been a problem with transactional databases that ride atop that file system. Though any traditional backup tools could quiet the server, none to date could reach into that server to tell these databases they needed a time out as well.

The result of this omission is that although image-level restores usually get your server back on-line relatively quickly, your Exchange, SQL and other transactional databases have the chance to return to service in an inconsistent state. This means running the necessary database utilities -- like ESEUTIL for Exchange -- to bring the database back to health.

Until now. I recently discovered that VizionCore's vRanger Pro v3.2 includes support for directly communicating with a Windows virtual machine's Volume Shadow Copy Service (VSS). This communication allows the backup engine to instruct the database to pause at the correct point in the backup so that the database will not return from a restore in an inconsistent state.

The vRanger documentation includes an in-depth discussion of how this works with VSS. The process is complex and yet elegant in its implementation. Now, we administrators get to shout for joy knowing that with the right products our virtualized databases can maintain transactional integrity -- and therefore complete restorability -- while we do our nightly backups.

About the Author

Greg Shields is a senior partner and principal technologist with Concentrated Technology. He also serves as a contributing editor and columnist for TechNet Magazine and Redmond magazine, and is a highly sought-after and top-ranked speaker for live and recorded events. Greg can be found at numerous IT conferences such as TechEd, MMS and VMworld, among others, and has served as conference chair for 1105 Media’s TechMentor Conference since 2005. Greg has been a multiple recipient of both the Microsoft Most Valuable Professional and VMware vExpert award.

comments powered by Disqus

Reader Comments:

Mon, Apr 21, 2008 Anonymous Anonymous

Wow, cool article. I was a little surprised you focused on vRanger though. I would have writen the article on System Center Data Protection Manager 2007. DPM gives you this capability with some of the enhancements they included in 2007. One such enhancement is the Virtual Server Volume Shadow Copy Service (VSS) writer, which enables System Center Data Protection Manager 2007 to protect virtualized environments. Check it out, you won't be disapointed.

Ed

Add Your Comment Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Comment:
Please type the letters/numbers you see above