Today I’ll be presenting a report that I developed called the OEM Backup Compliance Report. The primary goal of this report is to strengthen our visibility around backup compliance and help us proactively manage risks across our Oracle database landscape.
When we usually check backup information, we tend to rely on Commvault reports. While Commvault provides useful backup data, it only shows information for databases that are already registered and configured in Commvault.
This creates a potential visibility gap.
If a database is not registered in Commvault, we may not even know that it exists from a backup compliance perspective. In other words, there could be databases without backup coverage, and we would have very limited visibility into that.
To address this challenge, I leveraged the OEM repository database to build a report that directly analyzes the databases managed within OEM.
This report is designed to answer two key questions for our Oracle estate:
First, which databases have not been backed up in the last three days?
Second, which databases have never been backed up at all, meaning there is no backup configuration in place.
These two checks allow us to quickly identify systems that might be at risk and require immediate attention.
Let me briefly explain how the report works.
A script periodically scans all Oracle and RAC databases managed by OEM and collects key information such as the database name, the host name, and backup activity details.
The report then consolidates this information and highlights systems that require attention.
It also identifies higher-risk databases, particularly production environments or databases running in NOARCHIVELOG mode, since those environments typically have stricter recovery requirements.
Additionally, the report includes operational indicators such as:
Production status
Archive log configuration
Blackout status
And tracking references for remediation if needed
These details help us quickly understand both the technical state and operational priority of each database.
The real value of this report is proactive monitoring and faster risk identification.
With this visibility we can:
Quickly detect databases with missing or outdated backups
Ensure backup compliance across the Oracle environment
Support audit requirements with transparent reporting
And prioritize remediation for critical systems first
In short, this report gives us a centralized view of backup health across our OEM-managed database estate, which significantly improves our operational awareness.
Going forward, my recommendation is to incorporate this report into our regular operational reviews, so we can continuously monitor backup compliance and address any gaps before they become operational risks.
That concludes the overview.
I’ll now walk you through the report itself and demonstrate how it works.
