I've been using container pools for a while on one of our prod servers (built
with container pools) and in test, but in the last few months since upgrading
to 8.1.5 on all of my servers I created a new container pools on all of the
servers and switched everything over to backup to the new pools.
I echoed Stefan, Rick and Luc... 110%
We've been using the directory-container-pools for about 2 years and work
great!
And yes, plan accordingly and monitor the TSM-DB size as you migrate
backups to the container-pools
--Alex
On Wed, Sep 26, 2018 at 7:31 AM Michaud, Luc [Analyste principal -
Container pools saved the day here too !
On our legacy environment (TSM717), adding dedup to our seqpools just bloated
everything, until it became unbearable.
Migrating nodes to the new blueprint replicated servers w/
directory-container-pools solved a lot of our issues, especially with
copy-t
I have to second Stefan's position, while they have a few minor shortcomings,
for me most were only relevant to the initial build/migration. For me the
upside compared to file device class storage is phenomenal.
Initially I had reservations but now cannot imagine going back.
-Rick Adamson
---
Zoltan,
I'm not sure I understand your issues, we use directory containerpools for
all but a few of our Spectrum Protect customers and it's miles ahead of
what the fileclass-based storagepool bring in terms of performance,
Spectrum Protect database impact (size wise). Yes, it isn't capable of
cert
