Backup copy to Offsite with Windows Server 2012 R2 Dedup

[mikame]

hi
I need some help on figuring out why the offsite backup repository with Windows Server 2012 R2 DeDup gives me dedup saving of about a whopping 14GB when the backup data is 3,5TB? I have read and followed the info on "Best Practice for MS Server 2012 DeDup Repo" forum post.
I have also set up Windows Server 2016 DeDup as a main Backup Repository on another test system and the DeDup worked fine with that.

So a Backup Copy job to offsite through the wan/mpls (50mbit line).

Offsite Backup Repository IS formatted with 64K. Offsite Windows Serve 2012 R2 Dedup on with files older than 1 day and "General purpose file server".

Backup Repository Advanced settings;
all unchecked except "Decompress backup data blocks before saving".
I understood that "Align backup file data blocks" is not needed when using Windows DeDup.

Advanced Storage settings on the Backup Copy to offsite Job;
"Enable inline data deduplication"
Compression level: Dedup-friendly
"Enable backup file encryption" is ON/used with a password.

I understood that Copression level can be and is recommended to be ON since sending data through WAN (no Veeam WAN acceleration license so that is not in use).
Besides "Decompress backup data blocks before saving" is on on repository, so the Compression level should not matter?

What should I change to get Dedup ratios ?

I could change the compression level to None, which means more data flowing through WAN and possible have to delete the offsite backups and start a new FULL again (takes days/weeks to finish all using 50mbit line).

Does backup file encryption affect anything on windows dedup?

Thank you in advanced

[HannesK]

Hello,
probably the main point is

Does backup file encryption affect anything on windows dedup?

If you encrypt Veeam backups, then no deduplication system can do anything with it. It will always stay the same size.

Best regards,
Hannes

[mikame]

Yes, password encryption was the problem, thank you.

[doktornotor]

Hello,
probably the main point is

If you encrypt Veeam backups, then no deduplication system can do anything with it. It will always stay the same size.

Best regards,
Hannes

Hmmm... my test repo (64k NTFS iSCSI disk, W2019) used for encrypted backup copy jobs does not seem to care too much about encryption...

Code: Select all

> Get-DedupVolume | fl

Volume                   : I:
VolumeId                 : \\?\Volume{1af10aab-870f-4d61-a4a4-5ae1ec3d1eb1}\
Enabled                  : True
UsageType                : Backup
DataAccessEnabled        : True
Capacity                 : 2.34 TB
FreeSpace                : 1.08 TB
UsedSpace                : 1.26 TB
UnoptimizedSize          : 2 TB
SavedSpace               : 759.5 GB
SavingsRate              : 37 %
MinimumFileAgeDays       : 1
MinimumFileSize          : 32768
NoCompress               : False
NearInlineMode           : False
ExcludeFolder            :
ExcludeFileType          :
ExcludeFileTypeDefault   : {bin, vsv, slp, xml...}
NoCompressionFileType    : {asf, mov, wma, wmv...}
ChunkRedundancyThreshold : 100
Verify                   : False
OptimizeInUseFiles       : True
OptimizePartialFiles     : False
InputOutputScale         : 0
IdleTimeoutDefault       : 60
AutoStart                : True
ChunkIndexCacheVolume    :

Code: Select all

 
> Get-DedupStatus | fl

Volume                             : I:
VolumeId                           : \\?\Volume{1af10aab-870f-4d61-a4a4-5ae1ec3d1eb1}\
Capacity                           : 2.34 TB
FreeSpace                          : 1.08 TB
UsedSpace                          : 1.26 TB
UnoptimizedSize                    : 2 TB
SavedSpace                         : 759.5 GB
SavingsRate                        : 37 %
OptimizedFilesCount                : 41
OptimizedFilesSize                 : 1.97 TB
OptimizedFilesSavingsRate          : 37 %
InPolicyFilesCount                 : 41
InPolicyFilesSize                  : 1.97 TB
LastOptimizationTime               : 27.02.2019 20:17:16
LastOptimizationResult             : 0x00000000
LastOptimizationResultMessage      : The operation completed successfully.
LastGarbageCollectionTime          :
LastGarbageCollectionResult        :
LastGarbageCollectionResultMessage :
LastScrubbingTime                  :
LastScrubbingResult                :
LastScrubbingResultMessage         :