cancel
Showing results for 
Search instead for 
Did you mean: 

unable to add RHV manager to NB master

Riadh_R17
Level 4

Hi @all

We are unable to add the RHV manager in the netbackup webui

error message saying invalid authentication informations

we entered this fileds as below

- FDDN of the RHV manager

- username of the RHV manager : "root"

- password of the rhv manager user root : "PasswOrd"

- selecting the backup host : the master/media server which is the appliance 5250 in our case.

Your help please :)

1 ACCEPTED SOLUTION

Accepted Solutions

The problem was related to rhv hosts hostnames which should be added also in netbackup master hosts file and vice versa

the hostname of the rhv manager only is insufficient.

vxms logs in the backup host which is the master in my case was so helpful to identify the problem.

thank you @NurgulG for your help and answers :)

View solution in original post

6 REPLIES 6

NurgulG
Level 3

Hi,

Please check the following guides, you have to set CA sertificate from RHV and you have to enable virtualization in the bp.conf. i hope it works for you :)

https://www.veritas.com/content/support/en_US/doc/135031700-136106577-0/v137459713-136106577

https://www.veritas.com/content/support/en_US/doc/135031700-136106577-0/v136800511-136106577

Best Regards

 

Thank you @NurgulG for your answer

PS : we set VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED  to NO

it was resolved by entering "admin@internal" in the username field in place of root  (even admin without @internal wouldnt work)

we can now successfully add the RHVM in NetBackup  webui and get all its VMs.

but the backup of VM fails after creating the protection plan to backup VMs

here below job details

janv. 24, 2023 1:15:07 PM - Info nbjm (pid=320782) starting backup job (jobid=45) for client a5f7cdb3-818d-4e87-b475-940c5d4ee07a, policy BACKUPNOW+4287d509-a726-467b-bd7a-a55ebc830061, schedule FULL_be31d543-b1e4-4dfe-841a-84d915623a2f
janv. 24, 2023 1:15:07 PM - 0 ko estimés nécessaires
janv. 24, 2023 1:15:07 PM - Info nbjm (pid=320782) started backup (backupid=a5f7cdb3-818d-4e87-b475-940c5d4ee07a_1674562507) job for client a5f7cdb3-818d-4e87-b475-940c5d4ee07a, policy BACKUPNOW+4287d509-a726-467b-bd7a-a55ebc830061, schedule FULL_be31d543-b1e4-4dfe-841a-84d915623a2f on storage unit stu_disk_srv-backup using backup host srv-backup
janv. 24, 2023 1:15:07 PM - Info bpbrm (pid=303096) The data-in-transit encryption (DTE) is disabled for the client (srv-backup) as the global DTE mode is set to 'Preferred Off' and the client DTE mode is set to 'Automatic'
janv. 24, 2023 1:15:07 PM - processus démarré bpbrm (pid=303096)
janv. 24, 2023 1:15:08 PM - Info bpbrm (pid=303096) a5f7cdb3-818d-4e87-b475-940c5d4ee07a is the host to backup data from
janv. 24, 2023 1:15:08 PM - Info bpbrm (pid=303096) reading file list for client
janv. 24, 2023 1:15:08 PM - Info bpbrm (pid=303096) starting bpbkar on client
janv. 24, 2023 1:15:08 PM - Info bpbkar (pid=303106) Backup started
janv. 24, 2023 1:15:08 PM - Info bpbrm (pid=303096) bptm pid: 303125
janv. 24, 2023 1:15:08 PM - Info bptm (pid=303125) start
janv. 24, 2023 1:15:08 PM - Info bptm (pid=303125) using 262144 data buffer size
janv. 24, 2023 1:15:08 PM - Info bptm (pid=303125) using 30 data buffers
janv. 24, 2023 1:15:08 PM - Info bptm (pid=303125) start backup
janv. 24, 2023 1:15:08 PM - connexion
janv. 24, 2023 1:15:08 PM - connecté ; temps de connexion : 0:00:00
janv. 24, 2023 1:15:09 PM - début de l’écriture
janv. 24, 2023 1:15:10 PM - Info bpbkar (pid=303106) INF - Backing up Hypervisor Type RHV, VM Server 192.168.3.28, VM GUID a5f7cdb3-818d-4e87-b475-940c5d4ee07a, Display Name zmstore02
janv. 24, 2023 1:15:11 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:12 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:13 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:14 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:16 PM - Info bpbkar (pid=303106) 58 entries sent to bpdbm
janv. 24, 2023 1:15:16 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:16 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:16 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:16 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:16 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:17 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:18 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:19 PM - Warning bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: WRN - Failed to download the disk. Error: Couldn't resolve host name
janv. 24, 2023 1:15:35 PM - Critical bpbrm (pid=303096) from client a5f7cdb3-818d-4e87-b475-940c5d4ee07a: FTL - cleanup() failed, status 11
janv. 24, 2023 1:15:37 PM - Error bptm (pid=303125) media manager terminated by parent process
janv. 24, 2023 1:15:41 PM - Info srv-backup (pid=303125) StorageServer=PureDisk:srv-backup; Report=PDDO Stats (multi-threaded stream used) for (srv-backup): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled, where dedup space saving:100.0%, compression space saving:0.0%
janv. 24, 2023 1:15:42 PM - Critical bpbrm (pid=303096) unexpected termination of client a5f7cdb3-818d-4e87-b475-940c5d4ee07a
janv. 24, 2023 1:15:42 PM - Info bpbkar (pid=0) done. status: 11: system call failed
janv. 24, 2023 1:15:42 PM - fin de l’écriture ; temps d’écriture : 0:00:33
échec d'appel système(11)

NurgulG
Level 3

Hi,

You need high verbose bpbkar and VxMS logs on the backup host and also hostname resolution for netbackup appliance to RHV Managers, maybe you can add the hostname in the appliance host files. RHV managers also should be able to resolve appliance hostname. Can you also check following ports please?

 

NurgulG_0-1674567335494.png

Best Regards

Thank you @NurgulG  for your answer.

All ports are open and tested in bi directional

Hostnames are enetered in /etc/hosts of both Master/Media NetBackup and RHVM

RHVM was successfully added in netbackup webui by its FQDN.

The problem was related to rhv hosts hostnames which should be added also in netbackup master hosts file and vice versa

the hostname of the rhv manager only is insufficient.

vxms logs in the backup host which is the master in my case was so helpful to identify the problem.

thank you @NurgulG for your help and answers :)

NurgulG
Level 3

Hi,

I'm glad the problem is solved, have a nice day :)

Best Regards