- #Veeam backup repository recommendations update#
- #Veeam backup repository recommendations upgrade#
- #Veeam backup repository recommendations download#
- #Veeam backup repository recommendations windows#
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.
#Veeam backup repository recommendations download#
Veeam Backup & Replication v11a is available to download as 30-day free trial.Part 1 – Veeam Backup & Replication v10 to PureStorage FlashBladeĪuthors – Lawrence Ang, Rhys Hammond and Dilupa Ranatunga Introduction The Hardened Repository is now upgraded to the current installed version of your Veeam Server. Remember to disconnect any remote system (iLO, iDRAC, etc.) from your repository. Click Finish to exit the wizard.įrom the repository console, remove the service account used in Veeam from the sudo group and exit. This time the repository has been upgraded successfully.
#Veeam backup repository recommendations upgrade#
Select the Hardened Repository to upgrade and click Apply.Ĭlick Set User button and select Single-use credentials for hardened repository option.Įnter the Username of service account used and the Password then click OK. During the upgrade of other Veeam components to apply version 11a, the Hardened Repository was skipped. Open the Veeam console and select from the menu the Settings > Upgrade option. To apply the update, the first step is to add the used service account back to the sudo group.Įnable the remote access to your repository and login with the administrative account set during the installation of your Linux repository.Īdd the Veeam service account to the group sudo with the command: In addition, the account used by Veeam to connect the repository doesn't have any permission to do operations on the Linux machine since it is not a member of the sudo group. If the repository was configured by following the best practices, the Single-use credentials for hardened repository option was used to connect Veeam to the repository. This is an expected behavior since Veeam doesn't have the credentials stored anywhere to access the Hardened Repository.
#Veeam backup repository recommendations update#
When a new version or patch is released by Veeam, when you try applying the update to the repository, it will fail.
With the introduction of the Immutability feature in Veeam Backup & Replication v11, a Hardened Repository requires a specific procedure to be upgraded.Ī normal upgrade of this type of repository cannot be performed in the "classic" way due to the restrictions applied during the configuration procedure of the repository itself.
0 kommentar(er)
