We have multiple VTL's and chose to use them as a Storage Unit Group.
They are capable of deduplication.  The vendor states that the amount of
data/VTL increases the dedupe time and we are struggling to complete
this process.  Supposedly the time to dedupe has nothing to do with the
dedupe ratio - it is simply how much data that resides in a VTL (post
Dedupe + new data).  I see 2 VTL management philosophies and would like
your ideas for a 3rd or a hybrid idea.


The easiest to manage is to spread the data across all VTL's using NBU's
balancing algorythms.  However, even after dedupe processing, I expect
that over time the full backup will exist in every VTL.  Since total
storage consumed has an impact on the dedupe process, I want to find an
alternative.  That's where I need your help.

I've been thinking of the old college question of what is the best way
to fill a jar with rocks, pebbles, & sand.  Spread out your 1 TB Rocks
equally, Fill with 500 GB pebbles, and then define where the remaining
sand goes?

Storage Unit Groups don't appear to be the best fit for VTL's if you
want efficiency.

I would love to hear your feedback and ideas !!

Brian

This e-mail and any attachments may contain confidential information of 
Northwestern Mutual. If you are not the intended recipient of this message, be 
aware that any disclosure, copying, distribution or use of this e-mail and any 
attachments is prohibited. If you have received this e-mail in error, please 
notify Northwestern Mutual immediately by returning it to the sender and delete 
all copies from your system. Please be advised that communications received via 
the Northwestern Mutual Secure Message Center are secure. Communications that 
are not received via the Northwestern Mutual Secure Message Center may not be 
secure and could be observed by a third party. Thank you for your cooperation.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu