Example RAC configuration: Failover VIP is not available and backup is load balanced, simple script with manual policy failover

Article:HOWTO69221  |  Created: 2012-02-06  |  Updated: 2012-02-06  |  Article URL http://www.symantec.com/docs/HOWTO69221
Article Type
How To


Environment

Subject


Example RAC configuration: Failover VIP is not available and backup is load balanced, simple script with manual policy failover

Some implementations of RAC (Linux/Windows) do not include a failover VIP. On sites which do not need a robust backup script that determines the active instance in realtime, use the following configuration to manually initiate a backup from the secondary host when the primary host is down.

  • Create a first Oracle policy with an Application Backup schedule to receive the backup images from both hosts. Configure both vipnames or host names as clients in the policy. Do not configure an Automatic Backup schedule or a Backup Selection (script).

  • Create a second Oracle policy to execute the backup script on the primary host. Configure the vipname or host name of the primary host in the policy. Configure the pathname to the backup script in the policy. Create an Automatic Backup schedule with an open window in the policy.

  • Create a third Oracle policy that can be used to manually execute the backup script on the secondary host when the primary host is unavailable. Configure the vipname or host name of the secondary host in the policy. Configure the pathname to the backup script in the policy. Create an Automatic Backup schedule without an open window in the policy.

  • The backup script must be accessible to both hosts in the cluster, the clustered file system makes a good location.

  • Configure the backup to provide a host specific client name with each backup request using one of the following three options:

    • Configure RMAN to bind specific channels to specific instances and send specific client names on each channel for backup image storage and for connect-back to the requesting host for the data transfer. Do not use the failover VIP name, because it is active on only one of the hosts.

      ALLOCATE CHANNEL 1 ... PARMS='ENV=(NB_ORA_CLIENT=vipname1)' CONNECT='sys/passwd@vipname1';
      ALLOCATE CHANNEL 2 ... PARMS='ENV=(NB_ORA_CLIENT=vipname2)' CONNECT='sys/passwd@vipname2';
      ALLOCATE CHANNEL 3 ... PARMS='ENV=(NB_ORA_CLIENT=vipname1)' CONNECT='sys/passwd@vipname1';
      ALLOCATE CHANNEL 4 ... PARMS='ENV=(NB_ORA_CLIENT=vipname2)' CONNECT='sys/passwd@vipname2';

      Note:

      If one or more of these nodes are down, these allocation operations fail which causes the backup to fail.

    • Alternatively, configure Oracle to bind specific channels to specific hosts.

      CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' CONNECT 'sys/passwd@vipname1' PARMS 
         "ENV=(NB_ORA_CLIENT=vipname1)";
      CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' CONNECT 'sys/passwd@vipname2' PARMS 
         "ENV=(NB_ORA_CLIENT=vipname2)";
      CONFIGURE CHANNEL 3 DEVICE TYPE 'SBT_TAPE' CONNECT 'sys/passwd@vipname1' PARMS 
         "ENV=(NB_ORA_CLIENT=vipname1)";
      CONFIGURE CHANNEL 4 DEVICE TYPE 'SBT_TAPE' CONNECT 'sys/passwd@vipname2' PARMS 
         "ENV=(NB_ORA_CLIENT=vipname2)";
    • By default, the backup uses CLIENT_NAME from the bp.conf file which should be distinct for each host and is typically the physical hostname.

  • Configure the NetBackup master server to allow the physical host names access to all of the backup images.

    cd /usr/opnv/netbackup/db/altnames
    echo "hostname1" >> hostname1
    echo "vipname1" >> hostname1
    echo "hostname2" >> hostname1
    echo "vipname2" >> hostname1
    cp hostname1 hostname2

    If REQUIRED_INTERFACE or another means is being utilized on the client hosts to force NetBackup to use the IP addresses associated with the vipnames for the outbound user-directed backup requests, then also let the vipnames access all of the backup images.

    cd /usr/openv/netbackup/db/altnames
    cp hostname1 vipname1
    cp hostname1 vipname2

The second policy executes the backup script on the primary host when it is scheduled. RMAN starts the backup process on all of the hosts, and they send back the appropriate NB_ORA_CLIENT or CLIENT_NAME for that host. If the primary is down, initiate the secondary policy manually from the NetBackup master server and perform a similar backup. You can restore from either host or instance if either of these conditions is true: The 'SET AUTOLOCATE ON'; is enabled for the instance or the restore request is configured to specify the same client name as used when the backupset piece was transferred to storage.

SEND 'NB_ORA_CLIENT=client_name_used_by_backup';

See Oracle RAC with NetBackup best practices

See About NetBackup for Oracle operations

See Virtual names and RAC catalog maintenance


Legacy ID



v30171632_v71283312


Article URL http://www.symantec.com/docs/HOWTO69221


Terms of use for this information are found in Legal Notices