Backup of enterprise applications (Microsoft stack, IBM Db2, MongoDB, Oracle, PostgreSQL, SAP)
Post Reply
mweberv
Novice
Posts: 3
Liked: never
Joined: Feb 04, 2021 1:09 am
Full Name: mike weber
Contact:

Veeam RMAN Plugin for Oracle - Multiple VBRs

Post by mweberv »

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.
8) resume normal RMAN backups to NonProd VBR

Is this best/only approach or is there another solution that is less cumbersome?
PetrM
Veeam Software
Posts: 3815
Liked: 643 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Veeam RMAN Plugin for Oracle - Multiple VBRs

Post by PetrM »

Hi Mike,

I don't think there is a less cumbersome way to address this specific case, as long as you need to use two different Veeam B&R instances. I would recommend using a single Veeam B&R instance with two different repositories: one for production backups and one for non-production backups. With that, you can change the repository setting only, or you can use the plug-in in managed mode and create two different policies: one for non-production databases directed to the non-production repository and another for production databases directed to the production repository.

Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests