Feature request : Skip oracle log processing for inactive db

[jvandevelde]

This is a continuation resulting from a support case (#01832027 ) created after our recent upgrade from v8 to v9 (SP1).

We identified that the Application aware processing for Oracle databases is not correctly handling a situation where the Oracle database service is defined but not running.
In this situation, v9 SP1 gives a warning in the eventlogs :

Code: Select all

Unable to perform application-aware processing of Oracle database (SID: NAT) : Oracle error has occurred. ORA-12560: TNS:protocol adapter error  
--tr:OracleSession: failed to init server. 
--tr:Failed to create oracle session. 
--tr:Failed to create oracle session holder. SID: NAT.

In order to bypass or skip this warning, you can add registry entries on the host that would completely disable all Oracle log truncation actions (for all the defined instances) as specified in the release notes of v9 SP1 (https://www.veeam.com/kb2114)

However, this is not a good solution if you have multiple database instances defined and some of them are disabled/shutdown/not running.
I would expect (for the windows platform at least) that Veeam would be able to identify whether the database instance/service is actually running prior to attempting to make a connection to the database instance that would ultimately fail.

[Dima P.]

Hi jvandevelde,

Thanks for the feedback. I’ll share it with the team.

[TimLawhead]

Getting the same issues, nearly 4 years later on Veeam 9.5 Update 4.

My DBAs are shutting on and off database instances for applications that are going through decommissioning and aren't being actively used.

The link provided points to setting a registry key to stop all Oracle Processing for Application Awareness but doesn't help with instances that are being turned on and off. It'd be better if the Application Awareness processing for Oracle ran a check of active instances prior to the backup and skipped over the issue or if we had a way to turn this error from a Warning to an Information level alert...


The link: https://www.veeam.com/kb2114

Oracle
...
Added ability to disable Oracle processing without having to disable application-aware processing for the rest of applications running on the same VM. To enables this behavior, create DisableOracleProcessing (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the processed VM.

[PetrM]

Hi Tim,

I don't think that we should implement a preliminary check to skip inactive instances because the purpose of such warning is to inform about impossibility to process a specific database for any reason.

On the other hand, we may consider "change of color" for this message as long as we have many similar requests. Thanks for the idea and for your feedback!

Thanks!