Within environments where a dedicated backup network is specifically selected, Enterprise Vault backups may not protect partition and index resource locations configured within Enterprise Vault to use a DNS alias.
If the "Allow use of any available network interface, subnet, or protocol for Backup Exec agents not bound to the above network interface, subnet, or protocol” option is selected in "Network and Security", the job will complete but will utilize the production network.
The Media Server was unable to connect to remote machine vaultserver.domain.local using subnet 10.0.0.0/23 on network interface Network Team.
Backup Exec determines the subnet for an interface based on entries in the Advertisement Cache, which stores details on Remote Agents advertising back to the media server. The Backup Exec Remote Agent does not publish information for Enterprise Vault Index and Partition resources configured with DNS alias and assumes these resources possess a 255.255.255.255 subnet mask.
This issue is resolved in Backup Exec 2014 or later versions.
To resolve this issue and receive the new Backup Exec improvements please upgrade to the current version of Backup Exec.
NOTE: Symantec continues to focus on the current release and future releases, there are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see http://www.symantec.com
1. From Backup Exec default or individual job settings, select "Network and Security".
2. Check the "Allow use of any available network interface, subnet, or protocol for backup Exec agents not bound to the above network interface, subnet, or protocol”
This may cause traffic to run over the production network, but will allow for a successful backup of Enterprise Vault Partition and Index resources.
This issue applies to environments which possess dedicated backup networks and interfaces. Upon deeper investigation, individual machines belong to the same network and subnet.