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
Similar Messages
-
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
DougHello Doug,
on Windows the pipe syntax is as follows:
.\pipe\<pipename>
HTH,
Melanie -
AppV 5 HF5 packages using /appve fail for regular users on Win 7
Hello,
I've been struggling with some App-V packages that fail to start on Win 7 machines provided trough Xendesktop.
All packages in question make use of locally installed Internet Explorer 9 and /appve switch :
"C:\Program Files (x86)\Internet Explorer\iexplore.exe" /appvve:D89030F5-436B-4A82-A104-A5E5E8089824_6C521CD6-5116-4587-B9E8-E386075F7A79
All other streamed apps can be started fine (the ones not using /appve switch)
If I run this package as a regular user I always get an error that "Internet Explorer has stopped working" and a error message in the application log:
Faulting application name: iexplore.exe, version: 9.0.8112.16599, time stamp: 0x5473964b
Faulting module name: AppVEntSubsystems32.dll, version: 5.0.3404.0, time stamp: 0x537e6b1f
Exception code: 0xc0000005
Fault offset: 0x00084444
Faulting process id: 0xecc
Faulting application start time: 0x01d0348e2b754fcb
Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: C:\Program Files\Microsoft Application Virtualization\Client\Subsystems\AppVEntSubsystems32.dll
Report Id: 6adc7087-a081-11e4-96bf-001dd8f22044
If I start the application on the same machine using a domain account user the app starts fine.
Internet explorer works fine for the regular users.
On a machine running Windows server 2008 R2 the same user can start the packages without any problems.
I've been looking at the permissions needed but can't seem to get to the end of this...
Has anyone seen the issue or has any clue what I can do?
Thanks!It looks like some others have had issues with the /appvve switch in Citrix environments too:
http://discussions.citrix.com/topic/348733-publishing-app-v-50-app-with-appvve-switch/
I wonder if you've approached Citrix about this? I would assume it's something about the way Citrix pass the command
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
rorymon.com Twitter: @Rorymon -
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 -
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
AndyHi 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. -
How lot take log backup using script in HANA
We have SAP HANA SPS09.
1) We are using script provided by SAP Note#1651055 to take the data backup.But it seems it is not taking log backup.HOw can we schedule logbackup ? or we have to use DBACOCKPIT or Studio only?
2) My DB is log_mode OVERWRITE.I have taken backup using script.But when I tried to check the backup using below command
hdbbackupdiag --check -f -d /mnt/resource/backup/xb8_bkp_19022015/ --logDirs /mnt/resource/logbackup/,/usr/sap/XB8/HDB00/backup/log
ERROR: [110081] Catalog backup log_backup_0_0_0_0 not found
goazr1app904d:/usr/sap/XB8/HDB00>
Is it like we have the DB in OVERWRITE mode thats why we are getting this error?Will my recovery work ?
Thanks,
MofizurDid your issue got resolved?
We are having same issue. We are on Rev 82 and using DD Boost EMC to take the backup using BACKINT.
Though we are on Rev 82 I tried option provided by Pavan which didn't worked for me.
hdbbackupdiag --check --useBackintForCatalog --backintDataParamFile /opt/ddbda/config/sap_hana_ddbda.utl -d /usr/sap/A0T/SYS/global/hdb/backint
ERROR: [110081] Catalog backup log_backup_0_0_0_0 not found
Regards,
Nitin -
ORA-00313: open failed for members during restore from COLD backup
Hi all,
I took a cold backup of an 11.1 database using RMAN (database in mount state).
I used the following command to restore it:
restored the controlfile and then
RESTORE DATABASE FROM TAG 'TAGxxxxxxxxxx';
Now I'm restoring it and it's taking too much time. When checking alert log it says:
ORA-51106: check failed to complete due to an error. See error below
ORA-48318: ADR Relation [HM_FINDING] of version=3 cannot be supported
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_02.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
RMAN is still in progress, why does it complain about redo?
I'm not doing recovery since it was a cold backup.
Thanks in advance.Hi Michael,
Yes, it's the correct one because it says "full restore complete":
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_01.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
Tue Apr 30 14:38:14 2013
Full restore complete of datafile 32 /oracle1/oradata/******/apr_sesm_index_01.dbf. Elapsed time: 1:25:42
checkpoint is 12652187135448
last deallocation scn is 12651877642745
Tue Apr 30 15:38:04 2013
Full restore complete of datafile 34 /oracle1/oradata/******/apr_stage_data_01.dbf. Elapsed time: 6:42:52
checkpoint is 12652187135448
last deallocation scn is 12651877637877
thanks, -
Backup Failed for last two days
Dear All,
We are getting Backup failed for last 2 days and it throws below error .
BR0280I BRBACKUP time stamp: 2011-12-09 19.27.17
BR0312E Database instance SRX shutdown during online backup
BR0252W Function remove() failed for 'X:\oracle\SRX\sapbackup\.behkdcyf.013' at location BrCleanup-6
BR0253W errno 13: Permission denied
BR0252W Function remove() failed for 'X:\oracle\SRX\sapbackup\.behkdcyf.014' at location BrCleanup-6
BR0253W errno 13: Permission denied
BR0115I Compression rate for all files 4.4881:1
BR0280I BRBACKUP time stamp: 2011-12-09 19.27.19
BR0301W SQL error -24909 at location BrDbDisconnect-1, SQL statement:
'/* BRBACKUP */ ALTER TABLESPACE "PSAPSR3DB" END BACKUP'
'COMMIT RELEASE'
ORA-24909: call in progress. Current operation cancelled
BR0327W Disconnect from database instance SRX failed
BR0280I BRBACKUP time stamp: 2011-12-09 19.29.45
BR0317I 'Alter tablespace PSAPSR3 end backup' successful
BR0280I BRBACKUP time stamp: 2011-12-09 19.30.19
BR0317I 'Alter tablespace PSAPSR3700 end backup' successful
BR0280I BRBACKUP time stamp: 2011-12-09 19.30.19
BR0301E SQL error -1142 at location BrBackAlter-3, SQL statement:
'/* BRBACKUP */ ALTER TABLESPACE "PSAPSR3DB" END BACKUP'
ORA-01142: cannot end online backup - none of the files are in backup
BR0280I BRBACKUP time stamp: 2011-12-09 19.30.19
BR0318E 'Alter tablespace PSAPSR3DB end backup' failed
BR0280I BRBACKUP time stamp: 2011-12-09 19.30.29
BR0317I 'Alter tablespace PSAPUNDO end backup' successful
BR0056I End of database backup: behkdcyf.and 2011-12-09 19.27.18
BR0280I BRBACKUP time stamp: 2011-12-09 19.30.34
BR0054I BRBACKUP terminated with errors
Note : I have checked till now SAP is not down (ST02 - Startup: 14.09.2011 13:18:46)
Kindly suggest to resolve the issue as well what was the reason behind ...
ThanksHi ,
Thanks for ur valuable reply ..
I have already checked Tablespace status in DB02old , all the Table space are ONLINE , NOT ACTIVE .
Tablespace Size (kb) Free (kb) Used (%) Tab/ind Extents AutoExt (kb) Used (%) Status Backup
PSAPSR3 35.538.944 5.400.960 84 51.141 70.617 55.320.576 54 ONLINE NOT ACTIVE
PSAPSR3700 21.008.384 1.131.648 94 916 6.730 27.164.672 73 ONLINE NOT ACTIVE
PSAPSR3DB 5.816.320 3.763.328 35 3.091 4.581 10.485.760 20 ONLINE NOT ACTIVE
PSAPSR3USR 20.480 20.032 2 6 6 2.097.152 0 ONLINE NOT ACTIVE
PSAPTEMP 901.120 900.096 0 0 0 2.097.152 0 ONLINE NOT ACTIVE
PSAPUNDO 7.740.352 6.877.824 11 19 726 Off 11 ONLINE NOT ACTIVE
PSAPYBMCD 901.120 678.144 24 302 798 2.097.152 11 ONLINE NOT ACTIVE
PSAPYBMCI 901.120 758.208 15 371 912 2.097.152 7 ONLINE NOT ACTIVE
SYSAUX 972.800 716.160 26 1.769 2.898 2.097.152 12 ONLINE NOT ACTIVE
SYSTEM 1.177.600 724.480 38 1.226 2.413 5.242.880 9 ONLINE NOT ACTIVE
Kindly advise .
Thanks -
DB13 SXPG_COMMAND_EXECUTE failed for backup reason
Dear Gurus,
I am facing error during DB13 since passed few days during backup and update statistics .SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: For More Information, See SYS
cancelled after system exception ERROR_MESSAGE..
Please do need full.
Thanks,
Regards,
Snehal PatelHi,
Do you have Standalone gateway on your server ?
You can try Go to the db13 -> goto -> backend configuration
And change background or application server to the database server (where DB physically resides)
If you Database is on another host then SAPXPG_DBDEST_<dbhost> or <virtual_dbhost> (a TCP/IP connection) will play an important role for executing SAPXPG command.
1) Install a Gateway instance on the DB server
2) Mention the Gateway hostname and service ( sapgwxx) in the RFC destination SAPXPG_DBDEST_<DBHOST> using SM59.
Also check the permission of the SAPXPG file.
SAP Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13 - Point 8 -
I patched 2012 to the SP1 level and now I'm getting these warnings on many servers.
It seems to be considering these items as removable media?
DPM 2012, SP1, version 4.1.3313.0
Failed to update permissions used for end-user recovery on skutter.pmuk.net. Permissions update failed for the following reason: (ID 3123)
Affected area: skutter.pmuk.net
Occurred since: 11/01/2013 09:04:43
Description: Failed to update permissions used for end-user recovery on skutter.pmuk.net. Permissions update failed for the following reason: (ID 3123)
DPM is unable to enumerate contents in 2aad3f75a7e54a0f91b640d7f158f00a , 5702fef3756e4ca8af0554013951f32d , 78f9e6070fbd43aeb328700a88a3c926 , aquaria.pmuk.net_MTATempStore$ , ariel.pmuk.net_MTATempStore$ , atlantis.pmuk.net_downloads , atlantis.pmuk.net_MTATempStore$
, atlantis.pmuk.net_print$ , capricorn.pmuk.net_MTATempStore$ , CCM.pmuk.net_IvrDirectory , CCM.pmuk.net_MTATempStore$ , CHIRON.pmuk.net_MTATempStore$ , cpeserv-i03.pmuk.net_IMAGING , defiant.pmuk.net_idsc , defiant.pmuk.net_MTATempStore$ ,firebird.pmuk.net_Accts_serve
, firebird.pmuk.net_case , firebird.pmuk.net_Control ,firebird.pmuk.net_Fuel Cell , firebird.pmuk.net_HADCAD , firebird.pmuk.net_haddesign , firebird.pmuk.net_hadendurancelab , firebird.pmuk.net_HADEngCad , firebird.pmuk.net_HADPCLGainspeed ,firebird.pmuk.net_HADPCLProjects
,firebird.pmuk.net_HADPCLQuality , firebird.pmuk.net_HADPCLStandards , firebird.pmuk.net_hrXerox , firebird.pmuk.net_hs , firebird.pmuk.net_ITXerox , firebird.pmuk.net_JunHigashimura , firebird.pmuk.net_MTATempStore$ ,firebird.pmuk.net_office ,firebird.pmuk.net_OMPM
, firebird.pmuk.net_Outplacement ,firebird.pmuk.net_personal , firebird.pmuk.net_PJSESCANNER ,firebird.pmuk.net_pmuk ,firebird.pmuk.net_pwa ,firebird.pmuk.net_pwa2 , firebird.pmuk.net_scanfret ,firebird.pmuk.net_Siebel8 ,firebird.pmuk.net_Spares
,firebird.pmuk.net_test ,firebird.pmuk.net_TVDC ,firebird.pmuk.net_xeroxcpe$ ,firebird.pmuk.net_xeroxrd$ , HALLEY.pmuk.net_MTATempStore$ ,legion.pmuk.net_dfs ,legion.pmuk.net_MTATempStore$ , legion.pmuk.net_NETLOGON ,legion.pmuk.net_SYSVOL
, nemesis.pmuk.net_KEvin ,nemesis.pmuk.net_MTATempStore$ , PLEIDES.pmuk.net_Archive , PLEIDES.pmuk.net_DGHOME , PLEIDES.pmuk.net_MTATempStore$ ,PLEIDES.pmuk.net_print$ , roosevelt.pmuk.net_ARCserve$ ,roosevelt.pmuk.net_CHEYALERT$ , roosevelt.pmuk.net_HADQCEOLP
,roosevelt.pmuk.net_home3 , roosevelt.pmuk.net_MTATempStore$ ,roosevelt.pmuk.net_smssource , roosevelt.pmuk.net_WindowsEasyTransfer ,roosevelt.pmuk.net_XeroxScan , sagittarius.pmuk.net_MTATempStore$ ,sagittarius.pmuk.net_print$ , sakura.pmuk.net_MTATempStore$
,scorpia.pmuk.net_MTATempStore$ ,scorpion.pmuk.net_chandleram, scorpion.pmuk.net_Control ,scorpion.pmuk.net_CPE ,scorpion.pmuk.net_Digital ,scorpion.pmuk.net_Electrical , scorpion.pmuk.net_MTATempStore$ , scorpion.pmuk.net_NASUtils ,scorpion.pmuk.net_Personal
,scorpion.pmuk.net_QA ,scorpion.pmuk.net_QC , scorpion.pmuk.net_Technical , silverberg.pmuk.net_dfs ,silverberg.pmuk.net_MTATempStore$ ,silverberg.pmuk.net_NETLOGON , silverberg.pmuk.net_SYSVOL ,skutter.pmuk.net_dfs , skutter.pmuk.net_MTATempStore$ ,skutter.pmuk.net_NETLOGON
,skutter.pmuk.net_sharepoint-saver ,skutter.pmuk.net_SYSVOL , tempest.pmuk.net_MTATempStore$ , tempest.pmuk.net_Quarantine ,tempest.pmuk.net_SiteBackups , tempest.pmuk.net_tsdp , titania.pmuk.net_MTATempStore$ , valiant.pmuk.net_domino , valiant.pmuk.net_hadprod
, valiant.pmuk.net_MTATempStore$ ,valiant.pmuk.net_oracle ,vindaloo.pmuk.net_MTATempStore$ , virgon.pmuk.net_faxclient ,virgon.pmuk.net_FxsSrvCp$ ,virgon.pmuk.net_MTATempStore$ , xavier.pmuk.net_Address ,xavier.pmuk.net_downloads ,xavier.pmuk.net_drivers ,
xavier.pmuk.net_Exchange IS Starter ,xavier.pmuk.net_ExchangeOAB , xavier.pmuk.net_ExchangeUM , xavier.pmuk.net_MTATempStore$ , xavier.pmuk.net_out-arch , xavier.pmuk.net_Resources$ on the protected computer tower.pmuk.net. Recycle Bin, System Volume Information
folder, non-NTFS volumes, DFS links, CDs, Quorum Disk (for cluster) and other removable media cannot be protected. (ID 38 Details: )
Any Ideas? backups are OK, recovery points/sync's etc.
Mark.I am using DPM 2012 R2, what finally worked to me to resolve my problem with EUR was to:
In DPM I disabled EUR
In Computer Management delete all DPM Shares (\\?\c:\Program Files\...)
Using ADSI edit go to CN=MS-ShareMapConfiguration,CN=System,DC=X,DC=Y (Replace X & Y for your domain)
Delete all of the mappings within the container
In DPM enable EUR
In DPM on a protection group I created a new recovery point and selected “Only synchronize (available only for file data)”
Related article on ADSI Edit and DPM -
http://social.technet.microsoft.com/Forums/en-US/e0258384-8422-408c-8839-2580d616a9ec/edsi-edit-related-to-data-protection-manager?forum=dpmfilebackup
I hope this helps
JD Young -
Failed to get exclusive lock on the Extensible Firmware Interface (EFI) system partition.
[ Name] Microsoft-Windows-Backup
[ Guid] {1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}
EventID 517
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2012-09-13T02:01:26.193377500Z
EventRecordID 134130
Correlation
- Execution
[ ProcessID] 13508
[ ThreadID] 552
Channel Application
Computer SERVER.srv.local
- Security
[ UserID] S-1-5-17
- EventData
BackupTime 2012-09-13T02:00:15.711673900Z
ErrorCode 2155348254
ErrorMessage %%2155348254Shaon,
I am receiving an identical error message as the original poster.
Let me give you some information on my setup and what I have already tried.
I am running a Windows Server 2008 R2 domain controller with SP1 installed. The system also runs MS SQL 2008 and IIS. All critical and recommended updates are installed.
The server backs up to a set of one of two external hard drives over USB 2.0 every night using Windows Backup. The external hard drives are encrypted using BitLocker and rotated offsite every week. We had no problems until 27 November 2013. On
that date I installed the November Windows updates and rebooted. Backups have not worked correctly since that time.
The server has two hard drives. The first one contains an 100 MB EFI partition (created for the IBM System x3200 M3 server EFI hardware although it appears to be entirely empty). The second partition contains the OS and the SQL databases. The
second hard drive contains shared data files. None of the partitions are close to being full.
The backup fails with the following error in the Windows Backup interface:
EFI System Partition: Windows Server Backup failed to get an exclusive lock on the EFI system partition. Detailed error: Access is denied.
The event viewer contains the error listed by the original poster (in the detailed view). The general view has this description:
The backup operation that started at <time> has failed with the following error code '2155348254' (Windows Backup failed to get an exclusive lock on the EFI system partition (ESP). This may happen if another application is using files on the
ESP. Please retry the operation.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
This error is thrown about 1 minute after the backup begins. After encountering the error with the EFI partition the backup exits and does not attempt to backup the other partitions.
The most interesting detail about the problem is that if I reboot the server and immediately perform a backup it completes successfully. If I reboot the server and wait approximately an hour before starting the backup it will fail. The backups
will continue to fail until the server is rebooted, at which point I if a backup is started immediately it will succeed but all future backups will fail. Therefore, it seems that Windows Backup has access to the EFI partition immediately after a reboot
but loses access for some reason close to the hour mark (this is an estimate based on a little experimentation but not an exact number).
Reading the little bit of information available online for this error message I have tried disabling our antivirus (Kaspersky) with no effect. I have also replaced the first hard drive in the server that contains the EFI partition with not effect (the
old hard drive imaged to the new hard drive with no errors, but backups still fail with the new hard drive). Backups fail with either external hard drive connected, so it is unlikely that the external hard drive is the problem. I have erased all
the Windows Backup settings including wiping all data on the external backup drive and created a new backup with no effect. I attempted to not backing up the EFI partition but it is required for the system state. I have reviewed all the Windows
updates installed in 27 November 2013 but none of the KB articles reference anything that I could possibly see related to the backup except for possibly the installation of .NET 4.5.1. However, I do not believe that Windows Backup uses .NET. 'Vssadmin
list writers' does not list any obvious errors.
At this point I am stymied except to think that I have some esoteric hardware failure. I have contacted IBM support who ran an extensive hardware diagnostic which showed no hardware issues.
I run several other similar Windows Server 2008 R2 systems, but none of them are on this model of hardware and none of them have an EFI partition. They all installed the same November Windows Updates. All of them are able to backup to external
hard drives without issue.
Any support you can provide would be greatly appreciated. -
How do I use Time Capsule for backup only over an existing network (or ethernet)
Ok, first, I have been using Mac now for about 2 years and every little thing I do is much harder than advertised. I have yet to experience the mythical ease of Apple products.
With that said, I was talked into buying this 2TB Time Capsule. Which right now seems to serve nicely as a very expensive paper weight.
Here's what I am trying to do. I was told I could use this as a wireless backup. I have a cable modem and router in my house. I do not want to insert Time Capsule as the router. I would like to either hook it up to the existing network or have it just wireless. Whatever works best for backup use.
I set the time capsule up to connect to an existing network. Which it did. Green light is on.
When I select it as a backup drive in Time Machine, it works. However it does not back up. It will say Waiting to Backup and do nothing. If I select Back Up Now on Time Machine, it says it cannot find the disk.
Is it possibly because I had used another backup disk prior and kept it? When I set the Time Capsule I selected to use both.
I am at a loss. I am not a techie. And there are more options of use than the instructions cover.The problem is your method of connection I suspect.
The TC was always designed to plug into the main router. It does not have to be in the same room but it has to be ethernet connected.
Please post a few screenshots of the setup.. that makes it so much easier for me to work through it with you.
Posting screenshots here is easy.. press the little camera and select the shot from finder.
What I need is the summary page from your airport utility.. ie this one.
Then click on edit button which I have highlighted and show me the tabs for Internet, Network and wireless. eg this is the internet. (show me the whole thing.. I have cut it off to keep it small).
We can then work through the issues. -
Use external drive for Time Capsule backups AND file storage?
I have an external drive formatted by my MBP. I'm using it to store my iTunes music library and iPhoto pics. Can I use the drive for Time Capsule backups as well?
Yes, but that is not recommended. Storage and backup should be kept separate to reduce the chances of a disk failure. This is especially important because you cannot even partition a Time Capsule drive. Go get a separate drive for your storage needs. Get another drive for a second backup and use a different method of backup than Time Machine
-
I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
Anyone have an idea on other things to try to debug/resolve this?
Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
Thanks!After a week's worth of debugging, I found the issue.
The Java type returned from the call was defined as ArrayList. Changing it to List resolved the problem.
I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid. And, why it works in Debug mode and not in Release build is even stranger. Maybe someone can shed some light on the logic here to me. -
Transaction failed for unknown reason (100) Unable to complete backup at this time. Does anyone know how to solve this issue?
Thanks.The system is set up to backup files to the iCloud at the end of the day. This has ot happen for sometime now and the mesaage I get is the back up error.
Maybe you are looking for
-
I keep trying to upgrade my iPad using iTunes..The error message "cannot attach to iTunes store...error message (-3212). Suggestions?
-
JS -- XML Question - Can I add attributes using Javascript?
I want to add an attribute to an element tag, but I don't see how to do it programmatically. Is it possible? Also, is there a way to name an element tag dynamically? For example: The way to add a child element is to either use the appendChild method
-
1 .How can i Anonymise the business partner data (names, bank accounts), for this some reports do exist how can i deal with this???any suggestiosn gurus??? 2.how to Transport customisation changes from 450 to 453 for example??? 3.how to compile
-
So i have this PC it has an MSI 890GXM-G65 the board was originally built for AM3 support but after reading a bit here and there.. with a bios flash it can support AM3+ CPUs.. so that is exactly what i did.. updated the BIOS and it ran fine.. so
-
My track pad keeps getting disconnected. Reconnecting works for only a short time. Disconnecting the batteries works for a longer time. What is going on?