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

Question:

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

Reply
Question marked as Helpful

Oct 6, 2012 7:23 AM in response to Folbo In response to Folbo

Folbo wrote:

. . .

When I go to restore (enter Time Machine), I am not offered a choice of destination. I can only think that TM uses the 'latest' backup ... which contains one week of past history ... instead of my synology backup (6 months of history).

Correct. It uses the current or most recent backup.


How can I select which backup to use when restoring?

Use the Browse Other Backup Disks option, per Time Machine - Frequently Asked Question #17.


or how can I rebuild my TC backup from my Synology backup, if (when :-( ) it fails again?

Practically, that's often not realistic. If a backup set is intact and passes verification, you can copy it, but it takes a very long time. See FAQ #18. Since both are on a network, you'll need to copy the sparse bundle, per section 2 there.

Question marked as Helpful

Oct 6, 2012 7:27 AM in response to rrichard In response to rrichard

rrichard wrote:


Hi Folbo:


According to my long discussion with Apple Care, the way to change the current backup set which TM uses is to run a manual backup.


It's odd they didn't mention the Browse... option, as specified in the Help:


User uploaded file


Also covered in the blue box of Time Machine - Frequently Asked Question #34.


Message was edited by: Pondini

There’s more to the conversation

Read all replies

Page content loaded

Jan 25, 2012 5:13 PM in response to Folbo In response to Folbo

I have been having the same issue. I get the following message and need to create a new backup; it happens about once a month.


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


I also have a Synology NAS (DS209 current firmware). I contacted Synology support and they had me send them my Time Machine logs and kernel logs from the disk station. I received the following response from Synology today...


"I looked over the logs and the time machine logs,

and there isn't any errors with the disk station.

So the data over the network is somehow being corrupted, but your mac is initiating the scan.

are you using wireless?"


So it looks like Synology support is implying the corruption is due to Lion and wireless (I am using wireless). I have Applecare, I wonder if it's worth contacting them? I have since performed a new backup, so I am currently not having a problem. Perhaps the next time it gets corrupted, I will call Applecare.

Jan 25, 2012 5:13 PM

Reply Helpful (1)

Jan 31, 2012 11:44 PM in response to drm31078 In response to drm31078

Think I have a similar / the same.


For a while (post Lion) I had ****-and-all problems getting a stable backup regime running from my Macbook Pro to my Synology Diskstation 710+. However I got it working finally by:

- Adding 10.7.2 upgrade to the Mac

- Setting the Diskstation to a static IP

- Upgrading to the (then) latest Diskstation firmware

AND THEN FINALLY

- Repairing the sparsebundle on the Diskstation.


What I found strange was WHY was the sparsebundle needing repair in the first place? It was newly created by my Mac. Strange that, almost immediately, it was corrupt and in need of repair (elsewhere on these forums I reported all the errors produced in the Disk Utility logs when I did the repair).


Anyway, it stabilised. Then, after the Mac was away from the network for a while, the next time it connected to our LAN the error reappeared. I don't know if it was this passage of time which created the issue.


I will now try (again) the sparsebundle repair to see if that works.


What worries me is how we (as Mac and Synology users) avoid being bounced between Apple and Synology, which neither producing a satisfactory response and each saying the error is down to the other.


Has anyone made any progress with this?


Thanks

Jan 31, 2012 11:44 PM

Reply Helpful (1)

Feb 1, 2012 12:15 AM in response to Alastair Mac In response to Alastair Mac

UPDATE


Sure enough once again the sparsebundle is corrupted.


The error in Disk Utility when verified was:


Invalid sibling link

The volume Time Machine Backups was found corrupt and needs to be repaired


However when I then attempted to repair (as instructed), the Repair button was greyed-out and the utility says I need to reboot using the system disk bla bla bla...

Feb 1, 2012 12:15 AM

Reply Helpful

Feb 4, 2012 6:52 AM in response to Alastair Mac In response to Alastair Mac

Just happened to me again. Synology is saying it's Apples problem and that the diskstation is working fine. He seems to think data is getting corrupt via wireless connection. Which lends itself to the theory that it happens when backup is happening while it goes to sleep. This is absolutely ridiculous.

Feb 4, 2012 6:52 AM

Reply Helpful

Feb 7, 2012 5:10 PM in response to drm31078 In response to drm31078

Received another reply from synology pointing to Lion as the problem...



Here is what I received from my engineers.


This problem seems to have happened since OSX 10.7.

We use the open source - netatalk to support AFP and

it summarized that this problem also exists on Apple Time Capsule too.

(http://www.netafp.com/tn005-10-7-lion-time-machine-and-netatalkafp-620/

https://discussions.apple.com/message/17441528#17441528 )


For the Macs that doesn't trigger "Start New Backup" YET,

users may use the following method to try and fix the verification flag and avoid wiping out all old backup history.

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

http://pondini.org/TM/C13.html



Hey Apple are you seeing this?!?!

Feb 7, 2012 5:10 PM

Reply Helpful (1)

Feb 15, 2012 11:23 AM in response to drm31078 In response to drm31078

I'm am seeing this on new Macbook Air with Lion. In fact, it just did new Backup LAST NIGHT and this morning it tells me it needs to create a NEW one! (My wifes MB Air with snow leopard is NOT having this issue.) So definitely pointing to a Lion issue. I just upgraded to 10.7.3. Will that fix it, Apple?

Feb 15, 2012 11:23 AM

Reply Helpful

Apr 24, 2012 10:19 PM in response to Folbo In response to Folbo

Joining this group of people with the same problem: I have had it on my Synology DS211, and this on my iMac and my iBook. All after Lion. I hope Apple will sort this one out. Luckily it is at home, so the 3 times it has happened I have just re-created it.. but it doesn't give a good feeling.

Apr 24, 2012 10:19 PM

Reply Helpful

Apr 25, 2012 2:27 AM in response to Folbo In response to Folbo

I'm seeing this on two MacBook Pros - one (15" old case) on Snow Leopard and the other (15" unibody) on Lion - backing up to a Synology DiskStation DS212j over wireless. It has happened more often on Lion, but it has definitely happened on Snow Leopard.


I now have a UPS on the DiskStation, but that has not solved it. I was thinking that I might have to get a Time Capsule, but from what others have said, this won't solve it either.


C'mon Apple - what is the point of the best backup system if it regularly trashes your entire backup history?

Apr 25, 2012 2:27 AM

Reply Helpful

May 18, 2012 11:49 PM in response to Folbo In response to Folbo

I have the same problem. I am using a 13" macbook pro with a GOFLEX Home Agent from Seagate.


10.7.4 operating system. Every few months I get the verification failed message and have to start over. I access this mostly wirelessly. There are 2TB of space of which about 1.4 TB is used and the back-up takes 2 days and is about 380GB

May 18, 2012 11:49 PM

Reply Helpful

May 19, 2012 5:58 PM in response to Pondini In response to Pondini

Your help link is very nice. I think you may be right that the error is happening, because of some sort of wireless phenomenon. However, don't you think that the program should be smart enough to do some sort of error correction so that if the signal is weak it doesn't accept something that is not good.


In any case you note that this error only started being reported about May 2010.


Doesn't that suggest something more serious as I'm sure people didn't just suddenly start having WIFI problems after May 2010. There must be something else going on.


Do you have any suggestions of what people might do to try to avoid problems? Is there a way perhaps to change the time machine set-up so it doesn't do back-ups so frequently that they are done sometimes when a machine is about to go to sleep or some other interruption that might not be so good for the back-up.


Hourly in my mind is too frequent, but if it can be made to work that's fine. The problem is that since May 2010 something has changed.

May 19, 2012 5:58 PM

Reply Helpful (3)

May 19, 2012 6:17 PM in response to hansolo415 In response to hansolo415

hansolo415 wrote:


Your help link is very nice. I think you may be right that the error is happening, because of some sort of wireless phenomenon. However, don't you think that the program should be smart enough to do some sort of error correction so that if the signal is weak it doesn't accept something that is not good.

OSX does lots of that, as do all modern operating systems. But wireless communication is always the weak link, and there's only so much that can be done with a bad connection, interference, or power problems. When a NAS is used, it's also involved in the communications and error handling. Some older ones don't handle all of Apple's error detection properly.



In any case you note that this error only started being reported about May 2010.


Doesn't that suggest something more serious as I'm sure people didn't just suddenly start having WIFI problems after May 2010.

No. The verification was added then, to catch problems that were already occurring. At least, now you know there's a problem before you need the backups and find they're damaged.


Do you have any suggestions of what people might do to try to avoid problems?

There are a couple in the pink box of #C13, especially the Apple article. Study it carefully. If the signal isn't good, move your Mac and/or router around to find a better one.


What are your router and NAS plugged-in to? Could you be having power spikes or dips? They can wreak havoc. Consider a good surge protector or, better, a small U.P.S. system.


Is there a way perhaps to change the time machine set-up so it doesn't do back-ups so frequently that they are done sometimes when a machine is about to go to sleep or some other interruption that might not be so good for the back-up.

It's usually best to find and fix the problem, rather than change Time Machine's behavior. It handles sleep and most other interruptions without a hitch.

May 19, 2012 6:17 PM

Reply Helpful
User profile for user: Folbo

Question: Time Machine Frequent "Start New Backup"