I know 8.1.4.0 has a defrag option, that moves the content to existing
containers that have space instead of moving the container as a whole, that
might be a solution.
I do think it's new for 8.1.4.0 and I don't think there is a way to get rid
of them before that release.
On Wed, Feb 21, 2018 at
I don’t know, nor do I care one bit. What I care about are those empty
containers that I can’t get rid of.
> On 21 Feb 2018, at 16:39, Loon, Eric van (ITOPT3) - KLM
> wrote:
>
> Hi Remco,
> Could it be that your SQL Server admins are compressing the data which is
> send to the TSM server? If
#IBMStorage is keeping the data protection and availability momentum going
this year with more enhancements and more ways to reuse that data. The new
announcements of IBM Spectrum Protect V8.1.5 and IBM Spectrum Protect Plus
V10.1.1 provide you with more secure capabilities for your secondary da
Hi Remco,
Could it be that your SQL Server admins are compressing the data which is send
to the TSM server? If I'm correct you can turn on compression on the SQL server
itself as well as on the TDP/API client.
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
-Original Message--
we’re getting about 0% dedup savings (3 * full, plus diffful, plus log backups)
and about maybe 20% compression savings.
> On 21 Feb 2018, at 16:03, PAC Brion Arnaud wrote:
>
> Hi Remco,
>
> No direct answer to your question, but your statement " dedup on SQL is
> non-existant" is kind of ast
Hi Remco,
No direct answer to your question, but your statement " dedup on SQL is
non-existant" is kind of astonishing me ...
Here an extract of the output for "q stg DIR_SQL f=d" on my server (you guessed
it, this stgpool is dedicated to SQL backups ...) :
Deduplication Saving
Hi All,
today I ran into something new: an empty directory container. No, not an empty
directory, and empty container. We’re moving SQL backups from directories to
traditional tape, dedup on SQL is non-existant, so tape is cheaper, and after
the expiration period the container pool should be em