This Site Is Depreciated
  • This is the depreciated Version of Veeam Backup & Replication Best Practices
  • Contacting Veeam Software
  • DNS Resolution
  • Veeam Backup Server
    • Deployment Method
    • Backup Server Placement
    • Sizing and System Requirements
    • Veeam Backup & Replication Database
    • Protecting Veeam Backup & Replication Configuration
  • Veeam Enterprise Manager
    • vCloud Director Self Service Portal
  • Search Server and Indexing
  • Proxy Servers - Introduction
    • Proxy - VMware vSphere
      • Transport Modes
        • Direct Storage Access
        • Virtual Appliance Mode
        • Network Mode
        • Backup from Storage Snapshots
          • NetApp Data ONTAP integration
          • Nimble Storage integration
        • Selecting a Transport Mode
      • Sizing a Backup Proxy
    • Proxy - Microsoft Hyper-V
    • Proxy - Nutanix AHV
  • Primary and secondary Storage BPs
    • HPE 3PAR VMs disks considerations
    • DellEMC Data Domain advanced scalability
  • Backup Repository
    • Repository Types
      • SMB
      • Deduplication Appliances
      • Integration specifics
      • Windows Server Deduplication
      • Object Storage
    • Repository Planning
      • Sizing
      • Per VM Backup Files
      • Scale-out Backup Repository
        • Capacity Tier
    • Repository HA
  • WAN Acceleration
    • Analyzing Wan Acceleration Workload
    • Comparing WAN Acceleration Modes
    • Sizing For WAN Acceleration
    • Sizing Targets for WAN Accereration Relationship
    • Deployments For WAN Acceleration
    • Is WAN Acceleration Right For me
  • Tape Support
    • Tape Deployments
    • Tape Media Information
    • Tape Config Requirements
    • Tape Parallel Processing
    • Tape Virtual Full
    • Tape Writing to Tape
    • Tape Restores
  • Veeam Explorers
  • Interaction with VMware vSphere
  • Interaction with Microsoft Hyper-V
  • Job Configuration
    • Backup Methods
    • Encryption
    • Deduplication and Compression
    • Backup Job
    • Backup Copy Job
    • Replication Job
    • Application-Aware Image Processing
  • Data Verification Using Virtual Labs
  • Overview of Applications Support
    • Active Directory
    • Microsoft Exchange
    • Microsoft SQL Server
    • Microsoft SharePoint Server
    • Oracle Database
    • MySQL
    • IBM Notes/Domino
    • SAP HANA
  • POC Guide
    • Assessment
    • Accelerated Evaluation
    • Enhanced Evaluation
      • Workshop Example
      • Preparation
      • Automation
  • Infrastructure Hardening
    • Segmentation using Zones
    • Hardening Backup Repository - Linux
    • Hardening Backup Repository - Windows
  • Backup & Replication Anatomy
    • Backup
    • VM Restore
    • Instant VM Recovery
    • Windows File-Level Restore
    • Replication
  • Networking Diagrams
    • Backup Server
    • Proxy Server
    • Repository Server
    • Storage Integration
    • Data Validation
  • Application-aware Image Processing
  • Enterprise Manager
  • Sizing Summary
Powered by GitBook
On this page

Was this helpful?

  1. Backup Repository
  2. Repository Types

Windows Server Deduplication

PreviousIntegration specificsNextObject Storage

Last updated 4 years ago

Was this helpful?

Follow the recommendations provided in the configuration guidelines above; here is the summary:

  1. Use Windows 2012 R2 or Windows 2016 and apply all patches (some roll-ups contain improvements to deduplication). Having most up to date system is critical for ensuring data safety.

  2. Format the disk using the command line "/L" option (for "large size file records") and 64KB cluster size (use parameters /Q /L /A:64K)

  3. Follow for non-integrated deduplication storage in previous chapter.

  4. (For Windows Server 2016 and later) the "Virtualized Backup Server" deduplication profile is to be preferred ()

  5. Modify garbage collection schedule to run daily rather than weekly.

  6. Use backup jobs configured to perform Active full with Incrementals.

  7. If possible, spread active full backups over the entire week.

  8. Try to keep the .VBK files below 1TB in size (there is no official support from Microsoft for files bigger than this; see ). Large files take a long time to deduplicate and will have to be fully reprocessed if the process is interrupted.

  9. Where possible, use multiple volumes. Windows deduplication can process multiple volumes using multi-core CPU – one CPU core per volume; see for details.)

  10. Configure deduplication process to run once a day, and for as long as possible.

More information on Windows Server 2016 Data Deduplication can be found .

check the following link
https://msdn.microsoft.com/en-us/library/hh769303(v=vs.85).aspx
http://blogs.technet.com/b/filecab/archive/2014/12/04/sizing-volumes-for-data-deduplication-in-windows-server.aspx
here
compression and deduplication guidelines