I haven't been able to find any info on google/other places on this issue - so i'm hoping some of you guys have some info or ideas.
I realize it might be some setting in the SCOM management pack, but would appreciate if someone can point me at the right article/setting so i can talk to the SCOM admin about it.
The issue is that i'm running a couple SQL 2014 AlwaysOn Availability groups, and using Ola Hallengrens scripts to do the backup.
Backup preference is set to "prefer secondary"
What happens is that full backups are taken on the primary (active) node, while transaction backups are offloaded to the passive node.
The result of this is that i will have a consistent backup set, but will get alerts (from SCOM) that databases are not being backed up.
For instance one database will have info like this:
Primary node (at the moment):
Last Database Backup : 09-08-2014 05:00:15
Last Database Log Backup : 06-08-2014 08:16:59
Secondary node (at the moment):
Last Database Backup : 06-08-2014 08:16:58
Last Database Log Backup : 14-08-2014 14:55:01
(the 6th of august was when i added this DB to the AG)
So even if the backup is running as expect - then for the secondary server SCOM will raise an alert that I haven't done a full backup within the last 8 days (as we usually do full backups weekly)
Any ideas on how to work around this issue or how/where in the SCOM MP this behaviour can be tweaked?