NetWorker: How to configure Oracle RAC backups

Summary: This KB article helps you to configure an NMDA Oracle RAC Client to NetWorker Server manually.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions

RAC backups should be configured manually using the virtual IP/virtual node name (choose any of the virtual IPs you have)

Steps for manual configuration:

1. CONFIGURATION FILE (Action to be taken on all physical nodes)

a) Modify the "nmda_oracle.cfg" file under "/nsr/apps/config" on all physical nodes to include the ORACLE_SID, ORACLE_HOME, TNS_ADMIN (ensure it has 755 permissions)
b) Or you can also create a new configuration file (example - nmda_oracle_new.cfg file under /nsr/apps/config) and define the following parameters: ORACLE_HOME, ORACLE_SID, TNS_ADMIN (ensure sure it has 755 permissions)


"Mandatory" parameters of the NMDA configuration file, /nsr/apps/config/nmda_oracle.cfg:
MANADATORY:
ORCALE_HOME=
ORACLE_SID=
ORACLE_USER= (this parameter is used if you use operating system authentication, the connection string on the RMAN script will then be connect target /)

If not on the script, add on configuration file:
TNS_ADMIN=
NSR_DATA_VOLUME_POOL=Networker_Backup_pool_name

Recommended PARAMETER:
NSR_RMAN_ARGUMENTS=msglog'/nsr/applogs/msglog.log'append


2. RMAN SCRIPT:

a) Create the backup script and place it in the same path on all physical nodes. Example: /oracle/scripts/fullbackup.rman (confirm it has 755 permissions)
b) NSR_CLIENT should be set to the virtual node name.

NSR_CLIENT=virtual node name
 

NOTE: NSR_CLIENT is used to index the backups, so we use one of the virtual nodes as NSR_CLIENT, so that ALL our backups are indexed under it, this makes it easier in the restore process because you use the same NSR_CLIENT to restore the data instead of knowing which node took which backup.



Sample RMAN script:

connect target user/***@SID;
connect rcvcat rman/***@rcat;

RUN { 
ALLOCATE CHANNEL T1 TYPE 'SBT_TAPE' PARMS 'ENV=(NSR_SERVER=nw-srv,NSR_CLIENT=oracle_client-vip)'; 
ALLOCATE CHANNEL T2 TYPE 'SBT_TAPE' PARMS 'ENV=(NSR_SERVER=nw-srv,NSR_CLIENT=oracle_client-vip)'; 
ALLOCATE CHANNEL T3 TYPE 'SBT_TAPE' PARMS 'ENV=(NSR_SERVER=nw-srv,NSR_CLIENT=oracle_client-vip)'; 
ALLOCATE CHANNEL T4 TYPE 'SBT_TAPE' PARMS 'ENV=(NSR_SERVER=nw-srv,NSR_CLIENT=oracle_client-vip)'; 

backup full database tag FULL_DB format 'FULL_DB_%d_%T_%s_%p'; 
sql 'alter system archive log current'; 
backup tag DB_ARCHIVE_LOG format 'ARCHIVE_%d_%T_%s_%p' archivelog all delete all input filesperset 50 maxsetsize 20G; 
backup tag DB_CONTROLFILE current controlfile format 'CONTROL_%d_%T_%s_%p'; 

release channel T1; 
release channel T2; 
release channel T3; 
release channel T4; 

} 




3. Update the hosts files on all Oracle RAC client nodes and the NetWorker server to include the specified entry in each file:
• NetWorker server
• Both physical nodes
• Virtual node

4. From NMC, create dummy clients for "Each Physical Node." No need to schedule backup (if scheduled it takes backup of a LOCAL file system only). 

5. From NMC Create a new client for the virtual node MANUALLY by Right click >> New Client Properties (Keep the client in a newly created group and keep all the dummy clients in the same group) (confirm it has *@nodeX in "Remote Access" field, add all the node names)

NOTE: If there is a Multi-Node RAC, "RMAN backup script" and "ndma_oracle.cfg" should be on the same path (The Absolute path must be the same on all the nodes for these files, so you should keep a copy of the configuration file and RMAN script on all physical nodes under the same path)



6. Set the following parameters in the new client:

Backup command:

nsrdasv –z /nsr/apps/config/nmda_oracle.cfg -c virtual_node_name

Save set: RMAN:/oracle/scripts/fullbackup.rman

Once all the actions have been performed, you could run the backup from the newly created virtual node client resource.
 

Additional Information

See the NetWorker Module for Databases and Applications documentation: Support for NetWorker Module for Databases and Applications 

Affected Products

NetWorker Family
Article Properties
Article Number: 000222873
Article Type: How To
Last Modified: 01 Dec 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.