"Time Machine completed a verification of your backups."

Just did it again. Poof, another two weeks worth of backups gone. There's nothing helpful in the FAQ. I have no errors on any network links between my Mac and the TM box, and three other Macs on my network back up without issues.

This is driving me batty.

H.

I did. There's nothing in there about a *cause*. The link only contains info to the effect of "your backup is toast and a new one will be created." I'm trying to figure out *why* this happens every two weeks since I installed Lion, and *why* it only happens on one of three Macs I have running Lion and backing up using Time Machine to the same destination, and *why* there don't appear to be any diagnostics anywhere to assist me in determining the cause.

H.

I missed none of it, and it does not apply. None of it's on wireless - it's all wired - and it's all wired to the same infrastructure, to the same destination. If the stuff in the pink box applied, all three Macs would have trouble with their backups. But only one is.

H.

If you read my posts you'd note that I covered every point. If there were a loose or frayed cable I would see network errors on the links between the client and the server. I don't - which I mentioned. I specifically mention that all devices are running Lion and that only one is having trouble. I am backing up to a network attached storage device. This NAS has run just fine for quite some time and has hosted TimeMachine backups on my Macs for well over a year. This problem has only begun since I installed Lion, and it only exists on one Mac's backup set.

H.

The destination is a Time Machine server running on a Netgear ReadyNAS Pro Business NAS. The NAS is running 6x 2TB Seagate Enterprise-class SATA drives. The network isn't the issue. I install and diagnose networks for a living. There would necessarily be errors. I have equipment that meters them to excruciating detail, not only on every port, but also via separate data-gathering mechanisms including a sniffer, an RMON probe and Netflow, as well as SYSLOG monitoring. There are not only no Layer-2 port errors, there are no L2 or L3 retransmits of any type during the data transfer. There is no router between my Mac and the NAS. The destination NAS is attached to its network switch with twin Gig-E ports bonded using LACP. The Macs are all connected to that same switch with single Gig-E ports.

The only thing of any significance that has changed in this environment is the upgrade to Lion. And the error happens almost like clockwork, every two weeks.

H.

Poof. This time it was one week instead of two. Precisely one week, to the hour.

My Mac is up to date with 10.7.3.

I've found a ton of similar complaints around the Web on NAS forums. I'm starting to think it's some bizarre TM/Lion bug.

J.

Yargh. $$$.

H.