Jump to content

Recommended Posts

Posted
I've been using that for my servers but didn't think it backed up the exchange mailboxes. I'll take a look at this tutorial though for sure if they have a way to use it. Thanks a ton Arthur!
Posted
I'm using WSB in my quasi-test environment and it seems to work fine. Not that I trust it as far as I could throw it, it's probably the best free option. Without elaborating further, backup should be the last thing you go cheap on.
Posted

We use both Windows backup and for offsite, Attix5. Both use the VSS copy technique.

 

My understanding is that the VSS writer mechanism is built into a number of products, including (latest) Exchange and SQL server and thus, written by the people who know about the data being backed up. The backup solution then initiates the writer to do its thing then reads the data in a standard way irrespective to the product being backed up. This is then backed up.

 

I feel that this mechanism will work equally well whether or not its MS Backup or another paid product, ie Attix5. The fact that the product itself produces the backup data ensures that it is backing up pertinent data, something that another product, not using VSS, may have to specifically code for and thus may have to match any changes to underlying data structures for different product versions.

Posted
My understanding is that the VSS writer mechanism is built into a number of products, including (latest) Exchange and SQL server and thus, written by the people who know about the data being backed up. The backup solution then initiates the writer to do its thing then reads the data in a standard way irrespective to the product being backed up. This is then backed up.

 

I feel that this mechanism will work equally well whether or not its MS Backup or another paid product, ie Attix5. The fact that the product itself produces the backup data ensures that it is backing up pertinent data, something that another product, not using VSS, may have to specifically code for and thus may have to match any changes to underlying data structures for different product versions.

 

You are correct in that snap is built in to SQL, Exchange and Server 2008(R2) these days, and that applications simply talk to the VSS Service and VSS reader/writers to do the backup. The difference, however, is how the applications interact with the backups. For example, WSB will simply dump a vhd of the drive at a particular point in time.

 

The difference, however lies in the post-backup usability. Restoring with WSB is a cinch, however, you must restore to a recovery mode database. Anyone who's had to do this before knows while it is doable, it's a right pain and to be avoided. Some alternate solutions (read: paid) that also use VSS include things like (but not at all limited to) granular mailbox recovery, journaling that actually works, and so on and so forth. I've used StorageCraft's ShadowProtect and CommVault Simpana. Both are fantastic products. They do require a bit of an outlay but the benefits far outweigh the costs.

 

You may at first think WSB is cutting the mustard, but I think you'll find in time you need a more comprehensive suite.

 

My 2c.

Posted
Im just using the built in Windows Server Backup. It is now Exchange aware :-)

 

It is indeed and works well :) I've used it since I got my Exchange box :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...