ML and still get ".....TM must create a new backup.." error

No one has chimed in, and I understand that I didn't provide much info....I just have no idea why this happens.

So, this makes me curious, has anyone had the issue with Time Machine wanting to create a completely new backup with Mountain Lion yet...don't tell me I'm the only one!

If you do a fresh backup on ML do you still run into this issue?

I wouldn't be surprised if there were issues with TM in 10.8.0. NetGear will continue to update netatalk (AFP/Time Machine service) over time. There is a major Netatalk update that was released a little while ago that hasn't made it into ReadyNAS firmware yet. As that update isn't needed just yet I presume they're probably waiting for it to mature a bit.

I too have the problem, and have no idea why. It did not happen when I ran Snow Leopard, but it did happen with Lion, and it continues to happen with Mountain Lion. Every few weeks, I get the error message. The last time, I actually needed to use the backup, but could not (I didn't try the filesystem repair procedure mentioned above). I have a Mac Pro, and I have switched to using an internal drive for Time Machine (not the drive I use for my system or data; in fact, most of my data lives on my Readynas). An internal drive is not as safe as a Time Machine backup stored on a readynas located in another room of my house, but the frequent failures of the backups stored on the readynas have pretty much made them useless.

Hopefully, this will be fixed. I don't know if the problem is with the Readynas or with MacOS, but it sure is a problem.

I believe it's a problem with Mac OS X as users with Time Capsules have had the issue too. It is a frustrating issue.

Hmmm. thanks for the response. I had disabled TM so that I only performed manual backups (I've never had the problem if I only manually back up), but I'll activate again and see if it is fixed.

What do you mean by " a fresh backup"? TM rebuilt its entire database once already with 10.8.0, is that enough? Or do I need to go into the ReadyNas and delete it and start over more fundamentally?

Thanks,
Brandon

Not sure. Personally I would have deleted the old backup and started a new one.

I've had this problem before, so when I got a new machine (retina MBP) with ML, I started over from absolute scratch. After a month of trouble-free TimeMachining, I hit this tonight.

I'm running RAIDiator 4.2.21 and 10.8.1.

I have an Ultra 6 and am running RAIDiator 4.2.22 and 10.8.3 and experiencing the same. From time to Time I get the message that something is not OK and I should start a new Time Machine. When I do, it seems that everything is back to normal, but after some weeks, 4 at the most, I have to again start over.

Is the Problem more likely to be located on OSX or on the ReadyNAS?

You may wish to try 4.2.23 (due to be released soon).

thomasx wrote:
I have an Ultra 6 and am running RAIDiator 4.2.22 and 10.8.3 and experiencing the same. From time to Time I get the message that something is not OK and I should start a new Time Machine. When I do, it seems that everything is back to normal, but after some weeks, 4 at the most, I have to again start over. Is the Problem more likely to be located on OSX or on the ReadyNAS?

AFAIK it's a well known and continuing problem with practically all NAS devices. The only one that doesn't seem to have this problem is Synergy (according to MacRumors forums). It could be that the new OS6 Netgear units will not have this as they do have versioning, but who knows. I gave up on Time Machine for this reason and depend on CCC for OSX backups.