To enable backup and replication from Cisco HyperFlex snapshots, you must configure one or more backup proxies in the backup infrastructure. Backup proxies must meet the following requirements:
- The role of a backup proxy must be assigned to a Microsoft Windows machine. This can be a dedicated machine or backup server performing the role of the default backup proxy.
- NFS traffic between the backup proxy and storage system must be allowed.
- [Recommended] The backup proxy should be connected to the same network as source VMs. For more information, see Methods of Data Retrieving.
Backup proxies that process data of VMs hosted on Cisco HyperFlex read VM data from NFS stores over the NFS HyperFlex data network. Depending on the backup infrastructure configuration, backup proxies can read data over the following data paths:
- Over IO Visor on ESX(i) hosts. The IO Visor is a Cisco HyperFlex software module that represents NFS to an ESX(i) host. From the hypervisor’s perspective, the ESX(i) host is simply attached to NFS.
The data path over IO Visor is the preferred method — it provides the high speed of VM data reading. To read VM data over IO Visor, backup proxies must be connected to the same network as source VMs. You must also manually configure firewall rules. For more information, see Configuring Firewall Rules for Cisco HyperFlex.
- Over HyperFlex Controller Cluster IP. This data path provides lower speed of VM data reading than that over IO Visor.