netbackup operational manager problems

[cfearn]

Hi,

we've just upgraded to netbackup 6.0, running on a solaris 10 box. We've installed netbackup operational manager (NOM)on a different solaris 10 box, and after several days of fiddling, have managed to get the web interface up and running. However, we're having difficulties with the interaction between the NOM server and the netbackup server. We've defined a master netbackup server within NOM, but the master server keeps going into an offline state on the NOM monitoring screen, and the job monitoring reports incorrectly (ie, saying there are 2 active jobs when there are none). We're also unable to drill down into job logs, as we keep getting errors saying NOM cannot communicate with the netbackup server. The netbackup server itself is running fine with only some initial problems. Restarting all netbackup and NOM processes hasn't helped, neither has re-installing NOM, or re-booting.

Does anyone have any ideas before I throw the whole thing out the window??

cheers,

cf

 

[syjl]

According to page 50 of the release notes, Solaris 10 is not supported nor is 64 bit. You may be trying to do the impossible??

 

[tech2004]

NOM is supported for Solaris. Page 20 of the Operations Manager Getting Started Guide starts the planning and installation of NOM for Solaris. Were there any issues when you installed and setup the pre-req's for NOM, VxPBX and VxSSAT from the Veritas ICS CD?

 

[syjl]

tech2004

Yes. NOM is supported for Solaris 8 and 9 32 bit unless you have some info that is not in the documentation. Also, do not install NOM on the master or media servers.

 

[tech2004]

I would agree with your statement about not installing NOM on your Master Server unless you are sure you have a good catalog backup to recover from in case of database problems.

"Veritas Netbackup 6.0 Release Notes - Additional Operational Notes" dated September 2005 shows Solaris 10 as being supported for NOM installation, no 64 bit support on page 53.

http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/278130.pdf

Still would be a good idea to call support to verify though.

 

[cfearn]

hi, thanks for your comments. We did call symantec/veritas who confirmed that NOM is supported on solaris 10. NOM is installed on a server that has no other netbackup processes running on it besides the client. We're re-installed several times, patched both netbackup and solaris and still no joy.

There were no issues when we installed the pre-reqs - VxSSat etc. NOM appears to start up fine, it's just the comms between the NOM server and the master. I have tried re-establishing the trust relationship too.

 

[tech2004]

cfearn, I dont know if this will help but have you tried adding info for each of those Servers into the host file. I had an issue once where my master server wouldnt communicate with a client. I added the name and ip address of the client into the host file of the master server and vice versa. The master server could then communicate with the client and the backups were successful. I know this deals with something different but it may help. I dont know much about Solaris since I am working in a Windows environment.

 

[cfearn]

thanks for all suggestions. I have finally got NOM working by syncing the clocks on the NOM and netbackup server through NTP. NOM however doesn't give me the granularity I require when it comes to reporting on backup failures, and it's really slow to come up with the information, so I think I'll be giving up on this product anyway!

cheers!