Dedupe rate reporting in v7

[Aurock]

I understand v7 was supposed to change how the dedupe rate for a job is reported, but I am having trouble wrapping my head around the new numbers.

A backup job which typically reported 2.6-3.0x dedupe rate under v6.5 is now reporting a dedupe rate of 33.3, 50, or 100x under v7.

Is this typical for how the dedupe rate reporting changed in v7? If so, could someone help me understand the new system, perhaps point me to some documentation of how v7 calculates and reports the dedupe rate?

Thanks!

[foggy]

Steve, could you please provide the numbers for the data processed/read/transferred for this job as well as the compression rate and the backup size?

[Aurock]

From today's backup:

Processed 1.1TB
Data read 208.5GB
Transferred 41.4GB

Backup Size 36.6GB
Dedupe 33.3x
Compression 2.0x


From yesterday's backup:

Processed 1.1TB
Data read 121.1GB
Transferred 19.0GB

Backup Size 16.2GB
Dedupe 50.0x
Compression 2.3x

[foggy]

Yep, according to my math it should report something closer to 3.0x for both job runs. QC reports that there are some issues with dedupe rate calculation in some cases, these are currently under investigation. You could open the case to probably give us some more information about the circumstances in which those issues show up. Thanks.

[Aurock]

Ok, will do. I didn't want to trouble support if I was just not understanding something, but if the numbers aren't supposed to look this way, I'll go ahead and open a ticket.

Thanks!

[foggy]

Thanks. Those numbers are definitely not expected.

[marcin.dudziak]

Hello,

I have question about values in Reports (from job history). There are values like: Total size, Data read, Transferred, Backup size, Dedupe and Compression. Could someone explain what dependencies are between them?
For example for first full backup i have:
Total size 30,0 GB ----- Backup size 8,3 GB
Data read 14,4 GB ----- Dedupe 2,1x
Transferred 8,3 GB ----- Compression 1,7x

second (without any changes in VM):
Total size 30,0 GB ----- Backup size 16,1 MB
Data read 0 KB ----- Dedupe 1,0x
Transferred 0,9 KB ----- Compression 1,0x

third:
Total size 30,0 GB ----- Backup size 496,1 MB
Data read 732 MB ----- Dedupe 50,0x
Transferred 479,7 MB ----- Compression 1,5x

For example why there is 50x dedup in third one?

Thanks for your help.

[veremin]

Currently, there are some issues with how deduplication rate is reported. These cases are still investigated. So, you’d better contact our support team and provide required logs, so that, we can have a little bit more information regarding what might lead to the said problem. Thanks.

[foggy]

Also, there is another existing thread explaining job progress information, in case you need clarification on other values and dependencies between them.