Why won't Mozy complete my initial backup?
I have 2 big problems using Mozy Unlimited on Mac OS X 10.6 to backup ~50GB of photos and home videos over a 1Mbit upload bandwidth:
1. Mozy freezes doing nothing for long periods
Looking at the Mozy status window, there are frequent pauses of about 4 minutes with the message "Communicating with server..."
I looked in the Mozy.log file and see that this co-incides with a long wait after "Offering files" followed by "NSCFInputStream closed" and then "Disconnecting". For example there is a 3 minute wait from the attached Mozy.log:
2009-09-01 21:02:17.602 MozyBackup[51156:630f] INF (send) Offering 15 files (0 are removes)
2009-09-01 21:05:30.565 MozyBackup[51156:825f] INF (folder scanner) Starting
2009-09-01 21:05:30.621 MozyBackup[51156:825f] INF (folder scanner) Stopping
2009-09-01 21:06:17.824 MozyBackup[51156:630f] INF (send) NSCFInputStream closed
2009-09-01 21:06:17.825 MozyBackup[51156:630f] INF (send) Disconnecting
2009-09-01 21:06:18.732 MozyBackup[51156:630f] INF (send) Batch failed: Connection lost (0x80000003)
2009-09-01 21:06:18.735 MozyBackup[51156:630f] INF (send) Offering 15 files (0 are removes)
2009-09-01 21:06:19.032 MozyBackup[51156:630f] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.162)
2009-09-01 21:06:20.685 MozyBackup[51156:630f] INF (send) Server version is 1.3.0.18
2009-09-01 21:06:27.688 MozyBackup[51156:630f] INF (send) Server requested 13 files
2. Mozy has reset my backup
I'd had it running for a couple of days, and according to the Mozy account status page by yesterday evening I'd backed up around 13GB - despite the pauses above. But today it's back to 1GB. What has happened??? How come Mozy appears to have lost all my files?
Any advice/feedback welcome, as I'm on the verge of canceling though I really really want this to work.
Thanks,
James.
1. Mozy freezes doing nothing for long periods
Looking at the Mozy status window, there are frequent pauses of about 4 minutes with the message "Communicating with server..."
I looked in the Mozy.log file and see that this co-incides with a long wait after "Offering files" followed by "NSCFInputStream closed" and then "Disconnecting". For example there is a 3 minute wait from the attached Mozy.log:
2009-09-01 21:02:17.602 MozyBackup[51156:630f] INF (send) Offering 15 files (0 are removes)
2009-09-01 21:05:30.565 MozyBackup[51156:825f] INF (folder scanner) Starting
2009-09-01 21:05:30.621 MozyBackup[51156:825f] INF (folder scanner) Stopping
2009-09-01 21:06:17.824 MozyBackup[51156:630f] INF (send) NSCFInputStream closed
2009-09-01 21:06:17.825 MozyBackup[51156:630f] INF (send) Disconnecting
2009-09-01 21:06:18.732 MozyBackup[51156:630f] INF (send) Batch failed: Connection lost (0x80000003)
2009-09-01 21:06:18.735 MozyBackup[51156:630f] INF (send) Offering 15 files (0 are removes)
2009-09-01 21:06:19.032 MozyBackup[51156:630f] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.162)
2009-09-01 21:06:20.685 MozyBackup[51156:630f] INF (send) Server version is 1.3.0.18
2009-09-01 21:06:27.688 MozyBackup[51156:630f] INF (send) Server requested 13 files
2. Mozy has reset my backup
I'd had it running for a couple of days, and according to the Mozy account status page by yesterday evening I'd backed up around 13GB - despite the pauses above. But today it's back to 1GB. What has happened??? How come Mozy appears to have lost all my files?
Any advice/feedback welcome, as I'm on the verge of canceling though I really really want this to work.
Thanks,
James.
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?1. It may look like it is freezing when it's actually having network problems. It says communicating with servers because it is trying to re-connect and it may say that for a while if it keeps connecting then dropping, then connecting over and over. The 0x80000003 means you were connected then the connection dropped. You need to figure out why the connection is dropping. Are you on a wireless network? Does your ISP reset the connection? Do you have a firewall or proxy or any other security device that could be killing the connection?
2. The status goes off of your last backup. So if you had a 100gb external drive backed up, then unplugged it and ran a backup, your status would be 100gb less than what it was the day before. If you upgraded your OS to snow leopard or re-install mozy or something like that, it will think it has to start from scratch. However if you use the same encryption it should encode the files and compare them to what you already have backed up, then skip over it if it is already on the server. Also keep in mind the restores are done by date. So if you did a restore from today you would only see the 1gb, but if you select a date from a few days ago, you could restore the 13gb. Does that make sense? Mozy doesn't lose the data, it just reports from your last backup.1 CommentAdd a comment
-
Thanks for the quick reply, but I still think there are problems:
1. This is a wired connection, and the disconnect happens in the mozy.log every 2 or 3 batches of 15 files (so pausing for 3-4 minutes every 10 minutes or so). I don't have network connection issues in any other application.
2. I'm talking here about the 'Space Used' on the Mozy website, not the size of the backup in my status window. I subscribed to Mozy after upgrading to Snow Leopard and my 'Space Used' seems to have dropped from 13GB to 0GB (and now back up to 1GB) following just a restart of my Mac - no unplugging of drives etc.
Is there anything further I could check on my side? -
Inappropriate?This could have something to do with the data center you are on, but I would need more info. Do you have a ticket with support yet?
That's what I mean. Under space used on the website it only shows the last backup, however the restore will show the right amount depending on the date and time you select. Upgrading to Snow Leopard must have made mozy think the files are new and now it will encode and compare them against what you have already backed up, then tag it if the file is already there instead of uploading it. -
Inappropriate?Hey guys.
The user is on SNOW Leopard, which is not yet compatible with Mozy... The solution is to wait until Mozy gets it fixed...I’m confident
-
Inappropriate?I upgraded from leopard to Snow Leopard (over existing installation) and is working fine, however the Mozy Preference Pane needs to restart the System Preferences but when it does you can still control Mozy.
But my question is to all software developers Snow Leopard has been out with 3rd developers for months why is there so much lag with patches/fixes? -
Inappropriate?I've found Mozy to be too unreliable, and have switched to IDrive - so far it seems more robust, though it's not perfect.
-
Inappropriate?mozy works great on snow leopard except it makes you reload the preferences (which will be fixed soon).
-
Inappropriate?Sorry but this is not the case here. Mozy aborts every bacup with errors 2 and 11
I’m frustrated
-
Inappropriate?which errors 2 and 11? connection errors? client errors? server errors?
-
Inappropriate?Mozy has stopped working for me since i switched to Snow Leopard. Very frustrating to hear that it is supposed to work since, NOTHING, has changed on my end except switching to Snow Leopard, and since then Mozy doesn't seem to do anything.
-
Inappropriate?Mozy get all sort of client and connection errors for me too on 10.6.1. :(
-
Inappropriate?adam, upgrade to version 1.5
parrt, do you have a ticket with support that i could look at and help fix? -
Inappropriate?OK, I have no idea why auto-update did not install 1.5 for me, but after manual installation, it is now backing up!
I’m hopeful
-
Inappropriate?we haven't pushed 1.5 to auto-update yet. Usually we release a version and let a lot of people manually so we don't have everybody upgrading at the same time. Also the manual upgrades will tell us if we missed a bug or something (much easier than trying to fix it for everybody).1 Comment
-
Mike, I'm having similar issues and am in week two of support via email. Still no joy. Ticket number is: ZVO-705478
Any help appreciated. I seem to be in a loop of uninstall, re-install, scratch head, uninstall... -
Inappropriate?Dennis, every time you uninstall you are rebooting before you install again right?
I looked up the ticket, and you sent the zip file to support, but it looks like you aren't running mozy as an admin and it is having problems storing the crash files. Can you run it as an admin and then send the logs (alt click on the mozy icon and get the logs for support). Sometimes the client error 15 can be a problem with your spotlight and a backup set. Can you try to delete all of your backup sets, and only backup a file from your file systems tab? This will rule out that possibility if it still crashes. -
Inappropriate?I am having exactly the same problem. Mozy Tech Support suggested uninstalling an reinstalling Mozy. That did not change anything. In my case, we are talking over 200G worth of data. I have also had some trouble with the Restore feature on Mozy's website when trying to verify if my files are still there. I get a server timed out error. I do believe that Mozy must be having some difficulty with the connections to their servers. If that is the case, Mozy should just tell us.
DK -
Inappropriate?dallen, what is the ticket number you have with support? I want to look up your account and see if I can find anything. You didn't change encryption keys did you?1 Comment
-
I don't think I changed encryption keys. Not sure how to even do that. Here is my ticket# - Case ID: ZBS-695857
-
Inappropriate?I am seeing the same "communicating with server" freezing issue on my iMac running 10.6.1 (Snow Leopard) and MozyHome 1.5.2. Never had a problem until I upgraded to Snow Leopard. Now I can't get a 5GB backup to run all the way through and I have been trying for 10 days. VERY frustrating. I have an open ticket MAI-567059.