I've noticed two different behaviors with Stash when I "resume" Windows. On my PC at home, which has Windows XP Pro (32-bit) on it, when I resume (I generally always Hibernate there), Stash always seems to come to life immediately and synchronize anything that might need synchronizing. However, on my work laptop, which is running Windows 7 Pro x64, when I resume Windows, it seems that Stash, though still running, doesn't automatically synchronize. I pretty much always have to either Pause / Resume it manually, or in some cases I actually have to shut it down completely and start it back up again to get it to synchronize. Is this a known issue?
Solved! Go to Solution.
Thanks for posting with such complete information about this. I'm not sure that it's a known issue, but I'll make sure that our QA testers try to reproduce it based on what you describe.
No problem. This issue definitely seems like it might be a bug. I don't understand why it behaves differently on the two different environments. Of course, my work laptop is usually connecting to my employer's network (which has a firewall with a proxy server). Sometimes I work from home and connect to my employer's network via the VPN, which routes ALL internet traffic thru the VPN when it is connected. So this might be part of the issue, but Mozy Stash does connect, even when I'm in the office or connecting from home over the VPN. So it does seem like it should not be an insurmountable issue. I think maybe what it needs is some sort of a timer that causes it to retry every so often when it is in that state.
Dan, your feedback about proxies and switching networks is very interesting and may well be the clue to the bad behavior you've been observing.
In our upcoming Stash update we've added support for detecting changes in the network. We reset our proxy settings each time that happens. That is intended to permit Stash to properly reconnect to a "auto-detected" proxy, which may be the way that your corporate network is configured. We had to handle this area carefully because sometimes autodetection of proxies causes a 30 second freeze, otherwise your suggestion of a periodic timer might well have done the job.
So far we aren't aware of any negative interactions with VPNs, and have tried it behind several, but perhaps that is also a factor.
I have the same issue at the original poster. My Win 7 Pro desktop seems to be syncing just fine. However it is never put into sleep or hibernation mode, it is powered off each night.
My Win Vista laptop is usually put in hibernation when I'm done using it in the morning. When I Resume (usually the next day) I do not recall seeing the Sync notification pop up. If I open a file from the Stash folder (on my laptop) and then notice it is the not most current version, then I exit without saving (Excel spread sheet), the sync popup comes up telling me it is syncing the Excel file. It overwrites the newer version that is stored on the Stash website.
Today after reading the original post in the thread, I tried the Stash Pause/Resume command and it did then sync the 1 other file (a PDF) that needed to be sync into my laptop. For some reason this PDF file was not synced when the Excel file was uploaded a couple minutes earlier.
The laptop connects using DHCP with my wireless router. No proxy or VPN is being used.
Thanks for reporting this. It does sound like a slightly different issue than the Proxy/VPN one, and I don't know of any issue that should prevent Stash from noticing when a local file has changed.
If possible I would like to look at the Stash logs from your laptop and try figure out what was happening.
If you could run the "Collect log files" option found in the Help menu and email the zip file to email@example.com I could take a look. Also please let us know the name of the pdf and excel file that weren't syncing automatically.
Thanks for sending us the logs.
I took a look and logged a new bug based on the failure to download the pdf file that you experienced. So far I don't have an explaination, my guess is that we lost a network connection and didn't reconnect automatically the way that was expected. We will try to reproduce.
For the situation with the excel file I cannot see any signs of incorrect behavior for the loads. I'm wondering if Excel itself was doing auto-saves?
With the 0.11 build that we just shipped Stash will now be more efficient when uploading large files that you edit in your Stash. So this may reduce the risk of any conflict between Excel and our upload operation. We are also looking at more ways to speed up the time that we need to read the file while uploading a new version.
Thanks for your help with the Beta!
(Also the proxy fix that was mentioned earlier in the thread is part of the 0.11 release that just went live, so that should help when moving a laptop between a work and home network)