03-13-2014 12:06 AM
I was advised to post this here aswell: https://www-secure.symantec.com/connect/forums/netbackup-ops-and-scom-2012-monitoring#comment-9907871
With reguards to monitoring Netbackup with SCOM 2012. SCOM 2012 does not allow a windows server to be added as a network device like SCOM 2007. How are people getting around this limitation in order to monitor Netbackup Ops with SCOM 2012? The documentation seems to be a rewrite of the 2007 documentation not taking this limitation into account.
Please advise how we can proceed.
03-13-2014 08:23 AM
Please Review Thread: https://www-secure.symantec.com/connect/forums/scom-2012-and-netbackup-7x
"SCOM 2007 R2 MPs work with SCOM 2012. There will be no SCOM 2012 specific management packs. The one exception if you have SCOM 2012 beta is that there is a specific SharePoint 2010 MP for SCOM 2012 but this is a due to a "bug" and this will be sorted by SCOM 2012 RTM."
03-14-2014 01:11 AM
Thanks for the response, however as I stated in my origional post, the steps outlined in the documentation are inorrect, as the section titled "Deploying the SCOM Management Pack for NetBackup" requires the Netbackup server to de discovered in SCOM as a network device in order for SCOM to receive SNMP Traps.
This is something that worked in SCOM 2007 but is no longer possible in SCOM 2012. I would like someone to advise how they have got around this and made this solution work.
03-24-2014 12:53 AM
Was anyone able to get this to work?
09-16-2014 03:55 AM
Has anyone been able to get this working? I'm seeing more and more posts about the same issue with no responses.
09-16-2014 11:24 AM
I haven't seen any updates to the SCOM discovery from a NetBackup / OpsCenter perspective.
Our most recent Technote, includes the SCOM 2007 Management Pack..
Microsoft System Center Operations Manager Management Pack for NetBackup OpsCenter
Which includes the PDF for
I have also included the PDF as an attachment to this post.
As for SCOM 2012 Network Discovery, it appears they have improved functionality of this, and there are several Blog / TechNet / Microsoft posts regarding this... many of them mention Firewall related issues:
UDP - ports 161 / 162 bi-directionally (needs to be opened)
I have not tested this in a lab, but recommend reviewing all documentation...
If you are still unable to achieve positive results, please open a case with Symantec Support and potentially Microsoft support.
If you have any questions, please let us know.
09-16-2014 11:26 PM
Thank you for the response. The documentation which is the same for SCOM 2007 still says "Discover the Netbackup server as a Network device" as I stated in my origional post this is not possible due the way SCOM 2012 handles discovery of windows servers (it filters them out of network discovery). Which means that this method will no longer work.
The fact that I am seeing many posts in this regard and no one can confirm that they have got it to work is a concern.
I've opened a case with Symantec to see what they say but I would still like to hear on the forums if anyone has successfully implimeted this.
10-01-2014 08:40 AM
Have you heard anything back from Symantec on this? We have run into the same issue where we can't discover using SCOM 2012. Thanks
10-23-2014 08:18 AM
Have created a poll about Maintence Pack for SCOM 2012 https://www-secure.symantec.com/connect/forums/do-you-want-netbackup-maintenance-pack-scom-2012
Please vote on it
10-29-2014 10:35 AM
There is a workaround for discovering Windows devices as Network Devices in SCOM 2012. There's a link that explains this:
Unfortunately, this doesn't help since the SCOM 2007 OpsCenter MP requires the subject Windows Server to be discovered as a "Legacy Network Device". You can't discover new network devices in SCOM 2012 as "Legacy Devices", only under SCOM's new network device model.
In short, the SCOM 2007 OpsCenter MP doesn't work, unless you rewrite the entire MP to use the new SCOM 2012 network device model.
Symantec really needs to update this MP, IMO. Even a simple update that doesn't change the function of the original MP, but changes the network device model would be helpful.