4.5.5 Design Considerations
The vCloud Networking and Security
Edge (Edge) devices can be available in only one site at a time.
Having the hosts in maintenance mode on the r
ecovery side enforces this and also keeps them
in sync with all of the changes that happen at the primary site.
Removal of the primary interface after failover avoids loss of traffic for the primary site to a nonexistent interface
in the case of partial environment recovery. T
his is because
Edge always prefers
the locally attached interface for sending traffic instead of sending all traffic out of the default interface. The designation of a default interface is used only for cases where there are no locally attached networks. The Edge device uses this interface to send all unknown destination traffic to its designated default router. It is
prudent in the case where the environment might be failing back to its primary site to save all interface-
based rules and configurations before removal. This is because
all configurations associated with the interface are removed as soon as an interface is removed.
vCloud p
rimary sites that have d
irect organization n
etworks do not use
VXLAN so the recovery process is
identical to the existing vCloud DR r
ecovery process.
All of the vApps on that network must
have IP addresses reassigned
to the correct addressing used in the r
ecovery site Layer 3 network.
vCloud p
rimary sites that use isolated networks that are VLAN-
backed must
be recreated at the recovery site using the associated VLAN IDs available at the recovery site and the vApps reconnected to the new network.
If the Isolated networks were port
group-
backed, the port groups still exist in the recovery site, but their definitions must
be revisi
ted to verify that their configurations
remain
valid.
vCloud p
rimary sites that use r
outed or isolated VXLAN-
backed networks are easy
to recover due to VXLAN technology.