Best Practices for Integrity Virtual Machines

16/19
Leverage Existing Topologies
The topology of existing configurations is, typically, created for good reason. This may be more
important for networking than for other devices. For example, if existing servers have two network
connections – one for general use and another for backups then take care when virtualizing those
connections as illustrated in Figure 7. Carelessness in configuring them can result in serious
performance (and perhaps functionality) problems that did not previously exist. In this example,
interactive response times may increase on one VM due to its sharing a physical NIC with multiple,
traffic-intensive, backup connections.
Contrast this with Figure 8 which reflects the topology in the configuration of the virtual NICs so that
they are associated with virtual switches connected to the appropriate network connections for
general use and backups.
Figure 7 – Do not be careless in mapping virtual NICs to virtual switches as
illustrated in this example. Performance and functionality problems can be created
by not maintaining existing network topologies.
Integrity VM Host
VM
Backup
vswitch
VM VM VM
Interactive
vswitch
SUBNET X SUBNET Y
Integrity VM Host
VM
Backup
vswitch
VM VM VM
Interactive
vswitch
SUBNET X SUBNET Y