Backup aborted - Configuration Backup Failes

Over the past couple of days, I've started getting the Error "Backup aborted - Configuration backup failed" on 3560/2960 switches and 2900/2800 routers. Pretty much everything at my primary site and a few devices, but not all, at some of my clients. What's odd to me is that the devices with the backup failures now have a greyed out "Backup Now" button. Again that doesn't apply to all, but most devices.
Shawn Eftink
CCNA/CCDA
Please rate all helpful posts and mark correct answers to assist others searching for solutions in the community.

Hi Shawn,
We saw this same behavior this morning with a test ON100 in the lab. The ON100 may need to run through it's normal scheduled nightly maintenance window before the driver tries the backup and then subseqeuntly enables the Backup Now button within the portal. Please take a look at this customer again on Monday and let us know if the backup succeeded, and if the Backup Now button becomes available again. We are looking into what it will take to issue a fix, as a contingency plan, or until a fix can be deployed, we are looking into controlled periodic monthly reboots of all ON100 which might mitigate issue by clearing the /tmp ramdisk on the devices.
-mike

Similar Messages

WCS - "Configuration Backup" failed. How to debug?

In WCS, the backgroun task "Configuration Backup", to back up configurations from the controllers, is returning a "Backup Failed" message. How do I troubleshoot? Are they detailed logs somewhere, either via the WCS GUI or via the Linux command line?
thanks,

Same problem here...
I just upgraded my 3GS to iOS5 and signed into iCloud using my Apple ID...
Every time I click "Back Up Now" in the iCloud preferences on the iPhone, I get "There was a problem completing the backup. Please try again later."
On my wife's iPhone 4, I just performed a back up and there were no errors. I tried this also on my wife's iPad 2 and it worked perfectly.
I have tried the following:
1. In iTunes, when my phone is connected, I selected "Back up to iCloud" on the summary tab
2. Reset my phone using the steps in the above post
3. Deleted the iCloud account on my iPhone and logged in again
4. Tried to backup from 3 different wireless networks
None of the steps above fixed the issue which has been going on all day for me...
Any other help would be great - thanks!

ACS 5.3.0.40 On-demand Full Backup failed.

Hi,
I have ACS 5.3.0.40 Primary Secondary Authenticators , of which the Scheduled backup has stopped.
When checked the :
Monitoring Configuration >
System Operations >
Data Management >
Removal and Backup
> Incremental Backup , it had changed to OFF mode. without any reason.
The same was observed earlier too.
I have made the
Incremental Backup to ON and intiated the
View Full Database Backup Now. But it wasn't successful and reported an Error:
FullBackupOnDemand-Job Incremental Backup Utility System Fri Dec 28 11:56:57 IST 2012 Incremental Backup Failed: CARS_APP_BACKUP_FAILED : -404 : Application backup error Failed
Later i did the acs stop/start "view-jobmanager" and initiated the On-demand Full Backup , but no luck, same error reported this time too.
Has any one faced similar type of error /problem reported , please let me know the solution.
Thanks & Regards.

One other thing; if this does end up being an issue with disk space it is worth considering patch 5.3.0.40.6 or later since improves database management processes
This cumulative patch includes fixes/enhancements related to disk management to avoid following issue
CSCtz24314: ACS 5.x *still* runs out of disk space
and also fix for
CSCua51804: View backup fails   even when there is space in disk
Following is taken from the readme for this patch
   The Monitoring and Reporting database can increase when as records are collected. There are two mechanisms to reduce this size and prevent it from exceeding the maximum limit.
1. Purge: In this mechanism the data will be purged based on the configured data retention period or upon reaching the upper limit of the database.
2. Compress: This mechanism frees up unused space in the database without deleting any records.
Previously the compress option could only be run manually. In ACS 5.3 Patch 6 there are enhancements so it will run daily at a predefined time, automatically when specific criteria are met. Similarly by default purge job runs every day at 4 AM. In Patch 6 new option provided to do on demand purge as well.
The new solution is to perform the Monitoring and Reporting database compress automatically.
2.       New GUI option is provided to enable the Monitoring and Reporting database compress to run on every day at 5 AM. This can be configured under GUI Monitoring And Configuration -> System Operations -> Data Management -> Removal and Backup
3.       Changed the upper and lower limit of purging of Monitoring and Reporting data. This is to make sure at lower limit itself ACS has enough space to take the backup. The maximum size allocated for monitoring and reporting database is 42% of /opt( 139 GB). The lower Limit at which ACS purges the data by taking the backup is 60% of maximum size Monitoring and Reporting database (83.42 GB). The upper limit at which ACS purges the data without taking backup is 80% of maximum size Monitoring and Reporting database (111.22 GB).
4. The acsview-database compress operation stops all services till 5.3 patch 5 , now only Monitoring and Reporting related services are stopped during this operation.
5. Provided “On demand purge” option in Monitoring and Reporting GUI. This option will not try to take any backup, it will purge the data based on window size configured.
6. Even if the “Enable ACS View Database compress” option is not enabled in GUI then also automatic view database compress will be triggered if the physical size of Monitoring and Reporting database reached to the upper limit of its size.
7. This automatic database compress takes place only when the “LogRecovery” feature is enabled, this is to make sure that the logging which happens during this operation will be recovered once this operation is completed. ACS generates alert when there is a need to do automatic database compress and also to enable this feature.
8. Before enabling “LogRecovery” feature configure the Logging Categories in such way that only mandatory data to log into Local Log Target and Remote Log Target as Log collector under System Administration > ... > Configuration > Log Configuration
This “LogRecovery” feature can recover the logs only if the logs are present under local log target.
9       This automatic database compress operation also performed only when the difference between actual and physical size of Monitoring and Reporting database size is > 50GB.
10 The new CLI “acsview” with option “show-dbsize” is provided to show the actual and physical size of the Monitoring and Reporting database. This is available in “acs-config” mode.
           acsview     show-dbsize     Show the actual and physical size of View DB and transaction log file

Backup Fails with Invalid RECID Error

Hi All,
Please help me to understand Caution -section
below text is from
[http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
Backup Fails with Invalid RECID Error: Solution 2
This solution is more difficult than solution 1:
To create the control file with SQL*Plus:
   1. Connect to the target database with SQL*Plus. For example, enter:
      % sqlplus 'SYS/oracle@trgt AS SYSDBA'
   2. Mount the database if it is not already mounted:
      SQL> ALTER DATABASE MOUNT;
   3. Back up the control file to a trace file:
      SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
   4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
      # The following commands will create a new control file and use it
      # to open the database.
      # Data used by the recovery manager will be lost. Additional logs may
      # be required for media recovery of offline data files. Use this
      # only if the current version of all online logs are available.
      STARTUP NOMOUNT
      CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS ARCHIVELOG
      -- STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
          MAXLOGFILES 32
          MAXLOGMEMBERS 2
          MAXDATAFILES 32
          MAXINSTANCES 1
          MAXLOGHISTORY 226
      LOGFILE
        GROUP 1 '/oracle/oradata/trgt/redo01.log' SIZE 25M,
        GROUP 2 '/oracle/oradata/trgt/redo02.log' SIZE 25M,
        GROUP 3 '/oracle/oradata/trgt/redo03.log' SIZE 500K
      -- STANDBY LOGFILE
      DATAFILE
        '/oracle/oradata/trgt/system01.dbf',
        '/oracle/oradata/trgt/undotbs01.dbf',
        '/oracle/oradata/trgt/cwmlite01.dbf',
        '/oracle/oradata/trgt/drsys01.dbf',
        '/oracle/oradata/trgt/example01.dbf',
        '/oracle/oradata/trgt/indx01.dbf',
        '/oracle/oradata/trgt/tools01.dbf',
        '/oracle/oradata/trgt/users01.dbf'
      CHARACTER SET WE8DEC
      # Take files offline to match current control file.
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
      # Configure RMAN configuration record 1
      VARIABLE RECNO NUMBER;
      EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
      DEBUG 255');
      # Recovery is required if any of the datafiles are restored backups,
      # or if the last shutdown was not normal or immediate.
      RECOVER DATABASE
      # All logs need archiving and a log switch is needed.
      ALTER SYSTEM ARCHIVE LOG ALL;
      # Database can now be opened normally.
      ALTER DATABASE OPEN;
      # Commands to add tempfiles to temporary tablespaces.
      # Online tempfiles have complete space information.
      # Other tempfiles may require adjustment.
      ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
      # End of tempfile additions.
   5. Shut down the database:
      SHUTDOWN IMMEDIATE
   6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
      STARTUP NOMOUNT
      CREATE CONTROLFILE ...;
      EXECUTE ...;
      RECOVER DATABASE
      ALTER SYSTEM ARCHIVE LOG CURRENT;
      ALTER DATABASE OPEN ...;
Caution:
      If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.

Please help me to understand Caution -section
Caution:
If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
Rgds.

Time Machine backup fails about once a week

I'm backing up to an external firewire drive.
About once a week, a Time Machine backup will fail.
I have no other information on the failure. There are no errors in any of the log in
Console.app. Time Machine simply reports "Last Backup Failed", and that's it.
I looked through system.log, and found this;
system.log:Nov 25 08:59:51 kilroy-3 /System/Library/CoreServices/backupd[3897]: Error: (-43) SrcErr:NO Copying /Users/mauroj/Notebook/.DS_Store to /Volumes/TimeMachine/Backups.backupdb/kilroy/2008-11-25-085528.inProgress/D2D3A 24A-4AC2-4BBE-B95B-70F6C122AA07/MacIntosh HD/Users/mauroj/Notebook
Nov 25 08:59:51 kilroy-3 /System/Library/CoreServices/backupd[3897]: Copied 1132 files (90.0 MB) from volume MacIntosh HD.
Nov 25 08:59:51 kilroy-3 /System/Library/CoreServices/backupd[3897]: Copy stage failed with error:11
Nov 25 08:59:56 kilroy-3 /System/Library/CoreServices/backupd[3897]: Backup failed with error: 11
I'm not 100% sure this is the reason Time Machine failed and aborted, but it correlates
time-wise. So it appears backupd (aka Time Machine) is reporting it can not or will not
copy one particular file. There is no indication as to why.
This is buggy behavior for backup software. The message is broken, because there's no
"why" to the failure mode, and the software is broken, because it should be able to
recover from this, complete the backup, and simply report that a specific file was not
backed up.
If I can, I'll file a bug. Note to Apple - We RELY on backups. Stuff like this in the backup
software does NOT make us feel warm and fuzzy.
/jim

this is a known bug introduced by 10.5.3 update. lots of people have it (including myself). it's been acknowledged by apple. there is nothing you can or should do about it yourself. we have to wait for a fix from apple.

RMAN Backup Failed.

Hi Gurus,
My RMAN backup failed with below error.Please suggest.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 01/26/2013 22:48:56
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
RMAN>
Recovery Manager complete.
Thanks,

The message indicates that your database is in NOARCHIVELOG mode. You cannot make an RMAN Backup of a database that is OPEN if it is in NOARCHIVELOG mode.
You have two options
1. Make consistent RMAN Backups with the database only in MOUNT mode (SHUTDOWN ; STARTUP MOUNT)
OR
2. Configure for ArchiveLogs (create a target filesystem or FRA), set the database to ARCHIVELOG mode, monitor the volume of ArchiveLog generation, configure both Database and ArchiveLog backups.
Hemant K Chitale

RMAN LEVEL0 BACKUP FAIL

Use scripts to do level0 backup
scripts:
run {allocate channel c1 type disk;allocate channel c2 type disk;backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bkp_%T_%s_%p.dbf' databaseinclude current controlfile;release channel c1;release channel c2;}
Backup failed. Below is the log information:
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jul 2 23:30:09 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY0 (DBID=359019005)
using target database control file instead of recovery catalog
RMAN> run {
2> allocate channel c1 type disk;
3> allocate channel c2 type disk;
4> backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bkp_%T_%s_%p.dbf' database
5> include current controlfile;
6> release channel c1;
7> release channel c2;
8> }
9>
10>
allocated channel: c1
channel c1: sid=218 devtype=DISK
allocated channel: c2
channel c2: sid=279 devtype=DISK
Starting backup at 02-JUL-12
channel c1: starting incremental level 0 datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00004 name=/database/oracle/oradata/PRIMARY0/datafile/o1_mf_users_7b1my5cr_.dbf
input datafile fno=00010 name=/oradata/primary0/datafile/data02.dbf
channel c1: starting piece 1 at 02-JUL-12
channel c2: starting incremental level 0 datafile backupset
channel c2: specifying datafile(s) in backupset
input datafile fno=00005 name=/database/oracle/oradata/PRIMARY0/datafile/o1_mf_users_7b1mykwz_.dbf
input datafile fno=00011 name=/oradata/primary0/datafile/data03.dbf
channel c2: starting piece 1 at 02-JUL-12
RMAN-03009: failure of backup command on c2 channel at 07/03/2012 00:11:10
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2backup/bkp_20120627_1992_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c2 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on c1 channel at 07/03/2012 01:54:26
ORA-19510: failed to set size of 3986777 blocks for file "/backup/nissandb2backup/bkp_20120627_1991_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c1 disabled, job failed on it will be run on another channel
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c2 channel at 07/03/2012 00:11:10
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2backup/bkp_20120627_1992_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
RMAN-03009: failure of backup command on c1 channel at 07/03/2012 01:54:26
ORA-19510: failed to set size of 3986777 blocks for file "/backup/nissandb2backup/bkp_20120627_1991_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
Recovery Manager complete.
Could you please help check the reason?

Thank for your reply.
Yesterday I only modified the script.
Now the script is :
run {
allocate channel c1 type disk maxpiecesize 5120M;
allocate channel c2 type disk maxpiecesize 5120M;
backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bkp_%
T_%s_%p_%U' database
include current controlfile;
release channel c1;
release channel c2;
But still failed.The log is:
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Jul 3 23:30:11 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY0 (DBID=359019005)
using target database control file instead of recovery catalog
RMAN> run {
2> allocate channel c1 type disk maxpiecesize 5120M;
3> allocate channel c2 type disk maxpiecesize 5120M;
4> backup incremental level 0 tag 'level0' format='/backup/nissandb2backup/bk
p_%T_%s_%p_%U' database
5> include current controlfile;
6> release channel c1;
7> release channel c2;
8> }
9>
10>
allocated channel: c1
channel c1: sid=250 devtype=DISK
allocated channel: c2
channel c2: sid=245 devtype=DISK
Starting backup at 03-JUL-12
channel c1: starting incremental level 0 datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00004 name=/database/oracle/oradata/PRIMARY0/datafile/o1_m
f_users_7b1my5cr_.dbf
input datafile fno=00010 name=/oradata/primary0/datafile/data02.dbf
channel c1: starting piece 1 at 03-JUL-12
channel c2: starting incremental level 0 datafile backupset
channel c2: specifying datafile(s) in backupset
input datafile fno=00005 name=/database/oracle/oradata/PRIMARY0/datafile/o1_m
f_users_7b1mykwz_.dbf
input datafile fno=00011 name=/oradata/primary0/datafile/data03.dbf
channel c2: starting piece 1 at 03-JUL-12
RMAN-03009: failure of backup command on c2 channel at 07/04/2012 07:36:34
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1994_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c2 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on c1 channel at 07/04/2012 08:47:20
ORA-19510: failed to set size of 3986905 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1993_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
channel c1 disabled, job failed on it will be run on another channel
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c2 channel at 07/04/2012 07:36:34
ORA-19510: failed to set size of 3946992 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1994_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
RMAN-03009: failure of backup command on c1 channel at 07/04/2012 08:47:20
ORA-19510: failed to set size of 3986905 blocks for file "/backup/nissandb2ba
ckup/bkp_20120628_1993_1.dbf" (blocksize=8192)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
Recovery Manager complete.
Now I modify the rman parameter:
CONFIGURE MAXSETSIZE TO UNLIMITED; --> CONFIGURE MAXSETSIZE TO 5G;
Any other things, I need to check or modify? Please help.

ORA-00245: control file backup failed; target is likely on a local file sys

Hello,
our RAC (Linux, 11.2.0.3.0) is rather new and we are still on gaining experiences with that system...
When starting the backup with RMAN we are getting the following error:
Starting Control File and SPFILE Autobackup at 04-JUL-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 07/04/2012 16:41:48
ORA-00245: control file backup failed; target is likely on a local file system
The reason for the error is clear ORA-00245 - in a RAC environment the location of the Snapshot Controlfile must be on a shared location.
When executing the RMAN command "show all" on each node, we are getting
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD021.f'; # default
for node #1
and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD022.f'; # default
for node #2
When using a shared location for the Snapshot Controlfile do we still need to setup 2 different names for that file?
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD021.f'; # default
for node #1 and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD022.f'; # default
for node #2
Or should we configure just one Snapshot Controlfile?
The RMAN setup for "CONFIGURE SNAPSHOT CONTROLFILE NAME TO..." must be changed on both nodes - correct?
Hopefully my question is clear enough - any help will be appreciated.
Rgds
JH
Edited by: VivaLaVida on 05.07.2012 11:41

No, it must be configured on a shared storage:Not really required, i've RAC setup and snapshot is configured on local storage.
Configuring the RMAN Snapshot Control File Location
The snapshot control file is a copy of a database control file created in an operating system-specific location by Recovery Manager. RMAN creates the snapshot control file so that it has a consistent version of a control file to use when either resynchronizing the recovery catalog or backing up the control file. In Oracle RAC, the snapshot control file is only needed on the nodes on which RMAN performs backups; the snapshot control file does not need to be globally available to all instances in an Oracle RAC environment.
See below from doc.
http://docs.oracle.com/cd/B28359_01/rac.111/b28254/rman.htm#i455026

Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

Hello all,
Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
Time Capsule won't backup if Modem (Motorola SB6121) attached
This was on Feb 10th resolved. Few days later I upgraded to Yosemite. Backups were working fine since.
Yesterday I happen to notice my last backup was 5 days ago. I looked in the console logs and saw:
2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
I called Apple. Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
But the next hour it failed
Called Apple again, this time to Sr Advisor. He suggested factory reset of the TC and set up again. Also first backup worked then rest failed
Third call to Apple useless also. He was asking questions I didn't feel relevant. He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
I begged him to collect data to submit to engineering, which will take days to get a reply.
So I thought I would throw this out to the community....
TC Is NEW (replaced from last issue). Mac is 8 months old (iMac 27"), Os is Yosemite, TC also new (latest model)
Thanks...

Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

SCCM Site DB Backup failed

Hi
I found the Site DB backup has failed today....found the below error in smsbkp.log.
dont' know where to start troubleshooting. i am able to access the backup share
Error: Failed to backup
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy63\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES up to
\\Server1\Backup\CS1Backup\SiteServer\SMSServer\inboxes: ERROR: CTool::TreeCopy to
\\SERVER1\Backup\CS1Backup\SiteServer\SMSServer\inboxes failed. Error = [error code: 21, error message: The device is not ready.].
can some one help
thanks
ananth

Hi Torstepast two days backup again failed with the below error message...what is the permanant solution for this?
Error: Failed to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES up to \\psserver1\Backup\PS1Backup\SiteServer\SMSServer\inboxes: ERROR: CTool::TreeCopy to \\psserver1\Backup\PS1Backup\SiteServer\SMSServer\inboxes
failed. Error = [error code: 2, error message: The system cannot find the file specified.]. SMS_SITE_BACKUP 8/29/2013 4:26:05 AM 10748 (0x29FC)
STATMSG: ID=5043 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=psserver1 SITE=PS1 PID=8436 TID=10748 GMTDATE=Thu Aug 29 08:26:05.460 2013 ISTR0="\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES"
ISTR1="\\psserver1\Backup\PS1Backup\SiteServer\SMSServer\inboxes" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Failed to copy file(s) PS1Backup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Backup Failed for Component - PS1Backup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS\. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Failed to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS up to \\psserver1\Backup\PS1Backup\SiteServer\SMSServer\Logs: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT
CONFIGURATION MANAGER\LOGS is not readable.. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
STATMSG: ID=5043 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=psserver1 SITE=PS1 PID=8436 TID=10748 GMTDATE=Thu Aug 29 08:26:14.975 2013 ISTR0="\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS"
ISTR1="\\psserver1\Backup\PS1Backup\SiteServer\SMSServer\Logs" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Failed to copy file(s) PS1Backup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Backup Failed for Component - PS1Backup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA\. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Failed to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA up to \\psserver1\Backup\PS1Backup\SiteServer\SMSServer\data: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT
CONFIGURATION MANAGER\DATA is not readable.. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
STATMSG: ID=5043 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=psserver1 SITE=PS1 PID=8436 TID=10748 GMTDATE=Thu Aug 29 08:26:14.991 2013 ISTR0="\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA"
ISTR1="\\psserver1\Backup\PS1Backup\SiteServer\SMSServer\data" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Failed to copy file(s) PS1Backup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Backup Failed for Component - PS1Backup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT\. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Failed to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT up to \\psserver1\Backup\PS1Backup\SiteServer\SMSServer\srvacct: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT
CONFIGURATION MANAGER\SRVACCT is not readable.. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
STATMSG: ID=5043 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=psserver1 SITE=PS1 PID=8436 TID=10748 GMTDATE=Thu Aug 29 08:26:14.991 2013 ISTR0="\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT"
ISTR1="\\psserver1\Backup\PS1Backup\SiteServer\SMSServer\srvacct" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Failed to copy file(s) PS1Backup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Backup Failed for Component - PS1Backup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft Configuration Manager\install.map. SMS_SITE_BACKUP 8/29/2013 4:26:14 AM 10748 (0x29FC)
Error: Failed to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft Configuration Manager\install.map up to \\psserver1\Backup\PS1Backup\SiteServer\SMSServer: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft
Configuration Manager\install.map is not readable.. SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
STATMSG: ID=5043 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=psserver1 SITE=PS1 PID=8436 TID=10748 GMTDATE=Thu Aug 29 08:26:15.007 2013 ISTR0="\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft Configuration Manager\install.map"
ISTR1="\\psserver1\Backup\PS1Backup\SiteServer\SMSServer" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
Failed to copy file(s) PS1Backup\SiteServer\SMSServer. SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
Error: Backup Failed for Component - PS1Backup\SiteServer\SMSServer. SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
Error: Failed to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat up to \\psserver1\Backup\PS1Backup\SiteServer: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft
Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat is not readable.. SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
STATMSG: ID=5043 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=psserver1 SITE=PS1 PID=8436 TID=10748 GMTDATE=Thu Aug 29 08:26:15.007 2013 ISTR0="\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat"
ISTR1="\\psserver1\Backup\PS1Backup\SiteServer" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
Failed to copy file(s) PS1Backup\SiteServer. SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
Error: Backup Failed for Component - PS1Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
Waiting On SQL Backup for component CM_PS1 to complete... SMS_SITE_BACKUP 8/29/2013 4:26:15 AM 10748 (0x29FC)
Thanks
anan2k

Backup Failed-TM buddy logs posted-

Hello All
I absolutely cannot get TM to backup.
I have removed and re added my TM disk for use with TM
deleted plist file
The first log said something in Adobe Contribute couldnt be indexed, so I uninstalled Contribute
Still fails
Here is the latest log
Starting standard backup
Backing up to: /Volumes/Time Machine Backup/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
No pre-backup thinning needed: 47.90 GB requested (including padding), 73.21 GB available
Indexing a file failed. Returned -12 for: /Applications/.AdobePatchFiles, /Volumes/Time Machine Backup/Backups.backupdb/Patrick Gleason’s MacBook Pro/2009-02-06-120746.inProgress/63DA7DB4-2F22-425E-A5C2-D13094906896/Macintosh /Applications/.AdobePatchFiles
Aborting backup because indexing a file failed.
Stopping backup.
Copied 0 files (6 KB) from volume Macintosh.
Copy stage failed with error:11
Backup failed with error: 11
25 days since last backup
Every time I try I seem to get a different problem file.
I'm on a MBP, the last run of the old model-with multitouch-running 10.5.6
I connect to my WD Mybook via FW400 to do TM backups
The drive is 750 gb, 2 partitions about 500 general space and 250 for the TM partition. I have had success Backing up for as long as I can remember. No problems until recently.
Any Help is greatly appreciated

Christopher Gleason wrote:
Event store UUIDs don't match for volume: Macintosh
This means that something, probably an improper shutdown, caused TM to not be certain the records in the OSX +File System Event database+ match the contents of your hard drive.
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
Because of that, TM must do a "deep traversal" -- looking at every file and folder on your HD to determine what needs to be backed-up.
This is not a fatal problem, but the backup will be quite lengthy.
Indexing a file failed. Returned -12 for: /Applications/.AdobePatchFiles
Now that's a problem. That is, by the way, a hidden file (name starting with a dot). For now, the best thing to do is just exclude it from TM and try again, as there may be more problems.
To exclude it, go to TM's Preferences and click+ Options.+
In the next panel, click the plus sign at the bottom, and check Show Invisible items.
In the sidebar of the next panel, select your home folder, then navigate to the file in question.
Select it, click Exclude, then Done.
Then do a +Back Up Now+ from the TM icon in your Menubar.
Because of the UUID problem, your backup will be lengthy.
If there are further problems, post the logs again, and we'll see if there's something else you can do.
If TM runs ok, then you need to figure out what's wrong with the app.

Last backup failed---pls help

Hi All,
Our last scheduled Online backup failed.....pls help.
Details of log-:
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata2/xxx640_10/xxx640.data10
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata2/xxx640_9/xxx640.data9
BR0233E Backup utility has reported an error while saving file /oracle/xxx/sapdata4/xxxusr_1/xxxusr.data1
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata4/xxxusr_2/xxxusr.data2
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata1/undo_1/undo.data1
Cannot complete backup set "Bad catalog access for message #7598 in set 11![Major] From: OB2BAR_SAPBACK@pesbdbci "XXX" Time: 09/12/08 22:49:35 #Aborting connection to BSM. Abort code -2.
Cannot complete backup set "Bad catalog access for message #7598 in set 11!
[Major] From: OB2BAR_SAPBACK@pesbdbci "XXX" Time: 09/12/08 22:49:35 #Aborting connection to BSM. Abort code -2.
Cannot complete backup set "Bad catalog access for message #7598 in set 11!
[Major] From: OB2BAR_SAPBACK@pesbdbci "XXX" Time: 09/12/08 22:49:35 #Aborting connection to BSM. Abort code -2.
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata1/xxx640_5/xxx640.data5
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata2/xxx640_8/xxx640.data8
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata4/xxx640_13/xxx640.data13
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata1/system_1/system.data1
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata2/xxx640_6/xxx640.data6
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata3/xxx640_11/xxx640.data11
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata5/xxx640_14/xxx640.data14
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata2/xxx640_7/xxx640.data7
BR0233E Backup utility has reported an error while saving file /oracle/XXX/sapdata4/xxx640_12/xxx640.data12
BR0279E Return code from '/usr/sap/XXX/SYS/exe/run/backint -u XXX -f backup -i /oracle/XXX/sapbackup/.bdyukhxq.lst -t file_online -c': 1
BR0232E 59 of 83 files saved by backup utility
BR0280I BRBACKUP time stamp: 2008-09-12 22.49.35
BR0231E Backup utility call failed
Regards,
Prashant
Edited by: Prashant Shukla on Sep 15, 2008 2:21 AM

Hi prasanth,
How u resolved this we are also facing same problem.we are using DP only.
pls help me.
Regards,
Pavan

Time Capsule backup failed, volume read-only, can't delete

I've only been using Time Machine and Time Capsule for 2 months. This week it stopped working. First error message:
"Unable to complete backup. An error occurred while copying files to the backup volume."
Checking the Time Machine preferences, "Last backup" would read "backup failed"
When I got this error, all the wireless functions went offline, even thought the TC light was still green.
I would shut down, shut down the Time Capsule, shut off my modem reboot everything in order.
I would come back online, but after about 20 minutes to 1.5 hours into the next backup, same thing would happen again.
Next error message:
"Disk repair. The disk 'Backup of [my computer]' was not repairable by this computer. It is being made available to you with limited functionality. You must backup your data and reformat the drive."
Then: "Time Machine Error: The backup volume is read only. To select a different volume ... Time Machine preferences ... "
I spoke to someone at Apple, who sent me the Time Machine Troubleshooting page:
http://support.apple.com/kb/HT3275?viewlocale=en_US
Steps I went through:
1. updated my system software
2. updated the TC firmware to 7.4.1
3. dragged the sparsebundle to DiskUtility. It took a while (more than an hour?) but said the disk could not be repaired. When I tried again, the repair function wouldn't run.
4. tried to delete the sparsebundle, but it would choke at almost the end, sometimes it would just crash the finder, sometimes say "Sorry, an unexpected error occurred," sometimes "Operation cannot be completed because the item 'bands' is in use." I even tried to Stuff the bundle with 'delete original' checked, but the stuffing, after about 15 hours, jammed near the end (stuffed 20 gigs of 35 gigs).
5. tried to reselect the TC, and run backup anyways ... now it can't find the volume, back to the error messages and crashing Finder
6. checked password in Keychain, all ok.
Now what??
Do I use Airport Utility to erase it? At least TC is still showing up there. Or press the rest button on the back of the Time Capsule to reset to factory defaults?
I've resigned myself to losing my backups. Now I would just like to get it up and running again.
In hopes,
Linda

Now what??
Do I use Airport Utility to erase it? At least TC is still showing up there. Or press the rest button on the back of the Time Capsule to reset to factory defaults?
Yes, open Airport Utility and erase the drive. Once the sparsebundle is corrupted beyond repair there's little more you can do. However, do not reset the TC. Doing so will not erase the drive, but it will remove any custom configurations you may have setup for the router. Only if that part of the TC is also misbehaving should you use the reset button.

Backup failed: can't link file

Hi,
Somehow one hard disk went south, one that I luckily used to backup with Time Machine, so no harm done there, and now after bringing a drive up again, using the very same volume name, restoring with Time Machine was a piece a cake.
But, on the other hand, now whenever I try to have this new "old" volume being backed up with Time Machine, the latter reports a failure due to not being able to link files (something about UUIDs or similar).
How can I resolve this and get everything working as smoothly and neatly as before without loosing any of my backups or having to use another disk for the backup?
- MMHein

Hi,
Well my environment consists of:
*) Mac Mini (internal HD, 120GB, 42GB free, name "S" = System)
*) USB HD (external HD, Maxtor OneTouch 750GB, 408GB free, name "B" = Backup)
*) USB HD (external HD, Maxtor 250GB, 61GB free, name "D" = Data)
When volume/drive "D" got corrupted and couldn't be repaired or recovered, I had to sweep the partition, re-partition the drive and format it again, using the very same name for the volume as before ("D").
Next step was to perform a restore of the previously backed up contents of the former volume "D". As all my Time Machine backups are done exclusively to volume "B" it was rather a piece of cake, only a bit time-comsuming as I had something around 120GB to restore.
Having successfully accomplished this I now wanted to configure Time Machine to backup volume "D" again (which I have disabled for the duration of the restore). At first it seem to work just as intended (and it actually took quite a long time), but in the end Time Machine quit with an error message, saying it couldn't complete the backup ("...can't link files..."; so unfortunately an error message not found under the link you posted ).
In the system log the following entries can be found:
Jan 6 14:55:03 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Starting standard backup
Jan 6 14:55:03 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Backing up to: /Volumes/Backup/Backups.backupdb
Jan 6 14:55:06 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Event store UUIDs don't match for volume: MH Mac Mini
Jan 6 14:55:06 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Event store UUIDs don't match for volume: Data
Jan 6 14:55:06 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
Jan 6 15:16:35 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Node requires deep traversal:/Volumes/Data reason:kFSEDBEventFlagMustScanSubDirs|
Jan 6 15:17:19 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: No pre-backup thinning needed: 192.30 GB requested (including padding), 248.81 GB available
Jan 6 15:20:13 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Copied 5361 files (61.3 MB) from volume MH Mac Mini.
Jan 6 21:38:10 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Copied 34905 files (158.7 GB) from volume Data.
Jan 6 21:38:10 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Error (12): Link of previous volume failed for Data.
Jan 6 21:38:16 MH-Mac-Mini /System/Library/CoreServices/backupd[4434]: Backup failed with error: 12
Jan 6 21:39:59 MH-Mac-Mini com.apple.launchd[134] (0x10e440.Locum[5039]): Exited: Terminated
Cheers,
MMHein

TM backup failed again...help please!!

Its been working fine for months & failed 3 times in the last couple of days, following are log from TM Buddy -
Starting standard backup
Backing up to: /Volumes/Kui-2/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
2011-01-25 22:56:12.577 FindSystemFiles[274:907] Looking for system packages
2011-01-25 22:56:12.988 FindSystemFiles[274:907] Using system path cache.
Backup content size: 165.5 GB excluded items size: 16.1 GB for volume Macintosh HD
No pre-backup thinning needed: 179.23 GB requested (including padding), 595.28 GB available
Waiting for index to be ready (101)
Copied 89.5 GB of 149.4 GB, 51437 of 771314 items
Indexing a file failed. Returned 200 for: /Users/ckui/Library/Mail/[email protected]@imap.gmail.com/[Gmail]/All Mail.imapmbox/Messages/384041.4.emlxpart, /Volumes/Kui-2/Backups.backupdb/CKui’s MacBook Pro/2011-01-25-225613.inProgress/BCE58664-D000-43A6-90E9-7677E042857B/Macintosh HD/Users/ckui/Library/Mail/[email protected]@imap.gmail.com/[Gmail]/All Mail.imapmbox/Messages/384041.4.emlxpart
Aborting backup because indexing of file failed.
Stopping backup.
Stopping backupd to allow ejection of backup destination disk!
Copied 213216 files (110.4 GB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11

Hello again,
Got a brand new external drive; reformatted to Mac standard, started well then almost to the end of the backup (163.13GB to total of 165GB) it started back to "Calculating Changes" & "Indexing Backup"!
Thanks in advance for your help.
Here are the log from Buddy.......
Starting standard backup
Backing up to: /Volumes/Time Machine Backup Jan-2011/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Backup content size: 162.0 GB excluded items size: 7.6 GB for volume Macintosh HD
No pre-backup thinning needed: 185.29 GB requested (including padding), 1.82 TB available
Waiting for index to be ready (101)
Copied 43.7 GB of 154.4 GB, 199486 of 943126 items
Copied 102.3 GB of 154.4 GB, 222627 of 943126 items
Copied 134.3 GB of 154.4 GB, 491140 of 943126 items
Copied 492128 files (152.0 GB) from volume Macintosh HD.
No pre-backup thinning needed: 6.24 GB requested (including padding), 1.66 TB available
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)

Backup aborted - Configuration Backup Failes

Similar Messages

Maybe you are looking for