Add a database

You can add database instances manually on the Databases page.

Druva may not discover database instances running on an Oracle server host in the following cases:

PhoenixOracle service is not running.
The Oracle database instance is offline.
The database name is not available in the DB registry (etc/oratab) and the database instance is offline.
Database credentials are incorrect or missing.

Procedure

On the Databases page, click Add Database. The Add Database dialog opens.
In the Database Details section, provide the following details:
- Database Type: Select the type of database you want to backup. The following options are available:
  - Standalone
  - RAC
- Database SID: Enter the Oracle system identifier of the database instance that you want to back up.
- Oracle Server: Select the registered Oracle server host that is running the database instance.
- Oracle Home: Enter the Oracle directory that contains Oracle database software and the configuration files.
- Oracle Grid Home: Enter the location for Oracle Grid.
In the Database Authentication section, provide the following details:
- Authentication Type: Specify the type of method used to authenticate Oracle databases. Druva supports the following authentication types:
  - Oracle authentication: This type requires a user to provide a valid username and password to connect to the database. The connection is denied on providing an incorrect username and password.
    
    Database Credentials: This field is displayed only if the Oracle type is selected. Select the credential label from the drop-down list. Druva maintains the credentials securely in its Credential Store. You can assign credentials to one or more servers seamlessly without having to input the credentials manually each time. For more information, see Credentials store.
    In addition, you can also define credentials to connect to the database. For more information, see Add credentials.
  - OS authentication: In this authentication type, Druva will automatically detect the OS-authenticated user and uses the user details to connect to the database. Druva does not store the OS-user authentication details.
  - Wallet authentication: In this authentication type, the Oracle Wallet stores the login credentials into the credential store along with the alias name. The username and password are hidden from the system user, thereby reducing the security risk. You must provide the alias name to connect to the database. Oracle DTC retrieves the credentials using aliases that are set up when you encrypt and store the credentials in the credential store. For example, for username/password@db, you have stored the alias as cdb01, then you must connect to the database by using the alias cdb01 instead of the actual username.
    
    📝 Notes
    
    Wallet authentication type is supported only for client version 5.1.0 and above.
    Oracle recommends using Wallet authentication as it is the most secure authentication type.
  - TNS Alias: Specify the Transparent Network Substrate (TNS) entry that Oracle listener uses to connect to the database. The TNS alias is specified in the tnsnames.ora file located at $ORACLE_HOME/network/admin.
  - Wallet Alias: If you select Wallet as the authentication type, you must provide the Wallet Alias for connecting to the database. Wallet Alias is configured in the Oracle Wallet.
Click Test Connection to validate the Oracle credentials provided for the database. If the test connection is successful, you can save credentials and use them to connect to the database for further operations.
In the RMAN Recovery Catalog section, enable the Enable Recovery Catalog option to connect to the RMAN through the RMAN Recovery Catalog.
- If you have selected Oracle or OS authentication type, in the Catalog Credentials list, select the Catalog credential label. In addition, you can also define credentials to connect to the RMAN Recovery Catalog using New Credentials.
- In the TNS Alias box, specify the Transparent Network Substrate (TNS) entry that Oracle listener uses to connect to the Catalog. The TNS alias is specified in the
```
tnsnames.ora 
```
  file located at $ORACLE_HOME/network/admin.
  
  📝 Note
  You must specify the TNS alias if the environment variable, Oracle_SID, is not set on your Oracle server.
  The following is a sample entry for the TNS alias that is added to the
```
tnsnames.ora 
```
  file :
```
RACORA2 =   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = agdev-rac-n2-vip)(PORT = 1521))     (CONNECT_DATA =       (SERVER = DEDICATED)       (SERVICE_NAME = racora)     )   )
```
  We recommend that you add the required entry to the
```
tnsnames.ora 
```
  file and use the identifier (RACORA2, in this case) on the Management Console.
- If you have selected Wallet authentication type, in the Catalog Wallet Alias box, specify the wallet alias to connect to the catalog. Catalog Wallet Alias is configured in the Oracle Wallet. For example, if you have configured the wallet alias as
```
catdb 
```
  in the Oracle Wallet, you must enter catdb in the Catalog Wallet Alias box to connect to the catalog.
Click Save to add the database details.

The database is added successfully and listed on the Databases page.

Authenticate a database

Druva requires you to configure Oracle databases to authorize users and entities to connect to the databases. Druva enables you to authenticate users based on the following authentication types:

OS authentication: In this authentication type, Druva automatically detects the OS-authenticated users and uses the user details to connect to the databases.

📝 Note
Druva does not store the OS-user authentication details.

Oracle authentication: In this authentication type, you must provide a valid username and password to connect to the database. The connection is denied on providing an incorrect username and password. Druva maintains the credentials securely in its Credential Store. You can assign credentials to one or more servers seamlessly without having to input the credentials manually each time. For more information, see Credentials store.
In addition, you can also define credentials to connect to the database. For more information, see Add credentials.
Wallet authentication: In this authentication type, the Oracle Wallet stores the login credentials into the credit store along with the alias name. The user name and password are hidden from the system user, thereby reducing the security risk. You must provide the alias name to connect to the database. Oracle DTC retrieves the credentials using aliases that are set up when you encrypt and store the credentials in the credential store. For example, for username/password@db, you have stored the alias as cdb01, then you must connect to the database by using the alias cdb01 instead of the actual user name.
For a RAC database, you can select the server on which you want to run the authentication.

📝 Notes

Wallet authentication type is supported only for client version 5.1.0 and above.
Oracle recommends using Wallet authentication as it is the most secure authentication type.

Assigning authentication types to auto-discovered databases

Perform the following steps to assign an authentication type to auto-discovered databases.

Procedure

On the Phoenix Management Console, in the left pane, click All Databases.
On the Databases page, select the database to which you want to assign an authentication type.
Under the Authentication Type column, click Assign

.
On the Database Parameters dialog box, in the Database Authentication section, select the Authentication Type. For more information on supported authentication types, see Authenticate a database.
Provide values for the following fields depending on the authentication type selected in Step.4:

Authentication type	Field	Description
Oracle	Database Credentials	Druva Phoenix maintains the credentials securely in its Credential Store. You can assign credentials to one or more servers seamlessly without having to input the credentials manually each time. For more information, see Credentials store. In addition, you can also define credentials to connect to the database. For more information, see Add credentials.
Wallet	Wallet Alias	Alias for connecting to the database. Wallet Alias is configured in the Oracle Wallet.For example, if you have stored the alias as cdb01, then you must connect to the database by using the alias cdb01.

Click Test Connection to validate the credentials provided for the database. If the test connection is successful, you can save credentials and use them to connect to the database for further operations. If the test connection fails, then check if you are able to login to the database manually using those credentials.
In the RMAN Recovery Catalog section, enable the Enable Recovery Catalog option to connect to the RMAN through the RMAN Recovery Catalog.
Provide values for the following fields depending on the authentication type selected in Step.4:

Authentication type	Field	Description
Oracle or OS	Catalog Credentials	Select the Catalog credential label. In addition, you can also define credentials to connect to the RMAN Recovery Catalog using New Credentials.
Wallet	Catalog Wallet Alias	Alias for connecting to the catalog. Wallet Alias is configured in the Oracle Wallet. For example, if you have configured the wallet alias as catdb in the Oracle Wallet, you must enter catdb in the Catalog Wallet Alias box to connect to the catalog.

If you have selected Oracle or OS authentication type, in the TNS Alias box, specify the Transparent Network Substrate (TNS) entry that Oracle listener uses to connect to the Catalog. The TNS alias is specified in the tnsnames.ora file located at $ORACLE_HOME/network/admin.

📝 Note
You must specify the TNS alias if the environment variable, Oracle_SID, is not set on your Oracle server.
Click Test Connection.
Click Save.

Add credentials

You can define credentials and assign them to one or more servers seamlessly without having to input the credentials manually each time.

Procedure

On the Database Authentication page, click New Credentials.
On the Add Credentials page, provide the following details:
- Label: Enter a label to uniquely identify a credential that you want to store with Druva.
- Username: Enter the username of the credential you want to store with Druva. If your account uses a domain, enter the username as domain\username. For example, DruvaCorp\JohnDoe.
- Password: Enter the password of the credential you want to store with Druva.
- Confirm Password: Re-enter the password of the credential you want to store with Druva.
Click Save.

Druva lists all the credentials on the Credentials Store page. To view the credentials, select an organization if the organization is enabled, and then click Settings > Credentials Store on the top menu.

Update database parameters

When you trigger discovery, the Hybrid Workloads agent fetches the database parameters and lists the details on the Databases page. Druva lets you update values of the database parameters after the databases are discovered on the Databases page.

📝 Note
You cannot change the name of the database and Oracle server.

Procedure

Click the All Databases tab. The Databases page opens.
In the Database Name column, select the database for which you want to update the setting values, and click on the vertical three dots and then click Database Parameters.
On the Database Parameters dialog, update the required settings:
- Oracle Home: The Oracle directory that contains Oracle database software and the configuration files.
- Authentication Type: The type of method used to authenticate Oracle databases, such as Oracle, OS, or Wallet. For more information about the authentication types, see Authenticate a database.
  
  ❗ Important
  
  For a RAC database, if you change the authentication type from OS or Wallet to Oracle, make sure you reconfigure the database and provide a TNS alias for each node to avoid backup failure. Likewise, if you change the authentication type from OS or Oracle to Wallet, make sure you reconfigure the database and provide a Wallet alias for each node to avoid backup failure.
- TNS Alias: The TNS entry that the Oracle listener used to connect to the database.

Change backup policy

You can reconfigure a database for backup by changing its backup policy.

Procedure

Click the Configured Databases tab.
On the Configured Databases page, click the database for which you want to assign a different backup policy.
On the Configured database details page, click the more

icon and click Change Backup Policy.
On the Change Backup Policy dialog, select the required backup policy from the drop-down list.
Click Save.

Druva applies backup settings of the selected backup policy to all the existing recovery points.

Quick steps to back up Oracle databases

Configure Oracle databases for backup

About restore of Oracle Direct to Cloud Servers

Restore an Oracle database from a recovery point

Manage Oracle backups