Gostev wrote:I don't know if us using the existing Oracle server that you are already using to run other databases requires an extra license with Oracle licensing.
With the obvious disclaimer that I'm a Veeam employee, not an Oracle licensing expert, I can't think of any scenario that would require an extra license for this use case. If you use the "restore to a specific transaction" functionality Veeam does technically start another instance, but we use the binaries from the selected ORACLE_HOME. You can select any existing ORACLE_HOME, with a compatible Oracle version, in the environment. In most cases Oracle does not restrict the number of instances, or even ORACLE_HOMEs, that can be installed on a server, as licensing is by processor or by named user, not per-instance.
I suppose if you installed Oracle on a server to use specifically as a staging server, rather than using one of your existing servers, and you didn't have either enough named users (there is a minimum number of named users per processor/server which varies by edition) or enough processor licenses to cover this new instance, then you would probably need additional licensing, but I expect most users to simply use the existing Oracle server for the handful of times they'd want to browse and select a very specific transaction, the only use case that requires any staging.
The definitive guide for Oracle licensing is the Software Investment Guide
. Also, referenced is the Licensing Data Recovery
which covers Oracle licensing for failover environments, such as replication, and DR testing of backups (such as using Surebackup). Oracle is quite restrictive with these use cases, but does provide some limited use.
In summary, as already noted, Oracle licensing is very complex, and is governed by your specific purchase agreement with Oracle. No one at Veeam can claim that any specific use is compliant, only Oracle can do that, so if you have concerns, the absolute best bet is to ask your Oracle representative, and even better, get it in writing.