Do you use the VEEAM RMAN Pluin in your environments?
What are your experiences with it?
Do you have one or more than one Oracle database instances on a system?
Solved
RMAN plugin
+17Best answer by randyweis
I was asking this same question recently and did not get any “real-world” responses. I have a customer that is deploying this at scale and I’ve been assembling some best practices. The biggest issues were resolved with v11, and the metadata improvements. One task = 5 channels, so plan repository resources accordingly. If doing a backup copy job, make sure you keep that in mind as well - limit the tasks on the target repo so it doesn’t suck up all the task slots on the source and hang up the RMAN jobs (especially the archived redo log jobs). I recommend increasing the registry settings for max user ports to 64K and shortening the TCP timed wait delay to 30 seconds. Summary of the big points.:
Recommendations for infrastructure optimization:
- Set a backup window for backup copy jobs? No, no need.
- Reduce tasks on the BCJ target repositories, set to 20 or 30 per extent server
- BCJ can be set at repo level if there are two Oracle repos with different retention (e.g. for Prod and Non-Prod), or at job level if all RMAN backups go to one repository if you want different retention periods.
- TCPTimedWaitDelay - default 240, set to 30
- MaxUserPorts default 5000, set to 65536
- Do this on the Backup, repo and preferably on the database servers
+22Two more points (this might go on all day...)
- Dedicate the repository to Oracle RMAN in large environments. Don’t mix in VM workloads. This is both a resource issue and a configuration issue. See the point below.
- If targeting a SOBR, use the Performance Data Locality policy, so load balancing is based on available compute resources (cores). Note that this means that any Oracle database and redo log backups will likely be spread across extents. This setting works for plug-in backups since there is no Full and Incremental backup from Veeam’s perspective.
Thanks this is very good information and explains some issues that I have seen. So I take it separating the rman backups looks to be pretty essential.
+4Correct...and an edit is needed! Use Performance Policy (as opposed to Data Locality Policy), not Performance Data Locality Policy. 🤦♂️
+3I think RMAN is enough for backup. anyway I will try it in my lab and update you according
+7i will add my 2 cents , instant recovery is only available for oracle with application aware processing.
Oracle RAC can’t use the application aware processing, you have to deal with rman plugins.
Currently fighting with Oracle explorer to work properly with rman. It’s ok with rman command. I’m working on this with my dba colleague. I think i will open a ticket to the support later with more informations.
Backuping Oracle Node jobs:
- entire computer for the cluster, the acfs is not processing by default
- ACFS with one node on file level without snapshot
+7Hello guys,
what is your restoration strategy with rman on rac cluster? Are you using Oracle explorer or only rman cli?
I’m struggling to use the Oracle Explorer with rman, unfortunetaly explorer doesn’t seem able to write on asm group. I opened a ticket on support, we will see.
Obviously ASM is not seen by OS only by app.
ASM path is correctly shown in metadata backup.
+17As far as I know is RAC not supported by the Veeam Explorer for Oracle.
+7As far as I know is RAC not supported by the Veeam Explorer for Oracle.
It works, it was a problem the account selected didn’t have SYSASM priveleges.
Now everything is working great.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.