Since Veeam announced the Scale-Out Backup Repository technology coming in Veeam Backup & Replication v9, I’ve been asked already multiple times to give some practical examples on how to leverage it. Let’s see together one interesting way to leverage the “performance” policy available in Scale-Out Backup Repository.
In 2014, in a presentation I’ve done, I’ve said to people that in 2-3 years new and cheaper flash memory would have become the stardard solution for general purpose disk storage, thanks to a price per GB comparable with spinning disk. Seems that I was right after all.
If you want to backup virtual machines running on an NFS storage in vSphere using virtual proxies, Veeam has a dedicated registry key to protect you from NFS locks.
Lately, different bugs involving VMware CBT in vSphere 6 have created some justified concerns among users. But there are ways to guarantee successful backups even in these conditions.
One of the features coming in Veeam Backup & Replication v9 is per-VM backup chains.This great addition was in between a general announcement related to other backup storage improvements; in case you missed it, here we go with a dedicated post, because this feature is going to be great!
vSphere tags are incredibly powerful objects, that can be used in many and amazing ways. One of the possible use cases for tags is Data Protection. Veeam supports vSphere tags in both vSphere 5.5 and 6.0, and with them you can create advanced policy-based data protection rules.
A new species of Backup Repository is coming from Veeam: Scale-Out Backup Repository. With it, users will be able to simplify backup job management, improve backup performance, and spend less on backup storage. Veeam’s new Scale-out Backup Repository delivers these benefits by providing an abstraction layer over individual storage devices, effectively creating a single virtual pool of backup storage to which you can assign backup jobs, and offering the freedom to easily extend capacity as needed by simply adding additional storage devices into the existing pool.
When you have to deal with a large environment and several jobs in Veeam, automation via powershell is the only possible solution.