On 03/01/2012 02:15 AM, Steven Langdale wrote:
It looks like Allen has had a better experience, but in my recent
experience with ProtecTIER, 2 logical libraries with NetBackup& TSM
feeding in the "same data" (we were migrating to TSM) the data WAS
"different" and dedupe ratios dropped like a sto
It looks like Allen has had a better experience, but in my recent
experience with ProtecTIER, 2 logical libraries with NetBackup & TSM
feeding in the "same data" (we were migrating to TSM) the data WAS
"different" and dedupe ratios dropped like a stone.
As for using it as a justification to migra
Thanks all.
Could "better deduplicaion ratio" be one of justifications to migrate
BackupExec systems to TSM? Actually half of our systems use non-TSM
solutions and we (TSM guyes) would like to entice them to a single solution
for the whole enterprise. You know everybody resist change!
On 02/23/2012 04:11 AM, Daniel Sparrman wrote:
Yes, you can share it with multiple backup applications by defining
more than 1 library. Each library needs it's own dedicated drives
though (as with all VTL's).
Since TSM& BackupExec writes information differently to the VTL,
data backed up usin
Hi
Yes, you can share it with multiple backup applications by defining more than 1
library. Each library needs it's own dedicated drives though (as with all
VTL's).
Since TSM & BackupExec writes information differently to the VTL, data backed
up using TSM wont be deduped against data backed up
