Forum Discussion

alan_rickman's avatar
15 years ago
Solved

Oracle RAC configuration assistance

Hi all,

I've been tasked with setting up backups of our Oracle RAC. I've installed the agent on all four nodes in the cluster and they are visible under "Linux / Unix Servers" in Backup Exec 2010 client.

However there are no entries under "Oracle Real Application Clusters"

I noticed when running ./AgentConfig and selecting the option to "Configure Oracle instance information" this message was displayed:

"If this computer is a RAC node, you must perform additional steps for configuration before you continue. Refer to the readme for these additional steps."

Can anybody point me in the direction of the additional steps that are required?

Any help would be greatly appreciated!!

Thanks,

Alan

  • RAC database "TEST" with DB-ID "123456789" would look like this under BE Oracle RAC

    "RAC-TEST-123456789"

    Prereqs :-

  • Add O/S user that has DBA privileges (the owner of oracle binaries) to the beoper group
  • Copy /etc/oratab to /etc/VRTSralus/beoratab
  • Replace the dbname entries in /etc/VRTSralus/beoratab with the name of the Oracle SID of the RAC database on that machine
  • This example uses the root account to configure the agent.  Note: the user account with which you are logged in cannot be a member of the Oracle DBA group.  If root is a member of the Oracle DBA group, expect to see problems verifying the credentials.
  • Make sure you have installed the 64-bit agent if you are running 64-bit O/S.  The 32-bit version will install but it will also exhibit problems verifying the credentials.
  •  

    Next ----

     

    • Each node of the RAC has an Oracle SID which can be different from the database name
    • Each node's Oracle SID can be identified by the environment variable ORACLE_SID (echo $ORACLE_SID at a command line)
    • Example 2-node RAC
     
    Physical Host Name ORACLE_SID Database Instance Name DatabaseID
    OracleTest1 Test1 Test 123456789
    OracleTest2 Test2 Test 123456789


    To find the database instance name and database identifier (DB-ID)
    • sqlplus SYS as SYSDBA
    • or to connect to a specific Oracle SID, sqlplus SYS@Test1 as SYSDBA
    • select DBID,NAME from v$database;

    After you have the above values start the agent configuration utility :-

  • su - root
  • cd /opt/VRTSralus/bin
  • ./AgentConfig
  •  

     

    Configure database access

    Add system credentials

    Add the FQDN of the node you are running the above on

    view system credential used for oracle operation

     

    If all looks fine quit out of above and configure oracle instance information. Once you choose option 2 below information would show up

     

    you must perform additional steps for configuration before you continue.  Refer to the readme for these additional steps

     

    At this point the above note is referring to the afore-mentioned prerequisite: you need a modified copy of /etc/oratab called /etc/VRTSralus/beoratab with the database name entries updated to reflect the ORACLE_SID for that node:

    The ortab file would contain the following information on both the nodes.
    +ASM1:/oracle/product/10.2.0/asm:N
    TEST:/oracle/product/10.2.0/db:N

    The beoratab file on NODE 1 should be modified to reflect the  ORACLE_SID for that node as shown below. Same thing has to be done on the NODE 2

    beoratab file on NODE 1
    +ASM1:/oracle/product/10.2.0/asm:N
    TEST1:/oracle/product/10.2.0/db_1:N

    beoratab file on NODE 2
    +ASM1:/oracle/product/10.2.0/asm:N
    TEST2:/oracle/product/10.2.0/db_1:N

     

    Then configure Oracle Agent (add new instance)

    punch in the oracle dba usename and password

     

    Repeat the steps on other nodes of the RAC
     

    After you are done with above. On the BE server go to tools->Options->oracle->modify list

    add the accounts. For a 4 node rac you will have 5 entries

     

    One for each node plus one for the virtual node name as it appears in Backup Exec Selection lists

     

    add the node name and logon account

    for the virtual node name use RAC-TEST-123456789 and corresponding Linux account that will be used to authenticate the connection 

     

    Once the above is done your agent is configured. View it under ORAC. When connecting to the nodes to do file system backups, "connect as" the root account (or appropriate OS account which is a member of beoper group).  When connecting to the Oracle RAC, choose the account which is the oracle owner at the OS level.

     

     

    Let me know if the above steps were helpful

  • RAC database "TEST" with DB-ID "123456789" would look like this under BE Oracle RAC

    "RAC-TEST-123456789"

    Prereqs :-

  • Add O/S user that has DBA privileges (the owner of oracle binaries) to the beoper group
  • Copy /etc/oratab to /etc/VRTSralus/beoratab
  • Replace the dbname entries in /etc/VRTSralus/beoratab with the name of the Oracle SID of the RAC database on that machine
  • This example uses the root account to configure the agent.  Note: the user account with which you are logged in cannot be a member of the Oracle DBA group.  If root is a member of the Oracle DBA group, expect to see problems verifying the credentials.
  • Make sure you have installed the 64-bit agent if you are running 64-bit O/S.  The 32-bit version will install but it will also exhibit problems verifying the credentials.
  •  

    Next ----

     

    • Each node of the RAC has an Oracle SID which can be different from the database name
    • Each node's Oracle SID can be identified by the environment variable ORACLE_SID (echo $ORACLE_SID at a command line)
    • Example 2-node RAC
     
    Physical Host Name ORACLE_SID Database Instance Name DatabaseID
    OracleTest1 Test1 Test 123456789
    OracleTest2 Test2 Test 123456789


    To find the database instance name and database identifier (DB-ID)
    • sqlplus SYS as SYSDBA
    • or to connect to a specific Oracle SID, sqlplus SYS@Test1 as SYSDBA
    • select DBID,NAME from v$database;

    After you have the above values start the agent configuration utility :-

  • su - root
  • cd /opt/VRTSralus/bin
  • ./AgentConfig
  •  

     

    Configure database access

    Add system credentials

    Add the FQDN of the node you are running the above on

    view system credential used for oracle operation

     

    If all looks fine quit out of above and configure oracle instance information. Once you choose option 2 below information would show up

     

    you must perform additional steps for configuration before you continue.  Refer to the readme for these additional steps

     

    At this point the above note is referring to the afore-mentioned prerequisite: you need a modified copy of /etc/oratab called /etc/VRTSralus/beoratab with the database name entries updated to reflect the ORACLE_SID for that node:

    The ortab file would contain the following information on both the nodes.
    +ASM1:/oracle/product/10.2.0/asm:N
    TEST:/oracle/product/10.2.0/db:N

    The beoratab file on NODE 1 should be modified to reflect the  ORACLE_SID for that node as shown below. Same thing has to be done on the NODE 2

    beoratab file on NODE 1
    +ASM1:/oracle/product/10.2.0/asm:N
    TEST1:/oracle/product/10.2.0/db_1:N

    beoratab file on NODE 2
    +ASM1:/oracle/product/10.2.0/asm:N
    TEST2:/oracle/product/10.2.0/db_1:N

     

    Then configure Oracle Agent (add new instance)

    punch in the oracle dba usename and password

     

    Repeat the steps on other nodes of the RAC
     

    After you are done with above. On the BE server go to tools->Options->oracle->modify list

    add the accounts. For a 4 node rac you will have 5 entries

     

    One for each node plus one for the virtual node name as it appears in Backup Exec Selection lists

     

    add the node name and logon account

    for the virtual node name use RAC-TEST-123456789 and corresponding Linux account that will be used to authenticate the connection 

     

    Once the above is done your agent is configured. View it under ORAC. When connecting to the nodes to do file system backups, "connect as" the root account (or appropriate OS account which is a member of beoper group).  When connecting to the Oracle RAC, choose the account which is the oracle owner at the OS level.

     

     

    Let me know if the above steps were helpful

  • Hi,

    Thank you so much I followed your steps and have now had several days of successful Oracle backups!

    Not sure if I was looking in the wrong place but I couldn't find any information to that level of detail to help with configuring this.

    Thanks,

    Alan

  • You can keep a note of above and please mark the post as resolved