XCP-NG Backup and Migration Networks - Misunderstanding?

Computer Hardware & Server Infrastructure Builds
1

I think I’m fundamentally missing something here. When XOA does back ups to NFS, what specifically needs to talk to NFS? Is it XOA or the XCP-NG host, or do they both need it?

Reason I’m asking is I want to make a dedicated network for backups/migration. Should the IP of the backup/migration interface be on Network A (same network as XOA and XCP-NG hosts) or should it be on Network B, or does it just not matter?

If backup/migration is on Network B, where does the NAS go? Does it go on same network as XOA/XCP-NG or does it go on Network B? I can give XOA a secondary IP that is on Network B but that seems messy.

Having trouble finding this info and wrapping my head around it. Thanks for any input!

2

For backups XO needs to be able to talk to the “Remotes” which are the locations that the backups will be stored.If you wan to you can create a dedicated network for backups and add a second interface to XO within that network.

3

I followed video but still no progress. My dedicated mgmt is on 1gb copper.

I created a new network called BACKUP which is attached to a 10gb bond. Gave that network an IP and made it the default for backup/migrations under advanced pool options. I moved XOA to this network. I also made sure XOA can ping it. For simplicity I assigned it another IP on same network as hosts, xoa, and nas.

I watched network stats on host during backup and discovered the backup still uses the 1gb mgmt nic for backup traffic even though XOA is only connected to the 10gb ‘BACKUP’ network. I did specify the migration to use the 10gb BACKUP network.

It seems no matter what, XOA pulls the data via the hosts mgmt ip, then relays it to the NAS normally over the 10gb bond its attached to.

Any other ideas or might the only answer be to make sure mgmt interface is on 10gb as well?

Thanks!

4

Perhaps you do have to make the management IP the 10G, I would need to do more testing.

1 Like
5

Yes, I believe so. From my troubleshooting and user recommendation, my plan is to do dedicated 10GB NIC for MGMT and then a dedicated 10GB bond comprised of 2x NICS for VMs. Apparently mixing MGMT into the same bond as the VMs can cause some throttling issues, so the above 3 NIC solution should do it and is simple to follow. Thanks for the reply and the videos!

1 Like