Re: [ADSM-L] deduplication status

39 is actually not a great number; it means you are getting less than 2 for 1 
dedup.

Unless you have backups running hard 24 hours a day, those dedup processes 
should finish.
When you do Q PROC, if the processes have any work to do, they show as ACTIVE, 
if not they show IDLE.

I'd think that at some point during the day, you should have at least one of 
them go idle, then you know you have been as aggressive as you can be.  If not 
I'd add processes until you can see some idle time on at least one of them.

Just my 2cents.
W


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Tyree, David
Sent: Monday, July 28, 2014 11:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] deduplication status

                I've searched the archives but I can't really find the answer 
I'm looking for.
                Running on version 6.3.1.0.
                I have a primary storage pool running dedup. I run the "ID 
DEDUP" command, the reclamation command, and the expiration command throughout 
the daily cycle.

                I run the Q STGP F=D command to check the "Duplicate Data Not 
Stored" numbers and I'm getting 39% right now. Which sounds pretty good, I 
guess.

                My question is how to I tell if I'm running the dedup processes 
aggressively enough. Can I do something to increase that number?
                I realize that the dedup processes are never really finished 
because of the new data that is constantly coming in and old data is getting 
expired.

                Is there something I can look at to be able to tell if I need 
to adjust the ID DUP commands I'm running? More processes, less processes or 
change how long I run it...

                Something that tells me how much data has not been deduped yet 
versus how much has been processed.

                Is that kind of info accessible?

David Tyree
System Administrator
South Georgia Medical Center
229.333.1155