I've run into the issue of the system deleting all the alerts. You get a database error in the logs - mentions corruption detected, and proceeds to wipe the alerts. This is a 3 week old install that was running on 5.6.6. I just updated to 5.6.8.2 after it's second round of wiping the alerts last night. hoping that maybe it's fixed in the "various fixes". Another user mentions similar Constantly seeing no alerts in database - even after restoring via 'repair/regenerate'
So... since it appears that the alerts are only DB stored, and cannot be recovered from the clips in the event that the DB gets hosed, I'm looking for a way to recover for when this happens. I'm thinking snapshotting the DB directory periodically, and then restoring it in the event that it decides to kill what's in the active DB. I'll just lose whatever alerts happened between the time of the last snapshot and when I restore it. Until... whatever is actually causing it gets fixed. Or.. Is there some other way to get it to regenerate the alerts from history?
Win10 Pro 22H2 under VMware
8 gig ram
8 cores Xeon Silver 4208 @ 2.1Ghz - normally under 20% CPU
Local disk is 250 gig for 20 gig new, 140 gig Stored Rolling to Aux1 2TB / 30days on a 90 TB file share.
So... since it appears that the alerts are only DB stored, and cannot be recovered from the clips in the event that the DB gets hosed, I'm looking for a way to recover for when this happens. I'm thinking snapshotting the DB directory periodically, and then restoring it in the event that it decides to kill what's in the active DB. I'll just lose whatever alerts happened between the time of the last snapshot and when I restore it. Until... whatever is actually causing it gets fixed. Or.. Is there some other way to get it to regenerate the alerts from history?
Win10 Pro 22H2 under VMware
8 gig ram
8 cores Xeon Silver 4208 @ 2.1Ghz - normally under 20% CPU
Local disk is 250 gig for 20 gig new, 140 gig Stored Rolling to Aux1 2TB / 30days on a 90 TB file share.