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

additional information: to save on electricity (or hoping to do so ..) I plug out the WD drive every other day, and both times I got the message, it was after plugging it back in in the morning .. but others had this message even with WD drives that were permanently running, right?

ok, sorry, I just learned that I have to replace spaces by \ - did that. Next question: I seemed to gather from another post that the path does not need to include the name of the external drive? So instead of Volumes/MyBookLiveDuo/TimeMachine/ I can do /Volumes/TimeMachine/?

Hi. I have same problem over and over again.

I am using My Book LIve and Buffalo Linkstation Pro.

I finally fix with this tutorial in http://www.garth.org/archives/2011,08,27,169,fix-time-machine-sparsebundle-nas-b ased-backup-errors.html or http://ordo.dk/2013/11/time-machine-must-create-a-new-backup-for-you/

Thanks

Bambang

So I have a new Early 2013 rMBP 15" with Mountain Lion. First mac in a while and first time using Time Machine, setup on on a WD MyCloud that just came out that's compatible. First backup was back on Oct 31st. This morning I got the message about verification and starting a new backup. Last night I was restarting the machine a lot as I was tinkering with the mouse for a Windows like feel, but the system remains docked in clamshell mode and set to go to sleep like usual.

While the alert message was on my screen, I opened the Time Machine preferences and noticed bar saying it was looking for the disk. So on the alert message, I click backup later, which says it will remind me tomorrow. Then suddenly the search bar looking for the disk started moving, or could of been moving, and it went away and shows the next backup in an hour.

I enter Time Machine for my desktop folder and it seems to be working.

Could the verification message been caused by a temporary network issue and not a real problem with the backup and should be ignored? Or is this warning some part of the backup is corrup and not the entire thing?

I'd rather not start again on near 800 gigs over the network.

I'll also look at those links above.

Hold down the option key on your Mac while you click on the Time Machine "clock" icon at the top of the screen.

Select Verify Backups

If your backups are OK, you are OK....for now.

I just did that a few minutes ago, holding alt/option to verify backup. It immediatly brings up the earlier alert to back up later or start new backup.

I noticed the instructions to try and recover the backup say to not attempt over wi-fi. I don't have a thunderbolt to ethernet adapter at the moment.

Is this a known issue for wireless backups to Time Machine? Should I just abandon this whole MyCloud and connect a USB 3.0 drive to a hub connected directly to my laptop? It's the only machine backing up, so in a way, it doesn't make sense now that I think about it to slow backing up over the network just for one machine.

I don't have a thunderbolt to ethernet adapter at the moment.

That would be a very handy item to have if you can.

This error is fortunately not too common, but perplexing when it occurs.

An excellent resource for this issue would be:

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

Thanks for the replies

I'll pick up an adapter ethernet adapter when I have a chance for situations like this that need it. Though, I'm running out to get a new USB 3.0 drive to start a new backup and avoid this whole network drive thing. The initial 400gb backup took nearly 24 hours over the network.

The initial 400gb backup took nearly 24 hours over the network.

Ethernet, had it been available, would have been 9-10 hours.

I forgot to add, my laptop is set to never go to sleep while on the power adapter. I've never used an ethernet cable, as mentioned above, so it's always been wi-fi, no switching. I've taken the laptop on the road once several days ago, which then it goes to sleep on battery after 15 minutes. The last time thought, wi-fi was off, so by the time I docked it again, and turned on wi-fi after, it probably never knew it was gone.

Only thing different compared to the last two weeks, I restarted it around 8 times yesterday due to trying different mouse drivers and third party software.

I picked up a My Book For Mac 3TB USB 3 drive. Things are backing up much quicker, plus already formated for Mac and comes with 3 year warranty compared to the 2 year the non-Mac version.

FYI: Some good suggestions to fix this issue:

http://apple.stackexchange.com/q/93215/50686

I have exactly the same problem, every two or three weeks I get this message and have to lose all that is saved for a new one. It means that I still have to back up onto another hard drive to avoid loseing important material. There are five Mac's in this house, mine is the only one with mountain Lion and I am the only one with this problem! Apple are ignoring this because they don't actually care.

Hey Folks, further to this post train.

See earlier posts. In Dec 2010 under the Apple replacement programme I had my iMac Seagate HDD drive replaced. I then had an issue with TM and TC backups due perhaps to the different HDD UUID. Apple support could have advised me on Associating or Inheriting previous backups, but didn't. Anyway, I created a new backup and TM and TC ran seamlessly until today when up popped the same verification message again.

Is it the HDD or the TC drive? TC from June 2010 so perhaps on the way out?

Still nothing from Apple to help solve except create the new backup!

A 2010 TC is likely a Gen3.. but it could be last of the Gen2.. anyway it is old and I would say time to replace.. 3year reliable lifespan is about as much as you can hope for, when they use the cheapest domestic drives.. not, as the advertising says, server standard drives. Apple are being tricky with the numbers.. quoting old server drive standards.

I would still factory reset and see if it keeps saying the same thing.. but in the end corruption especially over wireless is to be expected.

Hey, thanks for that, but the TC has always been ethernet connected.