I’m a fan of Veeam, and use in production today. Thus, I wanted to share the write up.
“The goal of the joint whitepaper between Veeam and Nutanix is to help customers deploy Veeam Backup & Replication v7 on Nutanix, when used with VMware vSphere 5.x. This post will highlight some of the major points and how customers can head off some potential issues. The whitepaper covers all the applicable technologies such as VMware’s VADP, CBT, and Microsoft VSS. It also includes and easy to follow checklist of all the recommendations.”
The official whitepaper can be downloaded here.
Veeam is modern data protection for virtual environments, and are also a great sponsor of my blog. The web-scale Nutanix solution and its data locality technology are complimented by the distributed and scale-out architecture of Veeam Backup & Replication v7. The combined Veeam and Nutanix solutions leverage the strengths of both products to provide network efficient backups to enable meeting recovery point objective (RPO) and recovery time objective (RTO) requirements.
The architecture is flexible enough to enable the use of either 100% virtualized Veeam components or a combination of virtual and physical components, depending on customer requirements and available hardware. You could also use existing dedicated backup appliances. In short, our joint solution is flexible enough to meet your requirements and efficiently use your physical assets. For example, if you have requirements for tape-out, then you will need at least one physical server in the mix to connect your library to since tape Fibre Channel/SAS pass-thru is not available in ESXi 5.x.
“When virtualizing solution the last thing you want is your backup data stored in the same location as the data you are trying to protect. So the first best practice for a 100% virtualized solution is to use a secondary Nutanix cluster. The cluster would be comprised of at least three Nutanix nodes. This is where the virtualized Veeam Backup & Replication server (along with the data repository), would reside. Should you have a problem with the production Nutanix cluster, your secondary cluster is unaffected. Depending on the amount of data you are backing up and your retention policies, you may or may not want the same Nutanix hardware models as your production cluster. For example, you may want to consider the 6000 series hardware which are ‘storage heavy’ for your secondary cluster. The following figure depicts a virtualized Veeam backup solution.”
Read the full post.
Thanks to Derek Seaman for the write up.