Initial TM backup failed

I just got my Time Capsule and installed it this morning, all went very well.
I configured Time Machine and all was going great but I inadvertently caused the initial backup to fail when I reset the TC trying to configure a USB drive.
What will happen? Will the next scheduled backup pickup where the first one left off or will it do a new full backup or am I in trouble?
Pat

Thin Weasel,
Welcome to the Apple Discussions!
In addition to "Glasses" comments, consider the following:
*Interrupting A Time Machine Backup*
Just make sure your computer shuts down first, and then cut the power to the Time Machine drive. If the Time Machine disk shuts off during a backup it could cause problems later.
This KB article discusses backup interruptions related to the Time Capsule, but the information can apply to other Time Machine hard disks as well:
[http://support.apple.com/kb/HT1176]
Generally, Time Machine is smart enough to pickup where it left off when a backup is interrupted. It deals with the procedure of a normal shutdown or sleep with elegance. But if the backup process is interrupted by a system crash or some form of power interruption, then anomalies are introduced requiring TM to perform a "deep traversal". Since the average incremental backup only requires about 2-4 minutes, it shouldn't be that much of an inconvenience to just wait for the process to finish.
Unfortunately, if the initial full backup is interrupted by a power failure or such, then, to avoid issues later, it’s best to erase the drive and begin the full backup again.
As for "stopping" a backup, either using the TM menu or clicking the little "x" icon in the TM preference pane will work and should not be considered a dangerous interruption.
Hope this info is helpful.
Cheers!

Similar Messages

  • Time Machine initial backup fails OS 10.5 with no reason but 'bus error'

    I ran into an error on the last system update and had to go back to Leopard 10.5 just to see my stuff. I managed to move my home directory into the newly installed system and all my files are intact. Now I'm trying to get a Time Machine backup before I proceed (my initial mistake was not keeping up with them in the first place).
    I had some trouble early on and at one point decided to reformat the external drive (a Fantom Drives GreenDrive, usb, 500Gb). I formatted as Mac OS Extended (Journaled) as recommended, no partitions, and then tried my first initial Time Machine backup.
    It predictably spent a long time 'preparing...' and I followed along in the system log. Eventually, the copying began but early on (within the first 45 min) the backup failed with almost no indications in the log as to why. I've pasted the system log below.
    One thought I had was that it was weird that there was an automatic request for backup at 12:36:54. I also included the CrashReport, but I can't make any sense out of it.
    any ideas?
    System log:
    6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backup requested by user
    6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Starting standard backup
    6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backing up to: /Volumes/Deep Green/Backups.backupdb
    6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] No pre-backup thinning needed: 173.94 GB requested (including padding), 453.71 GB available
    6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] MDBackupBegin() returned result (910) > 0, waiting
    6/24/10 12:36:54 AM /System/Library/CoreServices/backupd[1190] Backup requested by automatic scheduler
    6/24/10 12:42:17 AM ReportCrash[1431] Formulating crash report for process backupd[1190]
    6/24/10 12:42:18 AM com.apple.launchd[1] (com.apple.backupd[1190]) Exited abnormally: Bus error
    6/24/10 12:42:24 AM ReportCrash[1431] Saved crashreport to /Library/Logs/CrashReporter/backupd2010-06-24-004204dylan-boyds-macbook.crash using uid: 0 gid: 0, euid: 0 egid: 0
    CrashReport:
    Process: backupd [1190]
    Path: /System/Library/CoreServices/backupd
    Identifier: backupd
    4 backupd 0x00007525 0x1000 + 25893
    5 backupd 0x00002332 0x1000 + 4914
    8 backupd 0x00015028 0x1000 + 81960
    9 backupd 0x0000ea64 0x1000 + 55908
    10 backupd 0x00008bfe 0x1000 + 31742
    11 backupd 0x00004c10 0x1000 + 15376
    12 backupd 0x000057b8 0x1000 + 18360
    0x1000 - 0x3dffb backupd ??? (???) <f50411bdb241b61699aa81b2f3dfb7d1> /System/Library/CoreServices/backupd

    I should have added that I've been through about half a dozen sites (including sanctioned apple sites) and their recommendations for getting Time Machine to work properly. I did format the drive once (with extended journaled format and GUID partition scheme, but I didn't zero it out. I'm trying that now and I'll try TM again in about 4 hours.
    This morning I tried turning Time Machine's automatic backups off (moved the slider to off in the preferences pane) and manually started a backup (right-clicking the TM icon in the dock and selecting "Backup Now"). It ran further along than before, but stopped again. This time, it gave an error, and I've pasted the log below. I looked but didn't find much helpful on "error 11."
    system log:
    Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup requested by user
    Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Starting standard backup
    Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backing up to: /Volumes/Deep Green/Backups.backupdb
    Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Event store UUIDs don't match for volume: Macintosh HD
    Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
    Jun 24 09:47:13 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: No pre-backup thinning needed: 175.31 GB requested (including padding), 453.11 GB available
    Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:YES Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to (null)
    Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
    Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Stopping backup.
    Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-8062) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
    Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copied 13360 files (1.5 GB) from volume Macintosh HD.
    Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copy stage failed with error:11
    Jun 24 10:14:03 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup failed with error: 11

  • Time Machine backups fail after initial backup in Yosemite

    After upgrading from Mavericks to Yosemite, I was able to run one backup to my trusty USB drive.  Subsequent backups all start with "Preparing backup", and will write roughly 900KB to disk (or so it says) and then fails.  I created a Time Machine-compatible network drive on my Drobo 5n, and again, the initial backup is successful, and subsequent ones fail.  This is concerning and infuriating.  I'm hoping someone out there has encountered this problem as well.
    Please note: this is regarding backups only.  I see a handful of discussions about not being able to perform restores in Yosemite, but that is not my issue.

    Same here.
    From Time Machine Buddy app:
    Starting manual backup
    Total content size: 424.3 GB excluded items size: 21.01 GB for volume Macintosh HD
    Found 2439814 files (403.3 GB) needing backup
    424.87 GB required (including padding), 250.63 GB available
    Deleted backup /Volumes/Backupmac/Backups.backupdb/.df. (3)/2014-10-23-120445.inProgress/F8CFC567-7E6E-49B0-B366-88DF31DAF49B containing 4 KB; 250.63 GB now available, 424.87 GB required
    Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
    Deleted 1 backups containing 4 KB total; 250.63 GB now available, 424.87 GB required
    Backup date range was shortened: oldest backup is now Oct 23, 2014
    Backup failed with error 7: Not enough available disk space on the target volume.
    It wants to do a full backup. Fine... so why doesn't it just delete more of the old backups to do so? I don't want to wipe the backup drive and start over now, but that seems like the only way to go.

  • Error message on iphone 3GS when initiating back-up for the first time "icloud backup failed - how to fix

    When initiating back-up of my 3GS to icloud for the first time, I repeatedly receive an error message reading:
    "iCloud backup failed
    There was a problem enabling iCloud backup"
    I cannot find a solution to this problem amd no amount of checking and rechecking account settings etc. has made any difference. Does anyone have experience of how to overcome this issue. The iCloud back-up initiated on my iPad without any problem so I do not think the problem is account related.
    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

  • Windows Server 2012 Windows Backup failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).

    The Volume Shadow Copy service initially was running under the context of System, so we thought that ‘System’ doesn’t have permissions to access network shares. 
    When the Volume Shadow Copy service was running under the context of System, this was the error logged:
    “failed with following error code '0x8078014B' (There was a failure in creating a directory on the backup storage location.).”
    Which is likely due to not having permissions to write to the network location. 
     This is a scheduled backup trying to write to a network location, so we changes the service to run under the context of an account that does have permissions to write to the network share.
      Then the error changed to this:
    “failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).”
    HRESULT 0x8078006b
    DetailedHRESULT 0x8004230f
    ErrorMessage %%2155348075
    BackupState 12
    VolumesInfo <VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0"
    BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0"
    TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228"
    DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0"
    FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0"
    /></VolumeInfo>
    We aren’t really seeing anything that gives any hint on what the issue is. 
    Any ideas?  Thanks in advance!

    We are trying to back up folders/files from 2 local drives (C: & D:), both of which have only 10% space used, and 100 GB free. 
    We are attempting to back the files up to a Remote Shared File (and there is 100+ GB free space out there). 
      If we try another network location, we receive the exact same error. 
     This is Windows Server 2012, not running Hyper-V and is a physical server not a VM.
    Thank you for the link. 
    Looking in: 
    Event Viewer / Application and Service Logs / Microsoft / Windows / Backup / Operational
    But it doesn’t seem to give any more details: 
    Log Name:     
    Microsoft-Windows-Backup
    Source:       
    Microsoft-Windows-Backup
    Date:         
    7/8/2013 8:00:12 PM
    Event ID:     
    5
    Task Category: None
    Level:        
    Error
    Keywords:     
    User:         
    SYSTEM
    Computer:     
    servername.edu
    Description:
    The backup operation that started at '‎2013‎-‎07‎-‎09T02:00:06.273000000Z' has failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).
    Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
    <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />
    <EventID>5</EventID>
    <Version>3</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2013-07-09T02:00:12.872602100Z" />
    <EventRecordID>30</EventRecordID>
    <Correlation />
    <Execution ProcessID="3028" ThreadID="3996" />
    <Channel>Microsoft-Windows-Backup</Channel>
    <Computer>servername.edu</Computer>
    <Security UserID="S-1-5-18" />
      </System>
      <EventData>
    <Data Name="BackupTemplateID">{A421E864-A115-4288-8D12-F4878CF8A248}</Data>
    <Data Name="HRESULT">0x8078006b</Data>
    <Data Name="DetailedHRESULT">0x8004230f</Data>
    <Data Name="ErrorMessage">%%2155348075</Data>
    <Data Name="BackupState">12</Data>
    <Data Name="BackupTime">2013-07-09T02:00:06.273000000Z</Data>
    <Data Name="BackupTarget">\\servername\BACKUP</Data>
    <Data Name="NumOfVolumes">2</Data>
    <Data Name="VolumesInfo">&lt;VolumeInfo&gt;&lt;VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0"
    IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /&gt;&lt;VolumeInfoItem
    Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0"
    NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /&gt;&lt;/VolumeInfo&gt;</Data>
    <Data Name="SourceSnapStartTime">2013-07-09T02:00:06.289250300Z</Data>
    <Data Name="SourceSnapEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="PrepareBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="PrepareBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupWriteStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupWriteEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="TargetSnapStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="TargetSnapEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="DVDFormatStartTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="DVDFormatEndTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="MediaVerifyStartTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="MediaVerifyEndTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupPreviousState">2</Data>
    <Data Name="ComponentStatus">&lt;ComponentStatus&gt;&lt;/ComponentStatus&gt;</Data>
    <Data Name="ComponentInfo">&lt;ComponentInfo&gt;&lt;/ComponentInfo&gt;</Data>
    <Data Name="SSBEnumerateStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBEnumerateEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBVhdCreationStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBVhdCreationEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBBackupStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBBackupEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SystemStateBackup">&lt;SystemState IsPresent="0" HResult="0" DetailedHResult="0" /&gt;</Data>
    <Data Name="BMR">&lt;BMR IsPresent="0" HResult="0" DetailedHResult="0" /&gt;</Data>
    <Data Name="VssFullBackup">false</Data>
    <Data Name="UserInputBMR">false</Data>
    <Data Name="UserInputSSB">false</Data>
    <Data Name="BackupSuccessLogPath">
    </Data>
    <Data Name="BackupFailureLogPath">
    </Data>
    <Data Name="EnumerateBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="EnumerateBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="PruneBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="PruneBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupFlags">0x9</Data>
    <Data Name="ComponentInfoSummary">&lt;ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" /&gt;</Data>
      </EventData>
    </Event>

  • "Backup failed" using Time Capsule

    Hello, trying to back up a Macbook using Time Capsule, keep getting the message that backup failed, even when I attach with MB to TB with an Ethernet cable.
    Anyone have any idea where I could begin to start looking for a solution?

    Hi James,
    Have you tried erasing your Time Capsule disk? If it's the initial backup, it could be that you have a corrupt sparsebundle file. Go into AirPort Utility > Manual Setup > Disks and select and erase the internal disk. Then try your backup again using an ethernet cable and see if that works.

  • BackUp failed because can't activate volume image

    Every time I'm launching an initial backup I'm told that the backup failed, because time capsule could not activate the backup volume image. I connectes my MacProBook 2.4 via an Ethernet cable and selceted the volume from system preferences 'time capsule', but still keep getting the same problem. What shall I do?

    Exactly the same problem here with my PowerBook5,8. No problem with my AirBook1,1.
    Any idea?

  • Time Capsule backup failed error -43?

    Hi and Thanks to Anyone in Advance!
    Below is the Time Capsule Error Log I get when doing a Time Machine Backup, wirelessly, on my 2T Time Capsule HD/Router.
    Initial Setup and Backup done via ethernet, flawlessly, two months ago. Subsequent backups worked until about three days ago (Why, I have not a clue!)
    Often, using Airport Utility, the Time Capsule does not appear. Turning off Computer Airport and on again, the disk becomes magically available for backup. Similar problem with wireless LAN printer...truly a pain. the printer needs to be deleted, and then added again in Print/Fax Preferences. (HP PhotoSmart C7250)
    I used Disk Utility" on my Computer HD with a repair permissions, then performed a TC reset, physically, and reconfigured the TC on the LAN, trying a new name "gotyourback" for the backup. Backup begins every time, but keeps failing after about five minutes.
    Hope this helps others with similar problem...
    Again,
    Thanks!
    Starting standard backup
    Attempting to mount network destination using URL: afp://Suz%20Tim%20Abri%20and%[email protected]/Data
    Mounted network destination using URL: afp://Suz%20Tim%20Abri%20and%[email protected]/Data
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Data/Rogers Rocks Home.sparsebundle mounted at: /Volumes/Time Machine Backups
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102f20b60 "The file “CM” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001c76a0 "The file “std” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001dfc50 "The file “js” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001e06c0 "The file “en” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001e11e0 "The file “disofactor.swf” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001e1320 "The file “diso.sol” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
    Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100527ec0 "The file “Download” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100194860 "The operation couldn’t be completed. Input/output error")
    No pre-backup thinning needed: 1.19 GB requested (including padding), 1.38 TB available
    Stopping backup.
    Error: (-43) SrcErr:NO Copying /Applications/The Learning Company to /Volumes/Time Machine Backups/Backups.backupdb/Rogers Rocks Home/2011-09-08-114311.inProgress/A0EF34AF-A412-4268-B48E-1FD4BF77C8BA/ROGERS LOVE/Applications
    Copied 177 files (33.0 MB) from volume ROGERS LOVE.
    Copy stage failed with error:11
    Backup failed with error: 11
    Ejected Time Machine disk image.

    Ok, if it is only 2months old it shouldn't be a problem..internally at least.
    ? (10.0.1.1) at b8:c7:5d:c6:3c:db on en1 ifscope [ethernet]
    It doesn't have a name.. although it has registered the MAC address and IP .. that is the TC unless you changed it the ? indicates there is an issue with device name. All the entries should have a name.
    ray-hs-mac-pro:~ Ray$ arp -a
    tc2.bigpond (192.168.2.104) at 60:33:4b:2e:91:77 on en1 ifscope [ethernet]
    andrew-gigabyte.bigpond (192.168.2.130) at 0:25:22:16:43:c7 on en1 ifscope [ethernet]
    bigpond.bigpond (192.168.2.254) at 0:24:17:71:ad:6d on en1 ifscope [ethernet]
    bigpond.bigpond (192.168.2.254) at 0:24:17:71:ad:6d on en0 ifscope [ethernet]
    ? (192.168.2.255) at ff:ff:ff:ff:ff:ff on en1 ifscope [ethernet]
    I have the TC in bridge and it is picking up the domain from my router.. if your using the TC as the main router then you should have entries for gotbackup.local
    You are running SL still?? Or lion?
    I thought of simply restoring the computer's settings to what they were 4-5 days ago, via Time Machine.
    The issue is network.. so restoring will not fix it.
    But so is my overdue dentist appointment...really not looking forward to either!
    My condolances to your dentist.
    I think you need to dig a bit harder to get the cause.
    Most importantly are you getting IP via dhcp from the TC?
    Do you have ethernet and wireless connected at the same time?

  • Time machine backups failing

    Hi,
    I have been backing up my iMac wirelessly to an external network drive using Time Machine without any problems.
    Just recently I have bought a Western Digital My Passport for Mac USB drive and tried to set up Time Machine to use that too. The initial backup worked fine but subsequent backups fail every time. I removed the backup from the drive and repeated the process and got the same results.
    The error log from Time Machine Buddy is:
    Starting manual backup
    Backing up to /dev/disk2s2: /Volumes/My Passport for Mac/Backups.backupdb
    Couldn't create backup directory for computer name Ramon-iMac, error: Error Domain=NSCocoaErrorDomain Code=512 "The file “Ramon-iMac 99” couldn’t be saved in the folder “Backups.backupdb”." UserInfo=0x7fbb205129f0 {NSFilePath=/Volumes/My Passport for Mac/Backups.backupdb/Ramon-iMac 99, NSUnderlyingError=0x7fbb205127e0 "The operation couldn’t be completed. Input/output error"}
    Backup failed with error 2: 2
    Starting manual backup
    Network destination already mounted at: /Volumes/TimeMachine
    Any help appreciated. I haven't ben able to find anything from a search of the community and Western Digital tech support have been useless.

    A third-party NAS is unsuitable for use with Time Machine, especially if it's your only backup. I know this isn't what you want to hear. I know that Time Machine accepts the NAS as a backup destination. I know that the manufacturer says the device will work with Time Machine, and I also know that it usually seems to work. Except when you try to restore, and find that you can't.
    Apple has published a specification for network devices that work with Time Machine. None of the third-party NAS vendors, as far as I know, meets that specification. They all use the incomplete, obsolete Netatalk implementation of Apple Filing Protocol.
    If you want network backup, use as the destination either an Apple Time Capsule or an external storage device connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
    Otherwise, don't use Time Machine at all. There are other ways to back up, though none of them is anywhere near as efficient or as well integrated with OS X. I don't have a specific recommendation.
    If you're determined to keep using the NAS with Time Machine, your only recourse for any problems that result is to the manufacturer (which will blame Apple, or you, or anyone but itself.)

  • EFI Folder on desktop during TimeMachine backup, backup fails.

    Hello,
    I am haing a very strange and infuriating problem.  The problem is whenever my Time Machine begins to backup a folder shows up on my desktop labeled "EFI".  The file size says 313.8MB, 312.6MB free.  Then my Time Machine backup fails time and time again (pun intended).
    The Time Machine is located on a MacMini Server, but even when I plug a TM drive directly into the USB it says the same thing and fails to backup.  I've tired different brand drives but still the same outcome.
    I then tired to clone the drive using SuperDuper but it can't even find the Macintosh HD.  So I did a PRAM reset, repaired permissions, wiped and partitioned the drive and did a clean install of the current OS.  I then used Migration Assistant to restore my data.
    It ran fine for a day and now the same thing is happening all over again, but now it shows the EFI folder anytime I connect a USB or network drive onto it, plus it now takes a good 5 minutes to even boot.
    I'ts absolutely maddening!  Since I owned this laptop it's had the screen replaced twice as well as the logic board for random shutdown issues.  I've begged and demanded for Apple to please replace this laptop since it was a month old.  Sadly, Apple has refused any resolution other than to keep replacing parts and adding scratches.  I purchased two twin units and the other unit has been whistling Dixie since day one.  My son got one and I got stuck with the evil twin.
    Any help would be greatly appreciated, but my guess is it is going to be shipped back to Apple for the 5th time.
    Thanks for reading!

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
    SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
    View ▹ Show Log List
    from the menu bar at the top of the screen.
    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
    Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
    CLEAR THE WORD "Starting" FROM THE TEXT FIELD
    so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressingcommand-V.
    ☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Time Machine. Backup failed with error code: 21

    Hi,
    I recently upgraded to Leopard 10.5.4 mainly for the time machine backup. I'm using a DNS-323 in a RAID1 configuration as the TM backup drive. Also I have the DNS-323 connected to my Airport Extreme through the ethernet to give NAS ability to my home network.
    After much hunting around the forums I got the sparsebundle created and copied to the DNS-323 share volume. See http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/ My thanks to flokru.
    However, TM is still not working. The console messages have the following:
    Network mountpoint /Volume/Volume_1 not owned by backupd... remounting
    Network volume mounted at /Volume/Volume11
    Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle
    Backup failed with error: 21
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Has anybody else seen this error or better yet, got a fix for it?

    James,
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Actually, it is not TMs failure to mount the volume that is causing your failure to backup. I have received the same Console message using a Time Capsule. However, Time Machines' attempt to 'remount' the volume always succeeds and the backup goes through. That appears not to be your experience, but it is NOT because the volume is not being mounted. It is.
    *Mount Point Conflict (TMDisk-1)*
    NOTE: the following distinguishes “network drive” (the physical hard disk) from “disk image” (the sparsebundle file TM uses to backup to).
    First of all, I am convinced that the second mount point that is created (in your case Volume11) is due to the fact that you already had the network drive mounted on your desktop at the time of the attempted backup. Was that the case?
    When you manually mount a network drive the system creates a mount point in the /Volumes folder (Let’s call it TMDisk ). While that exists any attempt by Time Machine to mount the same disk will created a second mount point ( TMDisk-1 )
    Nevertheless, as I have observed, this doesn't seem to prevent backups from taking place successfully, at least on the Time Capsule. And according to your Console logs it appears that your volume is being ‘remounted’ successfully.
    *”The Backup Disk Image Could Not Be Mounted”*
    The real issue is Time Machines' failure to mount the disk image (sparsebundle) contained on your network drive.
    +Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle+
    +Backup failed with error: 21+
    More often than not this is due to having the Time Machine backup disk image (sparsebundle) mounted on your desktop during a backup attempt.
    Eject the backup disk image (sparsebundle) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
    For more information, see an article on this here:
    [http://discussions.apple.com/thread.jspa?threadID=1715977]
    Alternatively, a backup disk image can fail to mount if there is a problem with your computer name.
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    Let me know if any of this helps.
    Cheers!

  • Time Machine Backups Failing w/ Error: (-36) SrcErr:YES

    Machine History: 
    2008 iMac
    2.8 GHz Core 2 Duo
    4 GB of 800 MHz DDR2 SDRAM
    Version 10.7.5 OSX
    External G-Drive 500 GB HD connected via Firewire.
    Late yesterday my iMac started acting crazy.  On reboot the machine did not come back up and was hung up on the Apple Logo.  The circular progress meter was spinning and the system would not boot into the OS.  At this point I started the system with the command key and R to get to the ulitlity menu.  At this point I initiated a full system restore back to a backup dated June 10th 2013.  The restore ran clean with no errors and the system came back up.  At this point I wiped out my G-Drive so that I could take a full backup of the system.  I partitioned the G-Drive 400 GB for Time Machine and 100 GB to manually backup photos and other files.  I created the partition and manually backup family photos since it seems that at times I've added photos into iPhoto and they don't get added into the backup sets. 
    At this point I noticed that the Spotlight Indexing job was running in the background.  The same time the Time Machine Full backup was running and initated and I'm not sure what happend.  I recieved a generic error stating that the backup could not be completed at this time.  Backups to disk will not run and recieve the same error.  It appears that there are a ton of files on my mac HD that have this Error: (-36) SrcErr:YES error.  I've tried a few things:
    Using Terminal to mv or cp the files locally on the mac HD.  This fails with I/O Errors
    Using Terminal to mv or cp the files to the backup HD connected via FireWire.  That fails with I/O Errors.
    I've confirmed that the files are readable by the application.  iMovie in this case.  I was able to play the video content.  So I belive that the files are in fact ok and good. 
    I've manually ran a full reindexing of spotlight.  I suspected that the indexing was out of sync and that Time Machine was having a hard time with the metadata.
    I've also confirmed that JPG file had this error in the /var/logs/system.log.  I was able to open the JPG with preview and iPhoto with no issues.  But, I can not copy or move the file to any locations on either the HD or the Backup HD. 
    Permissions on the files are rw-r-r.  In another case I changed them to rw-rw-rw and that still did not make a difference as I would have expected. 
    My fear is that my Mac HD is getting ready to take a DUMP literally.  Most of the stuff on the machine I don't care about however I do care about the family photo's and videos.  To this point I've been able to manually backup my photos to the external disk.  I have not yet backed up my videos.  Starting to get stressed about that.  I was about to take the PC in to Apple Care at the local store but wanted to disucss here as well.  Any help would be appreciated. 
    Excerpt from /var/logs/system.log just prior to backup failing last night.
    Jul 3 06:26:32 mikes-imac com.apple.backupd[1285]: Copied 165 files (78.0 MB) from volume Macintosh HD.
    Jul 3 06:26:32 mikes-imac com.apple.backupd[1285]: Copy stage failed with error:11
    Jul 3 06:26:32 mikes-imac mds[36]: (Error) Volume: Could not find requested backup type:2 for volume
    Jul 3 06:26:43 mikes-imac com.apple.backupd[1285]: Backup failed with error: 11
    Jul 3 07:19:15 mikes-imac xpchelper[1683]: for uid: 0 -- timeout while waiting on FSEvents flush; clearing cache.
    Jul 3 07:25:49 mikes-imac com.apple.backupd[1285]: Starting standard backup
    Jul 3 07:25:49 mikes-imac com.apple.backupd[1285]: Backing up to: /Volumes/Time Machine Backup/Backups.backupdb
    Jul 3 07:25:50 mikes-imac com.apple.backupd[1285]: 94.26 GB required (including padding), 313.25 GB available
    Jul 3 07:25:50 mikes-imac com.apple.backupd[1285]: Waiting for index to be ready (101)
    Jul 3 07:26:32 mikes-imac com.apple.backupd[1285]: Stopping backup.
    Jul 3 07:26:32 mikes-imac com.apple.backupd[1285]: Error: (-36) SrcErr:YES Copying /Users/{mac username}/Movies/iMovie Events.localized/Pre-K Graduation/clip-2010-06-17 19;24;00.mov to (null)

    This is done.  I went into the Apple store and they had me run SMART Untiliy on my machine.  There are a ton of bad sectors on my HD.  Time for a new disk. 

  • Time Machine Backup Fails - backup disk is unmounted during backup

    I've been having trouble on and off with Time Mahcine backups.  I have an iMac running Lion, an external USB HD which is my Time Machine disk.  It will run fine for a day or so and then fail with the "Unable to complete backup.  An error occurred while creating the backup folder".  If I run the Time Machine Buddy utility it shows the follwing error log:
    Starting standard backup
    Backing up to: /Volumes/Media/Backups.backupdb
    Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Media/Backups.backupdb/Kitchen size:37
    Backup failed with error: 2
    Stopping backup to allow backup destination disk to be unmounted or ejected.
    Backup failed because the destination disk was ejected or disconnected unexpectedly!
    Any idea why the backup disk would be unmounted during the backup?

    I have had a related problem.
    Over the last three-four years of using TimeMachine I have had FOUR (4) disk drives fail on me. In the first instance, the power supply failed twice. Switching from connection via Firewire to USB seemed to solve that problem.
    Then in May 2011 I bought TWO x Freecom HD 1 TB portable drives, I indicated to the Apple retailer, YooBee, expressly for use as TimeMachine backups.
    They have both FAILED for me, as per the description below, which I have filed on the Freecom support site.
    So FOUR disk drives failing over 3 to 4 years is beyond bad luck, beyond coincidence, but 'conspiracy' as Churhill might have put it. The common factor is that all four disks failed 'on watch' as being my TimeMachine drives. I am VERY ALARMED at his rate of failure, and wonder if there is a fault with TimeMachine in burning out the disks through some feature of excess use?
    I note the detailed advice here is pertinent ... but I've only just found it!
    Backup, restoring, formatting info: Apple Support Communities. (n.d.). Retrieved January 16, 2012, from https://discussions.apple.com/message/16276201#16276201 
    Message to Freecom Support Forum 2012-1-14, and YooBee.
    I was absolutely assured by my Apple Mac (YooBee, 123 Broadway, Newmarket) store that these drives would be perfect for TimeMachine backup. But to have TWO fail within 8 months of purchase is very, very, very alarming. One failing is bad luck. Two failing is more than coincidence....
    There was an alarming clicking noise from the disks.
    Disks were disconncted from USB.
    Message from Mac saying USB drive disconnected incorrctly. I DID NOTHING: Timemachine was just in the middle of doing a backup, perhaps. I was just working away when I noticed the tiny noise, above.
    I turned of Timemachine in preferences. Physically powered down and disconnected Freecom drive. Waited. Reconnected. Unable to remount. Used Disk Utility to mount, and initiated Repair.
    Message Apple disk utility
    Verify and Repair volume "MELLALIEU-01-FREECOM-HDD-1TB"
    Checking file system
    Volume repair complete
    Updating boot support partitions for the volume as required
    Error: disk Utility cant repair this disk. Back up as many files as possible, reformat the disk, and restore your backed up files"
    Another message
    Mac OS X can't repair the disk
    MELLALIEU-01-FREECOM-HDD-1TB
    You can still open or copy files on the disk, but you can't save changes to files on the disk. Back up the disk and reformat it as soon as you can.
    Well: the Freecom is not able to be remounted, even after plugging, and replugging the USB.
    This happened with TWO drives.
    And despite the suggestion to backup the files NONE are accessible.
    This is NOT what I expect to have happen with drives expressly purchased for use as TimeMachine backups.
    I managed to reformat the one that first failed, about two months after purchase. I have not attempted to reformat the latest failure-- and loose my complete Timemachine backup. Naturally, I don't use the reformatted disk for Timemachine, but a Vault for Aperture.
    Equipment specification and serial numbers:
    Freecom HD Mobile Drive xxs 1 Tb x 2
    model SSYAAA P/N 35154
    Purchased May 2011, YOOBEE, Newmarket.
    S/N 351540442100051.
    S/N 351540442100021.

  • Time Machine Backup Failed - Copy stage failed with error:11

    My TM backups started to fail on a Mac Book Pro running 10.5.8 a few weeks ago with the 'Copy stage failed with error:11' message. It seemed to happen after coming out of hibernation from clamshelling the laptop.
    This happened a few times before when I had initially set TM up so to 'fix' it I just blew away the TM backups and started fresh. I would rather not do that this time as I have accumulated 3 months worth of backups.
    My TM is on a samba share, I've searched a bit and followed a guide:
    http://blog.robberthamburg.nl/mac-osx-leopard-repair-a-time-machine-error-11-pro blem
    to try and fix the problem by deleting a .inProgress backup but this has not helped. unfortunately this has did not fix it. I had also read that there are sometimes problems with TM and Spotlight indexing so I have turned spotlight off completely. Still no luck.
    Here is a log dump of my latest backup attempt:
    Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Backup requested by user
    Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
    Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Mounted network destination using URL: smb://mdaemon@io:139/timemachine_lysithea
    Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Backup destination mounted at path: /Volumes/timemachine_lysithea
    Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
    Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 7.61 GB requested (including padding), 89.80 GB available
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:45:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:50:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:55:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:00:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:05:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:10:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:15:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:20:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:25:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:30:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:32:05 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:32:37 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:33:09 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:33:42 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:35:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:38:38 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:39:08 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:39:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:40:27 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:42:12 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:42:43 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copied 16247 files (5.9 GB) from volume Macintosh HD.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Restarting backup after linking failure.
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup destination alias resolved to path: /Volumes/timemachine_lysithea
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
    Sep 12 02:43:42 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 509.8 MB requested (including padding), 83.21 GB available
    Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copied 0 files (0 bytes) from volume Macintosh HD.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
    Sep 12 02:51:14 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
    Sep 12 02:51:15 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine disk image.
    Sep 12 02:51:18 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine network volume.
    Any help would be greatly appreciated

    mattdaemon wrote:
    My TM is on a samba share
    First problem: this is *not supported by Apple:* http://support.apple.com/kb/HT1733
    to try and fix the problem by deleting a .inProgress backup but this has not helped.
    Second problem: deleting (or changing or moving) things in TM backups via the Finder can hopelessly corrupt them.
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    These can usually be stopped by excluding the backups from any anti-virus scanning, and Spotlight indexing, at least on supported volumes. Unless you're sure you have Spotlight off entirely, try excluding your backups via System Preferences > Spotlight > Privacy.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
    Both of these appear to indicate problems on your backup drive, perhaps directory problems. For a supported one, a +*Repair Disk+* (not permissions) will often fix it. If there's a way to run that on your backups, it's worth a try.
    It's also possible there's a problem on your internal HD, so it's worth doing a +*Verify Disk+* (not permissions) on it, too, via Disk Utility. If that shows errors, you'll have to boot from your Install disc and use it's copy of DU to repair them.

Maybe you are looking for