Hi @ReweBackup ,
Oracle backup can be performed using RMAN interface too.
Docs click here
More details check the link → https://documentation.commvault.com/11.24/expert/20123_using_parms_in_oracle_allocate_channel_command.html
Let us know in case of any other questions.
Regards,
Hello @Gowri Shankar ,
Thanks for your summary. I have been knowing RMAN interface for many years ( Oracle / Backup administratation )
The SBT library libobk.so is re-linked like the example
Oracle Library Sbt Library libobk.so
so it is not nessasary to defined PARMS in Oracle Allocate Channel Command
like Using PARMS in the Oracle Allocate Channel Command
Maybe there are newer possibilities, which are not yet known :
- In CV i create a oracle database for instance ORCL like here
- Then i start with CV CLI a oracle database backup for instance ORCL in a linux shell script
The CV software handle with the defined CV oracle backup job the backup tape library , where teh backup will stored , backup retention and so on.
When i start a oracle database backup with the RMAN Interface i can define those Data Path parameter (MediaAgent, Library, Drive Pool) like :
Specifying the Media Parameters for Oracle RMAN Command Line Operations
Oracle Agent Media Parameters
?
Is this , what you mean ? So i don’t need CV CLI Commands ( qlogin, .. ) , i can define in SBT Parameters detailed CV informations ?
I know Oracle RMAN like this :
you have to configure RMAN Parameters after using “rman” command with “CONFIGURE”.
When you start a backup with RMAN it will store to a local a local linux directory , right.
Hi @ReweBackup ,
When using rman interface qlogin is not needed.
Media parameters are also options, the backup uses the data path based on the storage policy.
Media parameters are used in a specific scenario where you need to explicitly provide a data path or a library to use during the backup
Following is the sample script with the minimum parameters
run {
allocate channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=/opt/commvault/Base/libobk.so, BLKSIZE=1048576 ENV=(CvClientName=<ORACLE_CLIENTNAME>, CvInstanceName=Instance001)";
backup database;
}
Replace ORACLE_CLIENTNAME with the actual client name
Also change Instance001 if it is utilizing a different instance name
Let me know in case of any other question.
Regards,
Hello @Gowri Shankar ,
Thanks for your summary.
based on your information, the following procedure :
- Add a oracle database to CV ( text german )
- Define Storage Policy and more to the oracle database
- RMAN Backup Start with <StoragePolicyName>
extend your example :
run {
allocate channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=/opt/commvault/Base/libobk.so, BLKSIZE=1048576 ENV=(CvClientName=oradbhost, CvInstanceName=ORCL, SP=<StoragePolicyName> )";
backup database;
}
here parameter examples for oracle rman ( <StoragePolicyName> )
CV book with rman example
Kind regards