01-02-2013 10:21 PM
I need some help regarding Netbackup MSDP, I ma getting status 84 and upon further going though the logs:
01-02-2013 11:56 PM
NetBackup is the right forum for MSDP queries - I have moved the post.
Please show us all text in Activity Monitor details tab.
Also let us know exact NBU version and patch level - there have been many MSDP fixes over the last 2 years...
Please post bptm log as File attachment.
It seems that you have found TN http://www.symantec.com/docs/TECH183707 , right?
3. If "put=No," examine the <storage_path>/log/spoold/spoold.log file for the following message:
Storage Cache Manager: load completed
The message means that spoold finished loading the fingerprints. However, the new state probably has not been pushed to all processes yet.
4. If the spoold.log has the message, wait 5 minutes then run "crcontrol --getmode" again.
5. If "put=Yes," cache loading is complete and normal operations will resume.
If "put=No," contact your Symantec support representative.
01-03-2013 01:22 AM
Apologies for that. Activity monitor tab:
01-03-2013 02:44 AM
Seems this is a bug that is resolved in 22.214.171.124.
See this TN: http://www.symantec.com/docs/TECH190714
The TN is for Windows, but probably applies to Unix as well...
**** Hopefully Martin an Mark will be along soon with some more suggestions ****
01-03-2013 02:55 AM
You currently have PUT and STORAGED set as NO
It looks like storaged or queue processing has crashed and after 5 retries it locks itself down so will not allow anything to work again.
If you take a look in the storaged.log you will probably find a line telling you that with a nice little comment saying "contact support immediately" - worth doing anyway to try and trace what caused your issues but I guess for now you want to get it up and running so try the following:
Check spoold is actually running - if it is i would re-start it anyway (if in doubt reboot the server)
Next you need to run queue processing manually /usr/openv/pdde/pdcr/bin/crcontrol -processqueue
This will re-activate everything for you and then watch the --getmode until the PUT and STORAGED both change to YES (may well take 20 minutes or so as it needs to do a run through its logs to bring itself back on line)
Hope this gets you up and running - if not lets see some of the storaged.log to see what else is going on