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.
In my previous article Windows 2016 and Storage Spaces as a Veeam backup repository I talked about the advantages that Veeam Backup & Replication can bring when combined with Windows Server 2016 and the new ReFS 3.1 filesytem. Several people have asked already about some practical examples about how to design a solution using these technologies, so I thought it was time to give you one storage design.
Veeam introduced specific support for vSAN back in mid-2014 as part of Veeam Backup & Replication v7.0 Update 4. More than support I should say integration, because the software is capable of leveraging the specific architecture of vSphere vSAN to improve the backups executed against this platform.
Veeam Backup & Replication 9.5 has just been released in its GA (General availability) version yesterday, which means that every customer can download the new version and upgrade their own installation. While you download the software, let’s have a look at the What’s New document. There are as usual some really interesting things!
As Microsoft Windows 2016 is now finally generally available, people are starting to seriously looking at its features, and no doubt S2D together with the new ReFS 3.1 is one of the hot topics. I’ve first of all updated my lab with the final version of Windows 2016 in order to have my cluster in a “stable” state, than I started to focus on the different topics related to Windows 2016 and its usage as a Veeam repository. And I started to ask How can we leverage ReFS BlockCloning and Storage Spaces to make Windows 2016 the best solution for Veeam repositories? What about Storage Spaces Direct?”.
VeeamHub is a new github repository for the Veeam community, curated by Veeam engineers and architects. Here you can find scripts and other useful code.
After many years thinking about writing one, and many years never being able to do so, I was finally able to write a technical book. Topic? Veeam Cloud Connect.
This August I will present together with my colleague Clint Wyckoff at VMworld 2016 in Las Vegas. Our session is going to be a technical deep dive in one of the upcoming features of Veeam Backup & Replication 9.5, dedicated to service providers using vCloud Director.