Currently Being ModeratedNov 16, 2012 1:41 PM (in response to Joey!! 【ツ】)
Try C13 here
Currently Being ModeratedNov 16, 2012 1:52 PM (in response to LaPastenague)
Thank you, I figured the great Pondini would have good information about this message!
Unfortunately, it doesn't provide any insight as to what caused it, nor really how you can prevent it from occuring in the future. I guess I have to start over and just hope it works. And really hope it isn't a problem with the Time Capsule. It has been working great for my iMac, which has been backing up for nearly a full year to the same TC and never encountered this issue, and it is still working great after receiving this error on the rMBP.
Currently Being ModeratedNov 16, 2012 6:36 PM (in response to Joey!! 【ツ】)
As pondini says.. the causes are many and various.. but basically it has corrupted itself.. remember TM is always meant as a current snapshot of the computer.. if you want longer term storage you should use a disk image.
Wireless is definitely part of the trouble.. more packets are corrupted and sometimes missed I guess.. then TM checks the backup it discovers the corruption but instead of fixing it just starts all over again.
We do recommend to people if possible use ethernet.. but for laptop users that isn't easy.
Also it is the setup of the TC in the network.. if you have the TC setup in bridge or as a router that is fine. But if you are trying to transfer packets by double hop wireless that is to be avoided.
I would also just because Mountain Lion is a bit more difficult on the networking.
Reset the TC and use all SMB type names.. short, no spaces pure alphanumeric.
That is for TC itself, wireless.. I recommend different names for 5ghz so you can force connection and the hard disk name.
Fix and lock wireless as well. All of it can help.. a bit.
Currently Being ModeratedNov 16, 2012 7:13 PM (in response to LaPastenague)
Well, I don't think anything could be causing it that I'm aware of. Interference, power source, nothing I can think of. I've been backing up my iMac to the same TC wirelessly since December 2011 (and still am) and have never encountered this problem.
In any case, I went ahead and started a new backup. It took a couple hours to back it up over Wifi, and there were no hiccups. Just sad I lost all backup history, but oh well. I still have my iMac backup history clear to last year.
Currently Being ModeratedNov 16, 2012 7:24 PM (in response to Joey!! 【ツ】)
If you want to keep the history.. then archive off the TC to USB drive.
The only trouble is apple left that function out of the new airport utility, so you have to use v5.
Currently Being ModeratedNov 16, 2012 7:28 PM (in response to LaPastenague)
That wouldn't be possible - that was way too many GB for a USB drive. It wasn't super important because I still have my iMac backup history, which was basically the exact same as the rMBP because I restored my data via Time Machine from my iMac to my rMBP when I bought it.
Currently Being ModeratedNov 26, 2012 9:53 PM (in response to Joey!! 【ツ】)
I'm having the same issue, Mid-2012 rMBP and a 3rd Gen Time Capsule. Everything is up to date. I have an apostrophe in my Computer Name and have never had an issue with that.
I'm just trying to figure out how I can modify the .sparsebundle file so I can start a new backup without losing my history. I already figured out how to manually mount and copy files out of the sparsebundle, so not having it as my main backup "file" would be perfect.
If anyone knows how, feel free to post it here. If I figure it out, I'll do the same