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.

SAP Managed Tags:
SAP MaxDB

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Hi,

you should be able to find your answer here:

- SAP note 119863

- Official MaxDB / SAP DB documentation

- <a href="http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/276336.pdf#search=%22veritas%20maxdb%20database%20backup%20whitepaper%22">MaxDB Database Backup and Recovery White Paper (by Veritas)</a>

Hope that helps.

Regards,

Roland

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Roland,

Thanks for the quick response. I have gone through the documents before configuring Veritas Netbackup with MaxDB, but in the document, it says to have the configuration files with these variables as parameters but there is nothing told on if the files will get automatically created or I need to create it for myself.

I have tried it in both ways. I did not get any error in both the cases. But when I take a backup in tape device I get a file of 0 KB size where as the backup has been created in the local successfully.

From the document it says to refer the log in "dbm.ebp file, located

in the <install_path>\sdb\data\wrk\<database_name> directory" to look for errors, but the file is not created!!

Can you guess where the problem can be?

Regards,

N.Pradeep Chandru

Hi,

the staging files should be created automatically. In fact, they are recreated every time, therefor they should not exist before a backup.

Regarding your error: maybe you can find some more information regarding the current backup attempts in files knldiag, knldiag.err, dbm.prt and dbm.utl.

Which exact MaxDB or SAP DB version are you using?

Regards,

Roland

Hi,

1. I have run the backup by removing the satging file also.

2. Why is the file dbm.ebp not created?

3. why is the error and log files not created as specified in the bsi.env file? From the log files knldiag, knldiag.err, dbm,prt... i don' have any info on the errors generated. Where will the error generated by backint of maxdb and Veritas backint be there?

4. We are using Maxdb 7.6.00.12.

Regards,

N.Pradeep Chandru

Hi,

well, I admit that not receiving any errors in the MaxDB logfiles (knldiag, dbm.) and not having a dbm.ebp, is weird to say at the least.

In order to further analyze the issue, I urge you to open an official SAP message and open a WTS connection to the server in question. Without this and without anymore error information, it's neigh to impossible to help you solve the issue.

Regards,

Roland

Hi Roland,

How do I "open an official SAP message and open a WTS connection to the server" ? I am new to SAP so this question might be real a silly one.

Regards,

N.Pradeep Chandru.

Hi,

if you're an official SAP customer, then goto service.sap.com and then to the SAP Support Portal. There, you should be able to create a message (for queue BC-DB-SDB) and if you've created the message, setup a SAProuter and open the WTS connection to your system (as specified in SAP note 605795).

Regards,

Roland

Hi Roland,

thanks for your inputs.

Regards,

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

Hi, the part from the dbm.ebl which you did not show, possibly contains relevant information. So please show me the info that follows the following line in your dbm.ebl file:

2006-09-04 16:08:22

Cleaning up.

Copying output of Backint for MaxDB to this file.

...

Regards,

Roland

hi,

I am attaching the remaining part of the file

dbm.ebl

2006-09-04 16:08:22

Cleaning up.

Copying output of Backint for MaxDB to this file.

Begin of output of Backint for MaxDB (W:\backup\DB\backint_db.out)----

Reading parameter file U:\sapdb\sapdb\backint_parameter.txt.

Using C:\Program as Backint for Oracle.

Using C:\Program as parameterfile of Backint for Oracle.

Using C:\Program as history file.

Using C:\WINDOWS\Temp\backint.in as input of Backint for Oracle.

Using C:\WINDOWS\Temp\backint.out as output of Backint for Oracle.

Using C:\WINDOWS\Temp\backint.err as error output of Backint for Oracle.

Using staging area C:\WINDOWS\Temp\stage1 with a size of 104857600 bytes.

End of output of Backint for MaxDB (W:\backup\DB\backint_db.out)----

Removed Backint for MaxDB's temporary output file 'W:\backup\DB\backint_db.out'.

Copying error output of Backint for MaxDB to this file.

Begin of error output of Backint for MaxDB (W:\backup\DB\backint_db.err)----

Backint for Oracle must be a file.

End of error output of Backint for MaxDB (W:\backup\DB\backint_db.err)----

Removed Backint for MaxDB's temporary error output file 'W:\backup\DB\backint_db.err'.

Removed the Backint for MaxDB input file 'W:\backup\DB\backint_db.in'.

Have finished clean up successfully.

Regards,

N.Pradeep Chandru

Hi again,

the important error here is:

"Backint for Oracle must be a file."

This points to problems in the parameter file U:\sapdb\sapdb\backint_parameter.txt.

In that file, one specifies where several executables/files are located. If these locations contain spaces/blanks, they should get double quotes around them. In your case, I can see problems with:

Using C:\Program as Backint for Oracle.

Using C:\Program as parameterfile of Backint for Oracle.

Using C:\Program as history file.

Here, you would need to change the C:\Program with "C:\Program ...<rest of path>", then that problem should be solved.

Regards,

Roland

Ask a Question

Top Q&A Solution Author

User

Count