Skip to main content

Veeam Backup and Replication Best Practice Guide <WIP>

TheseThis areis justa noteswork in progress

Summary

This document is intended to provide the best practices for nowusing Veeam's Backup and Replication product with the StorONE Storage Appliance Software to Backup, Restore, and Replication Virtual Machines. 

Requirements / Recommedations

StorONE

The testing used to create this document was completed using StorONE version 3.8.0.66.  Later versions of the documentStorONE code can be applied to this process as well. 

Protocols

StorONE has been certified to be used with Veeam with the following protocols:

              CIFS/SMB - VeeamReady StorONE SMB Repository NFS - VeeamReady StorONE NFS Repository iSCSI - VeeamReady StorONE iSCSI Repository

              N+K Settings

              <TBD> Will note that 8+X is not needed for Veeam to be performant

              Snapshots/Retention

              <TBD>

              Recommendations of things NOT to do

              It is StorONE's recommendation to avoid using VMDK or RDM storage for the creation of Veeam Storage Repositories

              FromVeeam

              Veeam:

              Direct Connect Volumes

              For direct mounted volumes:(block) volumes (StorONE volumes presented directly to the Veeam Server) Veeam has specific recommendations for formatting and block size ( Veeam's Backup and Replication Best Practices )

                ReFS 64K

                From StorONE:

                Windows

                UseWindows a2k19+ directuse mappedReFS Volume/LUNwith using64KB either:block size

                Linux

                Format volumes with XFS and 4KB block size

                3-2-1 Backup Rule

                Veeam Blog Post Regarding the 3-2-1 Backup Rule

                Veeam Community Blog Post about the 3-2-1-1-0 "Golden Backup Rule"

                Summary of the 3-2-1 method/rule
                • iSCSI
                            • Maintain at least 3 copies of your data
                            • FCStore your backups on at least 2 different medias / storage devices
                            • NFSStore at least 1 copy in an offsite location
                            The additional 1-0 added as technology has advanced
                                          1 Offline or "air-gapped" copy (such as a StorONE snapshot) SMB0 errors after a backup recovery verification (which can be done with SureBackup)

                                          Things to NOT use:

                                            a VMDK (datastore) based backup repository an RDM (Raw Device Mapping) volume

                                            Vraid - 8+X is not required as Veeam is not a strictly sequential workload. 

                                             

                                            Process