Thanks, yes the upgrade has all gone smoothly! And yes, it was quite a big leap in versions! The newer client seems to be more efficient and generally more responsive so that’s good :).

Ah right, yes that makes sense. I am pleased to report that all backups since the upgrade have been successful and the MBW client is performing as expected – no issues whatsoever :).

Thank you Scott, that is much appreciated. Hope you have a great weekend :).

Glad to hear that the upgrade from 2.1.2 to 2.7.2 worked as expected (I don’t think that we test upgrading versions that far apart very often!). And you’re absolutely right about the cache rebuilding when you upgraded; we don’t typically require a rebuild when upgrading, but there were probably enough changes to the database schema between 2.1.2 and 2.7.2 that it was necessary.

If you have any questions or run into any trouble with the client going forward, feel free to contact me directly at sclarson@vmware.com.

Thanks for the link. It all seems to have updated correctly and is working fine.

Everything seems fine at the moment. Just as a note to anyone that upgrades – straight after the upgrade you get a long time ‘Scanning files’. Don’t worry, we’ve found this to be completely normal – its similar to the time taken to rebuild the cache.

I assume that when upgrading to the new version the cache is automatically rebuilt? Maybe you can confirm that Scott?

Anyway, thanks for the update Scott, much appreciated. The new version seems to be more responsive and quick. So thumbs up so far for the new version.

It’s scanned all the files correctly and worked out whats changed so that’s a good sign. Just waiting to see if the backup goes OK this evening. From what I’ve seen, can’t see any reason why it wouldn’t.

But I’ll report back on it tomorrow for everyone! :).

Alright, I’ve got a build of the latest version for you. Here’s the link:

https://www.mozypro.com/downloads/MyBusinessWorks-2_7_2_532-42178.dmg

Let me know if you run into any trouble with it.

That’s no problem, we always help out where we can :).

Yes the version of MyBusinessWorks that we are running is 2.1.2.94 – this is currently shown as the latest version of MyBusinessWorks – although I understand the MozyPro client is up to 2.7.0.526 for OS X 10.5+? Yes, it would appear that MyBusinessWorks is quite a bit behind with the releases compared to what Mozy is up to.

That would be very welcome news – as this problem isn’t particularly the most easy to solve – and there will be lots of customers out there from non-technical backgrounds who may not be able to solve it at all.

Thank you Scott. That’s much appreciated! More features and improved performance would most definitely be welcome :).

Good app by the way – does what it says on the tin! (Apart from this one hiccup that we had! 😉 – but I understand that the cache corruption isn’t necessarily related to the MBW/MozyPro itself). But if a newer version of MBW/MozyPro is able to detect the cache corruption and rebuild it that would be awesome :).

Thanks for your comment Scott. Look forward to hearing from you :).

Do you know which version of MyBusinessWorks/Mozy you’re running? Based on the screenshots that you posted, you’re probably running a rather old version of our software. Some of our partners (MyBusinessWorks, in your case) don’t always update the client software to the latest versions of MozyHome/MozyPro that we release. Most likely, we’ve already fixed the problem that you’ve encountered in a newer version of the software (and added more features, improved performance, etc.).

I’ll talk to the right people and make sure that we can get a newer version of the MyBusinessWorks Backup client out to you.

Thank you for your additional advice in your comment – it is much appreciated by ourselves as I’m sure it will be appreciated by our members and readers.

Indeed, we didn’t perform specific tests to try and determine the cause of the cache corruption, we only observed that the error was caused by a corrupt cache (and hence provided a solution for this problem). As you have identified, there could be many different reasons and situations that could cause a corrupt cache.

I’m sure customers (ourselves included!) will be happy to hear that you are able to provide assistance in case of this issue occurring and thank you for the link to the relevant knowledgebase article.

We’re pleased to note that the advice given in the Mozy knowledgebase article echoes the advice given in this article.

No problem. Thank you for stopping by and commenting – it is much appreciated :).