Each time an Online Backup is run within a DSS environment (manual or scheduled), each DSS receiving a backup shuts down the SpectroServer, restores the database with the latest one from the MLS, and then starts up again.
Within the VNM's events, it looks as though the DSS went down for some unknown reason which needs to be investigated. You can assume from the time of day that it was a scheduled backup, but it still appears like a system failure on the DSS side of things.
Does anyone else notice this? If so, perhaps it would be best to differentiate events caused due to backups from events caused due to failures.
Any ideas for a workaround?
Are you annoyed by the events, or by alarms ?
We get alarms every day at the online backup time: "CONTACT LOST TO PRIMARY ARCHIVE MANAGER" . The only work-around I can think off is a daily scheduled maintenance on the VNM.
I've used a delay in SANM for all of the OLB related alarms, so they show up on the UI but nobody gets notification unless backups take longer than usual.
I haven’t tested it, but one option might be to possibly use an event rule pair to put a “timer” (if you will) on the event so that it doesn’t generate unless the clear is received after X seconds…
Oh, that's a good solution too, then you don't even get the alarm displayed.
Both seem out of place, since they are caused by a backup and not due to a malfunction of any kind.
Agreed. Scheduling maintenance on the VNM would be more suitable, but this does not seem possible. Do you know of a way?