Updated on 2022-08-04 GMT+08:00

Planning the Network

Before installing and configuring eBackup, you need to understand the network requirements and suggestions for eBackup to facilitate network planning.

Typical Networking Suggestions

By default, eBackup has five network planes. You need to plan an IP address for each network plane to ensure communication between eBackup and peripheral components. Network Planes describes the network planes. This section describes typical networking suggestions for eBackup in VMware backup to the cloud.

  • Plan two IP addresses for eBackup: an internal IP address and a public IP address.

    In this scenario, ensure that the internal IP address can communicate with the terminal that accesses the eBackup management plane, vCenter Server/ESXi host, and production storage; ensure that the public IP address can communicate with the backup storage.

    In this case, configure two NICs for eBackup. One is configured with the internal IP address, and the other with the public IP address.

    The production management plane, backup management plane, internal communication plane, and production storage plane of eBackup are integrated and bound to the NIC using the internal IP address. The eBackup backup storage plane is bound to the NIC using the public IP address.

    Table 1 lists the example IP addresses of eBackup network planes and peripheral components.

  • Plan one IP address for eBackup.

    In this scenario, ensure that the IP address can communicate with the terminal that accesses the eBackup management plane, vCenter Server/ESXi host, production storage, and backup storage.

    In this case, configure one NIC for eBackup and configure an internal IP address for the NIC.

    All eBackup network planes are integrated. The production management plane, backup management plane, internal communication plane, production storage plane, and backup storage plane of eBackup are bound to the same NIC.

    Table 1 lists the example IP addresses of eBackup network planes and peripheral components.

Network Planes

Figure 1 shows the eBackup network planes.

Figure 1 eBackup network planes
Table 1 eBackup network plane description

Item

Description

Example Configuration (Two IP Addresses Planned)

Example Configuration (One IP Addresses Planned)

Terminal that accesses the eBackup management plane

The terminal uses the IP address of the eBackup management plane to access the eBackup system to configure and manage backup and restoration services.

192.168.1.11

192.168.1.11

vCenter Server/ESXi host

Centrally manages vCenter Servers or ESXi hosts of VMware VMs.

192.168.1.15

192.168.1.15

Production storage

Production storage connected to the VMware virtual environment

192.168.1.16

192.168.1.16

Backup storage

Purchased vault that stores backup data

10.10.1.15

192.168.1.18

Management plane

  • Production management plane

    Network plane between the backup server, backup proxy, and vCenter Server/ESXi host

  • Backup management plane

    Network plane between the backup server, backup proxy, and terminal that accesses the eBackup management plane

192.168.1.10

192.168.1.10

Internal communication plane

Network plane between the backup server and backup proxy

192.168.1.10

192.168.1.10

Production storage plane

Network plane between the backup server, backup proxy, and production storage

192.168.1.10

192.168.1.10

Backup storage plane

Network plane between the backup server, backup proxy, and backup storage

10.10.1.10

192.168.1.10