No old backups found

Having problems with TM. the Preference panel indicates this: Oldest Backup: None and Latest BackupL None. Problem is, I've been using this TM for more than a year. In other words, it seems as if all of my old backups are gone. i had a problem that indicated "the sparsebundle is in use" and it would not backup at all. REinstalled Airport Utility 5.6, disconnected all users, unplugged the TM, and not things seem to be working, at least the TM software is verifying the backup. Still, no old backups? Suggestions????
Sally Fally

And now, after verifying the backup, it is backing up only 4.25 GB of data from my Machintosn HD, which has maybe 70 GB of files on it.
Sally Fally

Similar Messages

I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

It must have found the old backup corrupt.. so you will more than likely have little choice. You can archive off the old backup if it is still useful.
You can also verify it. See A5 http://pondini.org/TM/Troubleshooting.html
He also has some info on this problem. eg C13.

MacBook Pro crashed while deleting old backups off partitioned external hard drive. Now only recognizes windows formatted half of drive. Can the Apple side be saved?

MacBook Pro 15-inch, Mid 2010
Processor 2.66 GHz Intel Core i7
Memory 8 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GT 330M 512 MB
Software OS X 10.9.5 (13F34)
I have an external hard drive:
2 TB Seagate Backup+Desk Media
Partitioned:
1TB - Windows NTFS
1TB - Mac (sorry I can't remember the formatting, whatever Mavricks asked me to use...)
What happened:
I was erasing 3 old backups from the Apple partition and my laptop crashed part way through emptying the trash. (it has done this many times before, where parts of the screen are frozen in square blocks displaced all over the screen. Screenshot not possible unless I use a separate camera).
When I force restarted my computer (holding down the power button) neither side of the drive was accessible. After running the Disk Utility and Verifying and Repairing the Disk Permissions and the Disk Itself (for the Windows side) I was able to access the Windows partition. However, upon attempting to do so with the Mac partition it tells me that it cannot be repaired. I have found many forums discussing SIMILAR situations but none with the same and here is why:
Up until this happening I could access ONLY the Windows partition when the drive was connected to either my Apple laptop in Bootcamp Windows 7 or my HP laptop in Vista, while my MacBook could access both sides of the drive. HOWEVER, after this crash, BOTH my Windows 7 and Vista can access both sides of the drive (so My files are still all there and accessible) but my MacBook Pro swears that the Apple partition is doomed.
Since the Apple side of my laptop is my primary workhorse I really want to figure out how to fix my drive.
So Questions:
1. Anything else I can provide to the experts out there to help me get this fixed?
2. Can I custom fix this via accessing the drive on either of the Windows systems?
3. Why would it suddenly show up in Windows when it became unaccessible to Mac?
Thanks All!

UPDATE:
It has been maybe a month since this happened.
After I made this post and was checking emails, walking away from computer, and then came back my Mac partition of the External Drive has shown up on the Desktop...
So, in the ever immortal way of asking the tech to come check the issue and the issue resolving itself, perhaps I should posted on the forum sooner...
NOTE: The disk still shows up as unusable in the Disk Utility and it appears that the files are read only (cannot make a new folder on this side of the external drive)
I still consider this a volatile issue because I do not want to lose the files on this half of the partition and I have not gotten a replacement drive yet (too much data to move to my computer and then format the current drive)

Time Machine - strange behavior while deleting old backups

Not sure if this is the right place, because this is actually not on Time Capsule, but on a Time Machine on an external USB drive.
In any case, I searched the web for "time machine delete old backups" and found many discussions of various aspects of this task. My objective is to clean up a partition on a the external drive that I no longer use for active TM backups, but to retain a small set of backups in case I need to go back to them. The partition now has other uses and I need the space. My main TM backup is now on a separate Time Capsule.
So again my objective is not to remove all backups, but just most of them.
It appears that the well-discussed procedure is the following:
Go into Time Machine.
Select the Macintosh HD.
Go back to one of the oldest backups.
Click on the Gear > click Delete Backup.
This procedure will remove one Backup at a time, and it seems to take 5 - 10 minutes for each backup.
Here is what I noticed that was "strange":
You could delete a selected backup using the above procedure.
For the first selected backup so deleted, there is a confirmation dialog with a warning message that it is not undoable.
After clicking OK on the warning message, the display backs up to the "Present" backup, and the administrative password is requested.
After the administrative password is entered, the backup starts but control is passed back to the user interface, and another backup can be selected to be deleted.
However, after the second backup is selected and deleted, there is no warning dialog, and no request for the administrative password. At this point the user interface is busy and nothing more can be done until the backup delete is completed. Except that the Time Machine can be exited by first pressing Escape, then Cancel on the lower left of the screen.
If the time machine is exited, there is a Delete Backups progress dialog with a progress bar for each backup so far requested. If the second backup was requested, as in the steps above, there would be two backups.
I discovered by playing around that either you had to wait within Time Machine for the deletion to complete, or alternatively exit Time Machine. While I was not sure what was going on, I kept starting one backup, then exiting Time Machine and re-entering Time Machine and requesting another delete operation. Each time after entering Time Machine, the warning/admin password sequence occurred and I was able to exit. And then immediately re-enter Time Machine and request another backup. Only by exiting and re-entering could another delete request be made.
When out of Time Machine, I thus saw the Delete Backups dialog with any number of concurrent "Delete One Backup" progress bars.
Because of the nature of the hard links used to indicate backups, I was wondering if these multiple delete operations could possibly be hung in a deadly embrace, so I decided to only do one at a time. Some further study to see if the multiple delete operations were all able to complete would be needed to know if this would be a good way to "queue up" multiple delete requests.
Bottom line: seems like kind of an odd implementation. Would be really nice if you could select many (say 30) individual backups and delete them all at once, rather than taking 5 - 10 minutes each. Again, this is because I am trying to reclaim disk space, but not delete all the backups from a Time Machine backup set that is not in active use.
Also, the method of "queuing up" backup delete requests is kind of odd, but seems to work, with the proviso that I have not yet confirmed that doing more than one at a time actually works.

Heinz-G?uenter Arnold wrote:
since the upgrade to SL it seem that Time Machine has problems to completely remove old backups completely. The "removed" backups do not show up in Time Machine anymore, but the backup folders and part of their contents can still be seen in Finder.
Hi, and welcome to the forums.
That happens occasionally, in both Leopard and Snow Leopard, sometimes after something was deleted from the Finder, but also after an abnormal shutdown or improper disconnection of the TM disk.
Run a +*Repair Disk+* on it via Disk Utility, in your Applications/Utilities folder. If it finds errors, but can't fix them all, run it again (and again) until it either fixes them all, or can't fix any more.

Time Machine not freeing up space with manual delete of old backups

I have time machine backing up an external RAID to a Drobo with 7.2TB of total space. The total backup size as estimated by TM is 4.6TB. This setup was running fine for me for a while, until I added some internal drives full of data to my Mac Pro, and forgot to tell TM to exclude them. I didn't realize this until TM told me my backup disk was full. Fine, so I excluded those drives, and then deleted all backups of those drives, as well as going back and deleting quite a few old backups in their entirety. I even went and found about 500GB of data that I no longer needed, deleted it from my RAID and then again deleted all backups of that folder from TM. But after all this, my drive still only has about 70GB of free space on it. When I know at a minimum there should be 500GB free, if not 1-2TB free after all that spring cleaning. How can I get that free space back? It seems as if TM is holding it hostage. I should add that slowly over the few days since deleting, my Drobo free space slowly creeps up. Maybe about 10GB every hour when I go and check free space available. Is this just TM taking forever to delete the old backups, even after the computer has been restarted, shut down, etc. multiple times?
I really don't want to have to erase the entire TM drive and start over, as it takes days to backup 4.6TB of data and slows down my whole system. Any help is appreciated!

I have no direct experience with a Drobo, but in many threads about them, as with many other 3rd-party NASs, either the built-in software creates a sparse bundle, or the instructions have the user do so.
But yes, a sparse bundle is a sparse bundle is a sparse bundle , so if you can locate it via the Finder, and have permission to it, you should be able to compact it manually, per those instructions.
If not, you'll have to talk with the Drobo folks.

Getting iTunes restore to recognize an old backup

Hi,
I am hoping that you can help me: I want to get iTunes to recognise an old backup of my iPad so that I can restore it onto the iPad and retrieve some files that are precious and would otherwise be lost. Afterwards, I will want to restore my iPad's current settings.
Explanation:
I accidentally deleted my apps from my iPad while trying to back it up onto my Mac. I thought it was a good opportunity to reorder the apps so downloaded only the ones I really wanted and reorganised them. I then realised that the data for my journal for the last two years and the flashcards application into which I had laboriously typed 1000 Mandarin words and phrases had been deleted. I tried restoring from backup but found that iCloud only holds the last one or two backups but some days had already passed and my old data had been overwritten. I then looked at the iTunes backup and didn't have one; I'd asked my son's Mac expert friend to clear some space on the iMac so he had removed old backups. For a while I thought I had no chance then I remembered that my Timemachine kept old backups so I looked at this forum to find out where iTunes backups are stored and searched my Timemachine archive for the files. I have now restored the data from the mobilesync directory from a few months ago but I found that I had to create the ~/Library/Application Support/MobileSync/Backup/ directory. I put the backup files into this but the backup did not appear in iTunes. Is there a way I can get iTunes to see the backup files and restore them or is there something that will let me view the files directly?
Thanks!
Tim

Hi
I have the same problem. the back up file I want to use to restore my iphone will not "show up" in itunes. I know where to find the file (and have made a copy of it) and I know where itunes places the backup files each time itunes makes a new (incremental) backup.
What /i dont know (and WISH i did know) is how to force itunes to "see" the backup file I want it to use....
What I've tried so far:
1 moving all the "wrong" back up files out of the mobilesync folder and leaving onle the "correct" backup file in the folder - but ituness "sees" nothing, i.e. the mobilesync folder appears to itunes to be empty.
2 moving the "correct" backup file to a different folder and then copying it back into the the mobilesync folder - but itunes still won't "see" the correct backup file.
It's really really sad and frustrating. I spent from 2pm till 2 am on it yesterday ...
My mishap was caused by a failed backup due to insufficient space on my hard drive... this meant that itunes aborted the backup, I then had to make space on the hard drive and try again. I had to do this several times... anyway, I know where the "correct" backup file was eventually placed, have copied etc (as above) but nothing I do results in itunes being able to "see" it and therefore allow me to use it as the source file from which to backup my iphone.
If there's anyone out there who thinks that can help me.........???? - I'd be truly impressed and deeply grateful.

Difficulties getting old backup data to new phone

So, I thought it would be a simple thing to do - But no.I had a Xperia ZR (with Lolipop) and bought myself a Z3 compact. Before I resetted my ZR and made a backup using the backup program that the phone has in it, not PC companion. The result was a nice 800mb file on the SD-card, with all the apps, messeges, contacts and so on on it. So far so good. The major problem starts when I was about to resett all my old data to my new phone, using the exact same program on the Z3 compact. It can´t find the file at all, there is no option in restoring my old data in that app "backup & restore". All files are there in a map called ´.semc-fullbackup´ but the app can´t obviously do anything with it. A little help would be much appriciated! P.S my Sony ZR is sold, so no luck there.. Cheers

There should be another option except for the one which requires the old phone found at Xperia transfer > Sony/Sony Ericsson device > Xperia backup from computer.
I believe you're swedish so it should look like this:

Time Machine: removing old backups w/o redoing whole thing!

I've been using time machine for years now. In the past, when my backup disk has become too full, I've wiped the entire backup (delete) then created a brand new one. Why?? Because having a backup of what I have RIGHT NOW is all I want or need.
Now, all that said I would rather just prune all files not needed. Right now my 250gb mac HD has a 475gb backup file, and I have 100gb free on my mac's HD.
Is there any way to remove all old backups...or prune up to, say a week prior? I would have to imagine that this would be of some value. Reasons:
1. Save me (some) time of pruning/deleting vs doing a wifi backup from scratch.
2. I could potentially lose all of my data should my HD crash before my backup completes.
Help?

Greazy wrote:
I've been using time machine for years now. In the past, when my backup disk has become too full, I've wiped the entire backup (delete) then created a brand new one. Why?? Because having a backup of what I have RIGHT NOW is all I want or need.
Then Time Machine is not the right backup app for you. The backups of things you've changed or deleted can be very useful, for a number of things, but if you really don't want that, you're using the wrong app, because that's what Time Machine is designed to do.
Try CarbonCopyCloner or SuperDuper, to make "bootable clones." CCC is donationware; SD has a free version, but you need the paid one (about $30) to do updates instead of full replacements, or scheduling. Either is easily found via Google.
Now, all that said I would rather just prune all files not needed. Right now my 250gb mac HD has a 475gb backup file, and I have 100gb free on my mac's HD.
Is there any way to remove all old backups...or prune up to, say a week prior? I would have to imagine that this would be of some value. Reasons:
1. Save me (some) time of pruning/deleting vs doing a wifi backup from scratch.
2. I could potentially lose all of my data should my HD crash before my backup completes.
Where is your backup disk? You mention a WIFI backup, so is it an external disk connected to a Time Capsule, or Airport, or another Mac; or are you backing-up to a Time Capsule, or ??
There are ways to limit the size of TM backups, depending on what version of OSX you're on (this is the Leopard forum, but your signature says you're on Snow Leopard), and where the backups are. Once you do that, Time Machine will delete old backups automatically when it needs room for new ones.
If they're on an external HD, partition it to the maximum size you want. If they're elsewhere, tell us where, and confirm what version of OSX you're on.

Time machine eliminating all of my old backups

I have Time Machine Backing up to an external 4T hard drive. TM is also set to back up another extenral hard drive that contains just photos to the same TM drive. It's been working seamlessly. Lost some photos today on the photo drive and found them on an old time machine backup and dragged them to the external drive (the icon on the desktop, not the icon in the Time Machine backup). All good. There were about 111g left on the Time Machine external drive and the imac has about 225g of data on it. So Time Machine started eliminating old backups one month at a time and looked like it wasn't going to stop....month after month. I turned off TM when it reached 400g of available space. How much extra room does a backup require and will it just keep going - eliminating ALL of my backups? Something just didn't feel right...

If you have more than one user account, these instructions must be carried out as an 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.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to a failed backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showning, 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 (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
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.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Logic Board replaced, Time Machine wont recognize old backups

I just got my Logic Board replaced and obviously having the problem with Time Machine recognizing old backups. I looked at old forums and found the macosxhints page (http://www.macosxhints.com/article.php?story=20080128003716101) on how to fix the problem but when I try to enter cd /Volumes/Time Machine/Backups.backupdb into terminal it gives me a message saying "no such file or directory" i dont know where to go from here any help would be appreciated thanks for your time

instead of Time Machine in that command you should enter "name of your TM drive" (put the name of your TM drive there and KEEP THE QUOTES). However, as you seem to be unfamiliar with terminal you will very likely have further problems following that hint. Try this one instead
http://www.macosxhints.com/article.php?story=20081216145458979&query=%2Bfsaclctl

Since Mavericks upgrade, Time Capsule stuck deleting old backups ... for days

I have a previous generation 2TB Time Capsule shared by three of us, each with separate accounts.
I know there's not much space left on the Time Capsule and that it's therefore expected that Time Machine would make room by deleting old backups. But my account seems stuck forever on these deletions (for over 72 hours now), while the other two accounts on the Time Capsule are working just fine.
I've been through Pondini's recommendations for (a) patience and (b) finally resetting Time Machine, but on it goes.
Here is the last couple of hours of the log (filtered for this problem). The entire log for the last 72 hours is too long to post -- but the pattern is the same, with the constant deletions barely making a dent, and sometimes in fact the space available decreases.
I'd cheerfully give up on the oldest backups, but meanwhile it's been 8 days since TC has been able to complete a backup. (I have been cloning the drive daily with SuperDuper just to make sure I have a fallback until this is figured out.)
Hoping one of you can recommend a course of action.
Thanks in advance for any help...
10/28/13 8:06:51.276 PM com.apple.backupd[758]: Found 1022200 files (58.34 GB) needing backup
10/28/13 8:07:01.173 PM com.apple.backupd[758]: 75.13 GB required (including padding), 16.43 GB available
10/28/13 8:07:05.162 PM com.apple.backupd[758]: Ejected Time Machine disk image: /Volumes/edbern/EB’s MacBook Air.sparsebundle
10/28/13 8:07:05.162 PM com.apple.backupd[758]: Compacting backup disk image to recover free space
10/28/13 8:25:44.384 PM com.apple.backupd[758]: Completed backup disk image compaction
10/28/13 8:25:44.388 PM com.apple.backupd[758]: Starting manual backup
10/28/13 8:25:44.915 PM com.apple.backupd[758]: Network destination already mounted at: /Volumes/edbern
10/28/13 8:26:04.847 PM com.apple.backupd[758]: Disk image /Volumes/edbern/EB’s MacBook Air.sparsebundle mounted at: /Volumes/Time Machine Backups 1
10/28/13 8:26:05.230 PM com.apple.backupd[758]: Backing up to /dev/disk3s2: /Volumes/Time Machine Backups 1/Backups.backupdb
10/28/13 8:26:31.228 PM com.apple.backupd[758]: Event store UUIDs don't match for volume: Macintosh HD
10/28/13 8:26:31.546 PM com.apple.backupd[758]: Waiting for index to be ready (100)
10/28/13 8:27:25.289 PM com.apple.backupd-helper[112]: Not starting scheduled Time Machine backup: Backup already running
10/28/13 8:27:31.784 PM com.apple.backupd[758]: Waiting for index to be ready (100)
10/28/13 8:27:56.892 PM com.apple.backupd[758]: Deep event scan at path:/ reason:must scan subdirs|new event db|
10/28/13 8:35:43.224 PM com.apple.backupd[758]: Finished scan
10/28/13 8:35:43.241 PM com.apple.backupd[758]: Not using file event preflight for Macintosh HD
10/28/13 9:05:03.078 PM com.apple.backupd[758]: Found 1022200 files (58.34 GB) needing backup
10/28/13 9:05:16.881 PM com.apple.backupd[758]: 75.13 GB required (including padding), 31.85 GB available
10/28/13 9:05:17.689 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/03624AE5-22CE-463C-9265-CE6A8826C535 containing 4 KB; 31.85 GB now available, 75.13 GB required
10/28/13 9:05:17.700 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/7503F996-8E27-4558-9308-15FC60270865 containing 4 KB; 31.85 GB now available, 75.13 GB required
10/28/13 9:23:23.471 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/C424E6F6-EFBE-4154-A543-375E805E68C8 containing 8.3 MB; 31.86 GB now available, 75.13 GB required
10/28/13 9:28:36.239 PM com.apple.backupd-helper[112]: Not starting scheduled Time Machine backup: Backup already running
10/28/13 9:55:03.037 PM com.apple.backupd[758]: Error: Error Domain=NSOSStatusErrorDomain Code=-36 "The operation couldn’t be completed. (OSStatus error -36.)" (ioErr: I/O error (bummers)) deleting backup: /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/C434BAEA-946E-4531-BA61-74DD5A34EFF2
10/28/13 9:55:03.037 PM com.apple.backupd[758]: Deleted 3 backups containing 8.3 MB total; 31.86 GB now available, 75.13 GB required
10/28/13 9:55:03.321 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.579 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.580 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.582 PM com.apple.backupd[758]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
10/28/13 9:55:03.702 PM com.apple.backupd[758]: Backup canceled.
10/28/13 9:55:11.830 PM com.apple.backupd[758]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
10/28/13 9:55:11.831 PM com.apple.backupd[758]: Failed to eject volume (null) (FSVolumeRefNum: -110; status: -35; dissenting pid: 0)
10/28/13 9:55:11.832 PM com.apple.backupd[758]: Failed to eject Time Machine disk image: /Volumes/edbern/EB’s MacBook Air.sparsebundle

Alas, it spent the night fruitlessly.   I think I need to find a way to kill the existing backup or dismount the disk first. Sorry I'm a bit thick about all this.
10/29/13 12:39:06.822 AM com.apple.backupd[1628]: Starting automatic backup
10/29/13 12:39:07.028 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:39:07.995 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:39:11.397 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 12:39:12.969 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc243f1c0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 12:39:13.059 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
10/29/13 12:39:13.060 AM com.apple.backupd[1628]: Waiting 60 seconds and trying again.
10/29/13 12:40:24.403 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:40:24.792 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:40:27.642 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 12:40:29.209 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc27275c0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 12:40:29.324 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
10/29/13 12:40:29.325 AM com.apple.backupd[1628]: Waiting 60 seconds and trying again.
10/29/13 12:41:40.533 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:41:41.252 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 12:41:44.549 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 12:41:46.208 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc26090d0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 12:41:46.309 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
10/29/13 12:41:46.310 AM com.apple.backupd[1628]: Giving up after 3 retries.
10/29/13 12:41:46.350 AM com.apple.backupd[1628]: Backup failed with error 31: 31
10/29/13 1:44:01.616 AM com.apple.backupd[1768]: Starting automatic backup
10/29/13 1:44:01.649 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:44:02.604 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:44:07.254 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 1:44:08.881 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af9531a70 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 1:44:08.962 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
10/29/13 1:44:08.962 AM com.apple.backupd[1768]: Waiting 60 seconds and trying again.
10/29/13 1:45:20.105 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:45:20.536 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:45:23.526 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 1:45:25.145 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af97030e0 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 1:45:25.280 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
10/29/13 1:45:25.280 AM com.apple.backupd[1768]: Waiting 60 seconds and trying again.
10/29/13 1:46:36.511 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:46:37.340 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 1:46:40.510 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
10/29/13 1:46:42.150 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af9608030 {MessageParameters=(
    "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
10/29/13 1:46:42.195 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
10/29/13 1:46:42.195 AM com.apple.backupd[1768]: Giving up after 3 retries.
10/29/13 1:46:42.198 AM com.apple.backupd[1768]: Backup failed with error 31: 31
10/29/13 2:49:46.227 AM com.apple.backupd[1880]: Starting automatic backup
10/29/13 2:49:46.301 AM com.apple.backupd[1880]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 2:49:47.381 AM com.apple.backupd[1880]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
10/29/13 2:49:50.418 AM com.apple.backupd[1880]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35

Are old backup files saved or deleted in iTunes

I had to restore my Iphone back to factory. The backup file I created was too big to restore and the Verizon tech (who I foolishly let take over my computer) backed up the empty phone over the old backup file. I found a program to restore the original backup data, but it's been overwritten by the recent backup. Does iTunes delete the the old backup files or store them in a different folder?

iTunes only keeps one normal backup, per iOS device. As you've found out, its an incremental backup in that data that has changed or deleted is added or removed from the backup. Unless you backup your computer, your data is gone.

After Migration Assistant, Time Machine refuses to use old backups

I've got to say I'm pretty disappointed with Time Machine.
I just dropped $2,000 on my second-ever Mac, a 15" MBP (Core i7 2GHz, 4GB RAM, 500GB 5200rpm hard drive, the stock low-end 15" config). From what I'd heard about Migration Assistant, I believed it would easily move my stuff over to my new Mac. For the most part it did, but a few things didn't transfer. Other posts on the topic detail them accurately - Desktop icon layouts, some settings, Growl, etc.
I told Migration Assistant to use my Time Machine backups, which have been happening without incident for a long time. My oldest backup is December 2010.
Now that my new MBP is about 99% set up like my old MBP, I am having a problem with Time Machine.
I get the error "Time Machine could not complete the backup. This backup is too large for the backup disk. The backup requires 355.61 GB but only 176.44 GB are available."
Looking at the Time Machine drive in Finder, I found that Time Machine is trying to create a new folder for backups and do a full backup. Where there was once one folder, "[My Name]'s MacBook Pro," there is now an additional folder, "[My Name]'s MacBook Pro 2." Time Machine is trying to back up into that second directory.
Now, I get it that this is a different computer. But really, if I use Migration Assistant to restore my Time Machine backup, I think it would be safe for OSX to assume that I want to continue using those backups. What is especially disappointing for me is, there were things that Migration Assistant did not restore properly. I probably haven't found them all. That makes it CRUCIAL that I have my Time Machine backups, but it seems that Apple thinks it's perfectly normal for me to want to FORMAT my Time Machine drive after Migration Assistant did a half-*** job of migrating my data. I need those backups now more than ever.
I do also have an online backup, but I still don't feel very comfortable destroying six months of local backups just to make Time Machine work again. Both MBPs were running the same (latest) version of Snow Leopard, so it stands to reason all that needs to happen is a very small incremental backup.
I have been Googling for hours. All I've found is a procedure for 10.5 that doesn't work in 10.6 where I get down into the Terminal and change a MAC address in a file on the Time Machine volume. But that's it. In fact it seems like there's no answer.
Come on Apple, you do everything else better than the competition. Why do I have to nuke six months of backups or buy a new 2TB external drive to make Time Machine work again? I assure you I want to continue making incremental backups against my old Time Machine backups, and promise to hold you not responsible should I screw something up by grabbing an old system file or something from February.
Would appreciate any help anyone could offer.

Did you use Setup Assistant when your new Mac first started up, or skip that, create a user account, then use the Migration Assistant app in your Applications/Utilties folder?
If you used Setup Assistant, when you started your first backup you should have gotten the message in #B5 of Time Machine - Troubleshooting. It sounds like you didn't (or chose Start New Backup). And no, the Leopard procedure doesn't work on Snow Leopard. That's what #B5 is for.
Usually, if you use Setup Assistant, Time Machine will still say it's going to do a full backup, and make room for it, but actually do an incremental backup (very, very slowly).
Either way, it usually deletes a lot of old backups. We're hoping that will be fixed in Lion.
Once it's decide to make a new backup, there's no known way to prevent it.

Time machine is deleting all my old backups after moving to different iMac

Hi - I had to move my data to a different machine and so I prepared a different iMac (early 2008). This is what I did:
I booted into Snow Leopard from my DVD
erased the HD
installed SL 10.6
booted into SL
ran software update to upgrade to 10.6.8 (to get the App Store)
installed Mountain Lion 10.8.2
used Migration Asistant to restore all my data, apps, and settings from my time machine backup
This all worked fine and at some point time machine asked me whether to inherit the time machine history. I confirmed this and all seemed fine until I noticed that time machine was backing for a long time and a lot of space was being freed on the time machine volume. I found that it was deleting all my old backups. Before I had data going back to 2010 but now I only have backups left from JAN 2012 onwards.
After some searching I found the excellent Pondini time machine site and performed the actions under B6 ("Reconecting" to your backups):
exxi:~ michael$ sudo tmutil inheritbackup /Volumes/tm2/Backups.backupdb/exxi
Password:
exxi:~ michael$ sudo tmutil associatedisk -a / /Volumes/tm2/Backups.backupdb/exxi/2013-02-03-150320/exxi_hd
I restarted the backup after applying the command above but it still is deleting old backups. I tried the same comand by associating it with an older backup but still it keeps deleting my backups.
What can I do to stop it from erasing all my backups?
Cheers
Michael

Just found this info in the Backup dashboard widget:
Starting manual backup
Backing up to: /Volumes/tm2/Backups.backupdb
Inheritance scan required for /, associated with previous UUID: [deleted]
Event store UUIDs don't match for volume: exxi_hd
Deep event scan at path:/ reason:must scan subdirs|new event db|
First backup after disk inheritance for / - complete scan required
Finished scan
Found 839161 files (154.88 GB) needing backup
188.83 GB required (including padding), 145.37 GB available
Deleted backup /Volumes/tm2/Backups.backupdb/exxi/2012-03-04-160328 containing 2.25 GB; 147.63 GB now available, 188.83 GB required
Deleted backup /Volumes/tm2/Backups.backupdb/exxi/2013-02-05-181442.inProgress/57E7F008-929C-4 DF8-B062-F034FEE7A606 containing 4 KB; 147.63 GB now available, 188.83 GB required
Deleted backup /Volumes/tm2/Backups.backupdb/exxi/2013-01-07-112745 containing 130.8 MB; 147.76 GB now available, 188.83 GB required
Removed 3 expired backups so far, more space is needed - deleting oldest backups to make room
Deleted backup /Volumes/tm2/Backups.backupdb/exxi/2012-03-11-191620 containing 2.08 GB; 149.86 GB now available, 188.83 GB required
Removed 4 expired backups so far, more space is needed - deleting oldest backups to make room
Backup deletion was canceled by user
Deleted 4 backups containing 4.46 GB total; 149.86 GB now available, 188.83 GB required
Backup date range was shortened: oldest backup is now Mar 31, 2012
Backup canceled.

Time Machine does not completely remove old Backups

Hi all,
since the upgrade to SL it seem that Time Machine has problems to completely remove old backups completely. The "removed" backups do not show up in Time Machine anymore, but the backup folders and part of their contents can still be seen in Finder.
The number of expired backups not removed is growing. I know one should not fiddle around with backups in Finder or Terminal - but the system does not allow me to remove any of the files/folders anyway.
Here is part of the log:
Found partially deleted backup - trying again to delete: 2009-08-06-211832
Error -47 deleting backup: /Volumes/Drobo/Backups.backupdb/MacBook Pro HGA/2009-08-06-211832
Deleted backup /Volumes/Drobo/Backups.backupdb/MacBook Pro HGA/2009-08-06-211832: 1.75 TB now available
Post-back up thinning complete: 5 expired backups removed
Backup completed successfully.
Any suggestions?
Thank you for helping
Heinz
Message was edited by: Heinz-G?uenter Arnold

Heinz-G?uenter Arnold wrote:
since the upgrade to SL it seem that Time Machine has problems to completely remove old backups completely. The "removed" backups do not show up in Time Machine anymore, but the backup folders and part of their contents can still be seen in Finder.
Hi, and welcome to the forums.
That happens occasionally, in both Leopard and Snow Leopard, sometimes after something was deleted from the Finder, but also after an abnormal shutdown or improper disconnection of the TM disk.
Run a +*Repair Disk+* on it via Disk Utility, in your Applications/Utilities folder. If it finds errors, but can't fix them all, run it again (and again) until it either fixes them all, or can't fix any more.

No old backups found

Similar Messages

Maybe you are looking for