Virtual Volumes, or VVOLs, has been one of the biggest addition in VMware vSphere 6. If your storage array supports them, you can start to play with it and decide if it’s time to migrate from monolithic VMFS volumes to this new exciting storage technology. VVOLs have several advantages over regular VMFS volumes, from the granularity of the volume management (essentially, we have now one “LUN” per virtual disk), to policy-based management, and so on. One of the aspects that people didn’t focused too much is the impact on backup operations coming from VVOLs.
An example of Veeam Scale-Out Backup Repository mixing whitebox servers
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.
Your Veeam backups are slow? Check the stripe size!
When dealing with backup repositories, be careful about the stripe size and its impact on performances!
New whitepaper: Designing and planning Veeam backup repository performance
I’ve just published a new Veeam whitepaper “Veeam Backup & Replication v8: Designing and planning backup repository performance”; in it you will learn about all the available backup modes, their I/O profile, and how to properly test a storage system to estimate the expected performances.