You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Time Machine Frequent "Start New Backup"

Why does my MBP time machine keep telling me that it needs to create a new backup?😠


It only seems to happen when the system comes out of sleep .... (wireless connection) ...


It happened to backups on my Time Capsule so often that I stopped using my time capsule for that ... it is now happening the same on my synology NAS ...


I cannot try a third option ... I don't have one!!!


I want to prevent it happening ... but do not know the cause ... and do not know how.


Apple's help on this is insulting (http://docs.info.apple.com/article.html?path=Mac/10.7/en/mh34042.html) ... I can read the dialogue box ... how does the help 'help' in any way? There does not seem to be any acknowledgement of this elsewhere from Apple ... and no way to contact them.


It has only been happening since Lion ... th same hardware has been fine for 12 months before that. It only happens on my MBP (17 " Mid 2010) and not on my children's MB, wife's MBP (13") nor my iMac.




Thanks.

Macbook Pro 2010, Mac OS X (10.7.2)

Posted on Jan 25, 2012 9:32 AM

Reply
394 replies

Mar 17, 2013 2:14 PM in response to austin_george

Actually, Austin, it can be effectivly argued that anything within this thread that does not directly contribute to a solution to the root problem is the very feces you condemn, which includes your own post.


I have filed a bug report on this topic, as have countless others here. And yet, what has Apple done? So far nothing. I've filed countless bug reports on many other topics as well, both via the Feedback form and the Developer Bug Reporter. You get no reply from Apple when you submit a bug via the standard Feedback form, but with the Develoer Bug Reporter, you get some interaction. But most of the time, you will receive and automated response from the Developer Bug Reporter that tells you the bug you reported has already been logged. And while, in theory anyway, your additional bug report will further encourage Apple to work hard on getting that bug fixed, most of the time the bugs seem to never get fixed. It's usually after mentioning this fact that the fanboys jump in and defend Apple with all their might saying we should trust that Apple is fixing things according to a priority list superior to our own. But all the while the bugs that afflict our daily lives go unfixed.


Until the bugs either get fixed or until there is an acceptable workaround that is easy enough for anyone to implement, any dialog we may share does not matter at all. But at least when it comes to moaning and complaining, when there is a long enough list of moaners who moan loud enough — often catching the media's eye — Apple may be stung by such a sufficiently painful stinger that they are compelled to act. Therefore moaning does not in fact "devalue the problem" at all. Instead, it has the potential to bring more attention to the problem! I cite the following as past evidence of the present truth I proclaim...


"Can anyone tell me what MobileMe is supposed to do?" After Steve Jobs receives a reasonably good answer he proceeds, "So why the f*** doesn't it do that?"


And here's what set Mr. Jobs off in a rage against his own team at Apple:


"Mossberg, our friend, is no longer writing good things about us."



Did Mossberg act alone? Was he the only voice out there saying negatives about MobileMe? Hardly! The media includes more than just the Wall Street Journal, and it is a very powerful influence on Apple. And enough people moaning and complaining in Apple's own forums is a powerful seed that can grow into a painful thorn bush when fertilized by the media. Therefore, any words here that discourage people from moaning and potentially inciting the media are words that truly "devalue the problem."


ANYTHING that gets Apple to act, fix bugs, and in general make things better for all of us is the only thing that matters. As such, go ahead and preach "file a bug report!" That is good advice we should all follow. But stop bashing folks in threads like this one when they vent some steam and cry out with, "Apple, are you listening?" You may be surprised to know that they are listening.


Never underestimate your collective power. Keep the pressure on Apple. Your cries are not in vain.

Mar 20, 2013 11:07 AM in response to JDW1

Hey guys!


i created a new backup to my new Linkstation NAS (the old one died unfortunately the same day as my iMacs HDD began to die. but i was incredibly lucky that it would run for almost 40min before becoming to hot. and connected as an external hdd, i could restore my system within initial OSX setup. but that's another story)


according to apple care's statement (see rrichards postings), i made the initial TM backup with wired connection AND i turned off ANY energy savings within OSX energy saving settings (no computer goto sleep, no hdd goto sleep). And no NAS goto sleep as well. no problems so far.


now i am curious to see if it will fail again. therefore i want to use garth gillespie's method (within terminal):


imac-IMACNAME:~ root# chflags -R nouchg /Volumes/TimeMachine/USERNAME\ MYNAMES\ iMac_2012-07-16-115951.sparsebundle

imac-IMACNAME:~ root# hdiutil attach -nomount -noverify -noautofsck /Volumes/TimeMachine/USERNAME\ MYNAMES\ iMac_2012-07-16-115951.sparsebundle

/dev/disk1 Apple_partition_scheme

/dev/disk1s1 Apple_partition_map

/dev/disk1s2 Apple_HFSX

imac-IMACNAME:~ root# tail -f /var/log/fsck_hfs.log

/dev/rdisk1s2: Executing fsck_hfs (version diskdev_cmds-491.6~3).

QUICKCHECK ONLY; FILESYSTEM DIRTY


.. or clean. i will see, if i dare.


anyone knows if this procedure would probably corrupt my backup?

Mar 20, 2013 11:55 AM in response to MacPear

I used garth gillespie's procedure to fix my sparsebundle and it fixed it with no problems. Trouble was that the verification problem came back after a couple of weeks.


I was TimeMachine on a MacBook on Lion via wifi but have since switched to Carbon Copy Cloner with no problems apart from it slowing my network as it backs up. I would love to switch back to TimeMachine though.

Mar 21, 2013 5:39 AM in response to MBPierre

Just to bump the link....


http://www.garth.org/archives/2011,08,27,169,fix-time-machine-sparsebundle-nas-b ased-backup-errors.html



I know there are some out there who don't agree with having to do this and that it should just work. I whole heartedly agree.


However, my data is too precious to do nothing about it. Some would argue the data integrity can't be trusted so continuing to backup this way is pointless. I'm confident the files I absolutley need to restore are OK.

Mar 24, 2013 4:26 AM in response to MacPear

Well,


there is one more thing about corrupt sparsebundles. On my Buffalo NAS, i created a folder for other reasons than Time Machine. I had some problems copying some folders to it (apparently some file permission issues), and afterwards I could only rename it but I couldn't delete it (Error -8072). It took me a loong time until i got the idea to connect to that drive not as "guest" but as user "admin" (admin account within the NAS, not my iMacs admin account). No more problems.


--->>> Right now I am connected as "admin" to the NAS. The initial backup was performed when I was connected to it as "guest". Anyone here who was ALWAYS connected to his/her NAS with the NAS-account, and had to start a new backup?

Mar 26, 2013 7:33 AM in response to MacPear

yes, I always log into the NAS using the time machine account (I have a ReadyNAS Ultra 4), and got the corrupt sparsebundle message. I have not gotten it in a really long time, and one other thing that may be causing this just occurred to me. I recently added 2 gigantic 3 TB drives and increased the amount of space available to Time Machine. Before, it had been running up against quota and removing old backups automatically. This was the last time I had a corrupt backup, which was months ago now.


Perhaps the bug is that OS X is corrupting the sparsebundle when it runs up against the limit of drive space or against the quota for the partition where the time machine backups are kept?

Time Machine Frequent "Start New Backup"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.