RMAN archivelog backup status
Job details
| Name: | RMAN archivelog backup status |
| Platform: | Oracle |
| Category: | Availability |
| Description: | Checks the status of RMAN archivelog backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
| Long description: | Checks the status of RMAN archivelog backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
| Version: | 1.3 |
| Default schedule: | 15,45 * * * |
| Requires engine install: | Yes |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & _cdb_v_rman_backup_job_details = ‘1′ & is_pluggdb = ‘0′ ]/.[is_rds = ‘0′] |
Parameters
| Name | Default value | Description |
|---|---|---|
| backup expire time | 24 | Backup expire time (in hours). If no valid backup exists within this time threshold a warning is returned. |
| return status when backup RUNNING | 1 | Return status value (ALARM – 2, WARNING – 1, or OK – 0) when RMAN backup status value is RUNNING. |
| return status when backup FAILED | 2 | Return status value (ALARM – 2, WARNING – 1, or OK – 0) when RMAN backup status value is FAILED. |
| return status when OLD backup | 1 | Return status value (ALARM – 2, WARNING – 1, or OK – 0) when RMAN backup is older than “backup expire time” parameter value. |
| return status when backup NOT IMPLEMENTED | 1 | Return status value (ALARM – 2, WARNING – 1, or OK – 0) when RMAN backup is not implemented. |
| return status when ARCHIVER STOPPED | 1 | Return status value (ALARM – 2, WARNING – 1, or OK – 0) when ARCHIVER is stopped. |
Job Summary
- Purpose: The purpose of this job is to check the status of RMAN archivelog backups, specifically targeting Oracle databases. It ensures backups are running as expected, detects if backups have failed or are outdated, and reports on the archival process status.
- Why: This job is crucial to guarantee data recovery and business continuity. Effective RMAN archivelog backup monitoring helps in avoiding data loss and supports faster recovery in case of database failures, ensuring backups are within the specified time frame and properly maintained.
- Manual Checking: You can manually check this by executing SQL commands on the Oracle database directly. Here’s an example command to fetch recent archivelog backup details:
select * from V$RMAN_BACKUP_JOB_DETAILS order by START_TIME desc;Monitoring Logic Implementation
The dbWatch job under ‘oracle_rman_backup_archivelog_status’ follows these specifics:
- It utilizes the V$RMAN_BACKUP_JOB_DETAILS view to gather detailed insights about recent RMAN backups.
- Specific conditions like backup age, status (Running, Failed), and archiver status are checked and appropriate alarm levels are triggered based on these conditions.
- Monitoring occurs regularly as determined by the default scheduling, which checks at specific intervals (e.g., every 15 and 45 minutes of each hour).
Dependencies and Execution Environment
The job relies on several key Oracle views:
- V$RMAN_BACKUP_JOB_DETAILS
- V$BACKUP_SET_DETAILS
- V$BACKUP_PIECE
- V$RMAN_CONFIGURATION
- V$RMAN_OUTPUT
Privileges for the dbWatch schema on these views must be granted sufficiently to enable the execution of the SQL queries.
Customization and Configuration
While the default thresholds and conditions are set, these can be tailored based on user’s specific needs or environmental conditions such as backup frequency, the criticality of the data, and storage infrastructure.
Parameters Table Overview
| Parameter Name | Description |
|---|---|
| backup expire time | Maximum allowable time since the last backup, beyond which the status warning or alarm will be triggered. |
| return status (each state) | Determines the alert level (OK, WARNING, ALARM) for various backup states (RUNNING, FAILED, OLD, NOT IMPLEMENTED, ARCHIVER STOPPED). |
Reporting and Alerts
The job handles result presentation and alert management effectively by:
- Generating comprehensive reports including statistics like the backup size, start and end times.
- Providing visual representations and historical trend analysis through built-in presentations like charts and detailed tables.
- Triggering alerts based on conditions specified, which ensures immediate attention to potential issues, promoting preemptive action.
In summary, the ‘RMAN archivelog backup status’ job in dbWatch serves as an essential component in the realm of database backup management, providing robust monitoring, alerting capabilities, and ensuring that backups are executed and maintained as expected for Oracle databases.