Can you take a look through your log, located at C:\Program Files\MozyHome\Data\mozy.log, after it's been sat on Communication with Servers for a while?
Paste the last 20 lines or so of it here, and it should give some insight into whats going wrong
It is related to the manifest file.
I had 73GB backing up with no problem for two years, and after upgrading the 188.8.131.52, I am still "communicating with servers...."
I can uninstall this version , install 1.16 and in a couple hours I am back with normal backups. I have even deleted the computer from my mozy account, renamed it, did everything it doesn't matter. When it connects it tries to synchronize what is at Mozy servers and because of the changes in the manifest file it never (36 hours running on 56Mbps connection) completes.
I installed the same version on a new PC and it runs fine (under a minute from login to select backup sets).
Last option, before going back to 1.16 is to have Mozy remove the backup set and the manifest from their servers. Maybe, then you can start clean again.
Another option would be: revert back to 1.16, unselect all backup sets and let it remove the files from the server. Then you have a small manifest and maybe upgrade works.
Regarding log files? All you get is "mozyconf.exe: using temp dir: C:\Users\[username]\AppData\Local\Temp\" You can actually see that it creates a bmp of the user in that folder and it also gets an initial 36Kb manifest.dat from the server. After that....nothing for ever. No errors no nonthing.
So will this bug be fixed soon? I haven't been able to back up for a week now, and I'm sick of paying for a service that doesn't work. It's clearly not user error.
Similar problem here. I can not complete a backup with Mozy 2.0. It will hang in various places, but never complete a download.
Running WinXP here...everyone else that's having probs running XP?
There does seem to be problems with 2.0 and getting stuck on communicating. However it doesn't seem to be happening in every instance. I have a few computers, and only 2 have the communicating problem.
I just went back to 1.16 and it worked out fine. You have to re-backup but of course non-changed files didn't have to upload.
I want to look at backend logs on this kind of behavior. Please collect username and site code, and message them to me in IRC. I have also relayed this to #support.
I guess I am better off than what I am reading of everyone elses communicating with server issues. At least I am getting an error "ConnectionError4" made the changes according to the Knowledge base article but still no resolve.
The protal states no backups for 3 days but the History report sort of shows some files being backed up, which is true?
Do I need to let it "bake" over this long weekend or is there a fix for this error code beyond what the knowledge base says to do (which I did)?
I took a screen shot of the History report and any insight would be appreciated!
Now, works... No magic on this end, wonder what happened upstream?
Have been streaming data for about 18 hours now.