Netbackup 7.5 Master server installation on Windows 2008 R2 SP1
Hi Everyone,
I am facing a problem while installing the master server setup on a windows 2008 r2 sp1 machine. The setup goes on fine till the stage where it calls and waits for the completion of tpext.exe command. When the command is initialized and I check the services column I find the nbemm.exe services running and after a while the execution attempts to stop the nbemm.exe service and proceed ahead for the setup to complete.
Now the issue is the setup keeps itself waiting for hours for the tpext.exe command completion which doesn't complete just because the setup on its own is unable to stop the nbemm.exe service. When I manually kill the nbemm.exe service via command line the setup proceeds ahead and gives the message of successful installation. But when I start the console and in host properties when I click on master server it gives the error "Unable to communicate with the EMM server : 77 " "Unable to list the devices".
I have tried formatting the system. Also upgrading the Netbackup version to 7.5.0.3 but in vain. Kindly help me with this issue.
Finally we were able to fix the most critical issues that we were working on since the past few days.
- This was a network problem on the ILO of a chassis wherein when we were trying to install the Master server setup it used to stuck at tpext.exe and this was solved when we monitored the system very minutely where we had an eye on the network behavior and suddenly when the ping response for the master server went down the master server console started working fine.
- The above issue was resolved when we removed the teaming done between the NICs and after installation and configuration when we re-teamed the NICs the setup worked absolutely normal.
- The second issue was with the multihomed network that we had here with the media servers on AIX platform as they were unable to communicate to the master server whereas the master server was perfectly communicating with the media server. We checked our configuration several times but could not find the solution to the problem.
- This particular issue resolved when we made just one single entry in the bp.conf file for media server i.e “Preferred_Interface <master server ip> match <media server ip>” . This one single line resolved the problem and the media server started communicating with master server.