We have setup two VBRs Version 12.2.0.334. The separate VBRs are used to store Oracle RMAN backups using Veeam Plugin for Oracle Version 12.2.0.334.
One VBR is used for Production databases and the other for NonProduction.
This configuration was done to accommodate and segregate the large number of databases we manage.
I am able to configure multiple Repositories within a VBR. No issues there.
Is there a way to configure the Plugin to communicate with multiple VBRs? Reconfiguration needs to be done when we perform a database refresh by restoring a Production backup to the NonProduction database server.
All of the actions occur on the NonProd database server.
1) run OracleRMANConfigTool to configure Plugin for the NonProd VBR
2) run RMAN Backups to the NonProd VBR
Then at a time for a refresh(restore from Production)
3) save the current (nonprod) veeam_config.xml aside
4) run OracleRMANConfigTool to configure Plugin for the Prod VBR
5) run RMAN restore of Production database
6) save the current (prod) veeam_config.xml aside
7) put the nonprod veeam_config.xml back in place.
resume normal RMAN backups to NonProd VBR
Is this best/only approach or is there another solution that is less cumbersome?
One VBR is used for Production databases and the other for NonProduction.
This configuration was done to accommodate and segregate the large number of databases we manage.
I am able to configure multiple Repositories within a VBR. No issues there.
Is there a way to configure the Plugin to communicate with multiple VBRs? Reconfiguration needs to be done when we perform a database refresh by restoring a Production backup to the NonProduction database server.
All of the actions occur on the NonProd database server.
1) run OracleRMANConfigTool to configure Plugin for the NonProd VBR
2) run RMAN Backups to the NonProd VBR
Then at a time for a refresh(restore from Production)
3) save the current (nonprod) veeam_config.xml aside
4) run OracleRMANConfigTool to configure Plugin for the Prod VBR
5) run RMAN restore of Production database
6) save the current (prod) veeam_config.xml aside
7) put the nonprod veeam_config.xml back in place.
Is this best/only approach or is there another solution that is less cumbersome?
Statistics: Posted by mweberv — Feb 25, 2025 10:35 pm








