Highlighted

Symantec System Recovery & SNMP

We've a selection of customers running a range of versions from Backup Exec System Recovery 2010 to Symantec System Recovery 2013 R2.
I've enabled SNMP on each and have software to receive the traps running, but nothing is seen.
I'm picking up HP alerts so I know that the receiver is alive.
The MIB files (identical for each version it seems) have been uploaded to the management tool

There's very little in the way of settings in BESR/SSR - tick boxes and one dropdown so I'm assuming there is something behind the scenes that needs to be configured.

I've been reading through a variety of articles and manuals.

The manual basically says "Tick the boxes and choose from the dropdown" with nothing further.
Should I be configuring Windows SNMP services in a particular way or is there some other settings I'm missing somewhere?

Any suggestions?

Regards,
Greg

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

My apologies - entirely

My apologies - entirely forgot about this.

This was a variety of failures - mainly on my part.

One server had had the firewall settings reset blocking SNMP traffic, one had secondary SNMP software receiving the traps and somehow blocking the PRTG one and finally the MIBs had to be reuploaded due to a change in the way these were processed by PRTG (no longer had to be translated before use)

I don't have much further in the way of detail as we didn't continue on with SNMP.

Ended up moving to the PRTG IMAP sensor and email reports for backups as the SNMP sensor didn't support "Fail if no success seen in X hours"

Long story short - not a Symantec issue

--Greg

View solution in original post

7 Replies
Highlighted

Have a look here:

Have a look here: https://www-secure.symantec.com/connect/forums/monitoring-symantec-system-recovery-using-snmp

Highlighted

The Symantec reply there is

The Symantec reply there is the manual text - I've already ticked the boxes and chosen the message types.
Unfortunately this doesn't appear to be generating the SNMP traps.

My receiver is currently unfiltered so will report any trap it receives
The MIB has already been uploaded so the descriptions should be correct once it does receive them.

I'm assuming there's some additional tweaks required to the Windows Server SNMP service or something else required in addition to this...

Greg

 

 

Highlighted

Have an addition look

Have an addition look here:

http://kb.paessler.com/en/topic/4823-backup-exec-snmp

https://www-secure.symantec.com/connect/forums/system-recovery-and-snmp-traps

http://www.symantec.com/business/support/index?page=content&id=HOWTO83595

Highlighted

Hi Markus, I've actually

Hi Markus,

I've actually already read all three of those:

http://kb.paessler.com/en/topic/4823-backup-exec-snmp doesn't have an answer to the SNMP issue (and has the Event Log solution I'm putting in place in case this never works)

http://www.symantec.com/connect/forums/system-recovery-and-snmp-traps points towards using SSR-MS which isn't something I particularly want to use when we have other management software in place.

http://www.symantec.com/business/support/index?page=content&id=HOWTO83595 is again the manual text - I have most definitely ticked those boxes and changed that drop down plus uploaded the MIB

Thanks again,
Greg

Ok, this may just turn out to

Ok, this may just turn out to be some mistakes from myself - I think I've got it working on 2010 and 2011.

Will report back on where I went wrong once I've some more solid results.

Greg

Highlighted

Any updates here?

Any updates here?

Highlighted
Accepted Solution!

My apologies - entirely

My apologies - entirely forgot about this.

This was a variety of failures - mainly on my part.

One server had had the firewall settings reset blocking SNMP traffic, one had secondary SNMP software receiving the traps and somehow blocking the PRTG one and finally the MIBs had to be reuploaded due to a change in the way these were processed by PRTG (no longer had to be translated before use)

I don't have much further in the way of detail as we didn't continue on with SNMP.

Ended up moving to the PRTG IMAP sensor and email reports for backups as the SNMP sensor didn't support "Fail if no success seen in X hours"

Long story short - not a Symantec issue

--Greg

View solution in original post