Time machine backup verification fails

My Macbook has been connected via Time Machine to a new WD Mybook Live 2 TB NAS for some 2 months. All seemed OK, with hourly, daily, etc., backups taking place.
But after the first month I received a ".... Time machine must create a new backup for you" message. Clicking the "start new backup" button erased all previous backups on the WD NAS & then started (again, apparently completing sucessfully) a complete new backup. A couple of days ago (one month further) the same problem occured again, indicating that the fault is permanent. Can anyone help me in solving this?
Checking various fora, the error message seems to indicate that the automatic monthly verification by Time Machine failed to verify the integrity of the backups but that there could be many possible reaons for the failure. I have checked all the obvious ones, but with no success.
The WD Mybook is correctly formatted. Via Finder I can browse all old backups (until Time Machine defines them as "faulty") & I can visually verify that the old data backed-up is indeed correct. The WD NAS is new & up to date.
I have completed a new backup &, using "Time Machine Buddy", have checked the status of this (latest & only) backup image on the WD drive. The information is meaningless to me but it seems to indicate that this backup, too, is faulty. See screenshot below. Thanks in advance for any help.

Pondini,
#C13 didn't give anything new to what I'd done. I believe it could be a bug in Time Machine. Saying so because the problem was fixed and didn't happen again.
I found that when the first backup was made across mid-night, there would be a problem. Also, transfer by a Windows 7 32-bit give slow network performance. Thus, I changed the PC with a Windows 7 64-bit, instead of 32-bit, the Gigabit Ethernet throughput sped up 3-4 times, the first backup completed in 2-3 hours before mid-night.
With the new initial backup done within the same day, I didn't get the error anymore in the last 3 weeks.

Similar Messages

Since upgrading to Lion, my time machine backups are failing - error message: The backup disk image "/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska's MacBook.sparsebundle" could not be accessed (error -1). Any ideas?

Since upgrading my Macbook to Lion, the time machine backups are failing - error message: "The backup disk image “/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska’s MacBook.sparsebundle” could not be accessed (error -1)." I have rebooted the TIme Capsule and it worked OK, but don't want to do that every time. Any suggestions? Thanks

Any new info on this?
I had the exact same problem and went crazy and spent a hecka lot of time trying to deal with my brand new 2TB Time Capsule and almost brand new MacBook Pro. Then I thought I fixed it...and I tried SO MANY things, I don't really know what did it...except taking out any apostrophe's in names of stuff that Apple puts in there...BUT...now it's back.
Grrr...

Upgraded to Mavericks and time machine backups keep failing.

I upgraded to Mavericks a few days ago and now I find my time machine backups keep failing. I first tried turning off the power to the time machine then turning it on again and I managed to get one complete backup but that took over 20 hours to complete.
The time machine backup mode never seems to get beyond " preparing backup" then showing the message "backing up failed, disc already in use"
The time machine backup worked fine before I upgraded, is there a way round this problem or will I have to go through reloading the time machine as if it were a new piece of equipment?
My wife's iMac is still on mountain lion 10.8.5 and the backups on the same Time Machine work fine.
Any help would be gratefully received
Greg

Hi,
I have exactly the same problem.
MBP 2011 running 10.9 named "ebook"
MacMini running 10.8.5 server with TM share
everything works fine UNTIL for some reason the MBP is interrupted during a TM backup ...
After that I get the disk already in use error !
Rebooting the MBP wont help, but I narrowed the problem down ...
Looking on the Mini server I noticed :
- the TM backup user stays connected over AFP, even after several hours of inactivity and a couple of reboots of the MBP. Killing the AFP connection works, But problem stil continues !
- looking on the MBP with "lsof | grep ebook" showed me that the SparseBundles were still in use by the AFP process ... Using the Server control panel and restarting AFP solved that ...
After restarting the AFP process the remote TM Backup started to work again !
A couple of days later, the same problem occurred again, fixed it by this work around ...
I hope there will be a more permanent solotiun for this !

My Time Machine backup keeps failing...how do I find out why?? MacBook Pro 5,1 OS 10.5.8, 6GB ram backing up to new OWC Mercury Elite-AL Pro 2TB

Forgive my clumsiness ---
My Time Machine backup keeps failing...how do I find out why?? MacBook Pro 5,1 OS 10.5.8, 6GB ram backing up to new OWC Mercury Elite-AL Pro 2TB

Have you formatted the disk to Mac OS Extended (Journaled)?
Caio.

My Time Machine backup keeps failing. I get a message the "Volume has the wrong case sensitivity for a backup". Please advise.

My Time Machine backup keeps failing. I get a message the "Volume has the wrong case sensitivity for a backup". Please advise.
Thanks, Howard

You can change the case sensitivity of the sparsebundle.. but I really doubt the error is real.
See A8 here.
http://pondini.org/TM/Troubleshooting.html
The sparsebundle should have case sensitivity turned on.
I cannot even fathom how it could have changed.
Let me recommend before you start fooling around with the sparsebundle.
Do a full network start.
Power everything off.. start up modem.. wait 2min.. power up the TC.. wait 2min.. power up any other network gear like switches.. wait..
Now power up the computer and try it.
If the error is the same.. I would do a factory reset of the TC.. give it all short names, no spaces and pure alphanumeric. Then reset TM .. see A4 in the same reference as above.. and do a verify of the backups.. A5 above and try the backup again..
No luck..
Then erase the TC and start over.. it is sometimes necessary as TM does get itself in a knot.

My time machine backup keeps failing

My Time Machine Backup keeps failing . Does anyone know what I should do

Launch your console program (located in the utilities folder) and click on all messages in then left column then type "backupd" in the filter box in the upper right. Read the messages, it may give you a clue as to what's causing the problem.

I had my hard drive replaced and since my Time Machine backups say failed

I had my hard drive replace and since my Time Capsule backups are failing. The exact message is:
The backup was not performed because an error occurred while copying files to the backup disk.
The problem may be temporary. Try again later to back up. If the problem persists, use disk utility to repair your backup disk.

No, replacing your hard drive has nothing to do with it. There is a problem with your backup drive. As far as Time Machine is concerned replacing a drive is no different than buying a new computer. Time Machine will need to make a brand new backup from scratch.
If you have a large enough backup drive this may not be a problem. Otherwise, you may not have sufficient space to maintain a new backup and keep the old one. So, I would suggest under the circumstances that you erase your backup drive, then start a new Time Machine backup from scratch.
Drive Erase
1. Open Disk Utility in your Utilities folder.
2. After Disk Utility loads select the volume you wish to format from the left side list. Click on the Erase tab in the Disk Utility main window.
3. Set the format type to Mac OS Extended (Journaled.) Click on the Erase button and wait until the process has completed.
For additional help with Time Machine: Visit Pondini's Time Machine FAQ for help with all things Time Machine.

Restore from Time Machine backup is failing

The internal drive on my daughter's iMac has failed for the second time in less than two years. I'm not able to restore from the Time Machine backup. The Time Machine restore process failed last time as well. Not surprisingly I'm now questioning whether Time Machine is an appropriate backup solution.
First question: *Is Time Machine a reliable backup and restore solution?*
- I get no errors whatsoever during backup from Time Machine
- Have yet to successfully be able to restore system (TM is 0 for 2 for us)
Second question: *Is it an issue with my setup?*
Based on the Macs and other items I already had, the setup that the local Apple store recommended to me for backup is what I followed. Here's a summary:
- 4 Macs on a network with Airport Extreme for router/wireless access
- Mac mini with 10TB of external storage has one 2 TB drive setup as a centralized Time Machine drive, which all the Macs on the network connect to
Backups all work with no error messages. Restoring individual files here and there through Time Machine has worked fine. Never really needed, but I tested it a few times from each Mac just to ensure everything was working fine.
Unfortunately, when my daughter's iMac internal drive failed I discovered that the restore not work. First issue was that restoring the system during OS X install was not an option because I was not able to get it to use the network drive. I was told to go ahead and install OS-X and then use the migration assistant, which unfortunately didn't work. Summary of what happened:
- My account on the iMac was successfully restored
- The main account with all the critical data (my daughter's) was created, but none of her data (iTunes music, school work, photos, etc) were restored
- No error message at the end of the restore
I know the Time Machine backup for her account was working as I had specifically checked to make sure that her iTunes music and photos were included in the backup just a week ago. Since the backup was being done to a drive connected to another Mac on the network, her iMac's backup was stored as a sparsebundle. In speaking with Apple support this morning, they had me try to mount the backup by double-clicking on the sparsebundle, which results in an error message indicating that it is corrupt. ARG!
After two failed restores, I'm convinced I need to change the setup either moving to drives directly connected to each Mac (seems like a waste) using Time Machine or switch to another backup tool.
What are your recommendations?

It may be helpful for others for me to post the approach I've decided to take, which seems to be working well.
Background:
I've confirmed with an Apple genius and with support, that the likely issue with both of the failed TM restores is that the TM backup was corrupted by the drive failures. Files get corrupted and are backed up to the drive. That is why in both cases it is the specific account that was running (also the highest priority for restore) is the one that is corrupted.
In nearly 3 decades of computing, I've yet to ever need to restore a single file or folder that I accidentally deleted. It's just not a scenario I care about. TM seems to fit this requirement well and has a very cool user experience to do it. Unfortunately, it also seems to have a tendency (0 for 2 in my case) to fail at restoring after drive failure.
Decision: no TM in my back up approach.
My primary need is for backup in case of drive failure. I also have some files that are extremely important that I want redundant backup for.
Decision:
1. ChronoSync for bootable backup clone of drives scheduled monthly and done over the home network. Can easily be triggered manually if there is a big change (SL install, etc) that I want to make sure is included
2. ChronoSync based sync of just critical files to a shared network drive that syncs daily. This is actually a large amount of data and includes family photos (Lightroom catalog and all photos), iTunes libraries, PLEX media library and other user created files.
Pluses:
1. Allows me to keep drives centrally located, which is definitely preferable for me
2. Easy rotation of drives with critical files for offsite storage
3. Over the network sync is fully supported by ChronoSync
4. Easy yet highly configurable UI. Unlike with TM I'm finding I can get the software to do precisely what I want, when I want.
Cons:
1. $40 cost for ChronoSync
I also looked at SuperDuper and Carbon Copy Cloner.
I tried implementing the above first with SuperDuper, but found the setup confusing and the overall execution and sync was not what I expected. For example, SuperDuper encountered some file errors and just halted the sync as a result.
I tried Carbon Copy Cloner next. The setup was more intuitive than SuperDuper; even though the UI is not as polished. I kept the offending files on the drive to see how CCC handled them. It did much better in that it identified the file issues, but completed the sync for the rest to the files on the system. Clear error message at the end with summary information and the ability to look at the details in the log.
Since I wasn't thrilled with either SD or CCC, I decided to check out ChronoSync. For me, it does a very good job of presenting a simple UI with the ability as need arrises to get in to adjust and fine tune the specifics (options, configuration, schedule, etc) to precisely what I want. Scheduling, including sequencing, is very well done. Performance was the best of the three. Full cloning and incremental sync/backups with ChronoSync were the fastest. Not really an issue for me, but still a plus. A big plus for ChronoSync was that it did by far the best job of maintaining file permissions. SuperDuper did the worst. For some reason after all three uses of SuperDuper with the backup approach above many of the original files had user and file permission changes. For example, user name was "Rachel" with Read/Write access. After sync/clone, user became "_unknown" with read/write access. CCC did a better job; though I did have a number of issues when using cloned drive to boot (these were resolved) and with restore some file permissions were not maintained.
I really think Apple (at least retail and genius employees) should be clearer about the limitations and issues with TM. After my first failed restore, I was told it was an unusual and very rare case. I was assured that the approach (including using a network drive was fine). With a second failed restore from TM, it became crystal clear in my opinion that this is not a very rare occurrence; and that there are fundamental aspects of TM that make it susceptible to backup corruption when a drive fails.
TM is a sexy solution for incremental file backup and restore when you accidentally delete a file or folder. If that's what you need, go for it. As part of a backup solution for drive failure? I just don't see the value UNLESS you want to have incremental hourly, daily, weekly, monthly backups that you can use for accidental deletions. The accumulation of all those snapshots ends up taking up a fair bit of space. I was surprised at my actual backup storage needs in my switch to the above approach.
Your needs are likely unique to you, so your mileage may vary. This is just my perspective after a fair bit of pain and a lot of discussion, reading and testing.

Time Machine backups suddenly failing with error 109 (console errors inc.)

I've been using Time Machine over my Airport Extreme Base Station for months without a single error, and all of the sudden it fails constantly with the error:
*The backup disk image “/Volumes/TARDIS-1/Derek’s iMac_001f5bf60eb1.sparsebundle” could not be accessed (error 109).*
I've tried selecting the drive again since it's mounted fine. It's mounted as TARDIS, not TARDIS-1, which I thought was a clue to the problem until I went to the Console to see all of the errors:
9/15/09 Sep 15 - 8:10:16 AM com.apple.backupd[12333] Attempting to mount network destination using URL: afp://[email protected]/TARDIS
9/15/09 Sep 15 - 8:10:16 AM com.apple.backupd[12333] Mounted network destination using URL: afp://[email protected]/TARDIS
9/15/09 Sep 15 - 8:13:35 AM com.apple.backupd[12333] Failed to mount disk image /Volumes/TARDIS-1/Derek’s iMac_001f5bf60eb1.sparsebundle (DIHLDiskImageAttach returned: 109)
9/15/09 Sep 15 - 8:13:35 AM com.apple.backupd[12333] Giving up after 3 retries.
9/15/09 Sep 15 - 8:13:41 AM com.apple.backupd[12333] Backup failed with error: 21
9/15/09 Sep 15 - 8:13:41 AM com.apple.backupd[12333] Ejected Time Machine network volume.
I've seen others say that Time Machine quit working after updating to Snow Leopard, but i've been running it since launch and the problems only appeared yesterday. Ideas?

I'm not sure why you call it a "phantom" drive, because I was quite intentionally connected to that network drive. In any case, I did as you recommended, in case that was the issue (though over the months I've often been connected to the network drive). Sadly, no dice.
9/15/09 Sep 15 - 8:50:18 AM com.apple.backupd[13136] Starting standard backup
9/15/09 Sep 15 - 8:50:18 AM com.apple.backupd[13136] Attempting to mount network destination using URL: afp://[email protected]/TARDIS
9/15/09 Sep 15 - 8:50:19 AM com.apple.backupd[13136] Mounted network destination using URL: afp://[email protected]/TARDIS
9/15/09 Sep 15 - 8:54:07 AM com.apple.backupd[13136] Failed to mount disk image /Volumes/TARDIS/Derek’s iMac_001f5bf60eb1.sparsebundle (DIHLDiskImageAttach returned: 109)
9/15/09 Sep 15 - 8:54:07 AM com.apple.backupd[13136] Waiting 60 seconds and trying again.
During the step "Making backup disk available..." in the Time Machine preference pane, looking in Volumes, I have:
lrwxr-xr-x 1 root 1 Sep 10 19:48 Macintosh HD -> /
drwx------ 13 root 398 Mar 10 2009 TARDIS
drwxr-xr-x 1 derek 12288 Mar 5 2009 Untitled
So it's properly connecting to TARDIS, it would seem, as root.

Time Machine backups always fail

Hello,
I have been trying for a week to get time machine working with my time capsule and it just wont do the initial backup. It starts out fine but then after so many gigs have been tranferred (anywhere from 10 -20 of 70 total) it just fails. If I try to start it again it shows it going from 1kb to 10mb to 35mb at which point it always fails again. I have tried different suggestions from around the forum but none of them have worked. I have even tried to backup to a different external hard drive over usb and it still gives the same error.With the time capsule I have tried over wireless and ethernet with same results.
please help

I am having the same issue. I just purchased a new iMac and transferred my data from my MacBookPro during initial startup. I'm guessing there is a file that Time Machine does not like. My plan is to reinitialize my iMac to factory and, instead of transferring data, I will re-install inidividual programs. Any suggestions to make this less painful would be helpful.
To initial poster: sorry I don't have an answer. Hopefully there is an answer out there for both of us. Thank you!

Time Machine backups keep failing

My backups to external disk keep failing; it shows only 100 MB of available space. OK; Fine; so I tell it NOT to back up a number of extra folders; in an attempt to add extra space; but I can't change that 100 MB number, no matter what I do. Is there a fix. Should I repair the external disk?
thanks
Message was edited by: raspberryaddiction

Are you running Leopard or Snow Leopard? You've posted in the Snow Leopard forum, but your signature shows 10.5.3, and the handling is different.
If you're on Leopard, go to +Time Machine Preferences > Options+ and remove the check from the +Warn before old backups are deleted+ box, and try again. Time Machine will delete your oldest backup(s) to make room for new ones, if it can.
If it still fails, or you're actually on Snow Leopard, see #C4 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).

Time Machine backup drive failed. Now what?

I bought a new drive and need to get my Time Machine files off the old failed drive. I'm sure there are plenty of discussions about this but I can't find any. (I so dislike the new design for the support communities.)
The old drive sometimes lets me access TM so I want to take advantage of one of those times to get everything across. I know it is a very slow process if it can be done.
Any suggestions?
Thanx

Jane Garcia wrote:
I may try Data Rescue but I may have another solution if I can make this work. I managed to get the backup drive to mount on my desktop--it's amazing what shaking the thing can do!--and it has two folders: Backups.backupdb and lost+found. I tried to copy the first one onto my desktop but it has 37,000 files and there isn't enough room.
If you've been backing-up your entire system, it should have several hundred thousand files, minimum.
The very existence of the lost+found folder means there's trouble.
Is there a way for me to hook up the new external backup drive and the old one and drag those two folders from the one to the new without having to go via my own hard drive?
Doubtful it will work; if the backups are damaged, as they certainly appear to be, the copy will fail.
Also, if this works, doesn't that mean that any TM backups onto the new external drive will co-exist with the old folders as opposed to absorbing them into the new TM backups?
If the backup completes successfully (highly doubtful), you should be able to continue backing-up to the copied Backups.backupdb folder.
Your best bet is to simply put the old drive "on the shelf" and let TM start fresh on the new one. You can always view and restore from the old ones (at least from the un-corrupted parts of it), via the Browse... option, per Time Machine - Frequently Asked Question #17.

Time machine backup keeps failing on specific folders

Hi,
I have checked the forum and tried all relevenant suggestions, unfortunatly to no avail. I was wondering if any users would have any sparks of genius and point me in the right direction....
I currently run time machine with an apple time capsulae and my Imac, it seems to run for most files and folders ok but will fail on the microsoft user data folder (with the NO copy error in console) as well as a few other random ones (such as the parralell virtual machine). As this stops my backups I have excluded them and it runs fine for now, although its not Ideal as my e-mails or virtual machine is not backuping up (these are the most important). i have check my friends mac and his time machine seems to backup completely and fine.
Any ideas, as the reason I bought the time capsule is to have the best backups available.
Thanks in advance.

Hi,
I have checked the forum and tried all relevenant suggestions, unfortunatly to no avail. I was wondering if any users would have any sparks of genius and point me in the right direction....
I currently run time machine with an apple time capsulae and my Imac, it seems to run for most files and folders ok but will fail on the microsoft user data folder (with the NO copy error in console) as well as a few other random ones (such as the parralell virtual machine). As this stops my backups I have excluded them and it runs fine for now, although its not Ideal as my e-mails or virtual machine is not backuping up (these are the most important). i have check my friends mac and his time machine seems to backup completely and fine.
Any ideas, as the reason I bought the time capsule is to have the best backups available.
Thanks in advance.

Time Machine Backup Consistently Failing

Hi, I've been unable to back up my MacBook for several weeks now. I've tried repairing the backup partition on Time Capsule, deleting the .plist file, and restarting the Time Capsule and nothing has helped. Here is the most recent message on Time Machine Buddy:
Starting standard backup
Attempting to mount network destination using URL: afp://Kit%[email protected]/Data
Mounted network destination using URL: afp://Kit%[email protected]/Data
Disk image /Volumes/Data/Kit's MacBook_0017f22a8caf.sparsebundle mounted at: /Volumes/Backup of Kit's MacBook
Backing up to: /Volumes/Backup of Kit's MacBook/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:must scan subdirs|new event db|
No pre-backup thinning needed: 13.64 GB requested (including padding), 749.24 GB available
Indexing a file failed. Returned 200 for: /Applications/Canon Utilities/MP Navigator EX 2.0.app, /Volumes/Backup of Kit's MacBook/Backups.backupdb/Kit's MacBook/2009-11-16-211117.inProgress/89CD17C3-7DFB-4B04-9AD3-FBB2818A6CBE/Macin tosh HD/Applications/Canon Utilities/MP Navigator EX 2.0.app
Aborting backup because indexing a file failed.
Stopping backup.
Copied 38 files (26.7 MB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11
Ejected Time Machine disk image.
Ejected Time Machine network volume.
Any suggestions? Thanks!

kit86 wrote:
Thanks for the suggestions. I excluded the file, and the backup actually progressed beyond "calculating changes," but then it failed because of another file in my Applications folder. I excluded that file, and the backup then failed again (yet another file in Applications).
That's an indication the problem is not with those files, but something wrong with your TC, or communicating with it (Applications is the first folder backed-up). I would suggest doing a +*Verify Disk+* on your internal HD, though, just to rule that out.
I doubt that the Time Capsule hard drive is failing, because my wife's laptop still backs up to the same Time Capsule without any problem. Maybe my partition on the drive is messed up?
It's possible, if there's a bad section of the disk that happens to be where TM is trying to add to your sparse bundle (since your sparse bundle passed +*Verify Disk).+* But it looks more like the data is getting garbled somewhere, then TM can't deal with it.
How are you connected to the TC? If via WIFI, try it while connected via Ethernet if you can (it'll also be faster for the big backup TM's trying to do). It isn't supposed to make a difference (OSX and your TC are supposed to be smart enough to deal with WIFI problems), but it might rule out signal problems.
If all else fails, you may have to delete the sparse bundle containing your backups and let TM start fresh.

Time machine backup error failing

I have been using time machine for nearly a year now and has proved very usefull in restoring my data when i had 2 hard disk crashes,and replaced and 1 motherboard failure before apple replaced the computer. It really gives great peace of mind insurance.
Anyway yesterday th backup failed with simple error message. i tried a couple of times again, same failure at same point. I tried a complete new backup to different disk but this also failed.
This is a transcript from console at time of failure
what do i need to do to fix
thanks
Paul
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Error: (-36) SrcErr:YES Copying /Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to (null)
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Error: (-36) SrcErr:NO Copying /Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to /Volumes/Time/Backups.backupdb/Paul Cathcart’s Computer/2008-10-25-145059.inProgress/EA7D8166-5CBC-49A6-9E35-DE608F36D194/Maci ntosh HD/Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Stopping backup.
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Error: (-8062) SrcErr:NO Copying /Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to /Volumes/Time/Backups.backupdb/Paul Cathcart’s Computer/2008-10-25-145059.inProgress/EA7D8166-5CBC-49A6-9E35-DE608F36D194/Maci ntosh HD/Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Copied 1406 files (679.3 MB) from volume Macintosh HD.
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Copy stage failed with error:11
Oct 26 10:09:45 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Backup failed with error: 11
Oct 26 10:11:53 paul-cathcarts-macbook-pro SyncServer[325]: SyncServer: Truth vacuumed. Next vacuum dat

Hello,
I have the same problem with Time Machine failing on the same database file. I believe it's more linked to the size of the file rather that on a corruption of it. I ran the repair tool of Microsoft (ou just need to depress the option key while starting the application) and the file is fine.
On my mac the file is 5 GB and I strongly believe that backinp up such a large file on a network filesystem like my Time capsule it's a challenge.
Any comment on that ? What is the maximum file size that the backupd procee can handle safely ?
Regards
Eric

Time machine backup verification fails

Similar Messages

Maybe you are looking for