Before you can set up Druva Phoenix in your infrastructure, ensure that you have configured organizations and administrators. For more information, see Quick steps to set up Druva Phoenix to back up Oracle databases.
Ensure that you read through the system requirements and prerequisites.
Note: These instructions apply to install the Phoenix agent on Oracle Linux, RHEL Linux, and CentOS servers. Druva Phoenix does not support database backups on the Windows server hosts.
The following video illustrates the process.
Step 1: Download the Phoenix agent on the Oracle server
- Log in to the Phoenix Management Console.
- On the menu bar, click the drop-down next to All Organizations and select the organization where you want to register the Oracle Server.
- On the menu bar, click Protect > Oracle > Direct to Cloud.
- On the Oracle page, click Register Oracle Server.
The Register Oracle Server page opens.
- In the Download and install Oracle agent on the server section, click Download to download the package.
After you download the agent installer, install the Phoenix agent on your Oracle server.
Step 2: Install the Phoenix agent on the Oracle Server
- Go to the directory that contains the Phoenix agent installer.
- Run the following command:
rpm –ivh <package name>
where <package name> represents the file name (along with the extension) of the installer.
Example: rpm –ivh druva-phoenix-oracle-client-4.9.3-107618.x86_64.rpm
Note: We do not recommend the use of a package manager, such as yum, for installing the Phoenix agent package to avoid any installation errors.
Step 3: Activate the Phoenix agent
After you install the Phoenix agent, you must activate the Phoenix agent by using the activation token generated at the time of registering the Oracle server. The token functions as a unique identifier and performs a one-time authentication of the Phoenix agent. After authentication, the Phoenix agent establishes a persistent connection with the Druva Cloud.
- In the Activate Server for Backup section, Druva provides a Default Activation Token that you use to activate the Oracle server. This token is valid for 25 servers and for 7 days.
- Click Copy Script to copy the activation script containing the activation command and activation token, save it to a text file, and click Done.
- You can also navigate to Manage > Activation Tokens from the top menu bar to get the activation token again.
- If this token has expired, click Generate New Token. In the Generate Token dialog box, enter the following details, and click Generate.
Field Description Token Label Specify a label to help you identify the token.
This token can activate
Specify the number of Oracle servers that the activation token can activate. The default value is 25 servers. The token expires in Specify the number of days after which the activation token expires. The default value is 7 days.
After you generate an activation token, activate the Phoenix agent on your Oracle server.
Note: We recommend that you use a single token to activate servers that share something in common. For example, you might want to use a token to activate all servers that are geographically co-located.
- The TMG drops the idle connections after a defined timeout duration, due to which the agent does an aggressive retry with the server.
Note: In TMG application, it is recommended to set connection timeout value to 5 minutes.
- The configuration file path for Phoenix agent on Linux is as follows:
- Open the command prompt.
- Run the activation script copied in Step 3.1.
Note: On Linux servers, the Phoenix agent writes logs to /var/log/Phoenix. The free space at this location should be at least 1% of your source data size.
After the Phoenix agent is activated, the registered Oracle server hosts appear on the Oracle Servers page.
The Phoenix agent intelligently discovers container databases (and pluggable databases for each container database) and standalone databases that run on the Oracle Server hosts and lists them on the Databases page. However, you can trigger the Discover Database operation on the Druva Phoenix Management Console to fetch details of the discovered databases. For more information, see Discover databases.