A high-level overview of the steps required to set up Oracle protection is given here. Proceed to the sections referenced in each step for detailed instructions.
To implement Oracle protection
| Step 1: | Ensure that all requirements have been met as described in Requirements for Oracle protection. |
| Step 2: | Install the required Unitrends Windows, Linux, or Solaris agent. For requirements, see Unitrends version requirements for Oracle protection. |
Notes:
| • | For Oracle on Windows clients. If you will be using the agent push feature, skip this step. The Windows agent will be installed automatically when you add the Oracle client to the backup system. For agent push requirements, see Push installing the Windows agents. |
| • | For Oracle on Linux clients. The Linux agent requires the installation of a Samba client dependency. When installing the latest Linux agent, you will be prompted to install a Samba client if you wish to protect Oracle data. For more information, see Needed dependencies for Oracle and To install the Linux agent for CentOS, Oracle Linux, and Red Hat clients. |
| Step 3: | Add the Oracle client to the Unitrends backup system as described in About adding clients. Upon adding the client, it displays in the Navigation pane as described in Display of Oracle application in the backup system. |
Important! Regarding the Establish Trust setting on the Add Client page, note the following:
| • | To use the agent push feature for an Oracle on Windows client, check the Establish Trust box and enter Windows administrative trust credentials. If you have a Windows administrative account that is also a member of the ora_dba group, use this account so you will not need to enter Oracle instance-level credentials later. |
| • | For Oracle on Windows clients that will not be using the agent push feature, uncheck the Establish Trust box. Client-level credentials are not used. |
| • | For all Oracle on Linux and Oracle on Solaris clients, uncheck the Establish Trust box. Client-level credentials are not used. |
| Step 4: | Add instance-level credentials to each instance you wish to protect as described in To create a new credential for an Oracle database. |
Note: For Oracle on Windows clients. If the NT AUTHORITY\SYSTEM user is a member of the ora_dba group, or if you are using the agent push feature and have entered a Windows administrative credentials on the Add Client page and this user is a member of the ora_dba group, skip this step. In these cases, the system can use the NT AUTHORITY\SYSTEM or Windows administrative credentials for Oracle backups and restores.
| Step 5: | Run backups as described in Executing Oracle backups. Before running backups, be sure requirements described in Oracle backup requirements have been met. |
| Step 6: | Set up bare metal protection to prepare for disaster recovery, if ever needed. See one of the following for details: |
| • | For Oracle on Windows, see Windows Bare Metal Protection. |
| • | For Oracle on Linux, see Bare Metal for Linux. |
| • | For Oracle on x86-based Solaris systems, see Bare Metal for x86 Platforms. |
| • | For Oracle on Solaris SPARC systems, see Bare metal for Solaris SPARC. |