SNMP Trap: Backup and Restore¶
A trap is generated on every backup.
Identification
The originating IP / hostname is used to identify the system generating the traps
The NMS is responsible for associating traps with each managed system, along with clearing of alarms and escalation to the relevant system operator
The trap OID is generic for various SNMP events monitored by the system
The SNMP system name is included as part of the variable binding to assist identification:
.iso.org.dod.internet.mgmt.mib-2.system.sysName.0 = standalone
Trap OID
.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotifications.mteTriggerFired
Variable Bindings - successful backup
.iso.org.dod.internet.mgmt.mib-2.system.sysUpTime.0 = 2 minutes (12065)
snmpTrapOID = mteTriggerFired
.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotificationObjects.mteHotTrigger.0 = “backup completed”
.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotificationObjects.mteHotValue.0 = 0
.iso.org.dod.internet.mgmt.mib-2.system.sysName.0 = standalone
Variable Bindings - failed backup
.iso.org.dod.internet.mgmt.mib-2.system.sysUpTime.0 = 2 minutes (12065)
snmpTrapOID = mteTriggerFired
.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotificationObjects.mteHotTrigger.0 = “backup failed”
.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotificationObjects.mteHotValue.0 = 5
.iso.org.dod.internet.mgmt.mib-2.system.sysName.0 = standalone
Severity Messages:
Info : Backup completed, INFO: Backup now runs regularly
Critical : Backup failed, ERROR: The last backup was more than 2 days ago,
Example: Critical: Backup failed¶
Note
Multi-line display is for example formatting purposes only.
Notification message from (1, 3, 6, 1, 6, 1, 1):('192.29.22.122', 29632):
Var-binds:
1.3.6.1.2.1.1.3.0 = 1365111
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.2.1.88.2.0.1
1.3.6.1.2.1.88.2.1.1.0 = Backup failed
1.3.6.1.2.1.88.2.1.3.0 = Creating/updating backup at
file:///backups/473bf9ae1027e3f2af6edbcc43d2c64f1ed4b87b
Using archive dir:
/root/.cache/duplicity/5e41da3a0b2fd68dbef152b9358f2c40
Using backup name: 5e41da3a0b2fd68dbef15
Message is truncated
1.3.6.1.2.1.88.2.1.5.0 = 0
1.3.6.1.2.1.1.5.0 = UN1-192.29.22.122
Resolution:
There may have been some form of corruption during the time that the backup was run.
Run backup manually and see whether the same failure is detected. If it is the case, investigate. Otherwise, contact L2 Support to investigate.
Example: Critical: ERROR: The last backup was more than 2 days ago¶
Note
Multi-line display is for example formatting purposes only.
Notification message from (1, 3, 6, 1, 6, 1, 1):('192.22.21.124', 44687):
Var-binds:
1.3.6.1.2.1.1.3.0 = 24804734
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.2.1.88.2.0.1
1.3.6.1.2.1.88.2.1.1.0 = ERROR: The last backup was more than 2 days ago
1.3.6.1.2.1.88.2.1.3.0 = Backup list: \
localbackup: \
URI: file:///backups \
Backups: \
No backups created yet
1.3.6.1.2.1.88.2.1.5.0 = 1
Resolution:
Investigate if the scheduler is set correctly and that the backup is set up correctly. Run a manual backup to test if it is working as it should. Otherwise, call Support to investigate.
Example: INFO: Backup now runs regularly¶
Notification message from (1, 3, 6, 1, 6, 1, 1):('192.22.21.124', 10865):
Var-binds:
1.3.6.1.2.1.1.3.0 = 25108817
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.2.1.88.2.0.1
1.3.6.1.2.1.88.2.1.1.0 = INFO: Backup now runs regularly
1.3.6.1.2.1.88.2.1.3.0 = Backup list: \
localbackup: \
URI: file:///backups \
Backups: \
1 backups have been created - most recently 2019-03-01 11:25
1.3.6.1.2.1.88.2.1.5.0 = 0
1.3.6.1.2.1.1.5.0 = UN1-192.22.21.124