cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Re: Netbackup 8.1 client and Windows failover cluster

Error bpbrm (pid=266152) [PROXY] Received status: 7648 with message Peer host validation failed for SECURE connection; Peer host: dwebapp1.kddc.local, Error: 8618, Message: Connection is dropped, because the host ID-to-hostname mapping is not yet approved..
Mar 10, 2019 11:59:59 AM - Error bpbrm (pid=266152) cannot send mail because BPCD on dwebapp1.kddc.local exited with status 61: the vnetd proxy encountered an error

How to resolve this error?

Please advice.

 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Netbackup 8.1 client and Windows failover cluster

@Rahul_Mekkalki 

NetBackup client should always be installed using node name on cluster nodes. Please DO NOT use virtual name while installation as it causes other issues. Reason is ... you can have more than one application in single cluster and they will have different virtual name hence node name should be used for NetBackup client installation.

In 8.1 you need to perform this additional task of host mappings.

https://www.veritas.com/support/en_US/doc/21733320-127424841-0/v126691256-127424841

Adding shared or cluster mappings

In certain scenarios, host ID to host name mappings are shared across host IDs. For example, in a cluster setup, virtual name is shared across all nodes. You need to add these shared mappings using the NetBackup Administration Console so that the master server can successfully communicate with the nodes.

See Add or Remove Host Mappings dialog box.

To add shared mappings

  1. In the NetBackup Administration Console, expand Security Management > Host Management.
  2. On the Hosts tab, in the details pane, right-click to view the options.
  3. On the right-click options, select Add Shared or Cluster Mappings.
  4. On the Add Shared or Cluster Mappings dialog box, specify the shared mapping name.

    See Add Shared or Cluster Mappings dialog box.

  5. Select host IDs to be mapped with the specified shared mapping name.
  6. Click Save.

View solution in original post

2 Replies
Highlighted

Re: Netbackup 8.1 client and Windows failover cluster

Initially we installed client with physical hostname. Then there was requirement to install with virtual host name.

So we have uninstalled netbackup client 8.1 and then installed with virtual hostname.

Since then we are facing this issue. Looks like certificate issue.

 

Please advice.

Highlighted
Accepted Solution!

Re: Netbackup 8.1 client and Windows failover cluster

@Rahul_Mekkalki 

NetBackup client should always be installed using node name on cluster nodes. Please DO NOT use virtual name while installation as it causes other issues. Reason is ... you can have more than one application in single cluster and they will have different virtual name hence node name should be used for NetBackup client installation.

In 8.1 you need to perform this additional task of host mappings.

https://www.veritas.com/support/en_US/doc/21733320-127424841-0/v126691256-127424841

Adding shared or cluster mappings

In certain scenarios, host ID to host name mappings are shared across host IDs. For example, in a cluster setup, virtual name is shared across all nodes. You need to add these shared mappings using the NetBackup Administration Console so that the master server can successfully communicate with the nodes.

See Add or Remove Host Mappings dialog box.

To add shared mappings

  1. In the NetBackup Administration Console, expand Security Management > Host Management.
  2. On the Hosts tab, in the details pane, right-click to view the options.
  3. On the right-click options, select Add Shared or Cluster Mappings.
  4. On the Add Shared or Cluster Mappings dialog box, specify the shared mapping name.

    See Add Shared or Cluster Mappings dialog box.

  5. Select host IDs to be mapped with the specified shared mapping name.
  6. Click Save.

View solution in original post