The network adapter of each network extension appliance on the tenant side gets an IP address from the production network for which this appliance is configured. For example, if there are 2 networks on the tenant production site, the tenant should configure 2 network extension appliances. On the tenant side, a separate network extension appliance must be deployed for every production IP network. The network extension appliance connects to a production network using a network adapter. Veeam Backup & Replication uses the network extension appliance on the tenant side to route requests between production VMs on the source host and VM replicas on the cloud host after partial site failover. To learn more about cloud failover, see Cloud Replica Failover and Failback. If the SP or tenant does not specify network extension appliance settings, or if the network extension appliance fails during the failover process, the tenant will not be able to fail over to a VM replica. The network extension appliance is an obligatory component if you want to use built-in cloud networking and failover capabilities of Veeam Cloud Connect Replication. Veeam Backup & Replication automatically deploys and configures the network extension appliance VM using the specified settings. To learn more, see Configure Network Extension Appliances. The tenant specifies network settings for the tenant-side network extension appliance when adding the SP or rescanning resources available from the SP in the tenant Veeam backup console. To learn more, see Specify Network Extension Settings. The SP specifies network settings for the provider-side network extension appliance when subscribing a tenant to a hardware plan. The network extension appliance VM is assigned an IP address from a tenant's production network and placed to the selected folder and resource pool created on the ESXi host or a selected folder on the Hyper-V host.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |