I’m collecting here all my publications:

March 2016: “A Deep Look at Scale-out Backup Repository”

December 2015: “Veeam Cloud Connect Replication: DRaaS that is extremely powerful and extremely easy”

October 2015: “Using Veeam and VMware vSphere Tags for Advanced Policy-driven Data Protection”

April 2015: “Veeam Backup & Replication v8: Availability for Oracle Environments”

February 2015: “Veeam Backup & Replication v8: Designing and planning backup repository performance”

November 2014: “Veeam Backup & Replication v8: Cloud Connect Reference Architecture”

September 2014: “Veeam for VMware Cloud Providers, Achieving the best RTOs and RPOs with Veeam Backup & Replication in Multi-Tenant environments”

August 2014: “Nutanix and Veeam Backup & Replication for Hyper-V: Best Practices”

June 2014: “Nutanix and Veeam Backup & Replication for vSphere: Best Practices”

April 2014: “NetApp Storage Snapshots with Veeam Backup & Replication

January 2013: “HP + Veeam: Fast VMware Recovery from SAN Snapshots

April 2012: “Veeam backup methods and the impact on destination storage I/O

April 2012: “Microsoft Licensing and Disaster Recovery”

  • Srinivas

    Re: HP+Veeam, Instant VM recovery from SAN snapshots.

    I was curious that your illustration showed the LUN was hosting a single VM. But in reality you may have multiple VMs on the LUN. Does this mean, that with Instant recovery, the smart clone volume (the new standalone LUN) has multiple VMs on it, and all of them are started on the vCenter that you point to?

    • Luca Dell’Oca

      Yes and no. The cloned volume has all the original VMs in it, but Veeam only uses the one you want.