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.
Whiteboard Fridays (on Wednesday): How to properly size your backup repository
I’m in the USA in these days, and part of my activities has been to stop by our Atlanta offices, I had a couple of meetings there, but the main reason has been to attend as a guest to the Whiteboard Fridays. These are live transmissions from the Atlanta offices, hosted by Jose Mendoza and Shawn Lieu plus some guests that join them from time to time, and the topics are usually deeply technical, and there is an extensive use of whiteboarding. No slidedecks, no recorded video, only a whiteboard and a pen.
This time, is about Veeam backup repositories, and how to properly design and size them!
Veeam storage snapshots and NetApp
In the new upcoming v8, Veeam Backup & Replication will add a new storage vendor for its Backup from Storage Snapshots support, and this vendor is NetApp. All the FAS and V Series will be supported, both in 7-Mode or Clustered Mode, with the only requirement being the OnTAP OS being at least 8.1.
After playing with the tech preview for a month now, I’d like to talk a little bit more about a couple of new technologies that are going to be in there.
Restore a single VMDK using Veeam Instant VM Recovery
Instant VM Recovery is one of the coolest feature of Veeam Backup & Replication. Regardless of the size of a VM, it allows to have it back in production and running in few minutes, because it’s not actually copied back into the production datastore, but directly executed from a backup file. It’s main use is to restore completely broken or lost VMs, but what if you want to restore a single VMDK, maybe because the original VM is fine and you only need one of its virtual disks? usually, a disk restore would require a complete binary restore into the production datastore, and if the disk is quite large it can take some time. What if you would be able to use Instant VM Recovery also for a single VMDK, instead of having to remove the old VM and swap it with the new one?
A new server for my lab
My Lab is built basically as a production environment: it has 3 * 1RU Rack servers, gigabit switches and a couple of iSCSI/NFS Storage array. It nothing as a home lab, it’s noisy and it consume a good amount of electricity. I was lucky enough to have a good friend with some free space in his racks inside a datacenter, and he’s hosting my hardware gear for free. As time goes by however my hardware is becoming old and start to show its limits. At some point, I decided it was time for a hardware refresh.
Veeam Backup with PernixData write-back caching
PernixData is, as of today, the only server-side caching solution for VMware offering write-back capabilities, that is the possibility to accelerate write operations. This feature is extremely helpful in increasing performances in virtualized environments running write intensive applications like databases, mail servers and others. However, the usage of this feature requires some proper configuration in order to correctly protect VM with Veeam Backup
Why I don’t like blade servers
After the recent release of VMware VSAN, there has been a series of blog posts from some of my peers talking about the design considerations that VSAN has brought. If you read them in the order they were published, you can follow the conversation that is going on: VSAN –…
Test Veeam Storage Snapshots in your lab
In a previous post, I described how you can configure a virtual proxy to access an iSCSI storage, in order to test DirectSAN backups. Veeam has an additional functionality, called Storage Snapshots, that improves even more DirectSAN backups performances when you have a supported storage. I’m going to show you in this post how you can configure it in your lab.
