Sap daily backup error

hello experts,
in that sap the daily backup of sap production server due to error during initialization for the error.one hour before take os level nt backup.then next take the sap daily base back up.
profile :initmpc.sap
return code :0005 Error during processing
log file :begjqkde.aft
No action log for this action found in the database
Check the detail log
Regards,
A.Sithanandan

Hi,
Here is the solution for your issue.
Check the SAP Note : Note 17163 - BRARCHIVE/BRBACKUP messages and codes for further details.
BR0216W Wrong volume %s in device %s, should be %s
BR0216W Falscher Datentraeger %s in Geraet %s, sollte %s sein.
BR0216E Wrong volume %s in device %s, should be %s
BR0216E Falscher Datentraeger %s in Geraet %s, sollte %s sein.
Explanation: You inserted an incorrect volume in the backup device. The volume name was determined automatically. The program requires that you accept this proposal.
Program reaction: Waits for the user to insert the correct volume (BR0216W) or processing to terminate (BR0216E).
User action: Insert the correct volume and continue the operation or repeat the processing.
Regards,
Baskar.N

Similar Messages

Schedule Daily backup error

Dear all,
Here is the error message in daily backup log file:
===================================================================
Backup Set 302 25-SEP-08
Backup Piece 302 25-SEP-08 /u02/db/backup/RMAN/backup_UAT_666356697_324_1_a4jrfiup_1_1.bck
Controlfile Copy 2 18-AUG-08 /home/oracle/rsbackup/UAT/backup_control.ctl
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on default channel at 10/03/2008 11:15:23
ORA-19569: no device is allocated to this session
Recovery Manager complete.
=====================================================================
Anything wrong? How can I solve this?
Best Regards,
Amy

I get the following error message:
RMAN> Run
2> {
3> CONFIGURE CONTROLFILE AUTOBACKUP ON;
4> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
5> allocate channel ch1 type disk format '/u02/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
6> backup incremental level 1 cumulative database plus archivelog delete all input;
7> backup current controlfile;
8> backup spfile;
9> release channel ch1;
10> allocate channel for
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "for": expecting one of: "channel_id, double-quoted-string, identifier, single-quoted-string"
RMAN-01007: at line 10 column 18 file: daily_backup_db.rmn
-------------------- Here is the backup script -------------------------
Run
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 1 cumulative database plus archivelog delete all input;
backup current controlfile;
backup spfile;
release channel ch1;
allocate channel for maintenance type disk;
delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;
Please advice,
Amy

Sap transactional backup error

Hi Experts,
In Sybase database, I am able to take database backup but while taking the transactional backup it is showing error.
i followed process for Database backup is
step 1: isql -Usapsa -X -S<SID>
step 2: Password
step 3:dump database <SID> to "File name.dmp"
step 4:go ,enter
and for transactional backup,
step 1: isql -Usapsa -X -S<SID>
step 2: Password
step 3:dump tran <SID> to "File name.dmp"
step 4:go ,enter
i think it is correct but it is getting error ,please tell me what is the reason ,and how to solve.The error message is shown below image.
Thanks & Regards,
Patan Thavaheer.

Please reply me.

Sap offline daily backup

Hi Experts,
                     I am facing one problem.yesterday i take Full NT Backup at (OS LEVEL).it will be successfully completed. Then i start the production server .the sap is work in good condition. then start sap daily backup schedule.but donot take the backup .
Log File:   begktxad.aft
Return Code:   0005 Error during processing
Database Host:   mpc
   No action log for this action found in the database
   Check the detail log
Log Details :
BR0216E Wrong volume MPCB29 found in device /dev/nmt0, expected: MPCB05
BR0218E Checking label on volume in device /dev/nmt0 failed.
Please check the report and give the details.
Regards,
A.Sithanandan

Wrong volume MPCB29 found in device /dev/nmt0, expected: MPCB05
You are not using the right tape... as you can see the system is expecting a tape with a different label. You need to fix your tape rotation
Regards
Juan

SAP daily checking

hi all
I'm assigned by my boss to create SAP daily check (Critical section)
Need your suggestion what to check
I already put DB13, DB14, ST02, ST03
but I need in detail, for example.. on ST02 the program buffer should not > 10.000
My friend said I have to put the log file in OS system also, but I don't know what log and where is the path?
and what to check inside the log?
Also, my boss concern about free space, he told me to aware about the free space.
So, what filesystem should I check everyday? /oracle/SID/oraarch, /usr/sap/trans? and??
thanks in advance
regards,
Della

Hi Rosa,
Tcode sm12 used for lock management .With this you are able to determine which locks are being used currently.You can detect and correct problems by deleting locks that you no longer want. You can also later analyze the cause of lock table overflows using the History .
In tcode sm12 you can see which type the lock object is with the help of Lock mode.Where S: shared lock, E: exclusive lock, X: exclusive and not cumulative, O: optimistic lock. Again from Table name column you are able to know in which row of the table are locked.From Lock argument column you are able to see the argument (key field) of the lock entry.
Lock entry with Blue color means that the locks have already been transferred to the update task (see also The Owner Concept), with the result that the backup flag is set. These locks are also rewritten to the lock table when the enqueue server is restarted.Black means that the lock (still) belongs to the dialog owner. The backup flag is not set.By double-clicking a lock entry, you can display detailed information, including the host name and number of the SAP System in which the lock was generated.Rosa remember never delete a lock when you are unsure and/or don't know what is this lock for.If you delete a lock without proper justification may be it generate an inconsistence.Locks are put on table and / or table entries when a process needs exclusive access to this DB table and/or record. Removing this lock could let for example another process to change the same data while the process is still running thus generating inconsistence.
Always try to match a lock with a process in SM66, a background Job in SM37, a DB session, in ST04 / detailed analysis / sessions or a user logged in with AL08/SM04.
If you have identified from where does the lock come, then first try to kill the job, then the related process, then kick the user out (best would be to ask him what is he doing) and finally the DB session.
Usually one of this action will remove the lock cleanly.If it is not the case, deleting a lock in SM12 would be the very last option.
The ABAP Dumps will occur with respective of the problem.If you got the error. check the error name and serach in.
http://service.sap.com/notes.
Few of the most frequently occuring dumps are :
1) TIME_OUT : this happens due to longer dialog execution time for a user compared to the parameter settings. We can ask the user to run the report in batch jobs instead of dialog. we can ask the user to reduce the search criteria if he is using one.
2) RAISE_EXCEPTION : This is due to error in exception handling of the abap program. If its a customer report we can ask the developer to modify code or if its a sap report we can raise issue with sap
3) DBIF_SQL_ERROR: this happens due to various problems with database.
suppose user is trying to write duplicate entries to the tables then it occurs, if there is problem with the datafile then also it occurs. you have to read the details of the error.
4) TSV_NEW_PAGE_ALLOCATION_FAILED: Error due to not enough extended memory to run the report. This happens during high memory usage time, We can ask the user to run the report during less load and also to reduce the input criteria which will in turn reduce the processing memory required for the internal table.
or we need to increase the extended memory parameters.
5) MEMORY_NO_MORE_PAGING: happens due to not enough space in paging area. Can be solved by increasing the paging file parameter value.
6) LOAD_PROGRAM_ERROR: this error happens if during runtime any of the repository objects are changed by means of transport. We can ask the user to rerun the program.

Backup error occured, Error code 3700 "hostfile_error"

HI,
We are trying to MaxDB database backup to tape and getting below error.
===================================================================================================
ERR
-24988,ERR_SQL: SQL error
-104,DBM command impossible at this time
3,Data backup failed
Servertask Info: because Error in backup task occured
Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700
Error in backup task occured, Error code 3700 "hostfile_error"
Backupmedium #1 (
.\pipe\backup) I/O Error
Backup error occured, Error code 3700 "hostfile_error"
===================================================================================================
I went through the previous threads regarding the same error but couldn't find a solution.
System Info is Win 2008, MaxDB version 7.7.07.14.
Here is the complete log, please suggest what can be done.
===================================================================================================
DBA Action starts:
Timestamp: 20110831100408   Function: sda   Object: DATA
2011-08-31 10:04:08
Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.
2011-08-31 10:04:09
Checking existence and configuration of Backint for MaxDB.
    Using environment variable 'BSI_ENV' with value 'G:\sapdb\data\wrk\MXP\bsi.env' as path of the configuration file of Backint
    Reading the Backint for MaxDB configuration file 'G:\sapdb\data\wrk\MXP\bsi.env'.
        Found keyword 'BACKINT' with value 'D:\sapdb\MXP\db\bin\backint.exe'.
        Found keyword 'INPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.in'.
        Found keyword 'OUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.out'.
        Found keyword 'ERROROUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.err'.
        Found keyword 'PARAMETERFILE' with value 'G:\sapdb\data\wrk\MXP\maxdb_config.par'.
        Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'G:\sapdb\MXP\sapdata'.
    Finished reading of the Backint for MaxDB configuration file.
    Using 'D:\sapdb\MXP\db\bin\backint.exe' as Backint for MaxDB program.
    Using 'G:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
    Using 'G:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
    Using 'G:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
    Using 'G:\sapdb\data\wrk\MXP\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 'G:\sapdb\MXP\sapdata\dbm.knl' as backup history of a database to migrate.
    Using 'G:\sapdb\MXP\sapdata\dbm.ebf' as external backup history of a database to migrate.
    Checking availability of backups using backint's inquire function.
Check passed successful.
2011-08-31 10:04:09
Checking medium.
Check passed successfully.
2011-08-31 10:04:09
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:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_
    Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
    Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
    Writing '
.\pipe\backup #PIPE' to the input file.
Prepare passed successfully.
2011-08-31 10:04:09
Starting database action for
     the backup.
    Requesting 'SAVE DATA QUICK TO '
.\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BackupMXP'' from db-kernel.
The database is working on the request.
2011-08-31 10:04:09
Waiting until database has prepared the backup.
    Asking for state of database.
    2011-08-31 10:04:09 Database is still preparing the backup.
    Waiting 1 second ...
    Done.
    Asking for state of database.
    2011-08-31 10:04:10 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2011-08-31 10:04:10
Starting Backint for MaxDB.
    Starting Backint for MaxDB process 'D:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_
    Process was started successfully.
Backint for MaxDB has been started successfully.
2011-08-31 10:04:10
Waiting for end of the backup operation.
    2011-08-31 10:04:10 The backup tool is running.
    2011-08-31 10:04:10 The database is working on the request.
    2011-08-31 10:04:15 The backup tool is running.
    2011-08-31 10:04:15 The database is working on the request.
    2011-08-31 10:04:25 The backup tool is running.
    2011-08-31 10:04:25 The database is working on the request.
    2011-08-31 10:04:40 The backup tool is running.
    2011-08-31 10:04:40 The database is working on the request.
    2011-08-31 10:05:00 The backup tool is running.
    2011-08-31 10:05:00 The database is working on the request.
    2011-08-31 10:05:13 The backup tool process has finished work with return code 2.
    2011-08-31 10:05:13 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.
2011-08-31 10:05:13
Filling reply buffer.
    Have encountered error -24920:
        The backup tool failed with 2 as sum of exit codes. The database request failed 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 failed with error -903.
Reply buffer filled.
2011-08-31 10:05:13
Cleaning up.
    Copying output of Backint for MaxDB to this file.
Begin of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----
        Reading parameter file G:\sapdb\data\wrk\MXP\maxdb_config.par.
        Using staging area D:\TEMP\STAGE1 with a size of 1048576000 bytes.
        Using staging area D:\TEMP\STAGE2 with a size of 1048576000 bytes.
        Using 2 file per Backint for Oracle call.
        Using C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe as Backint for Oracle.
        Using G:\sapdb\data\wrk\MXP\initMXP.utl as parameterfile of Backint for Oracle.
        Using G:\sapdb\data\wrk\MXP\BackintHistory.txt as history file.
        Using G:\sapdb\data\wrk\backint\backint1.in as input of Backint for Oracle.
        Using G:\sapdb\data\wrk\backint\backint1.out as output of Backint for Oracle.
        Using G:\sapdb\data\wrk\backint\backint1.err as error output of Backint for Oracle.
        Using a maximal delay for a Backint for Oracle call of 3600 seconds.
        Reading input file G:\sapdb\data\wrk\backint\sapdb.in.
        Backing up pipe
.\pipe\backup.
        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 2011-08-31 10:05:12.
        Calling 'C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\initMXP.
        Backint for Oracle ended at 2011-08-31 10:05:13 with return code 2.
        Backint for Oracle output:
        Backint for Oracle output:                          Data Protection for SAP(R)
        Backint for Oracle output:
        Backint for Oracle output:              Interface between BR*Tools and Tivoli Storage Manager
        Backint for Oracle output:              - Version 6, Release 1, Modification 0.0 for Win x64 -
        Backint for Oracle output:                    Build: 358 compiled on Nov 4 2008
        Backint for Oracle output:         (c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.
        Backint for Oracle output:
        Backint for Oracle output: BKI2027I: Using TSM-API version 6.2.3.1 (compiled with 5.3.2.0).
        Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
        Backint for Oracle output: BKI0005I: Start of program at: 08/31/11 10:05:12 .
        Backint for Oracle output: BKI1216E: There are no backup management classes available.
        Backint for Oracle output: BKI1215I: Average transmission rate was 0.000 GB/h (0.000 MB/sec).
        Backint for Oracle output: BKI1227I: Average compression factor was 1.000.
        Backint for Oracle output: BKI0020I: End of program at: 08/31/11 10:05:13 .
        Backint for Oracle output: BKI0021I: Elapsed time: 01 sec .
        Backint for Oracle output: BKI0024I: Return code is: 2.
        Backint for Oracle output:
        Backint for Oracle error output:
        Finished the backup unsuccessfully.
        #ERROR
.\pipe\backup
End of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----
    Removed Backint for MaxDB's temporary output file 'G:\sapdb\data\wrk\backint\sapdb.out'.
    Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----
        Backint for Oracle was unsuccessful.
End of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----
    Removed Backint for MaxDB's temporary error output file 'G:\sapdb\data\wrk\backint\sapdb.err'.
    Removed the Backint for MaxDB input file 'G:\sapdb\data\wrk\backint\sapdb.in'.
Have finished clean up successfully.
SAVE/RESTORE request:
SAVE DATA CANCEL
SAVE/RESTORE request accepted:
OK
SAVE/RESTORE result:
ERR
-24988,ERR_SQL: SQL error
-104,DBM command impossible at this time
3,Data backup failed
Servertask Info: because Error in backup task occured
Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700
Error in backup task occured, Error code 3700 "hostfile_error"
Backupmedium #1 (
.\pipe\backup) I/O Error
Backup error occured, Error code 3700 "hostfile_error"
DBA Action ends:
Timestamp: 20110831100513   State:    Failure
===================================================================================================

Hi Markus,
Thanks for quick response. I did checked KNLMSG file and it has XML file kind of information where as dbm.prt has some information and here it is
=================================================================================================
2011-08-31 10:18:30 0x00009ecc INF          1 DBMSrvCo A DBM Server client connection was established at 2011-08-31 10:18:29 (client process has process ID 24352 on computer 10.1.47.21).
2011-08-31 10:18:30 0x00009ecc INF        283 DBMSrv   Command 'auto_extend show' is being executed.
2011-08-31 10:18:30 0x00009ecc INF        419 DBMSrv   Command 'auto_extend' has ended with return code 0.
2011-08-31 10:18:30 0x00009ecc INF        283 DBMSrv   Command 'auto_update_statistics show' is being executed.
2011-08-31 10:18:31 0x00009ecc INF        419 DBMSrv   Command 'auto_update_statistics' has ended with return code 0.
2011-08-31 10:18:41 0x00009ecc INF        283 DBMSrv   Command 'backup_save "Backup" DATA RECOVERY' is being executed.
2011-08-31 10:18:42 0x00009ecc INF          1 DBMKnl   Sending an administrative statement to the database
                    0x00009ecc INF          8 DBMKnl   Statement: SAVE DATA QUICK TO '
.\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'
2011-08-31 10:19:47 0x00009ecc ERR          3 DBMKnl   Received the result of an administrative statement from the database
                    0x00009ecc ERR          9 DBMKnl   Statement: SAVE DATA QUICK TO '
.\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'
                    0x00009ecc ERR         10 DBMKnl   Returncode: -903
                    0x00009ecc ERR          5 DBMKnl   Errortext: Host file I/O error
2011-08-31 10:19:47 0x00009ecc ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'backup_save' has ended and failed with return code -24920.
                    0x00009ecc ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                    0x00009ecc ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
2011-08-31 10:19:53 0x00009ecc INF          2 DBMSrvCo A DBM Server client connection was released (client process has process ID 24352 on computer 10.1.47.21).
2011-08-31 10:19:53 0x00009ecc INF          1 DBMKnl   Sending an administrative statement to the database
                    0x00009ecc INF          8 DBMKnl   Statement: SAVE DATA CANCEL
2011-08-31 10:19:53 0x00009ecc ERR          3 DBMKnl   Received the result of an administrative statement from the database
                    0x00009ecc ERR          9 DBMKnl   Statement: SAVE DATA CANCEL
                    0x00009ecc ERR         10 DBMKnl   Returncode: -104
                    0x00009ecc ERR          5 DBMKnl   Errortext: DBM command impossible at this time

Backup error after kernel patch upgrade

Hi.
I have a backup problem after the kernel patch upgrade. I have SAP R3 4.6C on HPUX11.0 with an Oracle 8.17 database.
I have upgraded kernel patch from 1655 to 2337.
Afterward, I am getting following backup error:
BR280I Time stamp 2007-11-06 09.29.01
BR279E Return code from '/usr/sap/HAD/SYS/exe/run/backint -u HAD -f backup -i /oracle/HAD/sapbackup/.bdwnpztp.lst -t file_online -c': 2
BR232E 0 of 115 files saved by backup utility
BR280I Time stamp 2007-11-06 09.29.01
BR231E Backup utility call failed
Does anyone know how to correct this?
Thank you.

Hi Jun,
backint is a link file that is in SAP kernel directory which links to the backup client on the server.
eg:
lrwxrwxrwx 1 root other 32 Aug 13 2004 backint -> /usr/openv/netbackup/bin/backint
As part of kernel upgrade process, the kernel is backed up, mostly on the disk before upgrading. Check if this link exists and recreate it in the kernel directory, if no backup was done, compare it with other systems to get the details of the backint link.
Cheers,
Nisch

SAP Binaries Backup online or offline

Hello!
I woulld like to know, how to execute the regular SAP OS backup and have the following questions regarding this issue:
1) How often should I backup the SAP-Binaries-partition \usr\sap\...?
(daily, weekly, 1 times month)
2) Should the DB, SAP R/3 or some Services be stopped for this issue?
Do exist some file-locks avoiding offline backup of \usr\sap\... ?
3) What should be backuped from \usr\sap\...?
(trans, profiles)
Thank you very much!
regards
Thom

Hi Thom,
1). It's totally depend's on your system avilability(because you need to make the system offline), rest may be you can take OS level backup once in a month(standard practice with all the data centers).
2). Yes you better stop DB services and SAPOSCOL.
3). You can backup total dir structure and you better create one Emergency Repair Disk(ERD) in case of windows.
Regards,
Hari.
PS: Awarding points will get you some points.

Require backup script which deletes the daily backups after weekly backup

Hi,
I am new to Oracle administration. I require a backup script which will delete the daily backups (incremental) after weekly backup is taken (full database backup).
Currently I use Oracle 10g for one of my production server.
My backup strategy is given below.
I would like to take full database backup weekly(online). To be precise, on Saturday.
I need to have daily incremental backup and they should get deleted on Saturday after the weekly full database backup is taken.
Also I would like to keep 4 weeks full backups. After that one by one we need to delete the backup.
For example, if I have 4 weeks fullbackup of February, after taking full backup for first week of March, the backup of first week of February should get deleted.
Kindly help with your suggestions.
Thanks & Regards,
Rafnas

Hi,
Thank you for pointing to the blog. It was very much useful.
I was testing the backup strategy using your script. It worked fine for first set of daily backups.
After weekly backup is taken, the daily backup script fails for taking the backup from next day onwards.
It gives the following error stack.
Starting backup at 05-MAR-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/05/2009 01:47:55
ORA-01455: converting column overflows integer datatype
Could you please let me know why integer datatype comes into picture while taking backup?
Please advice.
Thanks & Regards,
Rafnas
Edited by: user10698483 on Mar 5, 2009 3:38 AM

PRD online backup error

hi all, can anyone help me regarding backup error on prd server. Following error log generated after unsucessfull backup.
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18                                                                                BR0203I to I:\PRDBACKUP\bdyuaxcq\SR3700.DATA18.Z ...                                                                                BR0280I BRBACKUP time stamp: 2008-09-10 22.41.12                                                                                BR0266E Program 'D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\mkszip -c D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18 > I:\PRDBACKUP\bdyuaxcq\SR3700.DATA18.Z' interrupted, exit status: c0000094
BR0272E Execution of program 'D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\mkszip -c D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18 > PRDBACKUP\bdyuaxcq\SR3700.DATA18.Z' through pipe                                                                    BR0224E Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18 to I:\PRDBACKUP\bdyuaxcq\SR3700.DATA18.Z failed due to previous errors
BR0280I BRBACKUP time stamp: 2008-09-                                                                        BR0317I 'Alter tablespace PSAPSR3700 end backup' successful                                                                                BR0115I Compression rate for all files                                                                                BR0056I End of database backup: bdyuaxcq.and 2008-09-10                                                                                BR0280I BRBACKUP time stamp: 2008-09-10 22.41.16                                                                                BR0054I BRBACKUP terminated with errors

Hi,
Take a look at following SAP note hope it may help you:
Note 896160 - BRBACKUP ignores file copy errors during disk backups
Note Language: Version: 3 Validity: valid since 07.02.2007
PDF Download Corrections Compare Versions SSCR
Go to SAP Note: Display
Content: Summary | Header Data | Releases | Related Notes
Summary
Symptom
During a disk backup using a copying process (with or without compression), BRBACKUP ignores any copy errors and the complete backup is seen as having been successful, even though not all files were backed up, for example:
BR0201I Compressing F:\ORACLE\UQA\SAPDATA3\UQA620_7\UQA620.DATA7
BR0203I to F:\oracle\UQA\sapbackup\database\bdreqpjw\UQA620.DATA7.Z ...
BR0266E Program 'E:\usr\sap\UPR\SYS\exe\run\mkszip -c F:\ORACLE\UQA\SAPDATA3\UQA620_7\UQA620.DATA7 > F:\oracle\UQA\sapbackup\database\bdreqpjw\UQA620.DATA7.Z' interrupted, exit status: c0000094
BR0272E Execution of program 'E:\usr\sap\UPR\SYS\exe\run\mkszip -c F:\ORACLE\UQA\SAPDATA3\UQA620_7\UQA620.DATA7 > F:\oracle\UQA\sapbackup\database\bdreqpjw\UQA620.DATA7.Z' through pipe failed
BR0224E Compressing F:\ORACLE\UQA\SAPDATA3\UQA620_7\UQA620.DATA7 to F:\oracle\UQA\sapbackup\database\bdreqpjw\UQA620.DATA7.Z failed due to previous errors
BR0053I BRBACKUP completed successfully with warnings
Other terms
BR*Tools, BRBACKUP
Reason and Prerequisites
There are program errors in BRBACKUP 7.00 patch level 0 to 6 and BRBACKUP 6.40 patch level 25 to 34.
Solution
These errors are corrected in BRBACKUP 7.00 patch 9.
These errors are corrected in BRBACKUP 6.40 patch 35.
For more information about downloading patches, see Notes 12741 and 19466.

Unable to Log-in *SAP System Message : Error while reading a Dynpro*

Hi,
We are facing issues while logging-in through SAP logon 710.
The system throws an error dialog box with the below message:
SAP System Message : Error while reading a Dynpro
At the OS level Java process server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

Hi Please find the contents of std_server.out below.
stdout/stderr redirect
node name   : server0
pid         : 4124
system name : KEC
system nr. : 01
started at : Mon Jul 27 15:44:57 2009
[Thr 5656] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00   PatchLevel 110760.44 is starting...
Loading: LogManager ... 250 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 47 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 93 ms.
Loading: LockingManager ... 32 ms.
Loading: ConfigurationManager ... 1032 ms.
Loading: LicensingManager ... 0 ms.
Loading: CacheManager ... 93 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (16 ms).
Service cross started. (31 ms).
Service file started. (31 ms).
Service memory started. (31 ms).
Service timeout started. (16 ms).
Service trex.service started. (32 ms).
Service userstore started. (0 ms).
Service jmx_notification started. (15 ms).
Service p4 started. (62 ms).
Service classpath_resolver started. (16 ms).
Service deploy started. (3722 ms).
Service MigrationService started. (31 ms).
Service bimmrdeployer started. (0 ms).
Service log_configurator started. (5177 ms).
Service locking started. (0 ms).
Service http started. (126 ms).
Service naming started. (157 ms).
Service failover started. (16 ms).
Service appclient started. (31 ms).
Service javamail started. (47 ms).
Service ts started. (47 ms).
Service jmsconnector started. (47 ms).
Service licensing started. (15 ms).
Service connector started. (93 ms).
Service iiop started. (94 ms).
Service configuration started. (16 ms).
Service webservices started. (265 ms).
Service dbpool started. (1204 ms).
Service UT started. (0 ms).
Jul 27, 2009 3:45:09 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "     Error while reading a dynpro                                        ". This message is critical if it appears during the startup of the AS Java.
Jul 27, 2009 3:45:09 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 27, 2009 3:45:09 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Backup error due to System Writer missing (enumeration of system32 printer dlls takes too long)

Hi,
On a Windows 2008 R2 we get a Windows Backup error while backupping System State (event id: 5, error code: '2155347997').
We tried *ALL* solutions found on Internet regarding the same issue (and we also applied the suggested hotfix KB2807849) but without success. So we DIGGED INTO VSS to see what is happening.
***1) First we saw that an USB printer had a problem and this resulted in
hundreds of entries in the following registry keys:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\Canon MF6500 Series #100010]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\Canon MF6500 Series #100011]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\Canon MF6500 Series #100012]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\79590]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StillImage\DeviceNameStore\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\79591]
***2) We completely removed ALL drivers/devices related to that printer (now the DeviceNameStore is empty and
pnputil -e returns no driver related to the printer)
***3) Using process monitor we saw that during vssadmin list writers the system is searching for the DLLs related to that printer AND SEEMS CAUGHT IN AN ENDLESS LOOP: this is an excerpt of the scan:
09:56:34,5205954   svchost.exe   324   RegSetValue   HKLM\System\CurrentControlSet\services\VSS\Diag\System Writer\IDENTIFY (Enter)   SUCCESS
09:57:18,2310377 svchost.exe 324 QueryDirectory C:\Windows\System32\spool\drivers\color\cnz005.icc NO SUCH FILE Filter: cnz005.icc
09:57:18,2312877 svchost.exe 324 QueryDirectory C:\Windows\System32\spool\drivers\color\cnf6500m.icc NO SUCH FILE Filter: cnf6500m.icc
09:57:18,2314854 svchost.exe 324 QueryDirectory C:\Windows\System32\cncmfp20.ini NO SUCH FILE Filter: cncmfp20.ini
09:57:18,2316416 svchost.exe 324 QueryDirectory C:\Windows\System32\cnclsi20.dll NO SUCH FILE Filter: cnclsi20.dll
... and so on
.... THE SAME FILES ARE REPEATED HUNDREDS OF TIMES!!!! ...
It seems that somewhere there is a catalog of system files which still contains the references to the (same) files used by the hundreds of devices that WERE present in the DeviceNameStore (see point ***1 above, but now it is empty), and the System
Writer continues to search/enumerate those files and fails.
How can I fix it ? Is there a way to "reset" the System Writer and "rebuild" (???) the correct files that it should backup? (in order to complete a successfull system state backup)
Can you help me?
Thank you in advance.
EDIT: some additional (useful?) information:
* we also ran chkdsk /f C:
* sfc /scannow completes without errors
* in the vssadmin list writers the "system writer" is missing (but - as said above - when we run it the associated process repeatedly search printer dll files in the System32 directory)
* perhaps those file are contained is some filemaps catalog ?!? Is there a way to "reset" them?!?
***EDIT 2***:
I found that the reference to those missing DLLs are in ***C:\Windows\inf\setupapi.ev3*** but if I move the file away the System Writer continues not being listed in vssadmin list writer (though the vssadmin command complete very fast).
This is what is happening:
svchost.exe   324   CloseFile   C:\Windows\inf   SUCCESS
svchost.exe   324   CloseFile   C:\Windows\System32\DriverStore\infpub.dat   SUCCESS
svchost.exe   324   CreateFile   C:\Windows\System32\DriverStore\infpub.dat   ACCESS DENIED
svchost.exe   324   CreateFile   C:\Windows\System32\DriverStore\infstor.dat   ACCESS DENIED
svchost.exe   324   CreateFile   C:\Windows\System32\DriverStore\infstrng.dat   ACCESS DENIED
svchost.exe   324   CreateFile   C:\Windows\System32\DriverStore\drvindex.dat   ACCESS DENIED
svchost.exe   324   CreateFile   C:\Windows\System32\DriverStore\INFCACHE.0   NAME NOT FOUND
svchost.exe   324   CreateFile   C:\Windows\System32\DriverStore\INFCACHE.1   ACCESS DENIED
svchost.exe   324   CreateFile   C:\Windows\System32\DriverStore\INFCACHE.2   NAME NOT FOUND
svchost.exe   324   CreateFile   C:\Windows\inf   SUCCESS
svchost.exe   324   QueryBasicInformationFile   C:\Windows\inf   SUCCESS
svchost.exe   324   RegCloseKey   HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup   SUCCESS
svchost.exe   324   CreateFile   C:\Windows\inf\setupapi.ev1   SUCCESS
svchost.exe   324   QueryStandardInformationFile   C:\Windows\inf\setupapi.ev1   SUCCESS
svchost.exe   324   CreateFileMapping   C:\Windows\inf\setupapi.ev1
svchost.exe   324   QueryStandardInformationFile   C:\Windows\inf\setupapi.ev1   SUCCESS
svchost.exe   324   CreateFileMapping   C:\Windows\inf\setupapi.ev1
svchost.exe   324   CreateFile   C:\Windows\inf\setupapi.ev2   SUCCESS
svchost.exe   324   QueryStandardInformationFile   C:\Windows\inf\setupapi.ev2
svchost.exe   324   CreateFileMapping   C:\Windows\inf\setupapi.ev2
svchost.exe   324   QueryStandardInformationFile   C:\Windows\inf\setupapi.ev2   SUCCESS
svchost.exe   324   CreateFileMapping   C:\Windows\inf\setupapi.ev2
svchost.exe   324   CreateFile   C:\Windows\inf\setupapi.ev3   SUCCESS
svchost.exe   324   QueryStandardInformationFile   C:\Windows\inf\setupapi.ev3
svchost.exe   324   CreateFileMapping   C:\Windows\inf\setupapi.ev3
svchost.exe   324   QueryStandardInformationFile   C:\Windows\inf\setupapi.ev3
svchost.exe   324   CreateFileMapping   C:\Windows\inf\setupapi.ev3   SUCCESS
svchost.exe   324   CreateFile   C:\Windows\System32\drivers   SUCCESS
svchost.exe   324   QueryDirectory   C:\Windows\System32\drivers\acpi.sys   SUCCESS
svchost.exe   324   QueryDirectory   C:\Windows\System32\drivers\rdpbus.sys   SUCCESS
svchost.exe   324   QueryDirectory   C:\Windows\System32\drivers\i8042prt.sys   SUCCESS
.... EVERYTHING IS OK UP TO HERE ...
svchost.exe   324   CloseFile   C:\Windows\System32\drivers   SUCCESS
svchost.exe   324   CreateFile   C:\Windows\System32   SUCCESS
svchost.exe   324   QueryDirectory   C:\Windows\System32\cncc6500.dll   NO SUCH FILE   Filter: cncc6500.dll
svchost.exe   324   QueryDirectory   C:\Windows\System32\cnci6500.dll   NO SUCH FILE   Filter: cnci6500.dll
svchost.exe   324   QueryDirectory   C:\Windows\System32\cncc6500.dll   NO SUCH FILE   Filter: cncc6500.dll
svchost.exe   324   QueryDirectory   C:\Windows\System32\cnci6500.dll   NO SUCH FILE   Filter: cnci6500.dll
... !!!!!GET CAUGHT IN AN ENDLESS LOOP!!!!!!!! (System Writer probably ends for timeout)...
Is there a way to rebuild/modify that file C:\Windows\inf\setupapi.ev3
Perhaps I can delete the catroot2 directory?

Hi,
Please check if there are number of files in Temporary ASP.NET folders under "C:\Windows\Microsoft.Net\Framework". If so, clear these files then restart the server to check the results.
In additional, you could try the steps below to troubleshoot the issue:
1. Give NETWORK SERVICE Read permissions on COM+ Event System.
a. Open the registry editor and navigate to HKLM\CurrentControlSet\Services\EventSystem.
b. Right click on the EventSystem and then select ‘Permissions’
c. Click on ‘ADD’ button and then type in ‘NETWORK SERVICE’ and give it READ permission.
d. Reboot the machine and then run the 'VSS admin list writers' to check if it shows up the 'system writer'.
2. If the step 1 doesn't work then move the contents of C:\Windows\winsxs\FileMaps to an alternate location. Then run the command 'VSS admin list writers' to check if it shows up the 'system writer'. Is so, some of those files maybe corrupted and we
need to identify them and replace the files from a healthy machine.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

JDeveloper 11.1.2.0.0 Version Application wizard : File Backup Error

hi
As shown in the scenario (sc1) screencast at http://screencast.com/t/GA7OcgYZ
the JDeveloper 11.1.2.0.0 Version Application wizard can fail sometimes, showing a "File Backup Error" dialog, with the message
"Failed attempting to back up imported resource
D:\screencast\VersionAppLockedIssueApp-v0.01\VersionAppLockedIssueApp\Model.
Check that there are no file system explorers viewing files in this location and that none of the files are open in other applications before resuming."
This even occurs when there are no other processes (like Windows Explorer or an editor) using/locking the file.
It should be possible to reproduce the behaviour using the example application
at http://www.consideringred.com/files/oracle/2011/VersionAppLockedIssueApp-v0.01.zip
which is really nothing special I think, so it might also reproduce using another application.
First open the application and also open the file "browseEmployees.jsf" in design view.
After that, as it seems, the Version Application wizard fails.
Note that it might be relevant that I am using Windows 7, as I can imagine that this could behave differently when using JDeveloper on other operating systems.
Also note, if I try to ZIP the application folder (instead of using the Version Application wizard) after opening the file "browseEmployees.jsf" in design view, I get a message like "WARNING: The process cannot access the file because it is being used by another process.
: D:\screencast\VersionAppLockedIssueApp-v0.01\VersionAppLockedIssueApp\.data\00000000\je.lck ",
as can be seen in the scenario (sc2) screencast at http://screencast.com/t/rFiL47Bil
As it seems that the Version Application wizard has managed to commit the source files, one workaround could be to checkout the source in another location and continue working there.
Other suggestions to avoid this issue, or deal with it, are welcome.
questions:
- (q1) Can this "File Backup Error" behaviour for the Version Application wizard be reproduced?
- (q2) How can this "File Backup Error" behaviour for the Version Application wizard be explained?
many thanks
Jan Vervecken

fyi
Today I noticed that there is a My Oracle Support note about this:
- note id 1353389.1 , "In JDeveloper11.1.2.0.0 the Version Application Wizard Failed with the Error: File Backup Error "
Its "Solution" section currently says:
"The problem is still investigated by development.
But there is a possible workaround for Bug 12912410 by unchecking the checkbox 'Perform Checkout' in step 5 of 6 in the wizard screen. "
regards
Jan

Time Machine making Daily backups of Entire Itunes Library

Hi There,
I have searched around the forums and cannot find an answer to my problem.
I am using time machine over a 1TB time capsule, my laptop is the only computer that is backing up to the drive,
Originally I noticed that my time machine backups were taking a long time (over 7 hours while connected through Ethernet)
I have downloaded BackupLoupe and using this utility I have found that daily backups of my entire Itunes music Library are being made (122GB).
Does anyone have any idea what may be causing this issue? I have followed the Time machine trouble shooting guide and Completely wiped the drive and started again,
I have performed a disk and permission repair on both the time capsule drive and on the Macbook through the install DVD, however each time I initiate time machine on the freshly reconditioned drives it happens again.
Any help would be greatly appreciated, I am going slowly insane.
Cheers
Josh

bigjnz wrote:
I have downloaded BackupLoupe and using this utility I have found that daily backups of my entire Itunes music Library are being made (122GB).
Is it only the iTunes folder; and the entire contents?
If so, the iTunes folder itself may be damaged. That happens occasionally; something in a folder object gets corrupted, and Time Machine either doesn't find real changes, or thinks everything changed.
In those cases, the only solution we've been able to find is to rename the folder, create a new one, move the contents, and delete the old one. The first backup afterwards will back up everything, but thereafter it should be ok.

Time machine backup error in Mavericks

I"m getting backup errors in Mavericks when it tries to back up to the Backups.backupdb folder in my 3TB external backup drive. This happens even when I turn Time Machine off!
This is the error I'm getting (taken from the console) when I manually start a time machine backup:
10/26/13 9:56:39.268 AM com.apple.backupd[18160]: Starting manual backup
10/26/13 9:56:40.826 AM com.apple.backupd[18160]: Backing up to /dev/disk2s2: /Volumes/Macbook Pro Backup 3TB/Backups.backupdb
10/26/13 9:56:46.069 AM com.apple.backupd[18160]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Macbook Pro Backup 3TB/Backups.backupdb/Macbook Pro 25 size:37
10/26/13 9:56:46.070 AM com.apple.backupd[18160]: Backup failed with error 2: 2
Has anyone seen this? At this point, I haven't been able to back up anything after upgrading to Mavericks, and I really don't want to delete the backup folder and start over.
I thought it might be a permissions problem, so I tried to use the disk utility to verify this. I wasn't able to select verify or repair disk permissions. When I tried to verify the disk, I got a 'Live file system repair is not supported' error. I've never seen this before.
Any thoughts on all of this?

I fixed this by hard booting, then repairing the disk. A restart didn't work.

Sap daily backup error

Similar Messages

Maybe you are looking for