Veeam and DD Boost – Results


My previous post showed how to setup a new DD appliance and integrate with Veeam using DD Boost see here

Now to show the juicy results.  In my setup I have three Veeam servers backing up to local disk as a tier 1 repository then a Backup Copy job to the DD2500 for long term tier 2 retention.  My tests were to compare using DD Boost with the recommended settings compared to without and comparing backing up directly to the DD2500.

Test 1 – Standard Veeam settings

Backup Job to Tier 1.  Job settings below.  Results 482GB processed in 55:36 @ 126MB/s overall

  • Veeam in-line dedupe – enabled
  • Veeam compression – extreme
  • Storage optimization – local target 1MB

Copy Job to Tier 2.  Job settings below.  Results 358GB processed in 43:03 @ 191MB/s overall

  • Veeam in-line dedupe – enabled
  • Veeam compression – Auto (keeps existing compression)

backup job to teir1 using extreme comp and depue in veeam  copy job to dd2500 using extreme comp and dedupe in veeam

Test 2 – Veeam recommended settings for DD Boost (see here)

Backup Job to Tier 1.  Job settings below.  Results 482GB processed in 37:01 @ 216MB/s overall

  • Veeam in-line dedupe – disabled
  • Veeam compression – optimal
  • Storage optimization – local target (16TB +backup files) 8MB

Copy Job to Tier 2.  Job settings below.  Results 363.9GB processed in 39:31 @ 230MB/s overall

  • Veeam in-line dedupe – disabled
  • Veeam compression – Auto (keeps existing compression)

backup job to teir1 using dd boost recommended settings  copy job to dd2500 using dd boost recommended settings

Test 3 – Direct to DD

Backup Job direct to the DD using Veeams recommended settings.  Job settings below.  Results 462.7GB processed in 1:15:17 @ 97MB/s overall

  • Veeam in-line dedupe – disabled
  • Veeam compression – optimal
  • Storage optimization – local target (16TB +backup files) 8MB

backup job direct to DD using recommended settings

Conclusion

As you can see using Veeam’s recommended settings the overall processing for tier 1 and tier 2 is just short of 50% quicker.  I end up with a slightly larger footprint on tier 1 but a smaller backup window.  By using DD Boost as a tier 2 copy job I have less impact on the production environment and by using copy jobs but also have an efficient data transport to the DD by only sending unique data.    Finally by using a dedupe appliance I have some fantastic long term capacity and dedupe rates.

One of the key benifits when using DD Boost is the time savings when taking a synthetic full.  Below are the results, the difference is incredible

  • Without DD Boost – synthetic full takes 37:47
  • With DD Boost – synthetic full takes 05:05!!

synthetic full none dd boost  synthetic full using dd boost

 

Leave a comment

Your email address will not be published. Required fields are marked *