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

Backup failed after Netbackup 8.1 client re-installation with virtual hostname.

Hi,

Netbackup failed with below erros after client re-installation iwth vitual hostname. 

Looks like certificate issue.

Error bpbrm (pid=286313) [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 1:12:13 PM - Error bpbrm (pid=286313) cannot send mail because BPCD on dwebapp1.kddc.local exited with status 61: the vnetd proxy encountered an error

 

Please advice,

Regards,

Rahul.

Tags (2)
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Backup failed after Netbackup 8.1 client re-installation with virtual hostname.

@Rahul_Mekkalki 

You will have to check the entry for Virtual name under

  1. In the NetBackup Administration Console, expand Security Management > Host Management. > Mappings for approval > Select Vitual name and approve the mapping

 

Important thing to note is the hostname with which it is trying to add the appings. 

View solution in original post

4 Replies
Highlighted

Re: Backup failed after Netbackup 8.1 client re-installation with virtual hostname.

@Rahul_Mekkalki 

Perform same steps as stated in other thread.

https://vox.veritas.com/t5/NetBackup/Re-Netbackup-8-1-client-and-Windows-failover-cluster/m-p/864466...

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.
Highlighted

Re: Backup failed after Netbackup 8.1 client re-installation with virtual hostname.

Hi,

It is not cluster setup. We have specific requirement to use virtual name.

We have installed client successfully. But we are facing below error .

Error: 8618, Message: Connection is dropped, because the host ID-to-hostname mapping is not yet approved

 Looks like certificate issue.

Please advice.

Highlighted
Accepted Solution!

Re: Backup failed after Netbackup 8.1 client re-installation with virtual hostname.

@Rahul_Mekkalki 

You will have to check the entry for Virtual name under

  1. In the NetBackup Administration Console, expand Security Management > Host Management. > Mappings for approval > Select Vitual name and approve the mapping

 

Important thing to note is the hostname with which it is trying to add the appings. 

View solution in original post

Highlighted

Re: Backup failed after Netbackup 8.1 client re-installation with virtual hostname.

Hi,

Issue resolved.

Thanks for support.

Regards.