I had opened a case under 07430939. With our previous backup solution, Data Protector, we had the option to specify a Recovery Catalog Server directly through the GUI in the RMAN jobs. For every backup — whether full, differential, incremental, or archive backups — the information was sent to the Recovery Catalog Server. Data Protector also allowed us to edit the generated RMAN script.
We have received the following response from support regarding the modification of the RMAN script in Veeam and the configuration of a Recovery Catalog Server:
Unfortunately only options in the shared wizard are available and regrettably it is not possible to edit RMAN scripts generated by the Veeam B&R server.
Can this be implemented? We also received the following response regarding this:
When some functionality is not available in Backup Policy, it is possible to trigger backup via the manually created RMAN scripts which allow higher flexibility: https://helpcenter.veeam.com/docs/backu ... racle-rman
How has the issue of accessing the RMAN Recovery Catalog Server been resolved for other customers while direct integration is not yet available?
Yes, the reply from the support team is entirely correct. You can use the plug-in in standalone mode to run custom scripts. The policy does not currently provide an option to run custom scripts. It's a feature request, and I cannot comment on the ETA.
Could you please clarify what problem you would like to solve using a custom script, and which problem is not addressed by the policy? For example, specific retention settings, archived logs backup mode, etc.
three things are currently not covered by the policy. The first is the ability to perform a synchronization with the Recovery Catalog after each backup. We might now have to handle this with a locally running script, which would be a step back compared to the implementation via Data Protector.
The second and third points are the backup of the spfile and the control file. This is how we have it configured in the customized RMAN script in Data Protector:
backup
format 'xxx<SID_%s:%t:%p>.dbf' spfile;
backup
format 'xxx<SID_%s:%t:%p>.dbf' current controlfile;
Many thanks for information! We process spfile and control file by policy, this use case is addressed. I agree that the synchronization with the remote recovery catalog could be a valuable improvement in future releases.