1-800-691-1991 | 9am - 8pm ET
EN

Architecture Guidelines for deduplicating storage systems

KB ID: 2660
Product: Veeam Backup & Replication
Version: Any
Published: 2019-01-22
Last Modified: 2021-12-06
Languages: FR
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

The following Veeam technologies are dependent on primary backup storage random I/O performance:

  • Instant Recovery (VM/Disk/NAS/Databases)
  • Windows and Linux File Level Recovery
  • Cloud Tier
  • Cloud Mobility
  • DataLabs
  • SureBackup
  • Staged Restore
  • Universal Restore (U-AIR)
  • On-Demand Sandbox
  • Secure Restore
  • Backup and Backup Copy Jobs when configured with one of the following:
  • Health Check
  • Compact processing
  • Synthetic Fulls
  • Forever Forward Incremental (Merges)
  • Reverse Incremental
  • Backup to Tape Jobs, specifically when performed with synthesized fulls
  • Replication when performed from backup as a source
  • Backup Copy Job processing on the source side
  • NAS Backup
    If you plan to create a scale-out backup repository for storing NAS backups that will consist of fast storage and slow deduplicating storage appliances, please review: Scale-Out Repository with Extents in Metadata and Data Roles

Cause

Applying deduplication to storage systems is a technique used to reduce the space required to maintain a desired backup retention. Deduplicating storage systems are often optimized for sequential write operations and can offer high ingest rates, however, there can be a trade off in the form of higher latency when random read operations are required, as they are with the list of features above.

Solution

When using Veeam with a deduplicating storage system a best practice can be to have a non-duplicating storage system as the primary backup target for the most recent restore points and then use backup copy jobs for long term retention.
It is important to note that while this is Veeam’s general recommendation, there is a wide array of different hardware deduplication options, some of which have Veeam specific features enabled or are built with solid state drives to improve random read performance. Because of this, Veeam encourages an in-depth recovery time and recovery point requirements discussion with a value-added reseller or the hardware manufacturer to determine how best to leverage deduplicating storage.
Veeam has worked with strategic alliance partners to list these use cases and offer several architecture options to meet the needs of any scenario.

NOTE: Veeam supports the general use of all storages, including deduplication appliances. For a list of devices known to be compatible through testing, please see the Veeam Ready Program.

Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.