This is expected. If you used the virtual name in the backup policy, you will only see that as a Client under the Hosts in the java console. If you try to connect to it, you will see that it is actually connecting to the active cluster node.
I understood, but I already have policy for this client, this a cluster hyper-v with node1 and node2, but in the policy was set clusterhv, so I can't see node1 and node2.
This is expected. If you used the virtual name in the backup policy, you will only see that as a Client under the Hosts in the java console. If you try to connect to it, you will see that it is actually connecting to the active cluster node.
Thanks for suggestion, sorry about my answer so later.
That's make sense because I used my virtual name in the backup policy, but when I went to Client under the hosts in console unfortunately I didn't see my virtual name BUT maybe is because my virtual name doesn't has client NBU installed, right? So I suppose everything is fine ..
What is the output of bptestbpcd -verbose -client <clusterhv fqdn>?
Also, are there any host mappings pending in the console?
Thanks for suggestion, sorry about my answer so later.
No one host mappings pending in the console
