Backup Exec: Configure Oracle on Linux (Archived Example)

This archived workflow configures the Backup Exec Oracle agent on Linux and the corresponding Windows backup server. The source uses BE15-era interfaces and Oracle 11g examples. It is titled for a standalone database but includes racdb1/racdb2 hosts and an explicitly RAC-labeled discovered resource. The steps below retain that limitation; they are not a complete RAC deployment procedure or a support statement for current Backup Exec or Oracle releases.

English terminal excerpts that contain no credentials are retained. Chinese dialogs and credential-related views are replaced by instructional English reconstructions. Blank fields and descriptive account labels are examples, not saved credentials or successful authentication. Match the actual product compatibility, instance topology and installed-version guide before applying configuration changes.

1. Prerequisites and name resolution

Have the intended Backup Exec server and required Oracle/Applications and Databases functionality available, with the compatible RALUS agent already installed on the Oracle Linux host. The source’s prerequisite line uses the name DPA without explaining it; this article’s actual commands and screens are for Backup Exec/RALUS, not a substitute configuration for another backup product.

On the Linux Oracle host, review /etc/hosts or the approved name-resolution service. Ensure the intended backup server name and Oracle host name resolve correctly from the systems that will communicate. Test the actual endpoints; a successful ping checks only part of connectivity and does not establish agent trust or database access. Preserve existing valid mappings. The combined illustration uses the source Windows example addresses; it does not reproduce unrelated original hosts-file entries.

Fresh combined Linux/Windows name-resolution illustration. Historical examples are racdb1 at 192.168.100.1 and BE15 at 192.168.100.215; verify the actual environment.

2. Check the Oracle OS account and instance file

Check the actual Oracle software owner, for example with id oracle. The account used for the agent’s OS-level Oracle operations must have the required beoper membership and appropriate Oracle OS privileges for the selected workflow. The source says the installer adds the Oracle owner; verify rather than assume this happened. Veritas documents installer-created beoper membership with environment-specific exceptions, so correct membership through the approved OS administration process while retaining existing required groups.

Fresh account-verification card replacing the original id output. It requests verification and does not invent user/group IDs or a successful result.

The source prepares /etc/VRTSralus/beoratab from /etc/oratab and checks that the SID and Oracle home identify the intended instance. Review and retain existing configured entries before copying or editing files. The pictured historical line is raci1:/u01/app/oracle/product/11.2.0/db_1:N. Use the actual instance entry instead of changing an arbitrary last line or assuming the example SID exists.

Fresh beoratab example: SID, Oracle home and Y/N field retained without surrounding source terminal details; no actual configuration is changed.

Use an authorized Oracle client connection to verify access to the intended instance before configuring backup integration. Supply any required database password locally and interactively; no source password or password-bearing connection command is reproduced. A database login test is separate from validating a backup or recovery.

Fresh database-access instruction replacing the original credential-related Oracle connection screen; no successful connection or password value is invented.

3. Configure database access in AgentConfig

In the source’s legacy sequence, run /opt/VRTSralus/bin/AgentConfig with the required administrative privileges on the Linux host. Choose 1, Configure database access, then 1, Add system credentials for Oracle operations. Enter the authorized Linux OS account in beoper and its password interactively. These OS credentials are distinct from the database SYSDBA credentials supplied when configuring the instance.

Follow the supported order and permissions for the installed release. The related Veritas 21.2 guide describes enabling database access after configuring an instance; this article preserves the older source’s sequence and does not claim it is mandatory for every version.

Original English Remote Agent Utility main menu: Configure database access selected with 1. Its RAC 12c note belongs to the original utility and does not make this a complete RAC guide.

Fresh English machine-information menu with Add system credentials selected; no original credential screen was used as image input.

Fresh explanation of interactive Linux OS account/password entry. It does not supply a sample password or substitute database credentials.

The source answers n to the custom-port question and y to commit. Keep matching communication settings on both sides; do not infer that a default port is reachable merely from selecting n. Its success line reports that an entry was added to the configuration file, not that an Oracle backup succeeded. Exit this submenu with 5 and the main utility with 3.

Original English prompt: custom connection port answered n in the historical example.

Original English commit prompt answered y, followed by an entry-added acknowledgement. This is a configuration result only.

Fresh machine-information menu at the source exit step: 5, Quit; stored account entries are omitted.

Original English main utility menu with 3, Quit selected.

4. Configure Oracle instance information

As the actual Oracle software owner, run /opt/VRTSralus/bin/AgentConfig in the appropriate environment. The source chooses 2, Configure Oracle instance information; 1, Add a new Oracle instance to protect; and entry 1 for raci1. Discover and select the intended local instance instead of relying on the example number or name. For RAC, stop and follow the additional matching RAC requirements noted by the utility.

Original English utility menu selecting Oracle instance information with 2; the source contains a minor capture artifact but the menu remains readable.

Original English Oracle Agent menu selecting 1, Add a new Oracle instance to protect, with its explicit additional-RAC-steps warning.

Original English discovered-instance selection: entry 1, raci1. Use the actual intended instance.

Supply the authorized database SYSDBA authentication for that instance locally. The source uses a SYSDBA user; its password is omitted here. This database login is not interchangeable with the Linux OS logon account that Backup Exec uses for machine-level access. Enter the actual Backup Exec server name or address when prompted.

Fresh blank database-authentication explanation replacing the credential-related source view; Linux OS and SYSDBA roles remain distinct.

Original English backup-server prompt with the historical address 192.168.100.215. It is not an address to use without verification.

The source answers n to both recovery-catalog use and a custom job template. Those are historical example choices, not universal requirements. Select the actual recovery-catalog arrangement and DBA job integration required by the environment.

Original English recovery-catalog prompt answered n.

Original English custom-template prompt answered n.

If using DBA-initiated jobs and a custom RMAN script, configure the corresponding DBA-initiated job template on the Backup Exec server and use its exact matching name when required. The source mentions DEFAULT as its default template name; check the installed version and configuration rather than assuming every installation uses it. It points to the historical sample path C:\Program Files\Symantec\Backup Exec\Scripts\oracle\backup-database.rman. The channel below uses the Backup Exec-compatible SBT media-management integration; do not substitute parameters from a different backup product.

The source’s minimal sample is allocate channel ch0 type 'sbt_tape'; inside a RUN block with backup database;. It is a teaching example, not a complete recovery policy: backup destinations, retention, archived logs, control-file handling and restore validation require the actual supported job design.

Original English minimal RMAN sample, including the sbt_tape channel and backup database command. No backup was run as part of this documentation work.

Fresh English DBA-initiated job-settings excerpt; actual template list entries are omitted, and none are fabricated.

The source commits the instance settings with y. Its acknowledgement also reports creation of a libobk.so link from the RALUS media-management library into its example Oracle home. Verify the applicable library setup for the actual Oracle architecture and agent version; this source message is not an instruction to overwrite an existing media-management library. Exit the instance submenu with 5 and the main utility with 3.

Original English commit result and libobk.so link message for the historical Oracle home; it does not prove a successful SBT backup or restore.

Original English Oracle Agent submenu exit with 5.

Original English main utility exit with 3.

5. Restart the agent using its supported service method

The source uses /etc/init.d/VRTSralus.init stop followed by /etc/init.d/VRTSralus.init start. Coordinate active jobs and verify that this legacy init script is appropriate for the installed agent/OS. A different service manager or agent release can require another supported method. No Oracle, RALUS or backup-server service was changed while preparing this English edition.

Fresh English legacy stop/start command card without the original terminal details or a fabricated successful restart.

6. Configure the Windows Backup Exec server

Open the Backup Exec management console with the administrative rights required for configuration. Check name resolution for the actual Linux host and backup server on Windows as well. The combined example below replaces the original Windows hosts screenshot; only the relevant host mappings are retained. Editing a hosts file alone does not establish network access, agent trust or a usable account.

Same fresh combined name-resolution illustration at the Windows step; unrelated original hosts entries are excluded.

Open Configuration and Settings > Logon Accounts > Manage Logon Accounts, or use the Logon Account Wizard in the source-era interface. Create or select a Backup Exec logon account corresponding to the authorized Linux Oracle OS user. Provide its actual password locally; the source’s example password is not reproduced. A Backup Exec logon account stores access credentials; it does not create the Linux OS user or grant that user its required groups.

Fresh English navigation summary for Logon Accounts and Oracle settings. It is not a literal screenshot of a particular installed console.

Fresh English Logon Account Management excerpt with an illustrative account description and no actual username or credential values.

The source leaves Restricted logon account unchecked. Apply the organization’s sharing and access requirements rather than treating that unchecked example as a universal recommendation. Ensure the intended jobs and administrators can use the configured account under the installed version’s rules.

Fresh English Add Logon Account dialog with all credential fields empty and the source’s unchecked restricted-account option explained.

7. Add the Linux host and inspect discovered Oracle resources

Under Backup and Restore, choose Add and select Linux computer. Review the trust option and establish trust only with the intended remote agent. Enter the actual Linux host to add, and select the previously configured Linux OS logon account. The source shows racdb1 and racdb2; those names are retained as historical examples, not as evidence that a single-instance setup requires two nodes.

Fresh English Add Server type-selection excerpt with Linux computer selected.

Fresh English trust-option excerpt: trust requested, with no claim that trust was already established.

Fresh English server-selection excerpt with the source’s two RAC-style names; follow the actual topology and matching RAC guide when applicable.

Fresh English logon-account selection excerpt. Its descriptive account label is illustrative, not a credential or test result.

Review the summary before Finish and then inspect the actual added hosts and discovered Oracle resources. The source says that an Oracle virtual resource is discovered automatically, but its resulting screenshot explicitly labels a RAC resource. Verify what the installed agent actually discovers and resolve any missing or unexpected instances. The reconstruction does not invent database names, instance IDs or backup history.

Fresh English pre-Finish summary: Linux computer, requested trust and source host names. It is not completion evidence.

Fresh conceptual resource-list illustration replacing the original RAC-labeled dashboard. Generic entries do not assert actual resource names or counts.

8. Map Oracle-operation credentials and validate

Open Configuration and Settings > Backup Exec Settings > Oracle. Configure the required Oracle-server/resource entries and select the authorized Linux OS logon account used for the intended operations. Check the host/resource names and requirements for the actual installed version. The following two source settings positions use the same English explanatory mapping; neither demonstrates a passed credential test.

Repeated fresh English navigation summary at the source Oracle-settings step.

Fresh English Oracle-operation authentication mapping with an empty server-name input and descriptive account labels, not saved real credentials.

Same fresh English mapping at the second source settings view; neither original view establishes a successful test or completed backup.

In Manage Logon Accounts, use the applicable Test operation for the actual Linux host and discovered Oracle resource. Resolve authentication or authorization failures before creating or running the intended database backup job. The source requests these tests but does not supply an independent successful test result, completed database backup or restore exercise. After selecting the correct database resources and supported job settings, review job/RMAN results and validate recovery through the appropriate restore test. Resource discovery and configuration-file acknowledgements are separate from recoverability.

English references and source scope

A corresponding public English version of the original protected BookStack walkthrough was not established. The related manufacturer English references below verify selected account/agent concepts, with their version scopes stated. They are not treated as identical BE15 screenshots or a current compatibility guarantee.