« Have VMware? An easy way to potentially win an iPad 2 | Main | Boston 2011 Marathon »

April 18, 2011

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e552e53bd2883301538df2ee7c970b

Listed below are links to weblogs that reference vSphere Changed Block Tracking **on Restore**:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Jason

OS switch for v6? Can this be done and preserve the datastore/config on a current v5 install?

I assume (hope) that Gen 1 hardware is still supported.

Sketch

Finally a TECHNICAL deep dive... I knew you still had it in you, Chad. Good job!

INDStorage

According to my notes, Gen1 is not supported. Gen2 and up for Avamar 6.

Dane Truhett

Great article! I do have a question that maybe someone of your expertise can answer. What would you estimate to be a reasonable amount of data a person could restore with Avamaron a straight client based restore. We are seeing VERY slow restore times on Avamar like a half a gig per minute. Literally 30 gig an hour. No way we can restore our large DBs for disaster recovery this way. You got any thoughts on this? The restore is a SQL database but we are also seeing slow times on non SQL....

The comments to this entry are closed.

  • BlogWithIntegrity.com

Disclaimer

  • The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC. This is my blog, it is not an EMC blog.

Enter your email address:

Delivered by FeedBurner