Oracle RMAN Plug-in: Intended long-term use of Force Delete

[rin]

Hi,

I would like to understand the intended usage of the Force Delete feature in Veeam Plug-in for Oracle RMAN.

The documentation describes Force Delete as a mechanism that automatically removes backup files older than the configured number of days.
Is this feature intended to be enabled continuously as part of normal operations for Oracle RMAN backups?

If so, are there any known limitations, considerations, or best practices for long-term use?

Additionally:
1. Are there any known performance impacts associated with keeping Force Delete enabled over time?

2. Are there any operational considerations when using Force Delete together with Oracle RMAN retention policies (for example, recovery window retention or KEEP UNTIL TIME)?

3. Is Force Delete primarily intended as a temporary housekeeping mechanism, or is continuous use considered a supported and recommended deployment model?

Could you please clarify the recommended usage from a product perspective?

Best Regards,
Rin

[HannesK]

Hello,
the scenario is a standalone plugin that does not have retention configured. See user guide

In the main scenario, when using Veeam Plug-In for Oracle RMAN, you must configure the retention policy using native Oracle RMAN tools. For details, see Configuring Retention Policy

If you are using the managed plugin, or you set the retention in RMAN, then the force delete is not needed.

1. no. Did you see any issues? If yes, what is the support case number?
2. normally DELETE OBSOLETE is the way to go.
2. yes, that's more like a housekeeping thing when DELETE OBSOLETE / retention is not used for whatever reason. You can run it as often as you like, but for "normal operations" it's not needed.

Best regards
Hannes