Time Machine completed a verification of your backups

[bollee23]

I posted a support request to Synology that answered me that it is a known issue that will be fixed in the 3.2 release.

Regards

[mrjcleaver]

I posted a support request to Synology that answered me that it is a known issue that will be fixed in the 3.2 release.

But then, isn't it true that 3.2 won't support the cs407?

[dagrafica]

I have the same problem. I use Mac Os X 10.6.8. Synology DS109. Time Machine backup over wifi through Airport Extreme.

I dont no if the problem began after upgrading to 3.2 beta, but stil on 3.2 1922 the problem is still there.

Maybe the uppgarde to make Mac Os X "Lion Ready" messed up something?

Apple Care said to me that Time Machine doesn't support NAS servers at all. So its possible that the problem is for Synology to solve. I can try backing up to a USB harddrive. I let you no the result!

[gd11_be]

Hi All,

I can confirm that I have had the same problem again today. This time on my MacBook Pro. I am running the latest DSM, and the latest MAC OSX Lion. Very very weird that this problem is still there.

Is anybody else still seeing this issue ? And what could be the reason ?

MacBook Pro: over Wifi, CISCO router, and DS211

[stephanstricker]

Hi All,

I can confirm that I have had the same problem again today. This time on my MacBook Pro. I am running the latest DSM, and the latest MAC OSX Lion. Very very weird that this problem is still there.

Is anybody else still seeing this issue ? And what could be the reason ?

MacBook Pro: over Wifi, CISCO router, and DS211

Just happened to me today. I dont know what scares me more, the fact that Synology destroys the TimeMachine backup or that TM can not repair itself.

Stephan

[sdudulon]

same problem here : i am running mac os Lion 10.7.2 and Time machine on a sinology DS110J.
It could have something to do with sleeping, because the error occurred in the morning after i waked up my mac....
Very frustrating : i have to do a new backup.
I hope this will be fixed soon

[gd11_be]

Yes, it also happened to me again .. this time on my iMac. Indeed related to 'sleeping' .. I think, because I remember that it happened after I put the iMac to sleep, while the backup was running ... this shouldn't happen !

So I need to be very careful to check: NOT put the iMac to sleep while the time machine is doing its thing

[drm31078]

Has happened to me twice since upgrading to Lion and DSM 3.2. Happened about a month apart. This is very annoying. Takes a very long time to start over, let alone losing all the history.

[dagrafica]

Second time for me this happens. I Havent upgraded to 3.2 1955 yet.

Look @ server from ssh: cat /etc/exports/
Do you see time machine and the clients IP? I realised that my imac have another IP then the one I hade before (dhcp from modem, not airport extreme. But got a message
that I didnt understand, something about "sync"

Played around a little changing the IP to current then executed exportfs -ra. Removed the entire line for time machine, restarted server, modem, (not airport though).
Adding time machine again (both server side and client side) without any positive results.

Last time this happened I called apple support, of course they could not help. But after resetting nvram (for the second or third time it suddenly worked)

We can solve this, if we had a time machine that worked

[dagrafica]

Follow this Guide i found: http://www.garth.org/archives/2011,08,2 ... rrors.html

heres my simplified tutorial for repairing time machine - but please read the whole article before you proceed with this steps.
(Make sure you have wired connection to a router from the computer)

Open terminal on Mac

type sudo su

type chflags -R nouchg /Volumes/{name of your network share}/{name of}.sparsebundle - - This may take a while

type hdiutil attach -nomount -noverify -noautofsck /Volumes/{name of your network share/{name of}.sparsebundle
you can monitor the filesystem check by typing tail -f /var/log/fsck_hfs.log
for me it only took a few seconds to see ‘The Volume was repaired successfully’

now edit the Time Machine sparesbundle file com.apple.TimeMachine.MachineID.plist using (for me) nano /volume1/Time Machine/your sparesbundle/com.apple.TimeMachine.MachineID.plist

delete
<key>RecoveryBackupDeclinedDate</key>
<date>{whatever-the-date}</date>

edit integer as below
<key>VerificationState</key>
<integer>0</integer>

after that I mounted time machine again and it worked again as expected.

[sdudulon]

Thanks a lot for your tuto : time machine has been broken this morning, and now it's working again. No use to do a brand new backup. Thanks a lot.

[2Too]

So what's the synopsis with this now?

I'm running DSM 3.2-1922 and Lion 10.7.2 and still receiving this error.

I commonly put my Macbook to sleep. Is that the issue?

Or should I follow this guide someone posted?

http://www.garth.org/archives/2011,08,2 ... rrors.html

[dagrafica]

2Too follow the guide!

Read it carefully. DO NOT create a new backup before you have tried this one!

[2Too]

I did read the guide. But I'd like to know what the source of the corruption is.

If this corruption is because the computer goes to sleep during a backup, then the steps the guide provides offers only a temporary fix. Correct?

[dagrafica]

If this corruption is because the computer goes to sleep during a backup, then the steps the guide provides offers only a temporary fix. Correct?

Time Machine will take off from where it was. Lets say you disconnect from the network - when your on again it continues.

If you find something that can prevent this let me know.