Time machine has created a new sparse bundle

I have booted my new Macbook from my time machine back up. Time machine has created a new sparse bundle and I cannot access the previous backups. Is there any way to make time machine to use the previous sparse bundle? Thanks, Karl

Use the old backups to continue backups or use them for migration etc..
If you have a new Mac then continuing to use the same backup is not recommended..
Info you can see here..
B5 and B6 http://pondini.org/TM/Troubleshooting.html
I do not think it is good idea.. however you can access the old backup to get files if you need them.
See Q17 here.
http://pondini.org/TM/FAQ.html

Similar Messages

Getting this error: Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.

I keep getting this error on my new Macbook Pro w/ Retina.
"Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you."
Connected to a wifi network and QNAP storage system. There are 5 computers on this network, and each backs up just fine. The issue is isolated to this one machine.
This error shows up every week or so.

A third-party NAS is unsuitable for use with Time Machine, especially if it's your only backup. I know this isn't the answer you want. I know 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.)

Time Machine would create a NEW backup

Hello,
sorry for my bad english, I'm not a native speaker.
I'm useing Mac OSX 10.7.3
Since a few days, I've some trouble with Time Machine. When TM would create a new backup in the normal hourly loop it creates the following message:
Time machine has completed the review of its backups. To improve the reliability time machine must create a new backup. (i hope it's the correct translation in englich)
Now I've to options:
1. I can create a new backup later
2. create a new backup
Does anyone knows what is wrong? I don't want to create a new backup, I want to use the old one.
I still have enough space on my backup volume. I'm using the Airport Extreme and a WD hard drive.
Thank you for your assist.
David

Unfortunately, the issue is that the wireless connection isn't fast enough. The error is saying that basically its going to take too long to do the work.
Not sure how apple makes the time capsule faster,but apparently it works.
Apple suggested configuration is either by a direct USB or FireWire connection, or use a time capsule.
Linc is correct in his last post. You can actually plug in your USB drive at random intervals and time machine will see it and do its thing. This will probably work better in the long run, even though you haven't had any issues up until now.

Time Machine must create a new backup for you

getting this error message Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you. don't want to lose the history off my backups how can i fix this without losing any backups.

You really can't.
That's not one of Apple's clearest messages; it means your backups are damaged beyond OSX's ability to repair them. See #C13 in Time Machine - Troubleshooting for details.

Why do I get this message every time I travel with my laptop and then return home: To improve reliability, Time Machine must create a new backup for you.

Why do I get this message every time I travel with my laptop and then return home: "To improve reliability, Time Machine must create a new backup for you."
I get this on my new MacBook Air, but never got it on my old MacBook Pro.
Thanks!

See #C13 in Time Machine - Troubleshooting.

I got the message: Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you. I got the message: Time Machine completed a verification of your backups. To improve reliability, Time Ma

I got the message:
Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.
Here's what the text of the system.log says when I filter for backupd:
Jan 9 11:37:14 justin-steeds-macbook-pro com.apple.backupd[2618]: Starting standard backup
Jan 9 11:37:14 justin-steeds-macbook-pro com.apple.backupd[2618]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:37:33 justin-steeds-macbook-pro com.apple.backupd[2618]: Recovery backup declined by user.
Jan 9 11:37:33 justin-steeds-macbook-pro com.apple.backupd[2618]: Backup canceled.
Jan 9 11:48:20 justin-steeds-macbook-pro com.apple.backupd[2859]: Starting standard backup
Jan 9 11:48:20 justin-steeds-macbook-pro com.apple.backupd[2859]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:48:42 justin-steeds-macbook-pro com.apple.backupd[2859]: Recovery backup declined by user.
Jan 9 11:48:43 justin-steeds-macbook-pro com.apple.backupd[2859]: Backup canceled.
Jan 9 11:51:07 justin-steeds-macbook-pro com.apple.backupd[2917]: Starting standard backup
Jan 9 11:51:07 justin-steeds-macbook-pro com.apple.backupd[2917]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:51:34 justin-steeds-macbook-pro com.apple.backupd[2917]: Recovery backup declined by user.
Jan 9 11:51:34 justin-steeds-macbook-pro com.apple.backupd[2917]: Backup canceled.
Jan 9 11:53:50 justin-steeds-macbook-pro com.apple.backupd[2987]: Starting standard backup
Jan 9 11:53:50 justin-steeds-macbook-pro com.apple.backupd[2987]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:54:07 justin-steeds-macbook-pro com.apple.backupd[2987]: Recovery backup declined by user.
Jan 9 11:54:07 justin-steeds-macbook-pro com.apple.backupd[2987]: Backup canceled

Since this is a MacBook Pro hardware community, you might get better results by asking your question at the Time Machine forum, located within the Lion discussion group.
https://discussions.apple.com/community/mac_os/mac_os_x_v10.7_lion

New MacBook on old Time Machine backup-creates a new one!

I've read lots of posts on this, but I can't seem to find the anwer to my problem.
I have a Time Machine backup of the last year. However, I just bought a new MacBook Air and I need for Time Machine to inherit this new Mac to my old backup.
I used Migration Assistant to transfer evrything from my old MacBook to the new one.
But when I turned Time Machine on, it starts creating a new backup.
I need it to keep using the backup of my old MacBook.
From what I've have read in other web pages where they show how to's on Time Machine, is that once I bring everything from my old Mac (restore from the Time Machine backup) the only thing I need to do is to plug in Time Machine to my new MacBook and it would start backing up where it left of, but it doesn't happen that way. It creates a new backup file. It has the same computer name but it appends a number "1" to the name to differentiate it from the original.
Please help
Thanks

You should have used Setup Assistant, not Migration Assistant, to transfer your data. I suggest you start over by booting into Recovery, erasing the startup volume, and installing OS X. When you reboot, Setup Assistant will start automatically. Follow the prompt to import data from a Time Machine snapshot. The backup history will then be inherited. The first backup will still be a full one; that can't be avoided.

"....To Improve Reliability, Time Machine Must Create a New Backup for You"

I bought the new Apple 2 TB Time Capsule thinking it would be a great way to get a powerful wireless router and handle file backup for both me and my wife's iMacs. She is running an up-to-date version of Snow Leopard and I am on the most recent update of Mountain Lion. The Time Capsule was installed and running by the first of August and we had no problems until this monday (7 weeks later) when I got the message that "Time Machine completed a verification of your backups. To improve reliability Time Machinge must create a new backup" My wife's back up was still ok but I had to go though the 5-6 hour process of re-copying all my files(using an ethernet connection) to the device. All went smoothly for a few days until I got the same message again about creating a new backup. Also my wife cannot enter her time machine files even though the computer is still being backed up. We have a stable internet service and both computers recieve a strong signal from the router. Is it possible that the Time Capsule Drive is defective? Is there any sort of maintenance such as zpping the PRAM that would help? This is really frustrating as it looks like the timemachine backup is totally unreliable and not worth fooling with. Is there any way to use the storage capability of the time capsule without going through time machine?
Thanks,
Reid McCallister

hi
rest assured you are not alone. i have the same problem and i hate it with a passion. in fact, i am the victim of this message as of 20 minutes ago and doing a full backup as I am typing this. I am so overly ****** that I actually posted here and will be calling or emailing apple next because I cannot take this anymore. the problem lies in time machine and unfortunately, there is no fix for that. time machine is the best idea of apple with the worst implementation ever. you have no obligation to use time capsule to benefit from time machine as this would not be legal anyway. i will give you 2 temporary solutions and let you decide which one works best for you:
1) open time machine preferences and turn automatic backups off. create a new full backup from scratch and only backup manually whenever you remember, preferably every day. the automation process is the problem that lies within time machine. also make sure that your system does not go to standy or sleep whatever that may be called. Power nap, despite all claims, is not compatible with time machine. install CAFFEINE, an app that keeps your mac awake and prevents from going to sleep while back up is in progress. use it like this and pray it will all go fine for a long time. you may wish to duplicate the first full backup to save time in case this should happen again so you have a base to start on
2) install CCC (carbon copy cleaner) I have not used it myself yet, but probably will be installing it after finishing this post. it is claimed to be better, yet it is yet to be seen by me personally.
unless time machine can be trained without any addons to use a specific wifi only for backup, these issues will persist.

Time Machine Error cannot write to sparse bundle -- file in use.

We're having trouble with a Time Machine backup. Twice in the last three days, the backups failed with the error message that the backup disk image is already in use. I noticed that the partition containing the backup sparse bundle is mounted twice in /Volumes -- /Volumes/X and /Volumes/X-1. The error message refers to /Volumes/X-2.
The icon that appears on the desktop has not cleared as if it's still doing a backup.
Looking at the sparsebundle directly gives me the "verificationstate" as 1 -- I recall reading that this is supposed to 0. Other values:
verificationdate == 2012-06-05, and VerificationExtendedSkip == false.
Note that the backup drive is attached to another Mac still running Leopard. This is run fine for years over a gigabit network.
Any ideas?

OK, we fixed this for now with the simple, but common Mac way of
throwing something in the trash.
In this case it seems to be a temporary network connection to the remote Time Machine partition. When Time Machine balks, the icon for the temporary mount gets stuck on the Desktop. We threw it in the trash (unmounting it) and then Time Machine can resume.
Apple networking is annoying, but then on the other, it's easy. We lose printing in a similar way.
Anyway, although we seem to be OK, I'd like to understand this a bit better. I can see in the "/Volumes" folder (in Terminal) three Time Machine mounts, not one as I would have expected, and they all appear to point to the same place:
drwx------   9 root                   wheel 264   Jun 22 10:23 TM-2
drwx------   9 root                   wheel 264 Jun 22 10:23 TM-1
drwx------   9 MYUSERNAME staff   264 Jun 22 10:23 TM
On the remote machine, the disc TM appears only once.
If you look at the listing of all three, they are identical. What gives?
Is this a consequence of the fact that we are putting the time machine backups on a remote machine (that is not a Mac OS server). We have to mount the remote disc before Time Machine will run, but from that point it works perfectly -- or as perfectly as any mac networking thing seems to work.

Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.

I just wanted to collect all my messages since oct 16th. under one roof. I have spent too much time with this problem already, will NOT edit this the way I should. It REALLY bugs me that Apple doesn't acknowlege it - would make life easier knowing that they are working on it.
I have the same problem. It all started around Oct. 13th when my old 13'' MacBook was doing it's last backup just before I got my current 15'' Pro. It was running up-to-date SnowLeopard, and have 1TB TimeCapsule (1st generation).
Now I have had this same problem every two weeks running Lion in my new MBP.
This does not seems to be just Lion-related, or because of lack of space - my HD was 320MB, now 750MB (350MB used).
TM will erase the disk in this particular case, and you will loose all the data history!!!
You should make a backup with CCC or similar on a separate disk to be on safe side.
I think that there will be a fix for this problem, we are not the only ones complaning.
After more research I ended up with two options: either the TC HD is at the end of it's 4 year life OR Lion TM settings > options > lock documents 2 weeks after last edit is somehow behind this problem. I unchecked this setting and will see after two weeks...
Meanwhile, fingers crossed.
SAME BIG PROBLEMS HERE TOO. JUST GOT A NEW 2TB TC bacause thought that my 4y. old 1st gen is kaput - but the problem returned just after 5 days of usage. And the newest airport firmware update did not help the situation at all...
Disk Utility verified TC disk OK, new MBP running Lion disk ok as well.
Tried about everything with my old MB with SnowLeopard.
I mean I have tried really everything since the problem occurred mid-september - new MBP, new OSX (Lion this time), new TC THIS WEEK, started fresh from the very beginning but the problem still exists.
I have no other software in my mac but from Mac App Store + Nikon + Adobe.
A virus? Others have it too?
Studied all day today and tried many options including ethernet / wireless settings (FYI: found out also that in Airport Utility alt-key brings the missin options in setting up wireless- and radio modes - confusing since no mention of this in the manuals).
There is a firmware/OSX - problem and it bugs me that Apple doesn't acknowlege it - would make life easier knowing that they are working on it.
Too many people are having these problems, and also I lost a couple of days of work while solving this on my own.
Here we are solving this mess as well. My 1st gen TimeCapsule began to work odd two months ago, needed to do fresh backups every week or two. Finally got a new one this week. Seemed to work fine first, but today a complete stop with my network. Problems occured not immediately after the firmware 7.6 update though. Seems that my iWork backups are a bit of a mess too since Pages keeps showing an unwanted photo in a written article after deleteting it from there...
I have my new TC 2TB as a base station downstairs + express extending to upstairs study + express joining for AirTunes (+ the old TC to play with). Lion and Airport Utility up-to-date.
Got also new MBP two months ago.
First thought that Lion is the problem, then that old TC is the problem - seems like APPLE is the problem...
BTW - DID YOU KNOW THAT YOU NEED TO HIT ALT-KEY TO SEE ALL OPTIONS FOR WIRELESS MODE AND RADIO MODE??? AND THAT SOMETIMES IPHONE AIRPORT UTILITY SHOWS THOSE OPTIONS, SOMETIMES NOT... sort of hard to figure that out without a mention in the instructions...

Unfortunately, the message pretty much says it all.
What it does not tell you is that your Time Machine backups are corrupted and Time Machine cannot repair them, so it wants to delete your entire backup file and start with a new one.
I'm afraid that AppleCare will tell you the same thing, but it's worth checking with them to see if there are any new developments in this regard for this puzzling issue which affects a small percentage of users.
Please post back on your findings if you pickup some additional useful information when you speak to Apple.

How to stop Time Machine from creating entirely new backup of external drive?

I've included an external drive to be backed up into Time Machine. For a few days, the drive was disconnected, however, so only Macintosh HD was getting backed up. I recently re-added the external drive. However, now it appears that since the external wasn't included in the most recent backups, it's decided to re-backup the entire drive.
Is there any way to prevent it from backing up the entire external drive and instead just backup the changes made, or is that not possible because there is a gap in the backups made for the external?

First, the amount that TM says it's going to back up is not necessarily the amount it will back up. You'll only know that when the backup finishes.
I haven't tried this myself, but it may be that after you exclude a volume, TM loses continuity with the previous snapshot. In that case, future backups should be incremental, as long as you don't exclude the volume again.

Time machine backup blocked; disc image sparse bundle needs ejecting

Team, I cannot backup to 2Tb time machine; error message as above. How do I 'eject' this disc image and what exactly is it?
Thanks
Nick B

OK, we fixed this for now with the simple, but common Mac way of
throwing something in the trash.
In this case it seems to be a temporary network connection to the remote Time Machine partition. When Time Machine balks, the icon for the temporary mount gets stuck on the Desktop. We threw it in the trash (unmounting it) and then Time Machine can resume.
Apple networking is annoying, but then on the other, it's easy. We lose printing in a similar way.
Anyway, although we seem to be OK, I'd like to understand this a bit better. I can see in the "/Volumes" folder (in Terminal) three Time Machine mounts, not one as I would have expected, and they all appear to point to the same place:
drwx------   9 root                   wheel 264   Jun 22 10:23 TM-2
drwx------   9 root                   wheel 264 Jun 22 10:23 TM-1
drwx------   9 MYUSERNAME staff   264 Jun 22 10:23 TM
On the remote machine, the disc TM appears only once.
If you look at the listing of all three, they are identical. What gives?
Is this a consequence of the fact that we are putting the time machine backups on a remote machine (that is not a Mac OS server). We have to mount the remote disc before Time Machine will run, but from that point it works perfectly -- or as perfectly as any mac networking thing seems to work.

I got the message: Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.

Here's what the text of the system.log says when I filter for backupd:
Jan 9 11:37:14 justin-steeds-macbook-pro com.apple.backupd[2618]: Starting standard backup
Jan 9 11:37:14 justin-steeds-macbook-pro com.apple.backupd[2618]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:37:33 justin-steeds-macbook-pro com.apple.backupd[2618]: Recovery backup declined by user.
Jan 9 11:37:33 justin-steeds-macbook-pro com.apple.backupd[2618]: Backup canceled.
Jan 9 11:48:20 justin-steeds-macbook-pro com.apple.backupd[2859]: Starting standard backup
Jan 9 11:48:20 justin-steeds-macbook-pro com.apple.backupd[2859]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:48:42 justin-steeds-macbook-pro com.apple.backupd[2859]: Recovery backup declined by user.
Jan 9 11:48:43 justin-steeds-macbook-pro com.apple.backupd[2859]: Backup canceled.
Jan 9 11:51:07 justin-steeds-macbook-pro com.apple.backupd[2917]: Starting standard backup
Jan 9 11:51:07 justin-steeds-macbook-pro com.apple.backupd[2917]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:51:34 justin-steeds-macbook-pro com.apple.backupd[2917]: Recovery backup declined by user.
Jan 9 11:51:34 justin-steeds-macbook-pro com.apple.backupd[2917]: Backup canceled.
Jan 9 11:53:50 justin-steeds-macbook-pro com.apple.backupd[2987]: Starting standard backup
Jan 9 11:53:50 justin-steeds-macbook-pro com.apple.backupd[2987]: Network destination already mounted at: /Volumes/TimeMachine
Jan 9 11:54:07 justin-steeds-macbook-pro com.apple.backupd[2987]: Recovery backup declined by user.
Jan 9 11:54:07 justin-steeds-macbook-pro com.apple.backupd[2987]: Backup canceled

Since this is a MacBook Pro hardware community, you might get better results by asking your question at the Time Machine forum, located within the Lion discussion group.
https://discussions.apple.com/community/mac_os/mac_os_x_v10.7_lion

Time Machine Creates New Sparse Bundle

I have a 1TB hard disk connected to a Mac Mini over USB. That disk is shared on the network. My laptop and my wife's laptop are both set up to use that shared disk for Time Machine backups. Generally, things have worked fine.
This morning, I discovered a message from Time Machine on my laptop stating that there wasn't enough space on the drive to complete the backup. That didn't make sense - too few files had changed. When I investigated, I discovered that Time Machine had, after a successful backup at 21:29 last night, started creating a new sparse bundle for its backups.
I restarted my laptop and ran Disk Utility's Repair function on the shared drive (using the Mac Mini to run the repair). I've toggled Time Machine off and back on in System Preferences. The behavior remains: even though there is an existing sparse bundle (machinename.sparsebundle) on that share, when I tell Time Machine to do a backup, it creates a new sparse image: machinename-1.sparsebundle and starts backup up all of my files to it.
Also, if I "Enter Time Machine," Time Machine informs me that it can't find the disk. But it does offer for me to "Use Previous Disk..." if I first mount the "old" disk image (machinename.sparsebundle). Having the old disk image mounted does not prevent Time Machine from making machinename-1.sparsebundle when I tell it to do a backup, however.
I'm at a loss. I've checked the console logs and there's nothing useful there. Is there some hidden setting something that "forces" Time Machine to write to a specific sparse bundle?
I'm rapidly reaching the conclusion that these "over the air backups" aren't worth the bother: a directly-attached disk seems much simpler and more reliable.
Thanks in advance for any helpful hints,
Tony

Pondini wrote:
When you do a +*Repair Disk+* on a directly-connected volume that contains a sparse bundle, the sparse bundle itself may not be repaired. Drag it into the Disk Utility sidebar via the Finder, then select it and try +*Repair Disk+* again.
Okay. I did this - but it told me that the disk appeared to be okay. Which jives with my intuition, since Time Machine is able to use that image +for recovering files+ if I manually mount it and inform Time Machine that it should use it.
Pondini wrote:
Try the widget in #A1 of [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).
Does the widget source a different set of logs than the Console app? When I select "All Messages" in Console, I get the following when I attempt to do a backup:
11/12/10 2:35:23 PM com.apple.backupd[9404] Starting standard backup
11/12/10 2:35:23 PM com.apple.backupd[9404] Attempting to mount network destination using URL: afp://media@Media%20Center.afpovertcp.tcp.local/Terrabyte
11/12/10 2:35:25 PM com.apple.backupd[9404] Mounted network destination using URL: afp://media@Media%20Center.afpovertcp.tcp.local/Terrabyte
11/12/10 2:35:26 PM com.apple.backupd[9404] Creating disk image /Volumes/Terrabyte/transient 1.sparsebundle
11/12/10 2:35:26 PM kernel AFP_VFS afpfs_mount: /Volumes/Terrabyte, pid 9405
11/12/10 2:35:28 PM hdiejectd[9413] running
11/12/10 2:35:38 PM hdiejectd[9413] quitCheck: calling exit(0)
I read this as "Time Machine didn't even bother trying to use my 'transient.sparsebundle' that exists on that disk."
A couple of notes:
* My wife has no difficulty backing up to her image on that same AFP share.
* Between my initial post and this one, I updated to 10.6.5 - with no change in behavior.

Time machine always propose a new fresh backup

Hi all,
I am running an iMac 21.5" Late 2012, with an Intel Core i5 at 2,7 GHz, 8Gb RAM. I have recently (some months) moved from Mavericks to Yosemite (by the way, experimenting a general slow down is the system, I have brought my mac to an Apple Store and, after their checks, they told me that the computer i perfectly fine...) and since then I am having problems with Time Machine backups. After the first backup, time machine correctly performs following backups for a while and then (say, generally after a couple of days of seemingly correct functioning) asks me for a fresh backup as the verification of the actual backup seems to be not not reliable enough.
Technically, the message I get is the following:
Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.
What I can't really understand is why is this happening so frequently... It is quite boring to have my machine backing-up a large amount of data (I have a 1TB HDD connected to an Airport Extreme, to which my mac connects via wi-fi) almost every two days...
Let me just add that I was NOT having such problems when running Mavericks on the very same iMac...
Is there any reported problem of this kind? What does it depend from? Is there any possible solution to this?
Any help would be very welcome!
Thanx, best regards
Stefano

Start with C13 in the 1st linked article.
Time Machine Troubleshooting
Time Machine Troubleshooting Problems

Time machine has created a new sparse bundle

Similar Messages

Maybe you are looking for