Use the preinstallation checklist to prepare the computer where you will install the agent, and to gather all of the information you will need during the installation.
Verify System Requirements
Verify that the computer where you will install the agent satisfies the minimum requirements. For more information, see System Requirements.
Verify License Requirements
Based on the licensing mechanism used in your CommCell environment, verify that the CommCell has the required licenses to use the Oracle Agent. For more information, see License Requirements.
Determine the Installation Location
Based on your environment, install the Oracle Agent on the appropriate computer.
|
Environment |
Where to install the software |
|---|---|
|
Non-Clustered |
On the computer on which the Oracle server resides. |
|
Clustered |
On the physical nodes of the cluster where the Oracle server resides. If you want to protect the Oracle Real Application Clusters (RAC), install the agent on all the nodes of the Oracle RAC. |
Prepare the Oracle Services to Restart
Commvault software restarts the Oracle services after the installation. Plan your installation for a time when a reboot can occur.
Define the PATH Environment Variable
Verify that the PATH environment variable includes the directory for Commvault executables.
For example:
PATH=E:\Commvault\ContentStore\Base; ...Gather Installation Data
Refer to the items in this section to gather the information that you will need during the installation. Record the information before you begin installing the software, so you can refer to it during the installation.
You can install the agent using either the CommCell Console or the installation package created by the Download Manager. Any item that applies to only one of these installation methods is noted.
Commvault Package to Install
-
For installations using the CommCell Console, install the Oracle package, which is under the Database category.
-
For installations using the installation package, install the Oracle package.
Note
If the File System Agent is not installed on the computer, the File System Core and File System packages are automatically installed with the package that you selected. The File System Agent will not consume any licenses.
To gather the required information for the File System Agent, refer to the Gather Installation Data section in the Preinstallation Checklist for the Windows File System Agent.
Client Computer Details
If the File System Agent or another package is already installed on the computer, you are not required to gather all the computer details again. The level of detail depends on how the package you selected is installed, as follows:
- For installations using the CommCell Console, the installation program requests only the name of the client computer.
For installations using the installation package, the installation program reads the details from the previous installation.
Restart the Oracle Services
Oracle services must be restarted after the installation.
-
For installations using the CommCell Console, select the Restart Oracle (if applicable) option. Oracle instances need to be restarted to load the Commvault media library. The media library is Commvault’s media management binary that streams data blocks to and from the Commvault media. The Commvault code executes in the context of the Oracle database.
-
For installations using the installation package, select the Process Manager option.
Auto Discovering Oracle Instances
By default, the Commvault software creates CommCell instances for Oracle databases under the following conditions:
-
Discovery is initiated every 24 hours.
-
When the Communications Service (GxCVD) is restarted (for example after a computer reboot).
-
Instances that are defined in the Oracle oratab file, which is created by Oracle at installation and acts as a database registry file. On Solaris systems, this file is normally located in the /var/opt/oracle directory and on Linux/UNIX systems, it is located in the /etc directory.
-
Instances that are in the NOMOUNT, MOUNT or OPEN state. The software does not discover instances that are shut down.
If you do not want the software to discover the databases, then you can set the nDisableAutoDiscoverInstancePostInstall additional setting on the CommServe computer and set the value to 1 before you install the Oracle Agent on your clients. When you set the additional setting to 1, the software makes the auto discovery feature unavailable on any client that you install the Oracle Agent software.