Using the Cisco HyperFlex integration means avoiding VMware VM Snapshots completely. Especially the VM snapshot delete can take a lot of time and consume serious amounts of storage resources until done. If you run a VM backup without the integration, the workflow will always create a VMware Redo-Log Snapshot Veeam will read all data while VMware redirects all writes into the Redo-Log File and after the backup/replica is done, the VM Snapshot will be deleted as shown in the graphic below on the left side. The main reason why Veeam started to integrate into storage arrays, regardless if it is Cisco HyperFlex or any other storage we support, is to avoid or at least minimize the time of VMware Redo-Log Snapshots (native VMware VM Snapshots). Why does Veeam integrate into Cisco HyperFlex? A brief overview on the integration itself was already done by my colleague Michael Cade earlier this year.īesides this blog post we already started the work on an implementation and best practice guide so stay tuned and check our website regularly. That’s why I want to answer the most common questions in this blog post. Since then I got a lot of positive feedback and questions around the integration. The integration leverages our Backup from Storage Snapshot technology to optimize the data transfer for Veeam backups as well as replications. With Veeam Backup & Replication 9.5 Update 2 we launched our integration with Cisco HyperFlex.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |