cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

MediaServer was re-IP'd - now seeing multiple issues

Go to solution
Bruce_Clegg
Level 5

‎08-22-2017 09:33 AM

We needed to move our media server running netbackup 8.0 to a different network segment.  Once this was accomplished we've encountered several issues: 

The Netbackup GUI takes a very long time to load and when it does, the activity monitor fails: "The Activity Monitor failed because of Operation now in progress.  For more details refer to the log files".  Looking under the Daemons tab, nbvault, bmrd, bpinetd, nbftclnt, nbkms,spoold, spad, nbazd, nbftsrvr, and nbfdrv64 daemons are stopped.

Not sure which log files to check.

When I attempt to look at the policies, they eventually display, but I get the error: !Backup Policy Management - Cannot connect on socket(25) - Can not connect to Remote Service:{DARSManagement-u1mannbu01p] (Status 25)

Probably more issues in the GUI - looking at the OS (linux 7.3) I see in /var/log/messages:

Aug 22 10:13:38 u1mannbu01p netbackup: NetBackup Policy Execution Manager started.
Aug 22 10:13:38 u1mannbu01p netbackup: NetBackup Storage Lifecycle Manager started.
Aug 22 10:13:38 u1mannbu01p netbackup: NetBackup Remote Monitoring Management System started.
Aug 22 10:13:38 u1mannbu01p netbackup: NetBackup Key Management daemon started.
Aug 22 10:13:38 u1mannbu01p netbackup: NetBackup Service Layer started.
Aug 22 10:13:38 u1mannbu01p netbackup: NetBackup Indexing Manager started.
Aug 22 10:13:38 u1mannbu01p netbackup: NetBackup Agent Request Server started.
Aug 22 10:13:39 u1mannbu01p netbackup: NetBackup Bare Metal Restore daemon not started.
Aug 22 10:13:39 u1mannbu01p su: (to nbwebsvc) root on none
Aug 22 10:13:39 u1mannbu01p systemd: Started Session c2 of user nbwebsvc.
Aug 22 10:13:39 u1mannbu01p systemd: Starting Session c2 of user nbwebsvc.
Aug 22 10:14:21 u1mannbu01p systemd-logind: New session 3 of user jshewey.
Aug 22 10:14:21 u1mannbu01p systemd: Started Session 3 of user jshewey.
Aug 22 10:14:21 u1mannbu01p systemd: Starting Session 3 of user jshewey.
Aug 22 10:15:46 u1mannbu01p netbackup: NetBackup Web Management Console started.
Aug 22 10:15:46 u1mannbu01p netbackup: NetBackup Vault daemon started.
Aug 22 10:15:46 u1mannbu01p netbackup: NetBackup CloudStore Service Container started.
Aug 22 10:15:46 u1mannbu01p netbackup: NetBackup Service Monitor started.
Aug 22 10:15:46 u1mannbu01p nbvault: Starting nbvault daemon
Aug 22 10:15:46 u1mannbu01p nbvault: Vault License validation FAILED. Error=159
Aug 22 10:15:46 u1mannbu01p nbvault: Shutting down nbvault daemon
Aug 22 10:15:46 u1mannbu01p netbackup: NetBackup Bare Metal Restore Boot Server daemon started.
Aug 22 10:15:46 u1mannbu01p systemd: netbackup.service: control process exited, code=exited status=2
Aug 22 10:15:46 u1mannbu01p systemd: Failed to start LSB: NetBackup.
Aug 22 10:15:46 u1mannbu01p systemd: Unit netbackup.service entered failed state.
Aug 22 10:15:46 u1mannbu01p systemd: netbackup.service failed.
Aug 22 10:17:52 u1mannbu01p systemd: Starting Cleanup of Temporary Directories...
Aug 22 10:17:52 u1mannbu01p systemd: Started Cleanup of Temporary Directories.
Aug 22 10:18:44 u1mannbu01p bprd[4852]: Cannot contact NetBackup bpdbm. Terminating.
Aug 22 10:22:54 u1mannbu01p SQLAnywhere(nb_u1mannbu01p): Starting checkpoint of "NBDB" (NBDB.db) at Tue Aug 22 2017 10:22
Aug 22 10:22:54 u1mannbu01p SQLAnywhere(nb_u1mannbu01p): Finished checkpoint of "NBDB" (NBDB.db) at Tue Aug 22 2017 10:22
Aug 22 10:22:54 u1mannbu01p SQLAnywhere(nb_u1mannbu01p): Starting checkpoint of "NBAZDB" (NBAZDB.db) at Tue Aug 22 2017 10:22
Aug 22 10:22:54 u1mannbu01p SQLAnywhere(nb_u1mannbu01p): Finished checkpoint of "NBAZDB" (NBAZDB.db) at Tue Aug 22 2017 10:22
Aug 22 10:24:46 u1mannbu01p systemd: Starting LSB: NetBackup...
Aug 22 10:24:46 u1mannbu01p journal: Symantec Authentication: 51216,195,5962,1287501632,nbatd,0,root: 1,u1mannbu01p.int.digsigtrust.com,10.1.24.15,0,AT_INIT,10.1.24.15,ROOT,14,3,AT Broker started in RAB mode at audit level medium
Aug 22 10:24:46 u1mannbu01p nbatd[5962]: V-18--1 Failed to open the acceptor
Aug 22 10:24:46 u1mannbu01p nbatd[5962]: 51216,195,5962,1287501632,nbatd,1,root: 1,u1mannbu01p.int.digsigtrust.com,10.1.24.15,4,AT_BROKER,10.1.24.15,nbatd,16,0,AT_BROKER,AT Broker is shutdown with status -1
Aug 22 10:24:46 u1mannbu01p netbackup: NetBackup Authentication daemon started.
Aug 22 10:24:46 u1mannbu01p netbackup: NetBackup network daemon started.
Aug 22 10:24:46 u1mannbu01p netbackup: NetBackup client daemon started.
Aug 22 10:24:46 u1mannbu01p netbackup: NetBackup SAN Client Fibre Transport daemon started.
Aug 22 10:24:46 u1mannbu01p netbackup: NetBackup Discovery Framework started.
Aug 22 10:24:47 u1mannbu01p netbackup: NetBackup Authorization daemon started.
Aug 22 10:24:47 u1mannbu01p netbackup: NetBackup Event Manager started.
Aug 22 10:24:47 u1mannbu01p netbackup: NetBackup Audit Manager started.
Aug 22 10:24:48 u1mannbu01p netbackup: NetBackup Deduplication Manager started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup Deduplication Engine started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup Enterprise Media Manager started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup Resource Broker started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup request daemon started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup compatibility daemon started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup Job Manager started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup Policy Execution Manager started.
Aug 22 10:24:49 u1mannbu01p netbackup: NetBackup Storage Lifecycle Manager started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Remote Monitoring Management System started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Key Management daemon started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Service Layer started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Indexing Manager started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Agent Request Server started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Bare Metal Restore daemon not started.
Aug 22 10:24:50 u1mannbu01p su: (to nbwebsvc) root on none
Aug 22 10:24:50 u1mannbu01p systemd: Started Session c3 of user nbwebsvc.
Aug 22 10:24:50 u1mannbu01p systemd: Starting Session c3 of user nbwebsvc.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Web Management Console started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Vault daemon started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup CloudStore Service Container started.
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Service Monitor started.
Aug 22 10:24:50 u1mannbu01p nbvault: Starting nbvault daemon
Aug 22 10:24:50 u1mannbu01p nbvault: Vault License validation FAILED. Error=159
Aug 22 10:24:50 u1mannbu01p nbvault: Shutting down nbvault daemon
Aug 22 10:24:50 u1mannbu01p netbackup: NetBackup Bare Metal Restore Boot Server daemon started.
Aug 22 10:24:50 u1mannbu01p systemd: netbackup.service: control process exited, code=exited status=2
Aug 22 10:24:50 u1mannbu01p systemd: Failed to start LSB: NetBackup.
Aug 22 10:24:50 u1mannbu01p systemd: Unit netbackup.service entered failed state.
Aug 22 10:24:50 u1mannbu01p systemd: netbackup.service failed.

Any help is appreciated

 

0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions

Go to solution
RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

‎08-22-2017 10:20 AM

NetBackup's communication handler (PBX) keeps a cache of hostname, so if you're changed the IP address you need to clear the PBX cache (on everything that talks to the media server.........)

Have you ensured that you've got forward and reverse lookups configured for the media server name with the new IP? And if so, is that being reflected on the master, medias, clients?

IF so, run bpclntcmd -clear_host_cache on the servers and it will clear the cache. 

Then run bpclntcmd -hn "media server name" to see if it picks up the correct IP.

Then do the reverse, bpclntcmd -ip "media server ip" to see if reverse lookup works.

View solution in original post

3 REPLIES 3

Go to solution
RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

‎08-22-2017 10:20 AM

NetBackup's communication handler (PBX) keeps a cache of hostname, so if you're changed the IP address you need to clear the PBX cache (on everything that talks to the media server.........)

Have you ensured that you've got forward and reverse lookups configured for the media server name with the new IP? And if so, is that being reflected on the master, medias, clients?

IF so, run bpclntcmd -clear_host_cache on the servers and it will clear the cache. 

Then run bpclntcmd -hn "media server name" to see if it picks up the correct IP.

Then do the reverse, bpclntcmd -ip "media server ip" to see if reverse lookup works.

Go to solution
Thiago_Ribeiro
Moderator
Moderator
Partner    VIP    Accredited

‎08-22-2017 10:41 AM

Hi,

After this IP change, master and media remains communicating each other? Are these on the same network?

Are you able to test communication from media ==> master / master ==> media?

I'm asking because one of the firsts error messages is this below, and I think that is can be a communication problem.

Aug 22 10:18:44 u1mannbu01p bprd[4852]: Cannot contact NetBackup bpdbm. Terminating.

 

Regards,

 

Thiago

0 Kudos

Go to solution
Bruce_Clegg
Level 5
In response to RiaanBadenhorst

‎08-22-2017 11:26 AM

That was it - I cleared the cache, checked dns with bpclntcmd (came up with correct server name/ip) and restarted netbackup - all appears to be working.  Thank You!

0 Kudos