Hello Stefan,
I do not think you can use client compression and de-duplication together.
De-duplication is skipping all data compressed by TSM Client or TSM Server.
By the way, de-duplication process is trying to reduce files, compressed by
operating system (for example, *.Z, *.zip, AIX system ima
Greetings,
The size of the volumes can be very relevant. Any of us who has
managed a large virtual tape environment has run into this same issue.
If you have 10TB in your pool, it would be a tempation to define 100
volumes of 100GB. That might not create any problem if you have a
relatively s
I don't remember seeing this in writing anywhere. I this a fact, or a
supposition? Does deduplication in TSM skip all data that has been
client compressed? I could see how that might affect the deduplication
algorithm, but if that is true, the customer is left with an unfortunate
deal with the D
Roger,
If you find a solution to that last problem, i.e. only 24 hours in a
day, please post it to the list. :-)
I am trying to understand the schedule you present. Are you saying
you run expiration at the same time your backups, backup stgpools, and
migration are running? Or do you run
On Sat, 29 Aug 2009, Stefan Folkerts wrote:
>TSM guru's of the world,
>
>Also client compression, does anybody have an figures on how this effect
>the effectiveness of deduplication?
>Because these are both of interest in a filepool, if deduplication works
>just as good in combination with compress
Greetings,
I already responded to a similar post today that was also about
client compression, and I don't want to waste listserv bandwidth beating
the same drum, but... I am going to. If you are sick of this subject,
don't read further.
What we mean by "best" is highly subjective. Hard
I do know from the beta program that 2 rules of files being skipped during the
de-dup (identify) process are:
1. Encrypted files are skipped.
2. Small files. I think < 4k was the rule.
There are some STE webcast events on De-dup that might list all the reasons.
And then there's the DSMSERV.OPT
Well, I"m confused again.
Just set up TSM for a customer with a TS3500 (3584).
Three logical partitions in the library, one for a for VTS, 1 for mainframe,
1 for TSM.
ALMS installed, VIO enabled.
TSM partition has 4 drives, 255 VIO slots.
Have assigned the TSM tape volser range to the TSM partition
