Hi, I have got the information from VERITAS Netabckup support that MaxDB7.6 is not supported by them. Does any one have a working solution with MaxDB7.6 and Veritas Netabackup. I made the changes with "" but still getting some errors like .in and .out files getting locked and they are not getting released. Any idea on how to trouble shoot. Incase any log files are required, please let me know. Regards, N.Pradeep Chandru.
-----Original Message----- From: Heinrich, Tilo [mailto:[EMAIL PROTECTED] Sent: Thursday, September 07, 2006 4:10 PM To: Chandru, Pradeep; maxdb@lists.mysql.com Subject: RE: Configuring Backup with external Backint Hello Pradeep, Combining line "Using C:\Program as Backint for Oracle." with line "Backint for Oracle must be a file." I suggest to enclose paths with spaces into double quotes within file "U:\sapdb\sapdb\backint_parameter.txt". Best regards, Tilo Heinrich SAP Labs Berlin -----Original Message----- From: Chandru, Pradeep Sent: Donnerstag, 7. September 2006 11:35 To: Heinrich, Tilo; maxdb@lists.mysql.com Subject: RE: Configuring Backup with external Backint HI Tilo, I am attaching the dbm.ebl file: ------------------ Start of a new external backup tool action ------------------ 2006-09-04 16:07:16 Using environment variable 'TEMP' with value 'C:\DOCUME~1\NET~1.BAC\LOCALS~1\Temp\4' as directory for temporary files and pipes. Using connection to Backint for MaxDB Interface. 2006-09-04 16:07:16 Checking existence and configuration of Backint for MaxDB. Using configuration variable 'BSI_ENV' = 'U:\sapdb\sapdb\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 'U:\sapdb\data\wrk\VERITAS\bsi.env' to configuration value 'U:\sapdb\sapdb\bsi.env'. Reading the Backint for MaxDB configuration file 'U:\sapdb\sapdb\bsi.env'. Found keyword 'BACKINT' with value 'U:\sapdb\dsm\db\bin\backint.exe'. Found keyword 'INPUT' with value 'W:\backup\DB\backint_db.in'. Found keyword 'OUTPUT' with value 'W:\backup\DB\backint_db.out'. Found keyword 'ERROROUTPUT' with value 'W:\backup\DB\backint_db.err'. Found keyword 'PARAMETERFILE' with value 'U:\sapdb\sapdb\backint_parameter.txt'. Finished reading of the Backint for MaxDB configuration file. Using 'U:\sapdb\dsm\db\bin\backint.exe' as Backint for MaxDB program. Using 'W:\backup\DB\backint_db.in' as input file for Backint for MaxDB. Using 'W:\backup\DB\backint_db.out' as output file for Backint for MaxDB. Using 'W:\backup\DB\backint_db.err' as error output file for Backint for MaxDB. Using 'U:\sapdb\sapdb\backint_parameter.txt' 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 'u:\sapdb\data\wrk\VERITAS\dbm.knl' as backup history of a database to migrate. Using 'u:\sapdb\data\wrk\VERITAS\dbm.ebf' as external backup history of a database to migrate. Checking availability of backups using backint's inquire function. Check passed successful. 2006-09-04 16:07:17 Checking medium. Check passed successfully. 2006-09-04 16:07:17 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 'U:\sapdb\dsm\db\bin\backint.exe -u VERITAS -f backup -t file -p U:\sapdb\sapdb\backint_parameter.txt -i W:\backup\DB\backint_db.in -c'. Created temporary file 'W:\backup\DB\backint_db.out' as output for Backint for MaxDB. Created temporary file 'W:\backup\DB\backint_db.err' as error output for Backint for MaxDB. Writing '\\.\pipe\VERITAS #PIPE' to the input file. Prepare passed successfully. 2006-09-04 16:07:17 Starting database action for the backup. Requesting 'SAVE DATA QUICK TO '\\.\pipe\VERITAS' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'test01'' from db-kernel. The database is working on the request. 2006-09-04 16:07:17 Waiting until database has prepared the backup. Asking for state of database. 2006-09-04 16:07:17 Database is still preparing the backup. Waiting 1 second ... Done. Asking for state of database. 2006-09-04 16:07:18 Database has finished preparation of the backup. The database has prepared the backup successfully. 2006-09-04 16:07:18 Starting Backint for MaxDB. Starting Backint for MaxDB process 'U:\sapdb\dsm\db\bin\backint.exe -u VERITAS -f backup -t file -p U:\sapdb\sapdb\backint_parameter.txt -i W:\backup\DB\backint_db.in -c >>W:\backup\DB\backint_db.out 2>>W:\backup\DB\backint_db.err'. Process was started successfully. Backint for MaxDB has been started successfully. 2006-09-04 16:07:19 Waiting for end of the backup operation. 2006-09-04 16:07:19 The backup tool process has finished work with return code 2. 2006-09-04 16:07:19 The backup tool is not running. 2006-09-04 16:07:19 The database is working on the request. 2006-09-04 16:07:19 The database is working on the request. 2006-09-04 16:07:24 The database is working on the request. 2006-09-04 16:07:34 The database is working on the request. 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. ---------- 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. -----Original Message----- From: Heinrich, Tilo [mailto:[EMAIL PROTECTED] Sent: Thursday, September 07, 2006 2:18 PM To: maxdb@lists.mysql.com Subject: RE: Configuring Backup with external Backint Hello Pradeep, The interesting information should be found in dbm.ebl, right after the line "Copying output of Backint for MaxDB to this file." (the one one you copied to your mail). If this does not give you a clue for the problem, please send the dbm.ebl to the mailing list. Best regards, Tilo Heinrich SAP Labs Berlin -----Original Message----- From: Chandru, Pradeep Sent: Mittwoch, 6. September 2006 13:04 To: maxdb@lists.mysql.com Subject: Configuring Backup with external Backint Hi team, I am getting a error message when I configure netbackup with Backint. I am attaching the logs for the same. 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. Has any one come across the same? Thanks in advance. Regards, N.Pradeep Chandru, -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
