How are Oracle DBs detected by Veeam?

[Yebo]

Is there a description how Veeam detects Oracle DB instances on a target backup VM (running MS Windows Server 2019), with application aware processing?
In the logs I can see the following lines:
...
< 6552> oralib| =======================
< 6552> oralib| Oracle restore is required: false
< 7408> oralib| Exploring oracle instances
< 7408> oralib| Found oracle instance: DBA. Is ASM: false, is autostart: true
< 7408> oralib| Found oracle instance: DBBT. Is ASM: false, is autostart: true
< 7408> oralib| Creating oracle session holder: BBDB.
...
Is it feasible to exclude DBBT from the backup processing? In this case, the Oracle DB is temporarily not used, it's MS Windows Service is set to "Disabled". In the backup job report, a warning is shown with details "Unable to perform application-aware processing ...".
Is there a registry key/value, added script to the job, or anything else, to exclude a particular Oracle instance from the job?

(Veeam v10, Enterprise Edition)

[PetrM]

Hello and Welcome to Veeam R&D Forums!

Rescan on Linux servers works via oratab/orainventory content analysis, while on Windows, it finds databases by parsing service names. However, excluding a specific database is not possible unless you are using our Oracle RMAN backup policy, which is available starting from v12.

Please give me some time to discuss the issue with my colleagues. We have made several optimizations in the rescan algorithm in recent versions, and it is possible that your specific problem may no longer persist with the latest version.

Thanks!

[Yebo]

Hello Petr,
thank you for the answer!

[PetrM]

Hello,

We discussed your case and I can confirm that this is the behavior by design. Let's treat it as a feature request. It's not the first time when I see the request to exclude specific databases, nevertheless, I'm not ready to share any information about ETA.

As a workaround, I can propose using our RMAN policy.

Thanks!

[Yebo]

Thanks!