When backup and restore jobs are created and submited from NVBU GUI, no matter how many SBT_TAPE channels have been allocated, there will be only one job created in NVBU.
However when running the same job from Oracle RMAN CLI that also allocates multiple channels within the same scripts, there will be as many non-scheduled jobs created in NVBU as channels allocated in the script.
Is it possible to run an RMAN CLI script with multiple channel allocations and create only 1 non-scheduled job in NVBU?
With the current version of the software NVBU 9.2 and Oracle APM 6.5.6, it is currently not supported to create an RMAN script with multiple channels that will create only one job.
The reason why the scripts submitted by the NVBU GUI do create only one job even when multiple channels have been configured, is because of the processes' parent/child relationship created when jobs are submitted by NVBU.
In the GUI it is NetVault Backup that creates the backup script, and launches the Oracle RMAN process.
Therefore the Oracle RMAN process becomes a child of the NetVault Backup process.
RMAN will in turn launch several NetVault Backup orasbt processes.
These orasbt processes will be children of Oracle RMAN but most importantly they will be grandchildren of the initial NetVault Backup GUI task.
These orasbt processes all work independently of each other and are unaware of each other.
However, since they inherit context from their parent, they all have a connection with their parent and grandparent process, ...
So the NetVault Backup orasbt processes will push back and register with their NetVault Backup grandparent, and all run as part of the same job created by the GUI.
The above cannot be done when submitting several channels from RMAN directly, in this case only, RMAN will create independent tasks, which will be received as independent jobs in NVBU.
This feature is currently not supported and would require extensive software change that must be validated by R&D.
Enhancement Request Bug 24096 has been opened with R&D to investigate whether this can be implemented on a future version of the Oracle APM.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center