Difference between revisions of "MOZY Issues"

From Ed's Mediawiki
 
Line 11: Line 11:
 
March, 2011:
 
March, 2011:
  
Because of a pretty major price increase associated with Mozy discontinuing "unlimited" backups, I removed Mozy in favor of CrashPlan.  Details: [[Crashplan notes]] No problems with this so far.  It works similarly to Mozy, but does local backups using an indexing scheme instead of a copy of the directories being backed up.
+
Because of a pretty major price increase associated with Mozy discontinuing "unlimited" backups, I removed Mozy in favor of CrashPlan.  Details: [[Crashplan notes]]
 
 
September, 2011:
 
 
 
CrashPlan is still working well for me.  I am backing up both desktop machines and my laptop.  One nice thing is that the CrashPlan software allows backing up to a drive on any other computer running their software, so you could conceivably mutually backup with a friend, and still have offsite backup.  I have had no issues at all with the CrashPlan software or servers, and I get a regular email reporting if there are issues, like the fact that the laptop has not been backing up or that since a power failure, the Mac has not done any backups.
 
 
 
October, 2012
 
 
 
Another year of good service from CrashPlan.  I had a C: drive failure early this year and had to bring up another drive.  Once this was done, and my files were restored from my local backup drive, I had to re-establish backups for what was essentially a new system. I did not do this correctly, and my backup set on CrashPlan's server was deleted, making it necessary to completely re-build it, which would take weeks.  CrashPlan customer service helped out a lot, eventually sending me a hard drive to bootstrap the backup.  I backed up to their hard drive, shipped it to them, and they put it up on their system.  This turned out not to be completely straightforward because of a network routing problem, and they moved me to another server.  Since then things have been fine.
 

Latest revision as of 09:09, 26 October 2012

Back to Maintenance log

MOZY online backup generally worked well for me, but at one point it stopped doing local backups and looking at the logs, there were a lot of errors, including what looked like database corruption. After back and forth with MOZY support, during which I learned a lot, I decided to uninstall and re-install the client and start over. This seemed to have solved the problem. But...

Things I learned

  • Mozy installs as a Windows service called MozyHome Backup Service. It normally starts automatically and takes care of itself, but during the figuring out stage, I found that it had been stopped for some reason.
  • Mozy uses the Volume Shadow Copy service, which sometimes stops for some unknown reason. It is this service that allows Mozy to make copies of open files, and it seems that it will run without it, but then has "snapshot" problems.
  • You don't have to back up most files that live in c:\Program Files. By looking at the backup logs, I found that it was trying to back up email cache files, and other working files used by running software. Whenever I have a problem with snapshot errors, I have specifically removed these files from the backup set, usually by eliminating the whole directory they live in.

March, 2011:

Because of a pretty major price increase associated with Mozy discontinuing "unlimited" backups, I removed Mozy in favor of CrashPlan. Details: Crashplan notes