Skip to main content
NetApp Backup and Recovery

Configure an Oracle database in NetApp Backup and Recovery

Contributors netapp-mwallis
PDFs

Change authentication and node settings for a standalone or clustered Oracle database. NetApp Backup and Recovery protects databases without these changes, but you might need to update settings if your environment changes after discovery.

Required NetApp Console role
Backup and Recovery super admin. Learn about Backup and Recovery roles and privileges and NetApp Console access roles for all services.

Configure an Oracle database

Change the configuration for a standalone or clustered Oracle database.

Steps

  1. From the NetApp Console menu, select Protection > Backup and Recovery.

  2. Under Workloads, select the Oracle tile.

  3. In the Oracle inventory, select the Databases menu.

  4. In the list of databases, select Configure database (standalone) or Configure RAC database (clustered) for the database you want to configure.

  5. Configure database settings: Set the authentication settings for the standalone or clustered database.

    • Select OS authentication to authenticate with the host operating system only. Backup and Recovery uses the host credentials that you specified during discovery.

    • Select Database authentication when the database requires credentials. Then choose existing credentials or add new ones, and pick the port to use for the connection.

  6. Configure RMAN catalog: Choose where metadata for backups and recovery operations is stored for this database or cluster when automatic cataloging is enabled in the protection policy or when you manually catalog a recovery point:

    • Select Target control file to store metadata in the database target control file.

    • Select Catalog database to store metadata in the RMAN recovery catalog. Choose the credentials and Transparent Network Substrate (TNS) name to connect to the recovery catalog.

      The RMAN recovery catalog is a separate database schema that the RMAN utility uses to store Backup and Recovery metadata for registered databases. It provides redundancy and long-term retention if the target control file is lost, or when you need historical data. Enabling this option registers datafiles and archive log copies in the RMAN repository so RMAN can track and manage them for reporting and recovery.

  7. Configure nodes (clustered databases only): Add or remove nodes from protection, or change node priority using the arrow buttons.

    Nodes with higher priority are protected first. Lower priority nodes are protected only if higher priority nodes are unreachable or unhealthy.

  8. When finished, select Done.

Result

Backup and Recovery connects to the database using the new settings.