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.
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?
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...
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.
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.
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.
Hey Apple are you seeing this?!?!
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?
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?
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
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.