RANT: VMWare Data Recovery Manager

1 06 2009

I just got VMWare Data Recovery Manager all configured. MAJOR GLARING PROBLEM. It only does block change tracking if you are backing up a vm that was created in vSphere 4.0. So for ALL your vms that were created in 3.5 (yeah, that would be all of them), it sends the entire snapshot every time the backup runs. For 4.0 created vms, it will send just the changes every backup. Sure, the data is deduped on the Data Recovery Manager, but ALL that data is still sent over the wire before it gets deduped. Dont they realize that we have other backup procedures in place that could be using network bandwidth during the “backup window”? I realize that this is very similar to using something like a Data Domain box as your backup target, but this is SO CLOSE to being an easy way for a set it and forget it, type vm backup. I dont want to worry about my network bandwidth getting totally hammered during the backup window, thank ya.

Maybe I am way off base here….If all your hosts can “see” the vmfs volume for the target of your backups, do they write directly to the store over their isci nics? Or do the snapshots have to flow “through” the data recovery manager vm? Im thinking its the latter…What part of my network is getting hammered when I hit GO?

Advertisements

Actions

Information

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




%d bloggers like this: