Restore uptodate status
Job details
Name: | Restore uptodate status |
Platform: | Oracle |
Category: | Internal |
Description: | Checks size of all snapshot logs. |
Long description: | |
Version: | 1.1 |
Default schedule: | 15m |
Requires engine install: | No |
Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’] |
Parameters
Name | Default value | Description |
---|---|---|
dbWatch_schema | dbwatch | Schema where dbWatch is installed |
return_status | 1 | Alarm or warning status if restore is older than configured parameter. 0=OK, 1=Warning, 2=Alarm |
restore_max_time | 192 | Maximum time since last restored in hours. 168=one week |
Job Summary
- Purpose: The purpose of this job is to monitor and check if the Oracle database restore function is current and within designated time frames.
- Why: This job is important because it ensures that the database restore operations are completed within an acceptable duration, typically set against a business-driven requirement such as operational continuity and data recovery objectives. If the time since the last restore exceeds the maximum allowable time (configured as a parameter), an alarm or warning can be triggered, indicating potential risks in data recovery strategies.
- Manual checking: You can check this manually in the Oracle database by issuing the following SQL command:
select round((sysdate-max(last_run))*24,0), to_char(max(last_run), 'YYYY-MM-DD HH24:MI:SS') from dbwatch.dbw_tasks;
Job Implementation
The monitoring job utilizes a SQL query to determine the duration since the last database restore and compares it with a predefined maximum acceptable time (‘restore_max_time’). If the period since the last restore exceeds the defined threshold, it changes the job’s status to either warning or alarm based on ‘return_status’. This facilitates real-time monitoring and quick response to potential issues.
Job Compatibility and Installation
The job is specifically designed for instances running an Oracle database management system where the dbWatch tasks table exists but without needing an active dbWatch engine. This makes it suitable for setups with specific configurations or in distributed database environments.
- Installable: Yes, the job can be installed on compatible Oracle database instances.
- Compatibility: Oracle databases with dbWatch tasks functionality and without an active dbWatch engine.
Job Output
The job’s primary output provides a status update and details about the last restore:
|_. Status |_. Details | | OK | Database restored at: [date and time]. X hours ago. | | Warning/Alarm | Database older than restore_max_time: X. Last restore: [date and time]. |
Job Scheduling
The job is configured to run every 15 minutes, ensuring frequent checks and updates on the database’s restore status, thereby maintaining a close watch on the critical timing aspect of database restores.
Reporting
- Title: Restore Uptodate Status
- Description: Reports on whether the Oracle database restores are being performed in a timely manner as per the configured thresholds.
The report template involves a detailed tabulation of restore statuses:
- Title: Details
- Table Presentation:
This formatted output helps in the visual representation and quick assessment of the database’s restore health in operational dashboards or review meetings.