Physical infrastructure for the Veeam server with IBM Cloud bare metal servers
Veeam all-in-one servers
This design uses IBM Cloud® bare metal servers in an all-in-one model with SATA disks as Direct Attached Storage (DAS) by using both RAID 1 and RAID 6 disk arrays. RAID 1 is used for the operating system and configuration database, and RAID 6 for the backup repository. An overview of the physical setup is shown in the following diagram.
The server CPU and RAM are sized to handle up backups for 500 VMs. You can select the backup storage repository size with RAID 6 with 8 physical disks of 2 TB, 6 TB, or 12 TB, which result in an effective capacity of 12 TB, 36 TB, or 72 TB.
RAID health is monitored through the IBM Cloud standard RAID monitoring for bare metal servers. For more information, see Name and location of the RAID monitoring daemon.
You can configure RAID alerts to bypass the monitoring process by changing the SMTP server and notification email destination in the configuration for a RAID card. However, if you change these configurations, IBM cannot notify you of RAID issues or track the problem until resolution. You are advised not to alter the provided configuration.
Network requirements
Each Veeam® bare metal server is deployed with dual private only 10 GbE NICs with standard NIC teaming.
The Veeam bare metal servers are deployed to have connectivity to the following infrastructure VLANs:
| VLAN | Designation | Traffic type |
|---|---|---|
| VLAN 1 | Private A | ESXi management, management, Geneve (TEP) |
| VLAN 2 | Private B | vSAN, NFS, vMotion, and Edge Geneve (TEP) |
The Veeam bare metal servers are natively provisioned to VLAN 1, and they need the following IP address from the private primary subnet of VLAN 1: One IP address for the all-in-one server, which is deployed and configured during server provisioning of the nontagged VLAN 1.
Each Veeam bare metal server needs to be VLAN trunked to VLAN 2. They need the following IP address from the private portable subnet of the VLAN 2: One IP address for the all-in-one server from the NFS or vSAN subnet, which is configured through the automation on the tagged VLAN 2.