#Veeam backup repository recommendations update#
#Veeam backup repository recommendations windows#

If you change the NFS protocol version at a later date (for example, if you updated the NFS share), youвЂ™ll need to reconfigure the Veeam backup repository (which weвЂ™ll be setting up shortly) by clicking through the Edit Backup Repository wizard in Veeam to update the information in Veeam Backup & Replication.Д¬urrently, Veeam Backup & Replication v10 supports filers presenting capacity via NFS share using protocol version v3.0 and v4.1 only. Note: Veeam Backup & Replication will use the highest NFS protocol version supported by the gateway and the repository. While v4.1 is supported by Veeam, in our experience, v3 was required for a successful mount of the NFS share to work. Next, we provide the NFS share name, the provisioned size and enable the NFSv3 option. We then click the вЂ+вЂ™ symbol to Create File Systems which will open a new dialogue box. LetвЂ™s get started вЂ“ After logging into our FlashBlade management interface, we are Lets get started вЂ“ After logging into our FlashBlade management interface, we are greeted with the typical Pure Storage interface, for those familiar with FlashArrays youвЂ™ll notice the interface is identical.ДЇirst, click on the вЂStorageвЂ™ option in the left-hand navigation pane. With the addition of ransomware-proofing backups with PureStorage SafeMode which will be discussed in a later article in this series, itвЂ™s pretty easy to see why these devices make great Veeam backup targets. The FlashBlade being an all-flash storage platform is designed to handle the random I/O traffic that can be generated from large Multi-VM Instant Recovery sessions (aka restore bootstorms).

New features in Veeam v10 such as the Multi-VM Instant recovery or data APIs are increasing the storage IOPS demanded which some legacy backup storage are failing to deliver. FlashBlades are great targets for Veeam for a couple of reasons, they provide high performance in a dense form-factor, they support multiple protocols such as NFS, SMB and Object Store in parallel and scaling out is a simple case of adding another blade. WeвЂ™ll be using a Pure Storage FlashBlade as the underlying storage for the NFS share in this guide. In typical Veeam fashion, itвЂ™s a simple wizard-driven process to add the NFS share just like any other backup repository types supported by Veeam. The great news is Veeam Backup & Replication v10 can now natively leverage an NFS share directly without any Linux machines acting as a middleman.

#Veeam backup repository recommendations windows#

Limitations around mounting an NFS share on Windows meant organisations were required to deploy workarounds that required Linux servers and NFS mount points which often ended up in the вЂtoo hard bucketвЂ™ for administrators who preferred the ease of Windows and SMB. Veeam Backup & Replication has supported backups directly from NFS ( Direct NFS Access) and restores directly to NFS ( Data Restore in Direct NFS Access Mode) natively for a while now but backing up to an NFS share was always a bit of a challenge. In this blog, weвЂ™ll be configuring an NFS share on a Pure Storage FlashBlade which will be utilised by Veeam Backup & Replication v10 as an NFS backup repository. Part 1 вЂ“ Veeam Backup & Replication v10 to PureStorage FlashBladeДЄuthors вЂ“ Lawrence Ang, Rhys HammondВ and Dilupa Ranatunga Introduction