Client hostname cannot be found in this context can mean that the master server cannot resolve the DAG name to a representative Exchange server. This probably means the Exchange DAG discovery I mentioned is not working.
Things to check:
- bprd log around the error should tell you about the failure to find a node for the DAG.
- Files with Exchange in their name on the master server at NetBackup/db/discovery. There should be an exchange.xml file and .dat file for each node of the DAG. If not, check the NetBackup Discovery Framework service on each client. The logs are in the nbdisco folder. Find all occurrences of ExchangeExplorer. If you don't find where ExchangeExplorer finds the DAG name and sends it to the master, look for a reason why it doesn't.
- Note that nbdisco should run as the NetBackup Exchange user called for in the doc. The best way to do this is to configure it in the host properties of each client.
- After setting the Exchange user in the host properties for each Exchange server, restart the NetBackup Discovery Framework service on each machine. After a few minutes, the exchange.xml and exchange.dat files should appear on the master server. The master chooses the most recent (last) client to send its discovery data to represent the DAG.
- If you do find the .xml and .dat files for at least one Exchange server in the DAG, please share them here.
- As Marianne suggested, can you ping every Exchange server from the NetBackup master?
(In this context, the "virtual name" is the DAG name.)