01-12-2016 03:02 PM
01-12-2016 05:34 PM
Hi Myousuf,
I'm guessing you had all NetBackup services shut down while doing your P2V (I hope so)? Leaving the hostname unchanged, but changing the IP address is supported. Have you tried the following steps?:
1) Shutdown all NetBackup services
2) ipconfig /flushdns
3) bpclntcmd -clear_host_cache
4) Start all NetBAckup services
NetBackup may still have the old IP address cached. I would also check your hosts file in case you have an entry there with the old IP address.
Hope this helps,
Steve
01-13-2016 06:20 AM
What is the output for nbdb_ping ?
Is nbemm and pbx_exchange running ?
As mentioned earlier check for /etc/hosts file of the master server for old entries with other ip ?
Check
Configure the logs for nbemm service using the following command:
Girish
01-13-2016 12:04 PM
There might be some indication of the problem in the NetbackupDB/log/server.log and the Netbackup/logs/nbdb/ logs
Have some times been able to start a problematic Netbackup Relational Database service by:
Shutting down Netbackup using bpdown -f -v in an elevated prompt
Running the Netbackup Relational Database service command by hand in an elevated prompt
Wait for the dbsrv process to stop, usually runs a short time
Start the Netbackup Relational Database service manually
Start Netbackup using bpup -f -v in an elevated prompt, if the Netbackup Relational Database service started and stayed started of at least a couple of minutes
Going from physical to virtual, the problem can be the disk response time, think the recommendation is not more than 20 ms for the drive hosting the NBDB
Could also be caused by a keeping time on the DNS server or the PTR not updated at the DNS register done by the server at reboot.
I would start with nslookup of the servername and the new ip-address to see there was a mismatch in a DNS record