Veeam Backup & Replication and the entire Availability Suite V8 is available today, and it has also a solution to fix the VMware CBT bug.
When it comes to choosing a backup mode in Veeam Backup & Replication,there is a constant trade-off between space efficiency and I/O efficiency. Forward mode is I/O efficient, while Reversed is space efficient. The new method coming in v8 will combine the pros of each, to offer an even better backup experience.
I’ve always been a fan of scale-out storage solutions, and I’ve always preached about them.
As data is skyrocketing, the best viable way to cope with this growth is having a system that can be scaled accordingly without the pain of data migrations involving TBs of data. One of the limits of scale-out systems however has always been the data protection techniques applied to them. RAID is inefficient, replication is too expensive, so what about Erasure Coding? Is it mature enough to become the new data protection technique for storage systems?
The first of a series of technical white papers I’m writing in these months has been published: Veeam for VMware Cloud Providers. Achieving the best RTOs and RPOs with Veeam Backup & Replication in Multi-Tenant environments. If you want to learn how to operate Veeam in a service provider environment, this paper is for you.
One of the biggest misconceptions about Veeam Backup & Replication, often fueled by competitors, is that it requires the complete server installation in order to run restores. So, this becomes a Single Point of Failure, just like many other solutions from competitors. This is completely untrue: there are two main features in Veeam that make restores possible even without the server installation.
Veeam Backup & Replication has always had since its first version the possibility to replicate VMs, together with the backup capabilities. Once a VM is replicated in a secondary site, it could become a great resource for additional activities: from automated recovery tests (called SureReplica in Veeam) to become also the source for cloning activities. Data are already locally saved, there is no need to retrieve anything else from the source site, so any operation is quick an easy. Are there any informations we should be aware of in doing these operations? Let’s find it out.
Veeam just released the new and latest patch for Backup & Replication 7.0, numbered Patch 4. The new patch can be installed on any previous version of 7.0 release, since as usual the patch is cumulative. The final build number after the upgrade will be now 184.108.40.2061.
There are as usual many improvements and fixes, and two big enhancements. The first one is the added support for Microsoft SQL 2014, but for sure the biggest news is with no doubt the support for VMware Virtual SAN, unofficially shorten VSAN by many.
Last week, Veeam and Nutanix have published a joint technical paper, regarding the best practices to use Veeam Backup & Replication v7 in a Nutanix infrastructure, when running VMware vSphere. The paper is 20 pages long, it has been written by myself and Derek Seaman, and you can download it here. This post however is about what’s “not” written in that paper, its story, and what I learned from this great experience.