{"id":10677,"date":"2021-10-31T06:29:31","date_gmt":"2021-10-30T20:29:31","guid":{"rendered":"https:\/\/nsrd.info\/blog\/?p=10677"},"modified":"2021-10-31T06:29:35","modified_gmt":"2021-10-30T20:29:35","slug":"crunching-networker-deduplication-stats","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2021\/10\/31\/crunching-networker-deduplication-stats\/","title":{"rendered":"Crunching NetWorker Deduplication Stats"},"content":{"rendered":"\n

If you use NetWorker with Data Domain, you’ve probably sometimes wanted to know which of your clients have the best deduplication \u2013 or perhaps more correctly, you’ve probably wanted to occasionally drill into clients delivering lower deduplication levels.<\/p>\n\n\n\n

There are NMC and DPA reports that’ll pull this data for you, but likewise, you can get information directly from mminfo<\/em> that’ll tell you details about deduplication for Data Domain Boost devices.<\/p>\n\n\n\n

You’ll find the information you’re after within the output of mminfo -S<\/em>. The -S option in mminfo provides a veritable treasure trove of extended details about individual savesets. To give you an example, let’s look at just one saveset in -S format. First, below, you’ll see the mminfo command to identify a saveset ID, then the -S option invoked against a single saveset.<\/p>\n\n\n\n

[Sun Oct 24 13:43:02]\n\n## ~  \n## root@orilla \n\n$ mminfo -q \"name=\/nsr\/scripts,savetime>=4 hours ago\" -r \"ssid,savetime(20)\"<\/strong>\n ssid          date     time\n3816067119    24\/10\/21 09:43:58\n3665074337    24\/10\/21 10:20:00\n\n[Sun Oct 24 13:43:10]\n\n## ~  \n## root@orilla \n\n$ mminfo -q \"ssid=3665074337\" -S<\/strong>\nssid=3665074337 savetime=24\/10\/21 10:20:00 (1635031200) orilla.turbamentis.int:\/nsr\/scripts\n  level=manual sflags=vF       size=2453183044   files=18         insert=24\/10\/21\n  create=24\/10\/21 complete=24\/10\/21 browse=24\/11\/21 10:20:00 retent=24\/11\/21 23:59:59\n  clientid=c6fb4ece-00000004-5fdabaf1-5fdabaf0-00019ed8-a41317f3\n          *backup start time: 1635031200;\n*ss data domain backup cloneid: 1635031201;\n*ss data domain dedup statistics: \"v1:1635031201:2459622768:395458878:151768627\";\n                       group: NAS_PMdG;\n            saveset features: CLIENT_SAVETIME;\n  Clone #1: cloneid=1635031201  time=24\/10\/21 10:20:01    retent=24\/11\/21  flags=\n    frag@         0 volid=3923434705 file\/rec=       0\/0     rn=0 last=24\/10\/21<\/pre>\n\n\n\n
There’s a support article that explains how to review this information, here<\/a><\/strong>. The line you’re looking for in particular though is the “*ss data domain dedup statistics” \u2013 outlined in that aforementioned support article.<\/p>\n\n\n\n
I recently wanted to review some deduplication details, and while DPA and NMC are options, I needed to analyse some data over the weekend<\/span>1<\/sup><\/a><\/span> and as such didn’t have access to the live DPA or NMC host for a particular environment. So, since I’m not doing anything social while Melbourne’s COVID case numbers remain so high, I tasked myself with writing a script to analyse deduplication statistics from raw mminfo -S<\/em> output. <\/p>\n\n\n\n
The script I wrote (in Perl, of course), can either be run on a NetWorker server via a query option, or against the saved output of mminfo -S<\/em>. The usage syntax is this:<\/p>\n\n\n\n
\"\"<\/a>
Usage Options for dedupe-analysis<\/figcaption><\/figure>\n\n\n\n
The script pulls the data and outputs at least three key data files, all in CSV format:<\/p>\n\n\n\n