Veeam Backup Best Practices for HybriStor

Follow

Veeam Server and Proxy Configuration

If backing up many VMs, consider deploying in a distributed configuration. Suggested implementations are described below. Please disable the proxy role on the Veeam backup server if running in a distributed configuration. Also please review our Guidelines for Maximum Concurrent Veeam Jobs with HybriStor article for additional information.

If you are using a VMware virtual HybriStor appliance, please configure your VM disks to use VMware paravirtual SCSI adapters before proceeding

Suggestion configuration for four concurrent backup jobs

  • Create one proxy with 4 vCPU (one vCPU per job)
  • Assign 16GB of RAM to the proxy. If this repository is setup for Per-VM backups, each VM is a task. That means each backup chain that is being processed to the repository can use up to 4 gigs of RAM. 
  • Disable the proxy role on the Veeam backup server

Suggestion configuration for 16 concurrent backup jobs

  • Create four proxies, each with four vCPU (16 cores total, one vCPU per job)
  • Assign 16GB of RAM to each proxy. If this repository is setup for Per-VM backups, each VM is a task. That means each backup chain that is being processed to the repository can use up to 4 gigs of RAM.
  • Disable the proxy role on the Veeam backup server
  • Target Veeam backup repositories with CIFS-backed (Shared folder) configuration.
     

NOTE: If Veeam backup jobs are taking several minutes to begin, and if the Veeam server or proxy is a VMware VM, check for overprovisioning of the VM as vCPU overprovisioning can impact performance negatively.

Registry Hack Alert

Currently a registry hack is required to support more than 4 Snapshots per Datastore by default (max 4 VMs per proxy until this registry edit is applied). Modify the registry entry for "HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\" by adding a new DWORD MaxSnapshotsPerDatastore and provide a decimal value, such as 16 (how many snapshots do you want to allow per Datastore).

Shared Folder Repository Configuration

Please follow our Configuring a Veeam Shared Folder Repository for HybriStor KB article for additional details.

Repository Veeam Settings

  • Repository Type: Shared Folder
  • Concurrent Tasks: 4-6 (or higher, depending on proxy configuration)
  • Per-VM Backup Files: ON
  • Decompress before storing: OFF
  • Align backup file blocks: OFF
    • For storage systems using fixed block size, you may want to enable the Align backup file data blocks option — then Veeam Backup &Replication will align VM data saved to a backup file to a 4Kb block boundary. This option provides better deduplication across backup files but it can result in greater amount of unused space on the storage device and a higher level of fragmentation.
    • It is recommended to disable this option for deduplicating storage that uses variable block size, such as the HybriStor
  • For Mount Server: check "Enable vPower NFS service on the mount server - used during Instant VM Restores to determine scratch disk location

Backup Job Configuration

These guidelines apply to optimal job configurations for physical HybriStor units used as Shared Folder Repository targets within Veeam Backup and Replication 9.5 software. We do not recommend exceeding these values, which could lead to performance degradation. 

Note: Processes means each Veeam process. Example - One VM with three .vbm or .vmdk les will be three processes.

Backup

Active Fulls per Proxy: 4 concurrent processes
Active Fulls per Share: 6 concurrent processes
Synthetic Fulls per Share and Proxy: 1 concurrent process (Includes backups and restores of all types) 

Full Restore

Full Restores from Active Full per Proxy: 4 concurrent processes
Full Restores from Active Full per Share: 4 concurrent processes
Full Restores from Incrementals per Share and Proxy: 1 concurrent process (Includes synthetic fulls) 

Instant Recovery

Note: Resources will start to be utilized during boot up of the VM. VM due to InstaCaching. Typical InstaCache size for hardware units is 200GB (not applicable to virtual appliance).

Instant Recovery VMs Booted per Share: 4 concurrent VMs booted
Instant Recovery VMs Booted per Appliance: (Size of total booted vm’s / 10) < InstaCache Size

Backup Veeam Storage Settings

  • Create Synthetic full backups periodically: Unchecked 
  • Enable Inline Deduplication: ON
  • Compression: None
  • Storage Optimization: Local target

Additional Resources

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.