RMAN channel Parma to send job name

[sergiosatler]

Hi!

Is there a way, a variable of something no set on PARMS in rman channel allocation to send to VBR the job name that is being executed.

Like NetBackup, I can pass PARMS=“NB_ORA_POLICY=RMAN_oracle_policy” and on the server of the NetBackup knows what policy is being used.

[Andreas Neufert]

No, for stand alone plug-ins the names of the background Jobs (transport jobs) are automatically given based on source servername/cluster and targets.

Can you please share what you had in mind to do with this parms? We might have something for similar purpose that works a bit differently.

[sergiosatler]

We have two crews, one is responsible for database administering, other for backup administering on VBR.

When a RMAN backup is called, a job is listed on VBR panel with a generic job name but, in RMAN, 3 types of backup is executed: full, differencial and cumulative.

I want to backup crew to know when different types of backup is being executed on RMAN side just looking up on VBR panel and I think I could pass a job name during the rman backup execution using a "_cumulative" suffix, for example.

[Andreas Neufert]

Thanks for sharing. By design all backups need to land in the same "transport job" on the backup server when you use stand-alone plug-ins.
By design of the Oracle SBT Plug-in, we do not even "see" that status of the RMAN backup job then and do not have access to even the catalog to see the status of the backup. It is designed with the maximum security concept in place. (Oracle starts our process that fowards data to Veeam with reduced rights). So the transport job in Veeam does only see if the data was received and stored correctly, not if the RMAN job completed or not.

2 workarounds.
Give the backup admin access to your Scheduler so that they can check what is processed (or any kind of script that queries current backup processes and their status).

Or give the Veeam scheduler (Veeam Application Policy Job) a go and schedule everything from the Veeam side. The DBA can start additional backups on demand in RMAN or RMAN script as well.

[sergiosatler]

Thanks for help, Andreas!

I think the way will be the backup administering team to schedule the rman jobs by themselves.

Regards

[Andreas Neufert]

If the DBA then wants to run own jobs, you need to prepare the RMAN scripts with the channel definition. See documentation for samples.
At least you need to define the same naming pattern and as well connect to the same repository UUID. (likely you use this today anyway).
Authentication from the plug-in to VBR will change to ceritificate based authentication which is even better and the plug-ins are maintained in "Protection groups" which takes care about software updates automatically.