Forum Discussion

remsma's avatar
remsma
Level 2
7 years ago

Nebackup and Rac one node

We  use netbackup version 8 to backup Oracle Rac Onde Node (include 3 nodes) version 12.2.0 Cluster database on linux, we have configured the netbackup policies to backup

 We use vip adress not scan adress. The database is relocated at the moment  on node1.

When we excute rman command netbackup we get failed on node2 and nod3

 RUN {

 ALLOCATE CHANNEL A01 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=nod1-vip.xx.se)' CONNECT 'yz/yz@PVIP1 as sysbackup';

ALLOCATE CHANNEL A02 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=node1-vip.xx.se)' CONNECT 'yz/yz@PVIP1 as sysbackup';

 ALLOCATE CHANNEL A03 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=nod2-vip.xx.se)' CONNECT 'yz/yz@PVIP1 as sysbackup';

ALLOCATE CHANNEL A04 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=nod2-vip.xx.se)' CONNECT 'yz/yz@PVIP1 as sysbackup';

 ALLOCATE CHANNEL A05 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=nod3-vip.xx.se)' CONNECT 'yz/yz@PVIP1 as sysbackup';

ALLOCATE CHANNEL A06 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=nod3-vip.xx.se)' CONNECT 'yz/yz@PVIP1 as sysbackup';

 SEND 'NB_ORA_SERV=netbackup-master1,NB_ORA_POLICY=hot_policy';

 

log

--------

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Feb 8 08:35:58 2019

 Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.

 RMAN> 2> RMAN> 2>

connected to target database: test (DBID=9999999)

 RMAN> RMAN>

connected to recovery catalog database

 RMAN> RMAN>

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40> 41> 42> 43> 44> 45> 46> 47> 48> 49> 50> 51> 52> 53> RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40> 41> 42> 43> 44> 45> 46> 47> 48> 49> 50> 51> 52> 53>

allocated channel: A01

channel A01: SID=1197 instance=test_2 device type=SBT_TAPE

channel A01: Veritas NetBackup for Oracle - Release 8.0 (2016110921)

 allocated channel: A02

channel A02: SID=32 instance=test_2 device type=SBT_TAPE

channel A02: Veritas NetBackup for Oracle - Release 8.0 (2016110921)

 allocated channel: A03

channel A03: SID=211 instance=test_2 device type=SBT_TAPE

channel A03: Veritas NetBackup for Oracle - Release 8.0 (2016110921)

 allocated channel: A04

channel A04: SID=26 instance=test_2 device type=SBT_TAPE

channel A04: Veritas NetBackup for Oracle - Release 8.0 (2016110921)

 allocated channel: A05

channel A05: SID=234 instance=test_2 device type=SBT_TAPE

channel A05: Veritas NetBackup for Oracle - Release 8.0 (2016110921)

 allocated channel: A06

channel A06: SID=436 instance=test_2 device type=SBT_TAPE

channel A06: Veritas NetBackup for Oracle - Release 8.0 (2016110921)

sent command to channel: A01

sent command to channel: A02

sent command to channel: A03

sent command to channel: A04

sent command to channel: A05

sent command to channel: A06

 sql statement: alter system archive log current

 Starting backup at 08-FEB-19

current log archived

channel A01: starting archived log backup set

channel A01: specifying archived log(s) in backup set

input archived log thread=2 sequence=2125 RECID=2188 STAMP=999660213

..............................

 channel A01: starting piece 1 at 08-FEB-19

RMAN-03009: failure of backup command on A04 channel at 02/08/2019 08:51:14

ORA-19506: failed to create sequential file, name="bk_113214_1_999678968", parms=""

ORA-27028: skgfqcre: sbtbackup returned error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

VxBSACreateObject: Failed with error:

Server Status: Communication with the server has not been initiated or the server status has not been retrieved from the serve

channel A04 disabled, job failed on it will be run on another channel

channel A02: starting archived log backup set

channel A02: specifying archived log(s) in backup set

input archived log thread=2 sequence=2128 RECID=2191 STAMP=999673235

input archived log thread=2 sequence=2129 RECID=2192 STAMP=999677823

input archived log thread=2 sequence=2130 RECID=2193 STAMP=999678948

Please advise how we can resolve it. I've reviewed the documentation but still confused about how to prcoeed.

Best Regards,

Remi

 

 

8
Linux
nebackup
NetBackup
raconenode
RMAN
Single Rac
  • Tape_Archived's avatar
    Tape_Archived
    Moderator
    7 years ago

    Ensure /etc/hosts on all three nodes have correct IP address of master & media server and you can ping through the interface that is being used for the backups (if you are not using primary interface for backup).

    Please run following command from master and media server for each of the nodes

    bptestbpcd -client node_name -verbose

    Please run following command from all three nodes

    bpclntcmd -pn

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    7 years ago
    You should probably change this to be unique for node two and three.

    CONNECT 'yz/yz@PVIP1

    eg

    CONNECT 'yz/yz@PVIP2
    CONNECT 'yz/yz@PVIP3
    • remsma's avatar
      remsma
      Level 2
      7 years ago

      Hi

      Thanks. I changed to be unique for node two and there. I get the same errors.

  • Marianne's avatar
    Marianne
    Level 6
    7 years ago

    remsma

    I am not Oracle RAC expert, but this statement says to be backup is probably not load balanced? 

     The database  relocated at the moment  on node1. 
    When we excute rman command netbackup we get failed on node2 and nod3

    Maybe this section of the manual might help?

    The backup script should be customized so that it starts RMAN on exactly one
    of the clients. If the script is executed on the primary, then start RMAN and
    perform the backup. If the script is executed on the secondary and the primary
    is up, then exit with status 0 so the NetBackup scheduler doesn't retry this client.
    If the script is executed on the secondary and the primary is down, then start
    RMAN and perform the backup. You can build the script customization around
    a tnsping to the primary or even a query of the database. Use this customization
    to see if the other instance is open and able to perform the backup.

    (See NBU for Oracle manual for more info... )

    • remsma's avatar
      remsma
      Level 2
      7 years ago

      Hi
      Thanks very much for your response. We will try to apply your suggestion if we will not be applicable to use scan adress instead.

      We use scan adress for connecting to database, when we try to use backup script using allocate channne disk and scan adress, we get no errors, everything executed succeffully.

      When we use netbackup. However when trying to connect, the connection to the node is random due to the nature of RAC. When the backup starts, the check is failing, resulting in a somewhat wrong error message of the client. Netbackup version 8.

      Is something missing.... In netbackupVersion 8 or  we need to complete some api...?????

      connect target xxx/yyyy@SCAN_ADRESS as sysdba
      connect catalog xyxy/xyxx@RMAN

      RUN {

      ALLOCATE CHANNEL A01 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=scan_adress.xx.se)' ;

      ALLOCATE CHANNEL A02 TYPE 'SBT_TAPE' PARMS 'ENV=(NB_ORA_CLIENT=scan_adress.xx.se)' ;

      SEND 'NB_ORA_SERV=netbackup-master1,NB_ORA_POLICY=hot_policy';

      -...............................................
      RMAN-03009: failure of backup command on C03 channel at 02/11/2019 15:27:31
      ORA-19506: failed to create sequential file, name="al_115403_1_999961946", parms=""
      ORA-27028: skgfqcre: sbtbackup returned error
      ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
      VxBSACreateObject: Failed with error:
      Server Status: Communication with the server has not been initiated or the server status has not been retrieved from the serve

      Recovery Manager complete.

      Mon Feb 11 15:27:32 CET 2019 ----------------End of Script------------------

      exit 1

       Best regards,

      Remi