I am attempting to back up a 3 node DAG and have a problem that appears occasionally. Each Exchange node has a Production NIC and a Backup (.bkup) NIC. When we installed Netbackup on the Exchange nodes we did so using the .bkup NIC. For example, the Netbackup Client Properties on the exchange servers list the client as 'ExchNode1.bkup.domain.org.uk' and 'ExchNode2.bkup.domain.org.uk'. This naming convention is identical in both the Preferred Server List within the DAG policy and also in the Client list within Host Properties.
When the DAG policy launches it spwans a child job(s) and uses the exact name of the exchange nodes listed above (presumably taken from the preferred server list). However, despite the 2nd last backup being successful using *.bkup.domain.org.uk, the last backup ran attempted to use 'Exch Node1.domain.org.uk', i.e. it drops the *.bkup. Why is the DAG backup doing this when .bkup is specified on the client itself, within the DAG policy and also within the Host Properties on the Master server.
The parent job is giving me a 'Client Name Mismatch(39)' and I can see within the child job it's attempting to use the non *.bkup name.
