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

I agree with your statement about the os update. However I chose not to update it so that couldn't be my issue for now

We were not clear. What we meant to say was that we rarely saw this issue until Lion appeared. It did first appear under Snow Leopard. It does not seem to matter whether the user upgraded to Lion from Snow Leopard, or the Mac came with Lion pre-installed.

Can I get the information off and put it on another external hard drive for now??

It's worth a try. I was not successful when I tried this in the past. The file seemed to transfer, but Time Machine could not open the file to view backups. You may have better luck.

Please keep us posted on your progress and findings with Apple Support.

Time Machine guru Pondini also has some good info about this issue in his excellent support documentation:

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

See #C13

I'm having a similar issue - usually about once a month - on both my Mac Mini (OSX Lion) and MBA (Mountain Lion).

Both are using the same NAS (QNAP TS410)

I found this:

http://support.apple.com/kb/HT4076

which is now archived an unsupported by Apple - last modified Feb 2011.

and, is more or less unslessly unhelpful.

I have the same issue, backing up to a Synology NAS running the most recent DSM version.

I have this issue too 😟

It repeats every 2 or 3 weeks and make the idea of Time Machine useless.

Using Synology NAS DS-409+ with latest DSM and new external USB HDD from Seagate as disk for backups.

The same for me.

I'm using "Western Digital My Book Live 2 TB Personal Cloud Storage Drive" (it's a newtwork storage).

Same problem. I have a Synology DS 412+. It was working fine the other day, and Time Machine even backed up at 12 a.m. this morning. I start to use my system this morning and discover the most recent time machine backup has failed with this message. I am on the latest version of Mountain Lion and (as far as I know) DSM. I have more than a year's worth of backup here. Am I really going to have to delete and start over again? Really? 😠

Same symptoms using Synology DS111.

Yep. I can tell you why. Unfortunately Apple's "Support Communities" police have deleted my earlier post on this topic, as no doubt they will delete this one. If not, I can suggests a solution: forget Time Machine (useless) and forget Time Capsule (useless and expensive). Both will let you down, very, very badly.

Same problem. I'm using WD MyBookWorld in combination with OS X 10.7.5

It starts one week after initial backup.

It's already the third time I restart!?

Does anybody has experience with OS X 10.8?

I see the same error message randomly appear from time to time as well, also using a Synology DiskStation.

One question I have for other Synology users is whether or not you've recently enabled "Antivirus Essential" on your DS. I noticed some time ago that it flagged and quarantined some block from one of my timemachine sparsebundle backups and essentially corrupted it. I thought that I specifically told it not to scan that backed up directory since that time, but I just saw this same message pop up and realized that Antivirus is still running on my DS.

Thoughts?

Edit: I just found the following blog entry on the topic as well..

I have the Synology DS111 and this problem but the antivirus package is not installed.

I have the same issue with backing up my MacBook to my ReadyNas duo. Very frustrating and continues to erode my confidence in Time Machine.

Also feel like apple is ignoring these concerns.

The same problem for me. Maybe Apple can answer something finally!!!

Same for me, Snow Leopard, QNAP TS119P+ (3.7.3), also every 2-3 weeks...

Very annoying as full back takes more than 24 hours !

Means also after 2-3 weeks you can forget about older files.

Following the instruction provided in the blog linked below, I was able to repair my backup and continue using it:

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

Note: It did require 3-4 executions of fsck_hfs for me before it spit out the "The Volume was repaired successfully" message.

Good luck!