Veritas NetBackup using backint: error -8020 Reply buffer filled

[Former Member]

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

[former_member229109]

Hello Andy,

In your case a Configuration File for Backint for MaxDB :

configuration variable

'BSI_ENV' = '/sapdb/data/wrk/BWA/backint/config'

/sapdb/data/wrk/BWA/backint/config ::

BACKINT /sapdb/BWA/db/bin/backint

INPUT /sapdb/data/wrk/BWA/backint/backint4MAXDB.in

OUTPUT /sapdb/data/wrk/BWA/backint/backint4MAXDB.out

ERROROUTPUT /sapdb/data/wrk/BWA/backint/backint4MAXDB.err

PARAMETERFILE /sapdb/data/wrk/BWA/backint/adapter.para

TIMEOUT_SUCCESS 600

TIMEOUT_FAILURE 300

ORIGINAL_RUNDIRECTORY /sapdb/data/wrk/BWA

=>

Could you please update with settings in the file /sapdb/data/wrk/BWA/backint/adapter.para < Parameter File for the MaxDB Adapter Program >

It should have following settings:

STAGING AREA:

FILES PER BACKINT CALL:

BACKINT: < Backint for Oracle !!!! >

PARAMETERFILE OF BACKINT: < parameterfile of Backint for Oracle >

HISTORY FILE:

INPUTFILE FOR BACKINT:

OUTPUTFILE FOR BACKINT:

ERRORFILE FOR BACKINT:

MAXIMAL DELAY OF BACKINT CALL:

=> Please check where the Backint for Oracle is located.

****

Please review the documentation at

http://maxdb.sap.com/currentdoc/default.htm -> Basic Information

-> Concepts of the Database System -> Administration

-> Backing Up and Restoring -> Using Backup Tools from Other Providers

< -> Connecting to VERITAS NetBackup >

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Natalia

Thanks for the reply.

I have raised the staging file size to 10 GB from 1 GB and the backup is running i for much longer than it was yesturday. Is error 8020 related to staging file size? Do I really need that big disk space for staging. Please advice me If I need to set any other parameters.

PARAMETERS in initBWA.utl that are set is--->

switch_list /sapdb/BWA/backintstage/.switch.lis

switch_sem /sapdb/BWA/backintstage/.switch.sem

switch_log /sapdb/BWA/backintstage/.switch.log

-

---

>cat config

BACKINT /sapdb/BWA/db/bin/backint

INPUT /sapdb/data/wrk/BWA/backint/backint4MAXDB.in

OUTPUT /sapdb/data/wrk/BWA/backint/backint4MAXDB.out

ERROROUTPUT /sapdb/data/wrk/BWA/backint/backint4MAXDB.err

PARAMETERFILE /sapdb/data/wrk/BWA/backint/adapter.para

TIMEOUT_SUCCESS 600

TIMEOUT_FAILURE 300

ORIGINAL_RUNDIRECTORY /sapdb/data/wrk/BWA/

-

---

># cat adapter.para

STAGING AREA: /sapdb/BWA/backintstage/stage1 10 GB

STAGING AREA: /sapdb/BWA/backintstage/stage2 10 GB

STAGING AREA: /sapdb/BWA/backintstage/stage3 10 GB

STAGING AREA: /sapdb/BWA/backintstage/stage4 1 GB

FILES PER BACKINT CALL: 2

BACKINT: /sapdb/BWA/db/bin/backint

PARAMETERFILE OF BACKINT: /sapdb/data/wrk/BWA/backint/initBWA.utl

HISTORY FILE: /sapdb/data/wrk/BWA/backint/BackintHistory

INPUTFILE FOR BACKINT: /sapdb/data/wrk/BWA/backint/backint4Oracle.in

OUTPUTFILE FOR BACKINT: /sapdb/data/wrk/BWA/backint/backint4Oracle.out

ERRORFILE FOR BACKINT: /sapdb/data/wrk/BWA/backint/backint4Oracle.err

MAXIMAL DELAY OF BACKINT CALL: 30

-

---

># cat dbm.ebp

2007-06-27 10:07:29

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-27 10:07:30

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-27 10:07:30

Checking medium.

Check passed successfully.

2007-06-27 10:07:30

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-27 10:07:30

Creating pipes for data transfer.

Creating pipe '/backup/BWA/BWAPIPE' ... Done.

All data transfer pipes have been created.

2007-06-27 10:07:30

Starting database action for the backup.

Requesting 'SAVE DATA QUICK TO '/backup/BWA/BWAPIPE' PIPE COUNT 3932160 BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BWAPIPE'' from db-kernel.

The database is working on the request.

2007-06-27 10:07:30

Waiting until database has prepared the backup.

Asking for state of database.

2007-06-27 10:07:30 Database is still preparing the backup.

Waiting 1 second ... Done.

Asking for state of database.

2007-06-27 10:07:32 Database is still preparing the backup.

Waiting 2 seconds ... Done.

Asking for state of database.

2007-06-27 10:07:34 Database is still preparing the backup.

Waiting 3 seconds ... Done.

Asking for state of database.

2007-06-27 10:07:37 Database is still preparing the backup.

Waiting 4 seconds ... Done.

Asking for state of database.

2007-06-27 10:07:41 Database is still preparing the backup.

Waiting 5 seconds ... Done.

Asking for state of database.

2007-06-27 10:07:46 Database has finished preparation of the backup.

The database has prepared the backup successfully.

2007-06-27 10:07:46

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-27 10:07:46

Waiting for end of the backup operation.

2007-06-27 10:07:46 The backup tool is running.

2007-06-27 10:07:46 The database is working on the request.

2007-06-27 10:07:51 The backup tool is running.

2007-06-27 10:07:51 The database is working on the request.

2007-06-27 10:08:02 The backup tool is running.

2007-06-27 10:08:02 The database is working on the request.

2007-06-27 10:08:16 The backup tool is running.

2007-06-27 10:08:16 The database is working on the request.

2007-06-27 10:08:36 The backup tool is running.

2007-06-27 10:08:36 The database is working on the request.

2007-06-27 10:09:01 The backup tool is running.

2007-06-27 10:09:01 The database is working on the request.

2007-06-27 10:09:31 The backup tool is running.

2007-06-27 10:09:31 The database is working on the request.

2007-06-27 10:10:06 The backup tool is running.

2007-06-27 10:10:06 The database is working on the request.

2007-06-27 10:10:46 The backup tool is running.

2007-06-27 10:10:46 The database is working on the request.

2007-06-27 10:11:31 The backup tool is running.

2007-06-27 10:11:31 The database is working on the request.

2007-06-27 10:12:21 The backup tool is running.

2007-06-27 10:12:21 The database is working on the request.

2007-06-27 10:13:16 The backup tool is running.

2007-06-27 10:13:16 The database is working on the request.

2007-06-27 10:13:49 The backup tool process has finished work with return code 2.

2007-06-27 10:13:49 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 :20070627

Time :00100745

Database :BWA

Server :s254176rg04

KernelVersion :Kernel 7.6.00 Build 035-123-139-084

PagesTransfered :1310720

PagesLeft :1673988

MediaName :BWAPIPE

Location :/backup/BWA/BWAPIPE

Errortext :end of file

Label :DAT_000000031

IsConsistent :true

FirstLogPageNo :1812226

DBStamp1Date :20070627

DBStamp1Time :00100742

BDPageCount :2984684

DevicesUsed :1

DatabaseID :s254176rg04:BWA_20070605_123955

Max Used Data Page

Converter Page Count :1609

The backup operation has ended.

2007-06-27 10:13: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.

2007-06-27 10:13:56

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 10737418240 bytes.

Using staging area /sapdb/BWA/backintstage/stage2 with a size of 10737418240 bytes.

Using staging area /sapdb/BWA/backintstage/stage3 with a size of 10737418240 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.

Using a maximal delay for a Backint for Oracle call of 30 seconds.

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-27 10:13:48.

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-27 10:13:48 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 advice

Thanks

[former_member229109]

Hello Andy,

You could see that you failed to run the command :

Calling Backint for Oracle at 2007-06-27 10:13:48.

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' .

The MAXDB Backint tool /sapdb/BWA/db/bin/backint called with the Oracle parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl, where you didn't give the information about the staging area.

At that step you need to call the Oracle Backint tool.

***

Please check where the Backint for Oracle is located.

As I wrote you above Could you please update with settings in the file /sapdb/data/wrk/BWA/backint/adapter.para < Parameter File for the MaxDB Adapter Program >

BACKINT: < Backint for Oracle !!!! >

And you have :

BACKINT: /sapdb/BWA/db/bin/backint

/sapdb/BWA/db/bin/backint is MAXDB Backint.

***

I gave you above also the reference to the documentation, where the Examples/Definitions of the all values for the Parameters are given.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Natalia

Thanks for explaing me again. Now I got Backint for oracle installed and running the below command.

/usr/openv/netbackup/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

Now my backup hangs at 1GB which is size of staging file. I dont know how to define the staging file location in initBWA.utl. currently below variables are set.

switch_list /sapdb/BWA/backintstage/.switch.lis

switch_sem /sapdb/BWA/backintstage/.switch.sem

switch_log /sapdb/BWA/backintstage/.switch.log

Please advice.

Thank you

Andy

[former_member229109]

Hello Andy,

Could you please run the MAXDB backup & update with new dbm.ebp.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Natalia

following is the dbm.ebp

2007-06-28 05:57:45

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-28 05:57:46

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-28 05:57:46

Checking medium.

Check passed successfully.

2007-06-28 05:57:46

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 '/data01/BWAPIPE #PIPE' to the input file.

Prepare passed successfully.

2007-06-28 05:57:46

Creating pipes for data transfer.

Creating pipe '/data01/BWAPIPE' ... Done.

All data transfer pipes have been created.

2007-06-28 05:57:46

Starting database action for the backup.

Requesting 'SAVE DATA QUICK TO '/data01/BWAPIPE' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BWAPIPE'' from db-kernel.

The database is working on the request.

2007-06-28 05:57:46

Waiting until database has prepared the backup.

Asking for state of database.

2007-06-28 05:57:46 Database is still preparing the backup.

Waiting 1 second ... Done.

Asking for state of database.

2007-06-28 05:57:47 Database has finished preparation of the backup.

The database has prepared the backup successfully.

2007-06-28 05:57:47

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-28 05:57:47

Waiting for end of the backup operation.

2007-06-28 05:57:47 The backup tool is running.

2007-06-28 05:57:47 The database is working on the request.

2007-06-28 05:57:52 The backup tool is running.

2007-06-28 05:57:52 The database is working on the request.

2007-06-28 05:58:02 The backup tool is running.

2007-06-28 05:58:02 The database is working on the request.

2007-06-28 05:58:17 The backup tool is running.

2007-06-28 05:58:17 The database is working on the request.

2007-06-28 05:58:37 The backup tool is running.

2007-06-28 05:58:37 The database is working on the request.

2007-06-28 05:59:02 The backup tool is running.

2007-06-28 05:59:02 The database is working on the request.

2007-06-28 05:59:32 The backup tool is running.

2007-06-28 05:59:32 The database is working on the request.

2007-06-28 06:00:07 The backup tool is running.

2007-06-28 06:00:07 The database is working on the request.

2007-06-28 06:00:47 The backup tool is running.

2007-06-28 06:00:47 The database is working on the request.

2007-06-28 06:01:32 The backup tool is running.

2007-06-28 06:01:32 The database is working on the request.

2007-06-28 06:02:22 The backup tool is running.

2007-06-28 06:02:22 The database is working on the request.

2007-06-28 06:02: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 :20070628

Time :00055747

Database :BWA

Server :s254176rg04

KernelVersion :Kernel 7.6.00 Build 035-123-139-084

PagesTransfered :131072

PagesLeft :2856899

MediaName :BWAPIPE

Location :/data01/BWAPIPE

Errortext :end of file

Label :DAT_000000065

IsConsistent :true

FirstLogPageNo :1823920

DBStamp1Date :20070628

DBStamp1Time :00055746

BDPageCount :2987947

DevicesUsed :1

DatabaseID :s254176rg04:BWA_20070605_123955

Max Used Data Page

Converter Page Count :1609

2007-06-28 06:02:41 The backup tool is running.

2007-06-28 06:02:42 The backup tool process has finished work with return code 2.

2007-06-28 06:02:42 The backup tool is not running.

The backup operation has ended.

2007-06-28 06:02:42

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-28 06:02:42

Cleaning up.

Removing data transfer pipes.

Removing data transfer pipe /data01/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 /data01/backint/stage1 with a size of 1073741824 bytes.

Using staging area /data01/backint/stage2 with a size of 1073741824 bytes.

Using staging area /data01/backint/stage3 with a size of 1073741824 bytes.

Using staging area /data01/backint/stage4 with a size of 1073741824 bytes.

Using 2 file per Backint for Oracle call.

Using /usr/openv/netbackup/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.

Using a maximal delay for a Backint for Oracle call of 30 seconds.

Reading input file /sapdb/data/wrk/BWA/backint/backint4MAXDB.in.

Backing up pipe /data01/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-28 05:58:08.

Calling '/usr/openv/netbackup/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-28 06:02:41 with return code 2.

Backint for Oracle output: WARNING: drives value missing from parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl

Backint for Oracle output: default drives value = 1

Backint for Oracle output: WARNING: sort_backup_type not specified in .utl file

Backint for Oracle output: WARNING: default sort_backup_type to <size> for restore

Backint for Oracle output: ********************************************************************************

Backint for Oracle output: Program: /usr/openv/netbackup/bin/backint 5.1

Backint for Oracle output: Input File: /sapdb/data/wrk/BWA/backint/backint4Oracle.in

Backint for Oracle output: Profile: /sapdb/data/wrk/BWA/backint/initBWA.utl

Backint for Oracle output: Function: BACKUP

Backint for Oracle output: Backup Type: BACKUP_FILE

Backint for Oracle output: ********************************************************************************

Backint for Oracle output: [21433.00] Backup started 06/28/2007 05:58:11

Backint for Oracle output: [21433.00]

Backint for Oracle output: [21433.00] 05:58:11 Initiating backup

Backint for Oracle output: [21433.00] 05:58:25 INF - Processing /data01/backint/stage1.0

Backint for Oracle output: [21433.00] 05:58:25 INF - offline backup for datafile: /data01/backint/stage1.0

Backint for Oracle output: [21433.00] 05:58:25 /

Backint for Oracle output: [21433.00] 05:58:25 /data01/

Backint for Oracle output: [21433.00] 05:58:25 /data01/backint/

Backint for Oracle output: [21433.00] 05:58:49 INF - Beginning backup on server uk6nbumedia1-b of client S254176RG04.

Backint for Oracle output: [21433.00] 06:02:31 /data01/backint/stage1.0

Backint for Oracle output: [21433.00] 06:02:31 INF - Client completed sending data for backup

Backint for Oracle output: [21433.00]

Backint for Oracle output: [21433.00] 06:02:39 INF - Server status = 0

Backint for Oracle output: [21433.00] 06:02:40 INF - Backup by sdb on client s254176rg04: the requested operation was successfully completed.

Backint for Oracle output: [21433.00]

Backint for Oracle output: #ERROR /data01/backint/stage1.0

Backint for Oracle output: ********************************************************************************

Backint for Oracle output:

Backint for Oracle error output:

Finished the backup unsuccessfully.

#ERROR /data01/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.

[Former Member]

hello Andy Curtis. I'm the real Andy Curtis, how did get to use my userid? I even got the password changed yesterday so really don't understand how your using my Userid. Maybe you could reply to this thread, then I will get an email notification.

[Former Member]

I work for one of the SAP consulting firms in UK and the display name for its OSS login is yours. We might be working for the same company. I was trying to understand and fix the problem and didn't bother to change the display name. which part of UK do you work in?

[Former Member]

I still couldn't change the display name. I thought andy curtis is someone in the management but I cant see you on the employee list.

[former_member229109]

Hello...,

Let go to the backup database problem. And let's check your next issue ...

You got the 'error -8020 Reply buffer filled' due to the fact that the

Backint for the Oracle failed with the errors ::

"

...

Backint for Oracle ended at 2007-06-28 06:02:41 with return code 2.

Backint for Oracle output: WARNING: drives value missing from parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl

Backint for Oracle output: default drives value = 1

Backint for Oracle output: WARNING: sort_backup_type not specified in .utl file

Backint for Oracle output: WARNING: default sort_backup_type to <size> for restore

Backint for Oracle output: ********************************************************************************

Backint for Oracle output: Program: /usr/openv/netbackup/bin/backint 5.1

Backint for Oracle output: Input File: /sapdb/data/wrk/BWA/backint/backint4Oracle.in

Backint for Oracle output: Profile: /sapdb/data/wrk/BWA/backint/initBWA.utl

Backint for Oracle output: Function: BACKUP

Backint for Oracle output: Backup Type: BACKUP_FILE

Backint for Oracle output: ********************************************************************************

Backint for Oracle output: [21433.00] Backup started 06/28/2007 05:58:11

Backint for Oracle output: [21433.00]

Backint for Oracle output: [21433.00] 05:58:11 Initiating backup

Backint for Oracle output: [21433.00] 05:58:25 INF - Processing /data01/backint/stage1.0

Backint for Oracle output: [21433.00] 05:58:25 INF - offline backup for datafile: /data01/backint/stage1.0

Backint for Oracle output: [21433.00] 05:58:25 /

Backint for Oracle output: [21433.00] 05:58:25 /data01/

Backint for Oracle output: [21433.00] 05:58:25 /data01/backint/

Backint for Oracle output: [21433.00] 05:58:49 INF - Beginning backup on server uk6nbumedia1-b of client S254176RG04.

Backint for Oracle output: [21433.00] 06:02:31 /data01/backint/stage1.0

Backint for Oracle output: [21433.00] 06:02:31 INF - Client completed sending data for backup

Backint for Oracle output: [21433.00]

Backint for Oracle output: [21433.00] 06:02:39 INF - Server status = 0

Backint for Oracle output: [21433.00] 06:02:40 INF - Backup by sdb on client s254176rg04: the requested operation was successfully completed.

Backint for Oracle output: [21433.00]

Backint for Oracle output: #ERROR /data01/backint/stage1.0

Backint for Oracle output: ********************************************************************************

Backint for Oracle output:

Backint for Oracle error output:

Finished the backup unsuccessfully.

#ERROR /data01/BWAPIPE

"

=> Could you please post /sapdb/data/wrk/BWA/backint/initBWA.utl file.

Thank you and best regards, Natalia Khlopina

[Former Member]

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

1. backint parameters

#

1. switch_list: is required and is used as a control file to communicate with

2. BACKINT and BRBACKUP for online backups. A switch list file is created

3. every time BRBACKUP wants to backup a file or when it wants to indicate that

4. a backup is finished. The switch_list parameter must be set to a file path

5. that is located in: $ORACLE_HOME/sapbackup/.switch.lis.

#

switch_list /sapdb/BWA/backintstage/.switch.lis

#

#

1. switch_sem: is required and is used as a control file which is used between

2. BACKINT and BRBACKUP to communicate. After the switch list file has been

3. created and closed, BACKINT creates the switch semaphore file and waits until

4. it is deleted by BRBACKUP. The switch_sem parameter must be set to a file

5. path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.

#

switch_sem /sapdb/BWA/backintstage/.switch.sem

#

#

1. switch_log: is required and is used as a control file which is used between

2. BACKINT and BRBACKUP to communicate. After the switch semaphore file has

3. been deleted, BACKINT opens and reads the switch log file to determine if

4. the process is successful. The switch log file is created by BRBACKUP. The

5. switch_log parameter must be set to a file path that is located in:

6. $ORACLE_HOME/sapbackup/.switch_log.

#

switch_log /sapdb/BWA/backintstage/.switch.log

#

#

1. backint_dir: is an optional parameter and must be set to a directory that is

2. public. BACKINT uses this directory for work space and to store files called

3. backint.times, which keeps track of backup information.

#

#backint_dir /oracle/SAP/sapscript/backint_dir

#

#

1. server: is an optional parameter and is the machine name of the NetBackup

2. Master server. The NetBackup Master server is the name of the machine that

3. provides most of the administration and control for Netbackup operations and

4. contains the NetBackup database. If BACKINT finds a $SAP_SERVER environment

5. variable, the server parameter's value will be overriden by the value of

6. $SAP_SERVER. Also, if the server parameter is not specified and there is no

7. environment variable then the server parameter value will default to the

8. SERVER option specified in the Netbackkup bp.conf file.

#

#server jupiter

#

#

1. client: is an optional parameter and must be set to a machine name that has

2. the NetBackup client software, an Oracle database, and a SAP environment.

3. In some cases the server and client machine will be the same machine. If

4. BACKINT finds a $SAP_CLIENT environment variable, the client parameter value

5. will be overriden by the assigned environment variable. If the client

6. parameter is not specified and there is no environment variable, then the

7. client parameter value will default to the CLIENT_NAME specified in the

8. Netbackkup bp.conf file. If the value is not in bp.conf, BACKINT uses the

9. value returned by the gethostname() libary function.

#

#client jupiter

#

#

1. drives: is an optional parameter and should be set to the number of

2. simultaneous tape drives to kickoff backup. Set NetBackup Server to support

3. multiple simultaneous client backups and the number of storage units/tape

4. drives for this backup policy. Based on the number of drives specified

5. BACKINT will simultaneously run the same number of bpbackup/bprestore

6. commands. So for example, if the drives parameter is set to 5, then 5

7. bpbackup/bprestore jobs will run at the same time. The drives parameter

8. should be set to the following rule:

#

1. drives = Number of storage units per policy X MPX number

#

1. The drives parameter value should not exceed the Set Maxium Jobs per Client

2. global attribute. If BACKINT finds a $SAP_DRIVES environment variable, the

3. drive parameter value will be overriden by the value of the $SAP_DRIVES

4. variable. If the drive parameter is not specified and there is no

5. environment variable, then BACKINT will exit with an error.

#

#drives 1

#

#

1. policy: is an optionl parameter and should be set to the name of a SAP policy

2. type that has been defined in Netbackup. The SAP policy must have a schedule

3. type of Application Backup defined in order for BACKINT to work. If BACKINT finds

4. a $SAP_POLICY environment variable, the policy parameter value will be

5. overriden by the value of the $SAP_POLICY variable. If the policy parameter

6. is not specified and there is no environment variable, then the policy

7. parameter value will default to the BPBACKUP_POLICY option in the NetBackup

8. bp.conf file. By default, BPBACKUP_POLICY is not in any bp.conf file, then

9. NetBackup uses the first SAP policy type that it finds that has the client

10. and a user-directed backup schedule.

#

policy AXON2541766-SAP

#

#

1. schedule: Is optional and must be set to the name of type Application Backup

2. schedule that is associates with a SAP policy type. The schedule can

3. define aspects of the backup such as how long Netbackup retains images,

4. maximum MPX per drive, storage unit, and volume pool. If BACKINT finds a

5. $SAP_SCHED environment variable, the schedule parameter value will be

6. overriden by the value of the $SAP_SCHED environment variable. If the

7. schedule parameter is not specified and there is no environment variable,

8. then the schedule parameter value will default to the BPBACKUP_SCHED option

9. in the NetBackup bp.conf file. By default BPBACKUP_SCHED is not in any

10. bp.conf file then, NetBackup uses the first schedule of type Application Backup

11. that it finds. It is higly recommended to set schedule parameter in *.utl file.

#

#schedule Default-Application-Backup

#

#

1. policy2: is optional and is the name of a policy to be used for the

2. secondary SAP backup. The secondary backup is performed for each SAP

3. database backup on files that are needed to track SAP backup information.

4. This option would be used to save the backup information on a different

5. media. If policy2 is not specified, then the policy parameter value is used.

#

#policy2 sap_sec_backup

#

#

1. schedule2: is optional and is the name of a Application Backup schedule to be

2. used for the secondary SAP backup. The secondary backup is performed for

3. each SAP database backup on files that are needed to track SAP backup

4. information. This option would be used to save the backup information on a

5. different media. If schedule2 is not specified, then the schedule parameter

6. value is used.

#

#schedule2 userbkps

#

#

1. sort_backup_type: [size | custom | device | drive ]

2. This parameter is optional and is used to specify four different backup

3. sort option. If sort_backup_type is not specified it will default to

4. the size option.

#

#sort_backup_type size

#

1. sort_backup_type: [image | custom | drive ]

2. This parameter is optional and is used to specify three different restore

3. sort option. If sort_restore_type is not specified it will default to

4. the image option.

#

#sort_restore_type image

#

#

1. custom_sort_file: is optional and is used in conjunction with the

2. sort_backup_type and sort_restore_type parameter. If the custom option is

3. specified on either the sort_backup_type or sort_restore_type parameter,

4. then the custom_sort_file parameter needs to be set to a valid file. The

5. value for this parameter must be a full path name to a custom sort file and

6. must have public permissions.

#

#custom_sort_file /oracle/SAP/sapscripts/custom_sort_file

1. master_time_offset: is an option parameter used to restore old backups

2. if there was a time difference between the master and client machines.

3. This option should only be used for restoring 3.0 or older backup or if a

4. backint restore can't find a specified backup. The master_time_offset is

5. specified in minutes. The value will be subtract from the start time and

6. 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

1. bpbackup or bprestore logs. The default is 5 seconds. When BACKINT is

2. called a number of bpbackup/bprestore commands can be running at the

3. sametime. BACKINT monitors each command and display the information to the

4. -o parameter. In some cases bpbackup/bprestore information is not displayed

5. because of the monitoring cycle. Therefore this option is used mainly for

6. debug reasons.

#

#sleep 5

#

#

1. policy_log: is optional and is the name of a policy to be used for

2. backing up a second copy of an archive log. If this option is specified

3. then two backups will be performed on the same archive log. The first

4. backup will go to the "policy" name option and the second backup will go

5. to the "policy_log" name option.

#

#policy_log sap_archive_logs

#

#

1. sched_log: is optional and is the name of a schedule to create a second

2. backing up of an archive log. If this option is specified then two backup

3. will be performed on the same archive log. The first backup will go to the

4. "schedule" option and the second backup will be go to the "sched_log" and

5. option. The "sched_log" name must be a valid schedule name under the

6. "policy_log" name option, otherwise it must be a valid schedule name under

7. the "policy" name option.

#

#sched_log Default-Application-Backup

#

#

1. retry_backup: is an optional parameter and should be set to the number of

2. retries for a failed backup. If this option is specified BACKINT will

3. retry a failed bpbackup job. The number of retries is determine by the

4. value on the retry_backup parameter.

#

#retry_backup 2

#

#

1. fail_backup: is optional and is used to stop the backup process immediately

2. when an error occurs. The standard behavior of BACKINT is to continue

3. processing even in the event of an error and then report what files failed

4. and what files were successful. If this parameter is specified then BACKINT

5. will stop process on the first error and report failures for all the

6. files that were not backed up.

#

#fail_backup

#

#

1. media_notify_script: is optional and is used to call a script when a

2. "Waiting mount" is displayed in a bpbackup/bprestore log. The value for this

3. option must be the full path name to a script. The script should also have

4. the right file permissions and should be tested before implementation. If

5. the message is encountered and this optional is specified, then the

6. following commands will be executed from BACKINT:

7. MEDIA_ID=A001;export MEDIA_ID

8. NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER

9. /oracle/SAP/sapscripts/sap_media_notify

#

#media_notify_script /oracle/SAP/sapscripts/sap_media_notify

#

#

1. restore_filter: is optional and is used to resolve linked file paths on a

2. restore. This parameter should be commented out and should be used only on

3. rare occassions. The following are the cases were this parameter is needed:

4. 1) Oracle table spaces use file paths

5. 2) The directory paths to the Oracle table spaces are linked paths

6. 3) The linked directory paths don't exist at restore time

7. The value for this parmater must be a fully qualified file path name to a

8. script, which has the right permissions and has been tested before being

9. implemented. The script must have an input and output parameter and be able

10. to modify the contents of a text file which contains file paths. The script

11. is responsible for converting linked directory paths into absolute directory

12. paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for

13. an example.

#

#restore_filter /oracle/SAP/sapscripts/restore_filter.sh

#

#

1. bplist_filter: is optional and is used to resolve linked file passes on an

2. inquire. This parameter should be commented out and should be used only on

3. rare occassions. Like the restore_filter_script parameter this is needed

4. for the following cases:

5. 1) Oracle table spaces use file paths

6. 2) The directory paths to the Oracle table spaces are linked paths

7. 3) The linked directory paths don't exist at restore time

8. The value for this option must be a fully qualified path name to a script,

9. which has the right file permission and has been tested before being

10. implemented. The script must have an input and output parameter and be able

11. to modify the contents of a text file, which contains file paths. The script

12. is responsible for converting absolute directory paths into linked directory

13. paths. This is just the opposite of the restore filter script. See

14. /usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example.

[former_member229109]

Hello,

From dbm.ebp ::

"

2007-06-28 06:02: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 :20070628

Time :00055747

Database :BWA

Server :s254176rg04

KernelVersion :Kernel 7.6.00 Build 035-123-139-084

PagesTransfered :131072

PagesLeft :2856899

MediaName :BWAPIPE

Location :/data01/BWAPIPE

Errortext :end of file

Label :DAT_000000065

IsConsistent :true

FirstLogPageNo :1823920

DBStamp1Date :20070628

DBStamp1Time :00055746

BDPageCount :2987947

DevicesUsed :1

DatabaseID :s254176rg04:BWA_20070605_123955

Max Used Data Page

Converter Page Count :1609

"

==> PagesTransfered :131072 < 10 GB >

PagesLeft :2856899 < ~22 GB left >

1)

From the dbm.ebp::

"

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.

"

=> MEDIANAME 'BWAPIPE' is not 'a parallel medium', there are NO restrictions

for the medium size < OK >.

Please update the thread with additional information::

A) What is the Maximum number of backup devices could be used in parallel for backup/recovery in MAXDB:

dbmcli -d BWA -u control,control param_directget MAXBACKUPDEVS

B) To see the medium's definition please update with output of the following command::

dbmcli -d BWA -u control,control medium_getall

C) As I saw in dbm.ebp

for Oracle output: WARNING: drives value missing from parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl

==> What environment variables did you set & for which user, check

$SAP_DRIVES variable in the XSERVER protocol, if you are running

MAXDB backup using DBMGUI.

Did you export Environment Variables for the External Backup Tool using

dbm command 'dbm_configset'?

-> Please review the information about 'drives' parameter in initBWA.utl::

"# drives: is an optional parameter and should be set to the number of

1. simultaneous tape drives to kickoff backup. Set NetBackup Server to support

2. multiple simultaneous client backups and the number of storage units/tape

3. drives for this backup policy. Based on the number of drives specified

4. BACKINT will simultaneously run the same number of bpbackup/bprestore

5. commands. So for example, if the drives parameter is set to 5, then 5

6. bpbackup/bprestore jobs will run at the same time. The drives parameter

7. should be set to the following rule:

#

1. drives = Number of storage units per policy X MPX number

#

1. The drives parameter value should not exceed the Set Maxium Jobs per Client

2. global attribute. If BACKINT finds a $SAP_DRIVES environment variable, the

3. drive parameter value will be overriden by the value of the $SAP_DRIVES

4. variable. If the drive parameter is not specified and there is no

5. environment variable, then BACKINT will exit with an error.

"

&& drives parameter is NOT set in initBWA.utl ....

Please note that I cannot give you support for the backint for Oracle interface configuration as this is beyond of my field of expertise.

Please also contact vendor to check the configuration of the parameters in the initBWA.utl.

And in parameter file /sapdb/data/wrk/BWA/backint/adapter.para you set

to use 2 file per Backint for Oracle call.

2)

Could you please run the following test:

-> Please change the adapter.para for the stage area settings:

STAGING AREA: /sapdb/BWA/backintstage/stage1 32 GB

STAGING AREA: /sapdb/BWA/backintstage/stage2 10 GB

STAGING AREA: /sapdb/BWA/backintstage/stage3 10 GB

STAGING AREA: /sapdb/BWA/backintstage/stage4 10 GB

FILES PER BACKINT CALL: 1

BACKINT: /usr/openv/netbackup/bin/backint

PARAMETERFILE OF BACKINT: /sapdb/data/wrk/BWA/backint/initBWA.utl

HISTORY FILE: /sapdb/data/wrk/BWA/backint/BackintHistory

INPUTFILE FOR BACKINT: /sapdb/data/wrk/BWA/backint/backint4Oracle.in

OUTPUTFILE FOR BACKINT: /sapdb/data/wrk/BWA/backint/backint4Oracle.out

ERRORFILE FOR BACKINT: /sapdb/data/wrk/BWA/backint/backint4Oracle.err

MAXIMAL DELAY OF BACKINT CALL: 300

=> Run the MAXDB backup & if the backup failed, please post dbm.ebp file.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Natalia

Many thanks for all your help.

The issue is to do with netbackup version and someone else is looking at it.

Thanks

[former_member229109]

Hello ,

Please update this thread with the solution or let us know if you have additional questions on this issue.

Thank you and best regards, Natalia Khlopina

[roland_mallmann]

Hey there,

I think you actually might have several issues:

a) MaxDB backup medium used possibly has a fixed (file)size, as the backup on the MaxDB side stopped at exactly 1GB (with about 2GB left)

b) your BackInt for Oracle parameter file (/sapdb/data/wrk/BWA/backint/initBWA.utl) doesn't seem to be correctly setup, as the below messages show:

"

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.

"

Regards,

Roland

P.S.: -8020 means: "Next volume required"