Veritas & Backint

Chaps,
I am trying to put together a backup strategy based on 4.6C, Unix, Oracle of out production systems.  The comapany uses veritas for general backups.
Any advice on wheather to use RMAN or Veritas and could someone give me some pointers to documentation as to how to setup veritas to integrate with SAP's BR tools .....
I am assuming that I am on the right lines.
Thanks.

Hello Claire,
I have recently setup the online backup policy for my SAP servers on Veritas Netbackup 5.0 it is very simple to use and manage..., my SAP servers running on Win2003 so if u would like to know the configuration of different scripts and changes made in SAP scripts then let me know....
also u can contact me on [email protected] for configuration document that i have made up myself for veritas netbackup....
Thanks
give rewards for the same..

Similar Messages

  • Veritas NetBackup using backint: error -8020 Reply buffer filled

    Hi All
    I'm trying to configure NetBackup on one of our SAP BW 7.0 system with MaxDB 7.6.00.35 running on Linux. I followed sap help and configure the backint. But when I execute the backup I'm getting the following error.
    Constructed the following reply:
    ERR
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    following is the dbm.ebp
    2007-06-26 21:35:40
    Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
    Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
    Using connection to Backint for MaxDB Interface.
    2007-06-26 21:35:40
    Checking existence and configuration of Backint for MaxDB.
    Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/BWA/backint/config' as path of the configuration file of Backint for MaxDB.
    Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB to configuration value '/sapdb/data/wrk/BWA/backint/config'.
    Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/BWA/backint/config'.
    Found keyword 'BACKINT' with value '/sapdb/BWA/db/bin/backint'.
    Found keyword 'INPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
    Found keyword 'OUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
    Found keyword 'ERROROUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/BWA/backint/adapter.para'.
    Found keyword 'TIMEOUT_SUCCESS' with value '600'.
    Found keyword 'TIMEOUT_FAILURE' with value '300'.
    Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/BWA/'.
    Finished reading of the Backint for MaxDB configuration file.
    Using '/sapdb/BWA/db/bin/backint' as Backint for MaxDB program.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in' as input file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/adapter.para' as parameter file for Backint for MaxDB.
    Using '600' seconds as timeout for Backint for MaxDB in the case of success.
    Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
    Using '/sapdb/data/wrk/BWA/dbm.knl' as backup history of a database to migrate.
    Using '/sapdb/data/wrk/BWA/dbm.ebf' as external backup history of a database to migrate.
    Checking availability of backups using backint's inquire function.
    Check passed successful.
    2007-06-26 21:35:40
    Checking medium.
    Check passed successfully.
    2007-06-26 21:35:40
    Preparing backup.
    Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
    Setting environment variable 'BI_REQUEST' to value 'NEW'.
    Setting environment variable 'BI_BACKUP' to value 'FULL'.
    Constructed Backint for MaxDB call '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
    B.in -c'.
    Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output for Backint for MaxDB.
    Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output for Backint for MaxDB.
    Writing '/backup/BWA/BWAPIPE #PIPE' to the input file.
    Prepare passed successfully.
    2007-06-26 21:35:40
    Creating pipes for data transfer.
    Creating pipe '/backup/BWA/BWAPIPE' ... Done.
    All data transfer pipes have been created.
    2007-06-26 21:35:40
    Starting database action for the backup.
    Requesting 'SAVE DATA QUICK TO '/backup/BWA/BWAPIPE' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BWAPIPE'' from db-kernel.
    The database is working on the request.
    2007-06-26 21:35:40
    Waiting until database has prepared the backup.
    Asking for state of database.
    2007-06-26 21:35:40 Database is still preparing the backup.
    Waiting 1 second ... Done.
    Asking for state of database.
    2007-06-26 21:35:41 Database is still preparing the backup.
    Waiting 2 seconds ... Done.
    Asking for state of database.
    2007-06-26 21:35:43 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2007-06-26 21:35:43
    Starting Backint for MaxDB.
    Starting Backint for MaxDB process '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
    B.in -c >>/sapdb/data/wrk/BWA/backint/backint4MAXDB.out 2>>/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Process was started successfully.
    Backint for MaxDB has been started successfully.
    2007-06-26 21:35:44
    Waiting for end of the backup operation.
    2007-06-26 21:35:44 The backup tool is running.
    2007-06-26 21:35:44 The database is working on the request.
    2007-06-26 21:35:49 The backup tool is running.
    2007-06-26 21:35:49 The database is working on the request.
    2007-06-26 21:35:59 The backup tool is running.
    2007-06-26 21:35:59 The database is working on the request.
    2007-06-26 21:36:14 The backup tool is running.
    2007-06-26 21:36:14 The database is working on the request.
    2007-06-26 21:36:34 The backup tool is running.
    2007-06-26 21:36:34 The database is working on the request.
    2007-06-26 21:36:41 The backup tool process has finished work with return code 2.
    2007-06-26 21:36:41 The database has finished work on the request.
    Receiving a reply from the database kernel.
    Got the following reply from db-kernel:
    SQL-Code :-8020
    Date :20070626
    Time :00213542
    Database :BWA
    Server :s254176rg04
    KernelVersion :Kernel 7.6.00 Build 035-123-139-084
    PagesTransfered :131072
    PagesLeft :2847194
    MediaName :BWAPIPE
    Location :/backup/BWA/BWAPIPE
    Errortext :end of file
    Label :DAT_000000025
    IsConsistent :true
    FirstLogPageNo :1777329
    DBStamp1Date :20070626
    DBStamp1Time :00213541
    BDPageCount :2978242
    DevicesUsed :1
    DatabaseID :s254176rg04:BWA_20070605_123955
    Max Used Data Page
    Converter Page Count :1604
    The backup operation has ended.
    2007-06-26 21:36:41
    Filling reply buffer.
    Have encountered error -24920:
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Constructed the following reply:
    ERR
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    2007-06-26 21:36:41
    Cleaning up.
    Removing data transfer pipes.
    Removing data transfer pipe /backup/BWA/BWAPIPE ... Done.
    Removed data transfer pipes successfully.
    Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
    Reading parameter file /sapdb/data/wrk/BWA/backint/adapter.para.
    Using staging area /sapdb/BWA/backintstage/stage1 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage2 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage3 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage4 with a size of 1073741824 bytes.
    Using 2 file per Backint for Oracle call.
    Using /sapdb/BWA/db/bin/backint as Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/initBWA.utl as parameterfile of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/BackintHistory as history file.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.in as input of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.out as output of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.err as error output of Backint for Oracle.
    Reading input file /sapdb/data/wrk/BWA/backint/backint4MAXDB.in.
    Backing up pipe /backup/BWA/BWAPIPE.
    Found 1 entry in the input file.
    Starting the backup.
    Starting pipe2file program(s).
    Waiting for creation of temporary files.
    1 temporary file is available for backup.
    Calling Backint for Oracle at 2007-06-26 21:36:40.
    Calling '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/initBWA.utl -i /sapdb/data/wrk/BWA/backint/backint4Oracle.in -c' .
    Backint for Oracle ended at 2007-06-26 21:36:40 with return code 2.
    Backint for Oracle output: Reading parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl.
    Backint for Oracle output:
    Backint for Oracle output:
    Backint for Oracle error output: No staging area is defined in the parameter file.
    Backint for Oracle error output: The path of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the history file is not defined in the parameter file.
    Backint for Oracle error output: The name of the input file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the output file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the error output file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output:
    Finished the backup unsuccessfully.
    #ERROR /backup/BWA/BWAPIPE
    End of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
    Removed Backint for MaxDB's temporary output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
    Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
    Backint for Oracle was unsuccessful.
    End of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
    Removed Backint for MaxDB's temporary error output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Removed the Backint for MaxDB input file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
    Have finished clean up successfully.
    Please help
    Thanks
    Andy

    Hi Natalia
    Thanks for the reply. Below is initBWA.utl file. At this stage The first staging file is successfully written to the tape and the backup fails after that. The problem I guess is the staging file is not getting deleted or over written after it is written to the tape. Thanks   
    backint parameters
    switch_list: is required and is used as a control file to communicate with
    BACKINT and BRBACKUP for online backups.  A switch list file is created
    every time BRBACKUP wants to backup a file or when it wants to indicate that
    a backup is finished.  The switch_list parameter must be set to a file path
    that is located in: $ORACLE_HOME/sapbackup/.switch.lis.
    switch_list /sapdb/BWA/backintstage/.switch.lis
    switch_sem: is required and is used as a control file which is used between
    BACKINT and BRBACKUP to communicate.  After the switch list file has been
    created and closed, BACKINT creates the switch semaphore file and waits until
    it is deleted by BRBACKUP.  The switch_sem parameter must be set to a file
    path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.
    switch_sem /sapdb/BWA/backintstage/.switch.sem
    switch_log: is required and is used as a control file which is used between
    BACKINT and BRBACKUP to communicate.  After the switch semaphore file has
    been deleted, BACKINT opens and reads the switch log file to determine if
    the process is successful.  The switch log file is created by BRBACKUP.  The
    switch_log parameter must be set to a file path that is located in:
    $ORACLE_HOME/sapbackup/.switch_log.
    switch_log /sapdb/BWA/backintstage/.switch.log
    backint_dir: is an optional parameter and must be set to a directory that is
    public.  BACKINT uses this directory for work space and to store files called
    backint.times, which keeps track of backup information.
    #backint_dir /oracle/SAP/sapscript/backint_dir
    server: is an optional parameter and is the machine name of the NetBackup
    Master server.   The NetBackup Master server is the name of the machine that
    provides most of the administration and control for Netbackup operations and
    contains the NetBackup database.  If BACKINT finds a $SAP_SERVER environment
    variable, the server parameter's value will be overriden by the value of
    $SAP_SERVER.  Also, if the server parameter is not specified and there is no
    environment variable then the server parameter value will default to the
    SERVER option specified in the Netbackkup bp.conf file.
    #server jupiter
    client: is an optional parameter and must be set to a machine name that has
    the NetBackup client software, an Oracle database, and a SAP environment.
    In some cases the server and client machine will be the same machine.  If
    BACKINT finds a $SAP_CLIENT environment variable, the client parameter value
    will be overriden by the assigned environment variable.  If the client
    parameter is not specified and there is no environment variable, then the
    client parameter value will default to the CLIENT_NAME specified in the
    Netbackkup bp.conf file.  If the value is not in bp.conf, BACKINT uses the
    value returned by the gethostname() libary function.
    #client jupiter
    drives: is an optional parameter and should be set to the number of
    simultaneous tape drives to kickoff backup. Set NetBackup Server to support
    multiple simultaneous client backups and the number of storage units/tape
    drives for this backup policy.  Based on the number of drives specified
    BACKINT will simultaneously run the same number of bpbackup/bprestore
    commands.  So for example, if the drives parameter is set to 5, then 5
    bpbackup/bprestore jobs will run at the same time.  The drives parameter
    should be set to the following rule:
    drives = Number of storage units per policy  X  MPX number
    The drives parameter value should not exceed the Set Maxium Jobs per Client
    global attribute.  If BACKINT finds a $SAP_DRIVES environment variable, the
    drive parameter value will be overriden by the value of the $SAP_DRIVES
    variable.  If the drive parameter is not specified and there is no
    environment variable, then BACKINT will exit with an error.
    #drives 1
    policy: is an optionl parameter and should be set to the name of a SAP policy
    type that has been defined in Netbackup.  The SAP policy must have a schedule
    type of Application Backup defined in order for BACKINT to work.  If BACKINT finds
    a $SAP_POLICY environment variable, the policy parameter value will be
    overriden by the value of the $SAP_POLICY variable.  If the policy parameter
    is not specified and there is no environment variable, then the policy
    parameter value will default to the BPBACKUP_POLICY option in the NetBackup
    bp.conf file.  By default, BPBACKUP_POLICY is not in any bp.conf file, then
    NetBackup uses the first SAP policy type that it finds that has the client
    and a user-directed backup schedule.
    policy AXON2541766-SAP
    schedule: Is optional and must be set to the name of type  Application Backup
    schedule that is associates with a SAP policy type.  The schedule can
    define aspects of the backup such as how long Netbackup retains images,
    maximum MPX per drive, storage unit, and volume pool.  If BACKINT finds a
    $SAP_SCHED environment variable, the schedule parameter value will be
    overriden by the value of the $SAP_SCHED environment variable.  If the
    schedule parameter is not specified and there is no environment variable,
    then the schedule parameter value will default to the BPBACKUP_SCHED option
    in the NetBackup bp.conf file.  By default BPBACKUP_SCHED is not in any
    bp.conf file then, NetBackup uses the first schedule of type Application Backup
    that it finds. It is higly recommended to set schedule parameter in *.utl file.
    #schedule Default-Application-Backup
    policy2: is optional and is the name of a policy to be used for the
    secondary SAP backup.  The secondary backup is performed for each SAP
    database backup on files that are needed to track SAP backup information.
    This option would be used to save the backup information on a different
    media.  If policy2 is not specified, then the policy parameter value is used.
    #policy2 sap_sec_backup
    schedule2: is optional and is the name of a Application Backup schedule to be
    used for the secondary SAP  backup.  The secondary backup is performed for
    each SAP database backup on files that are needed to track SAP backup
    information.  This option would be used to save the backup information on a
    different media.  If schedule2 is not specified, then the schedule parameter
    value is used.
    #schedule2 userbkps
    sort_backup_type: [size | custom | device | drive ]
    This parameter is optional and is used to specify four different backup
    sort option.  If sort_backup_type is not specified it will default to
    the size option.
    #sort_backup_type size
    sort_backup_type: [image | custom | drive ]
    This parameter is optional and is used to specify three different restore
    sort option.  If sort_restore_type is not specified it will default to
    the image option.
    #sort_restore_type image
    custom_sort_file: is optional and is used in conjunction with the
    sort_backup_type and sort_restore_type parameter.  If the custom option is
    specified on either the sort_backup_type or sort_restore_type parameter,
    then the custom_sort_file parameter needs to be set to a valid file.  The
    value for this parameter must be a full path name to a custom sort file and
    must have public permissions.
    #custom_sort_file /oracle/SAP/sapscripts/custom_sort_file
    master_time_offset:  is an option parameter used to restore old backups
    if there was a time difference between the master and client machines.
    This option should only be used for restoring 3.0 or older backup or if a
    backint restore can't find a specified backup.  The master_time_offset is
    specified in minutes.  The value will be subtract from the start time and
    added to the end time for a restore or inquire.
    #master_time_offset 2
    #sleep: is optional and is used to specify a sleep time to monitor the
    bpbackup or bprestore logs.  The default is 5 seconds.  When BACKINT is
    called a number of bpbackup/bprestore commands can be running at the
    sametime.  BACKINT monitors each command and display the information to the
    -o parameter.  In some cases bpbackup/bprestore information is not displayed
    because of the monitoring cycle.  Therefore this option is used mainly for
    debug reasons.
    #sleep 5
    policy_log: is optional and is the name of a policy to be used for
    backing up a second copy of an archive log.  If this option is specified
    then two backups will be performed on the same archive log.  The first
    backup will go to the "policy" name option and the second backup will go
    to the "policy_log" name option.
    #policy_log sap_archive_logs
    sched_log: is optional and is the name of a schedule to create a second
    backing up of an archive log.  If this option is specified then two backup
    will be performed on the same archive log.  The first backup will go to the
    "schedule" option and the second backup will be go to the "sched_log" and
    option.  The "sched_log" name must be a valid schedule name under the
    "policy_log" name option, otherwise it must be a valid schedule name under
    the "policy" name option.
    #sched_log Default-Application-Backup
    retry_backup: is an optional parameter and should be set to the number of
    retries for a failed backup.  If this option is specified BACKINT will
    retry a failed bpbackup job.  The number of retries is determine by the
    value on the retry_backup parameter.
    #retry_backup 2
    fail_backup: is optional and is used to stop the backup process immediately
    when an error occurs.  The standard behavior of BACKINT is to continue
    processing even in the event of an error and then report what files failed
    and what files were successful.  If this parameter is specified then BACKINT
    will stop process on the first error and report failures for all the
    files that were not backed up.
    #fail_backup
    media_notify_script: is optional and is used to call a script when a
    "Waiting mount" is displayed in a bpbackup/bprestore log.  The value for this
    option must be the full path name to a script.  The script should also have
    the right file permissions and should be tested before implementation.  If
    the message is encountered and this optional is specified, then the
    following commands will be executed from BACKINT:
      MEDIA_ID=A001;export MEDIA_ID
      NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
      /oracle/SAP/sapscripts/sap_media_notify
    #media_notify_script /oracle/SAP/sapscripts/sap_media_notify
    restore_filter: is optional and is used to resolve linked file paths on a
    restore.  This parameter should be commented out and should be used only on
    rare occassions.  The following are the cases were this parameter is needed:
      1) Oracle table spaces use file paths
      2) The directory paths to the Oracle table spaces are linked paths
      3) The linked directory paths don't exist at restore time
    The value for this parmater must be a fully qualified file path name to a
    script, which has the right permissions and has been tested before being
    implemented.  The script must have an input and output parameter and be able
    to modify the contents of a text file which contains file paths.  The script
    is responsible for converting linked directory paths into absolute directory
    paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for
    an example.
    #restore_filter /oracle/SAP/sapscripts/restore_filter.sh
    bplist_filter: is optional and is used to resolve linked file passes on an
    inquire.  This parameter should be commented out and should be used only on
    rare occassions.  Like the restore_filter_script parameter this is needed
    for the following cases:
      1) Oracle table spaces use file paths
      2) The directory paths to the Oracle table spaces are linked paths
      3) The linked directory paths don't exist at restore time
    The value for this option must be a fully qualified path name to a script,
    which has the right file permission and has been tested before being
    implemented.  The script must have an input and output parameter and be able
    to modify the contents of a text file, which contains file paths.  The script
    is responsible for converting absolute directory paths into linked directory
    paths.  This is just the opposite of the restore filter script. See
    /usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example.

  • Backup MaxDB 7.7.06.09 to Veritas Netbackup 6.5 fails

    We want to backup MaxDB to Veritas Netbackup server.
    According documentation found about this topic the backup is configured
    by creating 3 files: bsi.env, initWDO.par (for backint for MaxDB) and
    initWDO.utl (for backint for Oracle). The contents of these files are shown below.
    When running the backup, it seems that backint for MaxDB ends with return code 2,
    the error message received is:
      -24920,ERR_BACKUPOP: backup operation was unsuccessful
      The backup tool failed with 2 as sum of exit codes.
    Unfortunately no further errors/warnings are shown that points in any direction
    what's going wrong here.
    We start the backup via the following dbmcli-command:
    dbmcli -u control,****** -d WDO -uUTL control,****** backup_start BACKData_WDO
    (for the time being without xuser entries, first make sure the backup is ok)
    The files dbm.ebl, dbm.prt and several others do not show any additional details/hints.
    It seems as if the "save data quick" to the named pipe is ok, the sql-code returns "0".
    After this the backint for MaxDB should read the named pipe and write it to stage-files,
    but backint (for MaxDB) ends with return code 2.
    Any idea what might go wrong here?
    With kind regards,
    R. Hoogeveen
    The Netherlands
    File bsi.env:
    =========
    BACKINT                /sapdb/WDO/db/bin/backint
    INPUT                  /tmp/backint4maxdb_WDO.in
    OUTPUT                 /tmp/backint4maxdb_WDO.out
    ERROROUTPUT            /tmp/backint4maxdb_WDO.err
    PARAMETERFILE          /sapdb/data/wrk/WDO/initWDO.par
    TIMEOUT_SUCCESS        600
    TIMEOUT_FAILURE        300
    ORIGINAL_RUNDIRECTORY  /sapdb/data/wrk/WDO
    File initWDO.par:
    =============
    STAGING AREA:                  /tmp/stageWDO 1 GB
    FILES PER BACKINT CALL:        1
    BACKINT:                       /usr/openv/netbackup/bin/backint
    PARAMETERFILE OF BACKINT:      /sapdb/data/wrk/WDO/initWDO.utl
    HISTORY FILE:                  /sapdb/data/wrk/WDO/backint_history_WDO.log
    INPUTFILE FOR BACKINT:         /tmp/backint4ora_WDO.in
    OUTPUTFILE FOR BACKINT:        /tmp/backint4ora_WDO.out
    ERRORFILE FOR BACKINT:         /tmp/backint4ora_WDO.err
    MAXIMAL DELAY OF BACKINT CALL: 30
    File initWDO.utl:
    =============
    switch_list /tmp/.switch_WDO.lis
    switch_sem /tmp/.switch_WDO.sem
    switch_log /tmp/.switch_WDO.log
    drives 1
    client wdocsz01
    server backfire
    policy sap_WDO

    Lars,
    The /tmp/backint4maxdb.err file tells me:
    Backint for Oracle was unsuccessful.
    (Unfortunately that was all information in this file.)
    The backint4ora.in file tells me:
    /tmp/stageWDO.0
    (looks ok to me, also at the time backint4ora was started the stage file was created with non-zero size)
    The backint4ora.out file tells me:
    ERROR: incorrect format or option in .utl file (-p)
    (this seems as if the -p option is not recognized by the backint4ora executable)
    When I run this executable manually as user sdb it shows me the commandline that I should use, including the -p option.
    One strange thing I notice is that the order of the options is different from the commandline that is executed.
    (in the usage it shows -p as almost last parameter, the command executed has -p in the middle; I will see if I can execute the backint4ora command manually, since I have the stage file available, I have copied it during the process)
    The backint4ora.err file is empty.
    The commandline of the dbmcli command I execute shows me another interesting error message,
    this might also be the source of all problems here.
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    Could not get external backup ID's from the backup tool.
    I tried to retrieve the external backup id's manually for medium BACKDataWDO, it show me OK without any external backup id's.
    I am not sure, but I think this is correct since no successfull backup was created yet with external backup tool.
    Can it also be that the parameter "history file" from the initWDO.par file is set wrong?
    Currently it is set to "/sapdb/data/wrk/WDO/backint_history_WDO.log" (see above also), but I can imagine
    that this should be set to the dbm.knl or dbm.ebf file ??
    With kind regards,
    Roger Hoogeveen

  • Configure MaxDB with Veritas Netbackup

    Hi team,
        When i configure Veritas Netbackup with MaxDB I have the following queries:
    1. should i create a staging file (will it get created automatically) ?
    2. Will all the log, error & History files get created automatically?
    3. Should i use PIPES only to take backup? can't i use FILE backup?
    please help
    Thanks in advance
    Regards,
    Pradeep Chandru.

    Hi,
      I have made the log files to be generated. Now i am getting the following error:
    dbm.prt
    2006-09-04 16:07:15 0x00002624 INF        283 DBMSrv   command backup_save "test01" DATA RECOVERY
    2006-09-04 16:08:22 0x00002624 ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x00002624 ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    2006-09-04 16:32:50 0x00002624 INF        226 DBMSrv   DBM Server client disconnect: PID 7012 on computer xxxxxxxx.local
    dbm.ebl
      2006-09-04 16:07:49 The database is working on the request.
        2006-09-04 16:08:09 The database is working on the request.
        2006-09-04 16:08:20 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
        2006-09-04 16:08:21 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
    The backup operation has ended.
    2006-09-04 16:08:21
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    Reply buffer filled.
    2006-09-04 16:08:22
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
    dbm.prt
    (established at 2006-09-04 15:31:14): PID 11028 on computer xxxxxxxx.local
    2006-09-04 15:31:14 0x000026f8 INF        283 DBMSrv   command backup_start BACKt09 DATA
    2006-09-04 15:32:20 0x000026f8 ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x000026f8 ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    2006-09-04 15:32:20 0x000026f8 INF        226 DBMSrv   DBM Server client disconnect: PID 11028 on computer xxxxxx.local
    2006-09-04 15:32:53 0x00001900 INF        216 DBMSrv   DBM Server client connection (established at 2006-09-04 15:32:53): PID 7308 on computer xxxxx.local
    2006-09-04 15:32:53 0x00001900 INF        283 DBMSrv   command backup_start BACKt09 DATA
    2006-09-04 15:33:58 0x00001900 ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x00001900 ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    2006-09-04 15:33:58 0x00001900 INF        226 DBMSrv   DBM Server client disconnect: PID 7308 on computer xxxxxx.local
    Incase any logs are required then please let me know.

  • MaxDB backup through Backint on Oracle for TSM

    Hello Gurus:
    We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    I checked some forums and configured but backint is not recognizing MaxDB parameter file. Please see below parameter file and error logs.
    *BSI File:*
    BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    INPUT D:\sapdb\data\wrk\backint\sapdb.in
    OUTPUT D:\sapdb\data\wrk\backint\sapdb.out
    ERROROUTPUT D:\sapdb\data\wrk\backint\sapdb.err
    PARAMETERFILE D:\sapdb\data\wrk\LCD\maxdb_config.par
    ORIGINAL_RUNDIRECTORY L:\sapdb\LCD\sapdata
    *Parameter File - MaxDB_config*
    STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    FILES PER BACKINT CALL:     2
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    PARAMETERFILE OF BACKINT:     D:\oracle\SCD\102\database\initSCD.utl
    HISTORY FILE:     D:\sapdb\data\wrk\BackintHistory
    INPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.in
    OUTPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.out
    ERRORFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.err
    MAXIMAL DELAY OF BACKINT CALL:     30
    Error Logs:
    2010-03-30 17:38:35
    Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2010-03-30 17:38:35
    Checking existence and configuration of Backint for MaxDB.
        Using environment variable 'BSI_ENV' with value 'D:\sapdb\data\wrk\LCD\bsi.env' as path of the configuration file of Backint for MaxDB.
        Reading the Backint for MaxDB configuration file 'D:\sapdb\data\wrk\LCD\bsi.env'.
            Found keyword 'BACKINT' with value 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe'.
            Found keyword 'INPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.in'.
            Found keyword 'OUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.out'.
            Found keyword 'ERROROUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.err'.
            Found keyword 'PARAMETERFILE' with value 'D:\sapdb\data\wrk\LCD\maxdb_config.par'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'L:\sapdb\LCD\sapdata'.
        Finished reading of the Backint for MaxDB configuration file.
        Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
        Using 'D:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\LCD\maxdb_config.par' as parameter file for Backint for MaxDB.
        Using '300' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using 'L:\sapdb\LCD\sapdata\dbm.knl' as backup history of a database to migrate.
        Using 'L:\sapdb\LCD\sapdata\dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2010-03-30 17:38:35
    Checking medium.
    Check passed successfully.
    2010-03-30 17:38:35
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c'.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
        Writing '
    .\pipe\BACKscd #PIPE' to the input file.
    Prepare passed successfully.
    2010-03-30 17:38:35
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '
    .\pipe\BACKscd' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Back123'' from db-kernel.
    The database is working on the request.
    2010-03-30 17:38:35
    Waiting until database has prepared the backup.
        Asking for state of database.
        2010-03-30 17:38:35 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2010-03-30 17:38:36 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2010-03-30 17:38:36
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c >>D:\sapdb\data\wrk\backint\sapdb.out 2>>D:\sapdb\data\wrk\backint\sapdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2010-03-30 17:38:36
    Waiting for end of the backup operation.
        2010-03-30 17:38:36 The backup tool process has finished work with return code 2.
        2010-03-30 17:38:36 The backup tool is not running.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:41 The database is working on the request.
        2010-03-30 17:38:51 The database is working on the request.
        2010-03-30 17:39:06 The database is working on the request.
        2010-03-30 17:39:26 The database is working on the request.
        2010-03-30 17:39:37 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
        2010-03-30 17:39:38 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
    The backup operation has ended.
    2010-03-30 17:39:38
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    Reply buffer filled.
    2010-03-30 17:39:38
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
        **-- Begin of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)--**
                                     **Data Protection for SAP(R)**
                         **Interface between BRTools and Tivoli Storage Manager***
                         **- Version 6, Release 1, Modification 0.0  for Win x64 -**
                               **Build: 358  compiled on Nov  4 2008**
                    **(c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.**
            **BKI8310E: The keyword MAXIMAL is not allowed.**
            **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
            **BKI0020I: End of program at: 03/30/10 17:38:36 .**
            **BKI0021I: Elapsed time: 00 sec .**
            **BKI0024I: Return code is: 2.**       
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
        Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    End of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
        Removed Backint for MaxDB's temporary error output file 'D:\sapdb\data\wrk\backint\sapdb.err'.
        Removed the Backint for MaxDB input file 'D:\sapdb\data\wrk\backint\sapdb.in'.
    Have finished clean up successfully.
    Any help will be appreciated.
    Thanks,
    Miral.

    > We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    > *BSI File:*
    >
    > BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    > *Parameter File - MaxDB_config*
    > STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    > FILES PER BACKINT CALL:     2
    > BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    >
    >     Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
    > 2010-03-30 17:39:38
    > Cleaning up.
    >     Copying output of Backint for MaxDB to this file.
    >                                  **Data Protection for SAP(R)**
    >                      **Interface between BRTools and Tivoli Storage Manager***
    >                      **- Version 6, Release 1, Modification 0.0  for Win x64 -**
    >         **BKI8310E: The keyword MAXIMAL is not allowed.**
    >         **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
    >         **BKI0020I: End of program at: 03/30/10 17:38:36 .**
    >         **BKI0021I: Elapsed time: 00 sec .**
    >         **BKI0024I: Return code is: 2.**       
    >
    >     -
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
    >     Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
    >     Copying error output of Backint for MaxDB to this file.
    >     -
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    @Markus: thanks for the hint with the quote-formatting option!
    Concerning the issue:
    Sorry, but you misunderstood the way how the general BACKINT for Oracle interface is used with MaxDB.
    See, MaxDB comes with a own BACKINT executable.
    This is a enhanced BACKINT tools that allows pipes as data input channels - which is not supported by the Backint for Oracle.
    The MaxDB Backint serves as a adapter program between the MaxDB Kernel and the backint for Oracle program.
    So instead of
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    you should point it to the MaxDB provided adapater program.
    I propose to revisit the documentation on that topic [Connecting to a Backint for Oracle Interface |http://maxdb.sap.com/doc/7_7/45/746a5712e14022e10000000a1553f6/content.htm].
    best regards,
    Lars

  • Error BACKINT for Oracle Connection

    hi @ maxdb gurus...
    i have a problem backing up my maxdb 7.6.0.033 (serving for a mysap.erp2005 on aix 5.3) using the backint mechanism.
    -> backup media created: two pipes and one parallel medium containing these pipes
    -> bsi.env has been created
    -> backint4sapdb.sar contains
       4 staging areas each with 4096 MB
       files per backint call 2
    -> maxdb is about 57 gb perm. data area (and 6 gb temp.)
    i use the backup wizard (dbmgui) to invoke a complete data backup which starts (pipes are created in the file system) and runs until approx. 4 gb...then the backup terminates with error "-24920 backup operation was unsuccesful. The database request failed with error -8020"
    what might be the problem? are the staging areas too small? is says that when using only one stage area it must hold the complete database...can i then conclude that 4 staging areas must hold the database as well - meaning they must be around 15 gb each?
    GreetZ, AH

    yup...but that also means that the sum of the staging areas need as much space as the database ie. around 70 gigs netto! the staging files will be filled and thus grow until the defined size, meaning that the file system(s) need to be big enough!
    everything works fine until the stage files are filled (up to the defined size) and then stops...when i change the sizes of the staging areas i can reproduce the error!
    i compared the tsm implementation of that system with another system (live cache...kind of small regarding db size...) and found nothing serious...
    -> dbm.ebp (AIX 5.3, MaxDB 7.6.0.033, ERP2005, TSM 5.3.3.0)
    2006-11-09 13:56:50
    Using environment variable 'TEMP' with value '' as directory for temporary files and pipes.
    Using environment variable 'TMP' with value '' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2006-11-09 13:56:50
    Checking existence and configuration of Backint for MaxDB.
        Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/TDV/bsi.env' as path of the configuration file of Backint for MaxDB.
        Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB from '/sapdba/data/wrk/TDV/bsi.env' to configuration value '/sapdb/data/wrk/TDV/bsi.env'.
        Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/TDV/bsi.env'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'BACKINT' with value '/sapdb/TDV/db/bin/backint'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'INPUT' with value '/sapdb/TDV/backup/backint4sapdb.in'.
            Found keyword 'OUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.out'.
            Found keyword 'ERROROUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.err'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/TDV/backint4sapdb.par'.
            Found keyword 'TIMEOUT_SUCCESS' with value '6000'.
            Found keyword 'TIMEOUT_FAILURE' with value '300'.
        Finished reading of the Backint for MaxDB configuration file.
        Using '/sapdb/TDV/db/bin/backint' as Backint for MaxDB program.
        Using '/sapdb/TDV/backup/backint4sapdb.in' as input file for Backint for MaxDB.
        Using '/sapdb/TDV/backup/backint4sapdb.out' as output file for Backint for MaxDB.
        Using '/sapdb/TDV/backup/backint4sapdb.err' as error output file for Backint for MaxDB.
        Using '/sapdb/data/wrk/TDV/backint4sapdb.par' as parameter file for Backint for MaxDB.
        Using '6000' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using '/sapdb/data/wrk/TDV/dbm.knl' as backup history of a database to migrate.
        Using '/sapdb/data/wrk/TDV/dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2006-11-09 13:56:50
    Checking medium.
    Check passed successfully.
    2006-11-09 13:56:50
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c'.
        Created temporary file '/sapdb/TDV/backup/backint4sapdb.out' as output for Backint for MaxDB.
        Created temporary file '/sapdb/TDV/backup/backint4sapdb.err' as error output for Backint for MaxDB.
        Writing '/sapdb/TDV/backup/back-tdv-data-m10.pipe #PIPE' to the input file.
        Writing '/sapdb/TDV/backup/back-tdv-data-m11.pipe #PIPE' to the input file.
    Prepare passed successfully.
    2006-11-09 13:56:51
    Creating pipes for data transfer.
        Creating pipe '/sapdb/TDV/backup/back-tdv-data-m10.pipe' ... Done.
        Creating pipe '/sapdb/TDV/backup/back-tdv-data-m11.pipe' ... Done.
    All data transfer pipes have been created.
    2006-11-09 13:56:51
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '/sapdb/TDV/backup/back-tdv-data-m10.pipe' PIPE,'/sapdb/TDV/backup/back-tdv-data-m11.pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACK-TDV-DATA-G1'' from db-kernel.
    The database is working on the request.
    2006-11-09 13:56:51
    Waiting until database has prepared the backup.
        Asking for state of database.
        2006-11-09 13:56:51 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2006-11-09 13:56:52 Database is still preparing the backup.
        Waiting 2 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:56:54 Database is still preparing the backup.
        Waiting 3 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:56:57 Database is still preparing the backup.
        Waiting 4 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:57:01 Database is still preparing the backup.
        Waiting 5 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:57:06 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2006-11-09 13:57:06
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c >>/sapdb/TDV/backup/backint4sapdb.out 2>>/sapdb/TDV/backup/backint4sapdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2006-11-09 13:57:06
    Waiting for end of the backup operation.
        2006-11-09 13:57:06 The backup tool is running.
        2006-11-09 13:57:06 The database is working on the request.
        2006-11-09 13:57:11 The backup tool is running.
        2006-11-09 13:57:11 The database is working on the request.
        2006-11-09 13:57:21 The backup tool is running.
        2006-11-09 13:57:21 The database is working on the request.
        2006-11-09 13:57:36 The backup tool is running.
        2006-11-09 13:57:36 The database is working on the request.
        2006-11-09 13:57:56 The backup tool is running.
        2006-11-09 13:57:56 The database is working on the request.
        2006-11-09 13:58:21 The backup tool is running.
        2006-11-09 13:58:21 The database is working on the request.
        2006-11-09 13:58:51 The backup tool is running.
        2006-11-09 13:58:51 The database is working on the request.
        2006-11-09 13:59:21 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-8020
            Date                  :20061109
            Time                  :00135703
            Database              :TDV
            Server                :r4335
            KernelVersion         :Kernel    7.6.00   Build 033-123-130-873
            PagesTransfered       :377688
            PagesLeft             :6903331
            MediaName             :BACK-TDV-DATA-G1
            Location              :/sapdb/TDV/backup/back-tdv-data-m10.pipe
            Errortext             :end of file
            Label                 :DAT_000000017
            IsConsistent          :true
            FirstLogPageNo        :247812
            DBStamp1Date          :20061109
            DBStamp1Time          :00135651
            BDPageCount           :7280971
            DevicesUsed           :2
            DatabaseID            :r4335:TDV_20061109_135703
            Max Used Data Page    :0
            Converter Page Count  :5201
        2006-11-09 13:59:21 The backup tool is running.
        2006-11-09 13:59:22 The backup tool process has finished work with return code 2.
        2006-11-09 13:59:22 The backup tool is not running.
    The backup operation has ended.
    2006-11-09 13:59:22
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    2006-11-09 13:59:22
    Cleaning up.
        Removing data transfer pipes.
            Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe ... Done.
            Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe ... Done.
        Removed data transfer pipes successfully.
        Copying output of Backint for MaxDB to this file.
        ---------- Begin of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
            Reading parameter file /sapdb/data/wrk/TDV/backint4sapdb.par.
            Using staging area /sapdb/TDV/backup/stage1 with a size of 1585446912 bytes.
            Using staging area /sapdb/TDV/backup/stage2 with a size of 1585446912 bytes.
            Using 1 file per Backint for Oracle call.
            Using /sapdb/TDV/dbs/backint as Backint for Oracle.
            Using /sapdb/TDV/dbs/initTDV.utl as parameterfile of Backint for Oracle.
            Using /sapdb/data/wrk/TDV/backint4oracle.his as history file.
            Using /sapdb/TDV/backup/backint4oracle.in as input of Backint for Oracle.
            Using /sapdb/TDV/backup/backint4oracle.out as output of Backint for Oracle.
            Using /sapdb/TDV/backup/backint4oracle.err as error output of Backint for Oracle.
            Using a maximal delay for a Backint for Oracle call of 60 seconds.
            Reading input file /sapdb/TDV/backup/backint4sapdb.in.
            Backing up pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe.
            Backing up pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe.
            Found 2 entries in the input file.
            Starting the backup.
            Starting pipe2file program(s).
            Waiting for creation of temporary files.
            1 temporary file is available for backup.
            Calling Backint for Oracle at 2006-11-09 13:59:20.
            Calling '/sapdb/TDV/dbs/backint -u TDV -f backup -t file -p /sapdb/TDV/dbs/initTDV.utl -i /sapdb/TDV/backup/backint4oracle.in -c' .
            Backint for Oracle ended at 2006-11-09 13:59:20 with return code 2.
            Backint for Oracle output:
            Backint for Oracle output:                          Data Protection for mySAP(R)
            Backint for Oracle output:
            Backint for Oracle output:              Interface between BR*Tools and Tivoli Storage Manager
            Backint for Oracle output:              - Version 5, Release 3, Modification 2.0  for AIX LF 64-bit -
            Backint for Oracle output:                    Build: 275  compiled on Nov 20 2005
            Backint for Oracle output:         (c) Copyright IBM Corporation, 1996, 2005, All Rights Reserved.
            Backint for Oracle output:
            Backint for Oracle output: BKI2027I: Using TSM-API version 5.3.3.0 (compiled with 5.3.0.0).
            Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
            Backint for Oracle output: BKI0005I: Start of program at: Thu Nov  9 13:59:20 MEZ 2006 .
            Backint for Oracle output: BKI5014E: Tivoli Storage Manager Error:
            Backint for Oracle output: ANS1035S (RC406)  Options file '*' could not be found.
            Backint for Oracle output:
            Backint for Oracle output: BKI0020I: End of program at: Thu Nov  9 13:59:20 MEZ 2006 .
            Backint for Oracle output: BKI0021I: Elapsed time: 00 sec .
            Backint for Oracle output: BKI0024I: Return code is: 2.
            Backint for Oracle output:
            Backint for Oracle error output:
            Finished the backup unsuccessfully.
            #ERROR /sapdb/TDV/backup/back-tdv-data-m10.pipe
            #ERROR /sapdb/TDV/backup/back-tdv-data-m11.pipe
        ---------- End of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
        Removed Backint for MaxDB's temporary output file '/sapdb/TDV/backup/backint4sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
        ---------- Begin of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
            Backint for Oracle was unsuccessful.
        ---------- End of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
        Removed Backint for MaxDB's temporary error output file '/sapdb/TDV/backup/backint4sapdb.err'.
        Removed the Backint for MaxDB input file '/sapdb/TDV/backup/backint4sapdb.in'.
    Have finished clean up successfully.
    i invoke the backup through dbmgui, not dbmcli!
    any clues? thx in advance!
    GreetZ, AH

  • Backint - MaxDB

    Hello all,
    we are trying to backup our MaxDB using the backint interface. Unfortunately, the backup process fails with the error messages shown in the appended KNLDIAG log and EXTERNAL BACKUP log
    KNLDIAG
    0:32:53 31276     11560 COMMUNIC Releasing  T132
    2008-07-31 20:32:53 31276     12827 COMMUNIC wait for connection T132
    2008-07-31 20:32:54 31258     11561 COMMUNIC Connecting T125 local 3626
    2008-07-31 20:32:54 31276     12929 TASKING  Task T125 started
    2008-07-31 20:32:54 31276     11007 COMMUNIC wait for connection T125
    2008-07-31 20:32:54 31276     11561 COMMUNIC Connected  T125 local 3626
    2008-07-31 20:32:54 31276     11560 COMMUNIC Releasing  T125
    2008-07-31 20:32:54 31276     12827 COMMUNIC wait for connection T125
    2008-07-31 20:32:55  3634 ERR 11000 devio    write error (fd = 54): Broken pipe
    2008-07-31 20:32:55 31272     11000 vasynclo '/tmp/backintdb-pipe' devno 34 T72
    2008-07-31 20:32:55 31259     12822 TASKING  Thread 3634 joining
    2008-07-31 20:32:55  3634     11566 stop     DEVi stopped
    2008-07-31 20:32:55 31272     52024 SAVE     63992 pages -> "/tmp/backintdb-pipe"
    2008-07-31 20:32:55 31276     52012 SAVE     new tape required 4300
    2008-07-31 20:32:55 31276         1 Backup   Backupmedium #1 (/tmp/backintdb-pipe) end of file
    2008-07-31 20:32:55 31276         6 KernelCo  +   Backup error occured, Errorcode 4300 "new_hostfile_required"
    2008-07-31 20:32:56 31276     12929 TASKING  Task T142 started
    2008-07-31 20:32:56 31258     11561 COMMUNIC Connecting T142 local 3626
    2008-07-31 20:32:56 31276     11007 COMMUNIC wait for connection T142
    2008-07-31 20:32:56 31276     11561 COMMUNIC Connected  T142 local 3626
    2008-07-31 20:32:56 31276     11560 COMMUNIC Releasing  T142
    2008-07-31 20:32:56 31276     12827 COMMUNIC wait for connection T142
    2008-07-31 20:36:23 31276     11000 vasynclo '/sapdata/SOM/DISKD0001' devno 17 T143
    2008-07-31 20:36:23 31259     12822 TASKING  Thread 3629 joining
    EXTERNAL BACKUP
    2008-07-31 20:32:36
    Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
    Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
    Using connection to Backint for MaxDB Interface.
    2008-07-31 20:32:36
    Checking existence and configuration of Backint for MaxDB.
        Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/SOM/bsi.env'.
            Found keyword 'BACKINT' with value '/sapdb/SOM/db/bin/backint'.
            Found keyword 'INPUT' with value '/tmp/tsm-logs/som-backint4maxdb.in'.
            Found keyword 'OUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.out'.
            Found keyword 'ERROROUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.err'.
            Found keyword 'PARAMETERFILE' with value '/sapdb/SOM/db/bin/backintmaxdbconfig.par'.
            Found keyword 'TIMEOUT_SUCCESS' with value '600'.
            Found keyword 'TIMEOUT_FAILURE' with value '300'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/SOM'.
        Finished reading of the Backint for MaxDB configuration file.
        Using '/sapdb/SOM/db/bin/backint' as Backint for MaxDB program.
        Using '/tmp/tsm-logs/som-backint4maxdb.in' as input file for Backint for MaxDB.
        Using '/tmp/tsm-logs/som-backint4maxdb.out' as output file for Backint for MaxDB.
        Using '/tmp/tsm-logs/som-backint4maxdb.err' as error output file for Backint for MaxDB.
        Using '/sapdb/SOM/db/bin/backintmaxdbconfig.par' as parameter file for Backint for MaxDB.
        Using '600' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using '/sapdb/data/wrk/SOM/dbm.knl' as backup history of a database to migrate.
        Using '/sapdb/data/wrk/SOM/dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2008-07-31 20:32:36
    Checking medium.
    Check passed successfully.
    2008-07-31 20:32:36
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call '/sapdb/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c'.
        Created temporary file '/tmp/tsm-logs/som-backint4maxdb.out' as output for Backint for MaxDB.
        Created temporary file '/tmp/tsm-logs/som-backint4maxdb.err' as error output for Backint for MaxDB.
        Writing '/tmp/backintdb-pipe #PIPE' to the input file.
    Prepare passed successfully.
    2008-07-31 20:32:36
    Creating pipes for data transfer.
        Creating pipe '/tmp/backintdb-pipe' ... Done.
    All data transfer pipes have been created.
    2008-07-31 20:32:36
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '/tmp/backintdb-pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'backindb'' from db-kernel.
    The database is working on the request.
    2008-07-31 20:32:36
    Waiting until database has prepared the backup.
        Asking for state of database.
        2008-07-31 20:32:36 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2008-07-31 20:32:37 Database is still preparing the backup.
        Waiting 2 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:39 Database is still preparing the backup.
        Waiting 3 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:42 Database is still preparing the backup.
        Waiting 4 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:46 Database is still preparing the backup.
        Waiting 5 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:51 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2008-07-31 20:32:51
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process '/sapdb/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c >>/tmp/tsm-logs/som-backint4maxdb.out 2>>/tmp/tsm-logs/som-backint4maxdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2008-07-31 20:32:51
    Waiting for end of the backup operation.
        2008-07-31 20:32:51 The backup tool is running.
        2008-07-31 20:32:51 The database is working on the request.
        2008-07-31 20:32:56 The backup tool process has finished work with return code 2.
        2008-07-31 20:32:56 The backup tool is not running.
        2008-07-31 20:32:56 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-8020
            Date                  :20080731
            Time                  :00203248
            Database              :SOM
            Server                :bssomp02
            KernelVersion         :Kernel    7.6.00   Build 035-123-139-084
            PagesTransfered       :64000
            PagesLeft             :4907326
            MediaName             :backindb
            Location              :/tmp/backintdb-pipe
            Errortext             :end of file
            Label                 :DAT_000000055
            IsConsistent          :true
            FirstLogPageNo        :3321207
            DBStamp1Date          :20080731
            DBStamp1Time          :00203244
            BDPageCount           :4971302
            DevicesUsed           :1
            DatabaseID            :bssomp02:SOM_20070910_162640
            Max Used Data Page   
            Converter Page Count  :2676
    The backup operation has ended.
    2008-07-31 20:32:56
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    It seem to me that it is a MUST to use the Tivoli Data Protection for the MaxDB. Is anybody out there to tell me if this is right? Or ist it possible to directly transfer backup data from MaxDB to Tivoli Storage Manager (TSM) via a pipe?
    Thanks and kind regards
    Anette Feierabend

    > 2008-07-31 20:32:55  3634 ERR 11000 devio    write error (fd = 54): Broken pipe
    > 2008-07-31 20:32:55 31272     11000 vasynclo '/tmp/backintdb-pipe' devno 34 T72
    > 2008-07-31 20:32:55 31259     12822 TASKING  Thread 3634 joining
    > 2008-07-31 20:32:55  3634     11566 stop     DEVi stopped
    > 2008-07-31 20:32:55 31272     52024 SAVE     63992 pages -> "/tmp/backintdb-pipe"
    > 2008-07-31 20:32:55 31276     52012 SAVE     new tape required 4300
    > 2008-07-31 20:32:55 31276         1 Backup   Backupmedium #1 (/tmp/backintdb-pipe) end of file
    > 2008-07-31 20:32:55 31276         6 KernelCo  +   Backup error occured, Errorcode 4300 "new_hostfile_required"
    >     Receiving a reply from the database kernel.
    >     Got the following reply from db-kernel:
    >         SQL-Code              :-8020
    >         KernelVersion         :Kernel    7.6.00   Build 035-123-139-084
    > PagesTransfered       :64000
    > PagesLeft             :4907326
    >         MediaName             :backindb
    >         Location              :/tmp/backintdb-pipe
    >         Errortext             :end of file
    >         Label                 :DAT_000000055
    >         IsConsistent          :true
    >         FirstLogPageNo        :3321207
    >         DBStamp1Date          :20080731
    >         DBStamp1Time          :00203244
    >         BDPageCount           :4971302
    >         DevicesUsed           :1
    >         DatabaseID            :bssomp02:SOM_20070910_162640
    >         Max Used Data Page   
    >         Converter Page Count  :2676
    > The backup operation has ended.
    >
    > 2008-07-31 20:32:56
    > Filling reply buffer.
    >     Have encountered error -24920:
    >         The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    >
    >     Constructed the following reply:
    >         ERR
    >         -24920,ERR_BACKUPOP: backup operation was unsuccessful
    >         The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    > Reply buffer filled.
    Hi Anette,
    it looks pretty much as if the backup medium definition for the MaxDB contains a maximum size. Thus the database will request a new medium once the setup maximum pages for the medium (64000 in your case) are reached.
    Error -8020 says exactly this: "Next medium needed"
    Therefore I would propose to check the backup medium.
    > It seem to me that it is a MUST to use the Tivoli Data Protection for the MaxDB. Is anybody out there to tell me if this is right? Or ist it possible to directly transfer backup data from MaxDB to Tivoli Storage Manager (TSM) via a pipe?
    No, that's wrong - once you setup the backup medium correctly it will work.
    Best regards,
    Lars
    p.s.
    If you're an SAP customer -> open a support message.
    And - of course - you're using a very old version of MaxDB. Get the current patch here in the SDN download area or via SAP Service Marketplace!

  • Backup using backint fails for maxdb

    Hi All, I have configured backint for backup of maxdb for content server 640. I configured it as per the documents available, created the configuration fiale and the parameter file. Created the backup medium in dbmgui. Now when i try to run the backup using the pipe am getting the above mentioned error. Please find below the dbm.ebp log for the same...
    more dbm.ebp 2009-10-22 02:06:08 Setting environment variable 'TEMP' for the directory for temporary files and pi pes to default ''. Setting environment variable 'TMP' for the directory for temporary files and pip es to default ''. Using connection to Backint for MaxDB Interface. 2009-10-22 02:06:08 Checking existence and configuration of Backint for MaxDB. Using configuration variable 'BSI_ENV' = '/sapdb/CFC/lcbackup/apoatlas.env' as path of the configuration file of Backint for MaxDB. Setting environment variable 'BSI_ENV' for the path of the configuration fil e of Backint for MaxDB to configuration value '/sapdb/CFC/lcbackup/apoatlas.env' . Reading the Backint for MaxDB configuration file '/sapdb/CFC/lcbackup/apoatl as.env'. Found keyword 'BACKINT' with value '/sapdb/CFC/db/bin/backint'. Found keyword 'INPUT' with value '/tmp/backint4sapdbCFC.in'. Found keyword 'OUTPUT' with value '/tmp/backint4sapdbCFC.out'. Found keyword 'ERROROUTPUT' with value '/tmp/backint4sapdbCFC.err'. Found keyword 'PARAMETERFILE' with value '/sapdb/CFC/lcbackup/param.cfg' . Found keyword 'TIMEOUT_SUCCESS' with value '1800'. Found keyword 'TIMEOUT_FAILURE' with value '1800'. Finished reading of the Backint for MaxDB configuration file. Using '/sapdb/CFC/db/bin/backint' as Backint for MaxDB program. Using '/tmp/backint4sapdbCFC.in' as input file for Backint for MaxDB. Using '/tmp/backint4sapdbCFC.out' as output file for Backint for MaxDB. Using '/tmp/backint4sapdbCFC.err' as error output file for Backint for MaxDB . Using '/sapdb/CFC/lcbackup/param.cfg' as parameter file for Backint for MaxD B. Using '1800' seconds as timeout for Backint for MaxDB in the case of success . Using '1800' seconds as timeout for Backint for MaxDB in the case of failure . Using '/sapdb/data/wrk/CFC/dbm.knl' as backup history of a database to migra te. Using '/sapdb/data/wrk/CFC/dbm.ebf' as external backup history of a database to migrate. Checking availability of backups using backint's inquire function. Check passed successful. 2009-10-22 02:06:08 Checking medium. Check passed successfully. 2009-10-22 02:06:08 Preparing backup. Setting environment variable 'BI_CALLER' to value 'DBMSRV'. Setting environment variable 'BI_REQUEST' to value 'NEW'. Setting environment variable 'BI_BACKUP' to value 'FULL'. Constructed Backint for MaxDB call '/sapdb/CFC/db/bin/backint -u CFC -f back up -t file -p /sapdb/CFC/lcbackup/param.cfg -i /tmp/backint4sapdbCFC.in -c'. Created temporary file '/tmp/backint4sapdbCFC.out' as output for Backint for MaxDB. Created temporary file '/tmp/backint4sapdbCFC.err' as error output for Backi nt for MaxDB. Writing '/sapdb/CFC/lcbackup/pipe1 #PIPE' to the input file. Writing '/sapdb/CFC/lcbackup/pipe2 #PIPE' to the input file. Prepare passed successfully. 2009-10-22 02:06:08 Creating pipes for data transfer. Creating pipe '/sapdb/CFC/lcbackup/pipe1' ... Done. Creating pipe '/sapdb/CFC/lcbackup/pipe2' ... Done. All data transfer pipes have been created. 2009-10-22 02:06:08 Starting database action for the backup. Requesting 'SAVE DATA QUICK TO '/sapdb/CFC/lcbackup/pipe1' PIPE,'/sapdb/CFC/ lcbackup/pipe2' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACKINT_ONLINE1'' from db-kernel. The database is working on the request. 2009-10-22 02:06:09 Waiting until database has prepared the backup. Asking for state of database. 2009-10-22 02:06:09 Database is still preparing the backup. Waiting 1 second ... Done. Asking for state of database. 2009-10-22 02:06:10 Database is still preparing the backup. Waiting 2 seconds ... Done. Asking for state of database. 2009-10-22 02:06:12 Database has finished preparation of the backup. The database has prepared the backup successfully. 2009-10-22 02:06:12 Starting Backint for MaxDB. Starting Backint for MaxDB process '/sapdb/CFC/db/bin/backint -u CFC -f back up -t file -p /sapdb/CFC/lcbackup/param.cfg -i /tmp/backint4sapdbCFC.in -c >>/tm p/backint4sapdbCFC.out 2>>/tmp/backint4sapdbCFC.err'. Process was started successfully. Backint for MaxDB has been started successfully. 2009-10-22 02:06:12 Waiting for end of the backup operation. 2009-10-22 02:06:12 The backup tool is running. 2009-10-22 02:06:12 The database is working on the request. 2009-10-22 02:06:14 The backup tool process has finished work with return co de 2. 2009-10-22 02:06:17 The database is working on the request. 2009-10-22 02:06:27 The database is working on the request. 2009-10-22 02:06:42 The database is working on the request. 2009-10-22 02:07:02 The database is working on the request. 2009-10-22 02:07:15 Canceling Utility-task after a timeout of 60 seconds ela psed ... OK. 2009-10-22 02:07:17 The database has finished work on the request. Receiving a reply from the database kernel. Got the following reply from db-kernel: SQL-Code :-903 The backup operation has ended. 2009-10-22 02:07:17 Filling reply buffer. Have encountered error -24920: The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903. Constructed the following reply: ERR -24920,ERR_BACKUPOP: backup operation was unsuccessful The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903. Reply buffer filled. 2009-10-22 02:07:17 Cleaning up. Removing data transfer pipes. Removing data transfer pipe /sapdb/CFC/lcbackup/pipe2 ... Done. Removing data transfer pipe /sapdb/CFC/lcbackup/pipe1 ... Done. Removed data transfer pipes successfully. Copying output of Backint for MaxDB to this file. -
    Begin of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- -
    Data Protection for mySAP(R) Interface between BR*Tools and Tivoli Storage Manager - Version 5, Release 4, Modification 0.0 for Linux x86_64 - Build: 303 compiled on Nov 16 2006 (c) Copyright IBM Corporation, 1996, 2006, All Rights Reserved. BKI0008E: The environment variable BI_CALLER is not set correctely. The current value is "DBMSRV" usage: backint -p  [-u ] [-f ] [-t ] [-i ] [-o ] [-c] where:  backint utility user  backup | restore | inquire | password | delete  file | file_online  parameter file for backup utility  name of a text file that defines the objects default: STDIN  Pool for processing messages and the results of the executed function. default: STOUT BKI0020I: End of program at: Thu 22 Oct 2009 02:06:14 AM EDT . BKI0021I: Elapsed time: 01 sec . BKI0024I: Return code is: 2. -
    End of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- - Removed Backint for MaxDB's temporary output file '/tmp/backint4sapdbCFC.out '. Copying error output of Backint for MaxDB to this file. - Begin of error output of Backint for MaxDB (/tmp/backint4sapdbCFC .err) - End of error output of Backint for MaxDB (/tmp/backint4sapdbCFC.e rr)--
    Removed Backint for MaxDB's temporary error output file '/tmp/backint4sapdbC FC.err'. Removed the Backint for MaxDB input file '/tmp/backint4sapdbCFC.in'. Have finished clean up successfully.
    Also, is there any specification about the user permissions and about how the backup should be run?

    Hi Lars,
    I understand that its a clumpsy over here, but i already have raised an OSS message and SAP said, that they cannot support this issue with backint. If you can provide me with an email id, i can send you the log files which would be easy to read.
    My issue is that am not able run backup for maxdb of content server 640 using the backint tool.
    I have created the configuration file and the parameter file as per the specifications from http://maxdb.sap.com/doc/7_7/a9/8a1ef21e4b402bb76ff75bb559a98a/content.htm and http://maxdb.sap.com/doc/7_7/50/075205962843f69b9ec41f34427be7/content.htm.
    THe server is registered to the TSM server. Now when i run the wizard to take the backup using the backint tool, it gives the error "Begin of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- -
    Data Protection for mySAP(R) Interface between BR*Tools and Tivoli Storage Manager - Version 5, Release 4, Modification 0.0 for Linux x86_64 - Build: 303 compiled on Nov 16 2006 (c) Copyright IBM Corporation, 1996, 2006, All Rights Reserved. BKI0008E: The environment variable BI_CALLER is not set correctely. The current value is "DBMSRV" usage: backint -p  [-u ] [-f ] [-t ] [-i ] [-o ] [-c] where:  backint utility user  backup | restore | inquire | password | delete  file | file_online  parameter file for backup utility  name of a text file that defines the objects default: STDIN  Pool for processing messages and the results of the executed function. default: STOUT BKI0020I: End of program at: Thu 22 Oct 2009 02:06:14 AM EDT . BKI0021I: Elapsed time: 01 sec . BKI0024I: Return code is: 2. -
    End of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- - Removed Backint for MaxDB's temporary output file '/tmp/backint4sapdbCFC.out '. Copying error output of Backint for MaxDB to this file. - Begin of error output of Backint for MaxDB (/tmp/backint4sapdbCFC .err) - End of error output of Backint for MaxDB (/tmp/backint4sapdbCFC.e rr)--
    Removed Backint for MaxDB's temporary error output file '/tmp/backint4sapdbC FC.err'. Removed the Backint for MaxDB input file '/tmp/backint4sapdbCFC.in'. Have finished clean up successfully."
    I think this should be fine to read...
    Krishna KK

  • How to install & confgiure Oracle9i on Veritas Cluster Server

    Hi,
    I want to know how to install oracle9i on Veritas Cluster Server having OS as Solaris 9. Also How to configure oracle in VCS so that it can be failover.
    I really appreciate the replies.
    Thanks,
    Shrikant

    I want to install following component
    Oracle 9i form server & report server
    Oracle HTTP Server in SSL mode
    Oracle As Web Cache
    Regards
    Arvind

  • SAP R/3 4.7 migration using Veritas PDC solution

    Hi,
    I would like to do a heterogeneous system copy.
    My current environment:-
    OS= IBM AIX
    DB=Oracle 9i
    DB size=6TB
    Storage= Veritas Storage foundation suite (Portable Data Container)
    Target system:-
    OS=HPUX
    DB=Oracle 9i
    DB size=6TB
    Storage= Veritas Storage foundation suite (Portable Data Container)
    Instead of using SAP tool (SAPINST,migmon, R3ta) to export/import the SAP system.
    Can I make use of the VERITAS -PDC solution? Whereby I will do a snapshot of the Oracle datafile.
    And then do some veritas pdc conversion to HPUX . And present the datafile to HPUX (target system).
    Is this supported by SAP? What is the impact if SAP say it is not supported method to do migration?
    I saw a document say it is not supported, but it is dated 2005.
    Thanks.
    Best Regards,
    CK chai
    Does anyone

    The first thing you should be aware of:
    If you do heterogeneous migrations you must have a certified migration consultant on-site, otherwise you loose support for problem occurring through the migration and for the target system (see http://service.sap.com/osdbmigration --> FAQ).
    The only "supported official" way is doing an R3load export and import.
    You can use other ways (e. g. also transportable tablespaces with Oracle 10g) but the responsibility of doing that is in the hand of the migration consultant.
    Markus

  • Getting backup using "backint for Oracle" to work

    Hi
    We are trying to get the backups to work on MaxDB 7.6 using the backint for Oracle interface.
    I have created an environment/config file and set the variable NSR_ENV.  The contents of this file is as follows:
    NSR_HOST           cmsapapp01.csenergy.com.au
    NSR_HOME           "C:\Program Files (x86)\Legato\nsr\bin"
    NSR_POOL           SAPData
    NSR_EXPIRE         year
    NSR_EBIDTYPE        NSAVETIME
    NSR_USEOUTPUT        SAVE
    I have created a backup media with the following options:
    Backup Type:  Full Backup
    Device Type:  PIPE
    Backup Tool:  NSR
    Device File:  c:\temp\file.pipe0
    When I run this, I get the following error:
    Begin of error output of NetWorker (C:\WINDOWS\TEMP\temp1204089773-1)----
            save: VSS Enabler is requested from NetWorker License Manager.
            save: c:\temp\file.pipe0: No such file or directory
    Am I doing something wrong...
    OS is Windows 2003.
    Thanks
    Doug

    Hello Doug,
    on Windows the pipe syntax is as follows:
    .\pipe\<pipename>
    HTH,
    Melanie

  • Veritas volume manager for solaris 10

    Hi All
    which version veritas volume manager will support solaris 10 06/06.
    can you just update a link for reference
    Regards
    RPS

    Hello,
    we are currently using solaris 9 with veritas volume manager 3.5.So i would like to know if i upgrade to solaris 10 06/06.whether i can use 3.5 or not.
    Using the Veritas (Symantec) support site, I have found the following document
    VERITAS Storage Solutions 3.5 Maintenance Pack 4 for Solaris
    http://seer.support.veritas.com/docs/278582.htm
    The latest supported version listed for VxVM 3.5 with MP4 applied is Solaris 9. That means the answer is NO.
    I understand that searching the Veritas knowledge base might be tough and time consuming, but it's their product ...
    Michael

  • Veritas volume manager on Solaris 10(X86)

    is it possible to install veritas volume manager on solaris 10 (x86) ?

    You should check the supported operating system matrix for Storage Foundation to see what they support. But yes, Solaris x64 is supported. I don't think they support 32-bit x86.
    Darren

  • What is Veritas HA, and How to verify that Veritas HA system is "lights on"

    Hi, Friends:
    I have two questions,
    1.What is Veritas HA?
    2.How to verify that Veritas HA system is "lights on"?
    thank you very much,
    Jerry

    Veritas HA = Veritas High Availability.
    http://www.google.com/search?q=veritas+HA&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

  • CSM with Veritas HA geographic redundancy fails over without visible reason

    Hello.
    Cisco Security Manager shuts down and Veritas fails it over to another site, I have no idea why. It is clean installation without elements.
    In Veritas engine log I found this:
    2013/02/06 12:52:22 VCS INFO V-16-2-13001 (KV-CSM-01-1) Resource(APP_CSManager): Output of the completed operation (monitor) 60012-202: The following process is not running     Process= NameServer     State  = Administrator has shut down this server     Pid    = 0     RC     = 143     Signo  = 0     Start  = 2/6/2013 12:35:58 PM     Stop   = 2/6/2013 12:52:05 PM     Core   = Not applicable     Info   = Server started by admin request
    Veritas CSM resource log:
    2013/02/06 12:52:22 VCS ERROR V-16-2-13067 Thread(3916) Agent is calling clean for resource(APP_CSManager) because the resource became OFFLINE unexpectedly, on its own.
    CSM syslog:
    Feb 06 12:52:08 127.0.0.1 100: <30>   dmgt[9004]: 3021(I):Died method called for process (NameServer, pid=9700).Feb 06 12:52:08 127.0.0.1 100: <30>   dmgt[9004]: 3021(I):Died method called for process (EDS, pid=8444).
    Eds.log is attached.
    NameServer.log is empty.
    As we can see from monitor.pl (csm agent script), EDS and NameServer are critical processes to run CSM.
    What I should do to prevent such behaviour?

Maybe you are looking for

  • Material loss in stock transfer

    Dear All can you please suggest how to compensate / adjust the material loss in stock transfer for 1) inter copany stock transfer 2) intra company stock transfer Regards Nil

  • Converting MS powerpoint files to pdf files with preservation of text so that it can be indexed

    I have a bunch of powerpoint presentation that I want to convert to pdf documents so that I can make them available over the web.  I have already done this, but it seems that there are a variety of formats that you can get depending upon on the conve

  • XI and Third party systems are on diff OS which affects File adapter

    Hello, I hav ea sceanrio where XI is on Unix and third party system is on Windows. We are using a file adapter to give data to third party.on third party system os level script reads this file. When ever XI is file adapter is writing file that time o

  • KDE + undo in joe editor

    Hi. I have recently switched to kde-unstable repo and am having a problem. New konsole (so yakuake as well) uses 'ctrl-shift-minus' to shrink the font size. This is also the shortcut for the joe editor to 'undo' changes (in text console it's simply C

  • Procure to pay process

    Dear all, Can somebody provide me detailed information about 1.Procure to pay process 2.Types of purchase orders 3.Types of payments So please respond as soon as possible Thanks in advance Varma