RMAN backup status

Job details

Name:	RMAN backup status
Platform:	Oracle
Category:	Availability
Description:	Checks the status of RMAN backup from V$RMAN_BACKUP_JOB_DETAILS performance view.
Long description:	Checks the status of RMAN backup from V$RMAN_BACKUP_JOB_DETAILS performance view.
Version:	3.2
Default schedule:	10 6 * *
Requires engine install:	Yes
Compatibility tag:	.[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & (version like ‘11%’)]

Parameters

Name	Default value	Description
backup expire time	24	Backup expire time.
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.

Job Summary

Purpose: The job’s main task is to monitor and ensure the successful execution and completion status of RMAN (Recovery Manager) backups on Oracle database instances, specifically those running version 11g.
Why: RMAN backups are crucial for data recovery in Oracle databases. A failed or delayed backup could pose a serious risk to data integrity and availability. Monitoring status helps in proactive issue resolution and ensures business continuity.
Manual checking: You can manually check the RMAN backup status by querying the Oracle view V$RMAN_BACKUP_JOB_DETAILS:

SELECT * FROM V$RMAN_BACKUP_JOB_DETAILS;

Implementation Details

Scheduled Tasks: The monitoring job regularly (default schedule at 6:10 daily) checks the backup status by executing stored procedures and functions that query the RMAN backup details.
RMAN Backup Check: It checks the time since the last completed backup and whether any backups are running or have failed by analyzing the data against predefined critical time frames and backup states.
Data Processing: Data for backup status is fetched, processed, and stored in a custom table ‘backup_job_details’. The outcome influences the reported status and may trigger alarms.

Dependencies and Permissions

Self-Dependency: The task checks its own status against RMAN backup status.
Other SQL Objects: The job uses functions like ‘f_get_rman_output’ for error descriptions and a stored procedure ‘rman_backup_status’ for examining and evaluating backup status.
Required Grants: Given that access to multiple Oracle dynamic performance views is needed, the task includes SQL code to grant the necessary SELECT permissions on these views at the installation time.

Outputs and Reporting

Report Title	Function	Output Description
RMAN Backup Statistics	History and Statistics	Displays a history and statistical analysis of RMAN backups including details such as start time, end time, status, elapsed time, and size of data processed (input/output) in MB.
Backup Size History	Graphical Representation	Provides a visualization of backup sizes over time, helping in trend analysis and capacity planning.
RMAN Backup Pieces	Detailed Log	Shows detailed records of individual RMAN backup pieces from the V$BACKUP_PIECE view including all relevant metrics such as elapsed time, device type, status, etc.
RMAN Configuration	Configuration Lookup	Lists RMAN configuration settings which can be crucial for troubleshooting and understanding backup behaviors.

Additional Notes

Error Handling: The task is designed to handle exceptions by logging errors into a designated DBW_ERRORS table and returning this information for troubleshooting.
Update and Feedback Mechanism: Uses ‘dbw_updateCheckValues’ for updating the internal status and to communicate with dbWatch Control Center, ensuring that the backup status is appropriately reflected in monitoring dashboards.

This job is critical as it ensures that RMAN backups, essential for disaster recovery, are performed correctly and within expected time frames. Moreover, it facilitates immediate response and resolution in case of failures or delays in backups.