Include archive log monitoring statistics along with Oracle DB via RMAN during the backup process

[mark.tagle]

We have raised this concern with Veeam Support case 07987153,07985616, and they recommended submitting a formal request via the Veeam R&D Forums.

This feature is crucial for streamlining our monitoring process. Currently, the Veeam Plug-in for Oracle RMAN is installed as an agent on our IBM AIX machines. When an Oracle Database backup is performed, the Veeam Backup & Replication (VBR) 13.0 console only displays basic database backup statistics.

During the RMAN backup process, the Spool Log is stored in a local directory on the AIX machine. While we currently monitor these logs at the OS level, it is vital for our operations to have centralized visibility. We kindly request a feature that integrates the monitoring of RMAN Spool Logs (including Archive Log status) directly into the Veeam Console alongside the standard Oracle Database backup progress.

We encountered an error in the Archive Log during the backup process. While the Veeam Backup Console 13.0 reported a 'Successful' status, the RMAN Spool Log at the OS level showed a failure. This discrepancy between the Veeam Console and the actual RMAN logs is a major concern for us, as it makes accurate monitoring impossible.

We kindly request feature that the Veeam Backup Console be updated to monitor and display the RMAN Spool Logs directly along with Oracle Database Backup Process. Specifically, we need the visibility of the Archive Log backup process within the console to ensure seamless, centralized monitoring. Integrating these logs would allow us to verify the full backup status without needing to manually check logs at the OS level.

Current Setup:
IBM AIX Machine Standalone mode with Veeam Agent and VeeamOracleRMANPlugin Installed
The monitoring of Oracle Database Backup is shown in the monitoring statistic of VBR 13.0 Console.

[tj818]

What was the error detected in the Archive Log Backup that Veeam didn't detect?

[PetrM]

Hello,

The feature request is noted. I believe it could be a good addition to our Oracle RMAN backup policy, but I'm not ready to comment on an ETA.

However, I'm also interested in understanding the reason for this discrepancy. What was the root cause of the error?

Thanks!