OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 768 days ago.
This article documents how to disable the processing of Oracle instances by Application-Aware Processing without disabling Application-Aware Processing processing for other applications running on the same machine.
Disable Oracle Processing for a VM Protected by Veeam Backup & Replication Windows OS Add the following registry value within the Guest OS of the protected VM: Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and ReplicationValue Name: DisableOracleProcessing Value Type: DWORD (32-bit) ValueValue Data: 1 A value of 1 enables the registry settings, which disables Oracle processing. Linux OS Create a file named VeeamOracleAgent.xml in the folder where the oracleagent is located in the guest (/tmp by default) with the following string: <config DisableOracleProcessing="true"></config> Disable Oracle Processing for a Machine Protected using Veeam Agent for Microsoft Windows Add the following registry value within the guest OS: Key Location: HKLM\SOFTWARE\Veeam\Veeam Endpoint BackupValue Name: DisableOracleProcessing Value Type: DWORD (32-bit) ValueValue Data: 1 A value of 1 enables the registry settings, which disables Oracle processing.
There is no way to exclude specific Oracle databases from being processed by Application-Aware Processing. As an alternative to completely disabling Oracle processing, it is also possible to force the skipping of databases in NOARCHIVELOG mode without warnings. To enable this behavior: For VMs running Windows, create OracleSkipNoArchiveLogDB (DWORD) registry value under the HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key. For VMs running Linux, add OracleSkipNoArchiveLogDB="true" to the VeeamOracleAgent.xml config file. For Machines protected using Veeam Agent for Microsoft Windows, create OracleSkipNoArchiveLogDB (DWORD) registry value under the HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup key.
