Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

6330

July 13th, 2012 07:00

DataDomain Dedup information in mminfo

Hi all,

We have a NetWorker 7.6SP3 environment and are using DDBoost with DataDomain devices.

In the NMC reports, we can see some DataDomain statistics and also see the dedup information for each save set or client or so.

Is it also possible to see this kind of information from the mminfo command?

Ive been reading through the man-page of mminfo, but can't find any field which provides this info.

Kind regards

Tim

5 Practitioner

 • 

274.2K Posts

November 16th, 2012 08:00

size is the pre dup value that standard mminfo see's

size=335633084

this is also reported in the domain dedup statistics wth mminfo -avq ssid=537106346 -S

"v1:1342414086:336723696:297880120:148206473";

the 3rd value from the end

The last value 148206473 is the actual deduped data sent to the DD

standard mminfo withn the attrs switch added will also give you the same output as  -S

14.3K Posts

July 15th, 2012 13:00

I do not have Boost, but I believe mminfo -mv was supposed to give de-dupe ratios?

63 Posts

July 16th, 2012 00:00

Doesn't seems like it has dedup info

state volume                  written  (%)  expires     read mounts capacity volid      next type       
DD2backup.001           6989 GB 100% 09/15/2012   0 KB     3      0 KB 2799796831    0 Data Domain
       DD2backup.001.RO           0 KB   0% 09/15/2012 8089 KB    3      0 KB 2783019617    0 Data Domain
        DD2backup.001           6989 GB 100% 09/15/2012   0 KB     3      0 KB 2799796831    0 Data Domain
       DD2backup.001.RO           0 KB   0% 09/15/2012 8089 KB    3      0 KB 2783019617    0 Data Domain
        DD2backup.001           6989 GB 100% 09/15/2012   0 KB     3      0 KB 2799796831    0 Data Domain
       DD2backup.001.RO           0 KB   0% 09/15/2012 8089 KB    3      0 KB 2783019617    0 Data Domain
       DD2backup.001           6989 GB 100% 09/15/2012   0 KB     3      0 KB 2799796831    0 Data Domain 
      DD2backup.001.RO           0 KB   0% 09/15/2012 8089 KB    3      0 KB 2783019617    0 Data Domain 
      DD2backup.002           5563 GB 100% 09/15/2012   0 KB     1      0 KB 921178609     0 Data Domain
       DD2backup.002.RO           0 KB   0% 09/15/2012 6142 KB    3      0 KB 904401394     0 Data Domain
       DD2backup.000           6213 GB 100% 06/19/2013   0 KB     3      0 KB 14685926      0 Data Domain 
      DD2backup.000.RO           0 KB   0% 06/19/2013  96 MB     3      0 KB 4292876008    0 Data Domain
       DD2backup.002           5563 GB 100% 09/15/2012   0 KB     1      0 KB 921178609     0 Data Domain 
      DD2backup.002.RO           0 KB   0% 09/15/2012 6142 KB    3      0 KB 904401394     0 Data Domain

63 Posts

July 16th, 2012 02:00

Ah perfect,

The -S did provide some datadomain dedupe statistics.:

mminfo -avq ssid=537106346 -S

ssid=537106346 savetime=07/16/2012 06:25:12 AM (1342412712) sscsbeno4120:NOTES:_txnlogs_19

  level=incr   sflags=vF       size=335633084    files=5          insert=07/16/2012

  create=07/16/2012 complete=07/16/2012 browse=07/30/2012 11:59:59 PM retent=07/30/2012 11:59:59 PM

  clientid=78602123-00000004-4fe01689-4ff2f050-104c1900-6212ba99

*ss data domain backup cloneid: 1342412713, 1342412714;

*ss data domain dedup statistics: "v1:1342412713:336721860:297860833:147743551",

                              "v1:1342412714:336721860:297860833:147743551",

                              "v1:1342414085:336723696:297880120:148206473",

                              "v1:1342414086:336723696:297880120:148206473";

                       group: ATLAS_CHA_LN_DN_Daily_Incr-20;

  Clone #1: cloneid=1342412713  time=07/16/2012 06:25:13 AM    retent=07/30/2012  flags=F

    frag@         0 volid=4292876008 file/rec=       0/0     rn=0 last=07/16/2012

  Clone #2: cloneid=1342412714  time=07/16/2012 06:25:14 AM    retent=07/30/2012  flags=F

    frag@         0 volid=  14685926 file/rec=       0/0     rn=0 last=07/16/2012

  Clone #3: cloneid=1342414085  time=07/16/2012 06:48:05 AM    retent=07/30/2012  flags=F

    frag@         0 volid=4259321593 file/rec=       0/0     rn=0 last=07/16/2012

  Clone #4: cloneid=1342414086  time=07/16/2012 06:48:06 AM    retent=07/30/2012  flags=F

    frag@         0 volid=4276098803 file/rec=       0/0     rn=0 last=07/16/2012

Now I just have to figure out what they mean :-D

14.3K Posts

July 16th, 2012 02:00

I'm quite sure there has to be some hidden switch to get that info too. I just did strings against mminfo and could not find obvious hint except -q dedupe one I mentioned earlier.

14.3K Posts

July 16th, 2012 02:00

I know there is dedupe switch (-q dedupe) which used to work with Avamar - not sure if it works with DD Boost though - you may wish to check.  If this data is part of mdb, which I don't know, then querying ssid info should show it.  In such case mminfo -q ssid= -S should give you detailed data about ssid.  If you don't see it there, I suspect this information is not part od mdb and might be calculated with NMC by checking mdb data and data from DD in combination.

63 Posts

December 18th, 2012 05:00

Thanks Hoppo,

That's indeed what I need.

The mminfo -r attrs indeed also provides that info. Great!!!

No Events found!

Top