Hi, i'm facing some problems with Backup Exec 15, i've created a backup network on a virtual server with 2 interfaces, one for lan and other for backup.
Yesterday i started a backup but unfortunately, it is going to the incorrect interface, for instance, it starts on X interface(correct) and after a few minutes, the traffic change to Y interface(wrong).
What can i do to solve this?
If performing virtual agent backups then it is difficult to configure scondary networks for Backup Purposes as we have to use whatever the vCenter server is providing, so you would have to originally configure your vCennter to communicate with all ESX hosts on the same secondary network. Best Practice if you want to backup VMs in VMware without using the LAN is actually to use SAN Transport to backup and don't even try to use a secondary network. Hence we do not really support such a configuration
If using traditional agent backups, then each server (or vitual server in your case) that you want to backup will have to name resolve to the IP address on the secondary network and similarly the Backup Exec Server must name resolve from each server being backed up using it's IP address on the secondary network which in most environments means using host files to overrule DNS records. The secondary network of course has it's own IP address scheme that is separate from that of the main LAN. Doing tihs in virtual machines does result in both having to configured extra networks to your virtual machines and loses the simple DR restore capability (for each VM) that is possible from VMware agent backups
