The RMAN Backup Failures alert notifies you when its configured condition is met on Oracle instances so you can investigate and respond.
Mini DBA describes this alert as: RMAN backup jobs that failed or completed with errors in the last 24 hours Failed RMAN jobs directly affect recoverability even if an older successful backup exists. Empty demo/user databases with no user tables visible to the monitoring login are ignored to avoid recoverability noise. Remediation: Review V$RMAN_BACKUP_JOB_DETAILS, RMAN logs, media manager output, storage availability, credentials, and backup schedule. Mini DBA evaluates this alert once a minute so changes are detected quickly. Because duration is used, Mini DBA can avoid treating a single short spike as a full incident when the condition clears quickly.
This alert protects storage and recovery capacity. It helps you find growth, retention, and backup conditions that can stop writes, break recovery objectives, or leave the server without enough working space for normal database activity.
Enable it on systems with recovery objectives and on any database where a missed backup or archive problem would require business escalation. Test and lab systems can use looser settings if they are recreated from source control or seed data.
Threshold meaning: Failed jobs. Major threshold: 1 jobs. Minor threshold: 1 jobs. Comparison direction: over. Duration is used, so prefer requiring the condition to persist before paging people for transient spikes. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.
Run or restart the missing backup after checking storage and job history. Confirm that restore requirements are met, clear failed schedules, and make sure backup monitoring reports the next successful run.
For recovery and replication alerts, route notifications to the people who own recovery objectives. Higher thresholds can be reasonable for reporting replicas, but production failover paths normally need tighter settings and explicit escalation.