Revolving around the core of technology
Hi,
luckily I today had a look in the 'log file' (IMHO it doesn't deserve that name) after a backup completed 'successfully'. Just 4 files were transferred, not a single error.
I knew there were more to transfer as a database had changed and some word documents added.
When opening the tree in S. client the missing (on the server) files are blue (depite the other, red ones) and the checkbox checked. Unfortunately not even a 2nd run of that profile transferes the files. And even worse: Not a single hint in any log file.
This happens as long as a huge (700MB) *.pst is part of the backup job. Once it's unchecked all the other files are synchronized.
Regards, Frank
P.S. What I am /very/ disappointed about is not the error/bug itself (not syncing files) but that one cannot trust your software. It always says 'successfully' :(
Frank,
Could you please send us the log files from the client side via email. We need to see SyncrifyClient.log. If you are sure this file has no useful information, please call us and we will figure out what is going on.
Imran
2nd try:
Here you go:
Backup with Outlook.pst, just 4 files got synced.
2012-10-03 09:04:48,660 {INFO Thread-13} [com.synametrics.syncrify.client.cX] $L - Backup started for profile: 1. Job number: 1684
2012-10-03 09:04:48,661 {INFO Thread-13} [com.synametrics.syncrify.client.cX] $L - Using local cache
2012-10-03 09:04:51,525 {INFO Thread-13} [com.synametrics.syncrify.client.H] $L - Forcing single thread processing for Outlook\Outlook.pst
2012-10-03 10:02:55,063 {INFO Thread-13} [com.synametrics.syncrify.client.cX] $L - Backup completed for profile: 1. Job number: 1684. It was successful.
Unchecked Outlook.pst, now 48(!!!) files got synced. Some of them haden't been synced for weeks!
One pretty clear example: [PathToFile]\backup(2012-9-13 10.27.57).ext - Entire file - 114024 bytes
2012-10-03 10:35:52,863 {INFO Thread-34} [com.synametrics.syncrify.client.cX] $L - Backup started for profile: 1. Job number: 1978
2012-10-03 10:35:52,863 {INFO Thread-34} [com.synametrics.syncrify.client.cX] $L - Using local cache
2012-10-03 11:14:05,536 {INFO Thread-34} [com.synametrics.syncrify.client.cX] $L - Backup completed for profile: 1. Job number: 1978. It was successful.
P.S. A default setting for the edit window of just 6 lines height is a bad joke! I have PLENTY of space on my 46" flatscreen, no need to 'optimize' the input window for iPhones, don't you think?
Frank,
I see two possible reason for this to happen:
Imran
Dear Imran,
1) is already known to you: The drive does not support VSS. Besides: Locked files are reported as locked (well, at least as far as I experienced it).
2) for now I just disabled the folder cache but today Sash faced the same:
http://www.synametrics.com/SynametricsWebApp/Forums?operation=4&msgID=3741
You might consider it a bug. And IMHO it's a pretty bad bug (2nd worst, right after falsifying backupped data comes not backing up data at all).
Please have a sincere look into this issue now.
Thank you, Frank
Frank,
As with any cache, there is a chance of it getting stale. Syncrify is designed to:
Having said that, I recommend you continue backing up without cache. I say that because VSS cannot be used on your end and it is better to back those files up the minute they because available. We will try to recreate this problem on our end.
Imran.
You're right, Imran,
it was enabled on the server.
But is such an option really a good idea for an unreliable cache which "can become stale".
I see it not as a feature as the admin is responsible if he forces the user to use unsafe technologies.
Yours, Frank
Frank,
Your message appear to suggest not using cache entirely. To say cache is an unsafe technology is not correct.
Yes, I know you are running into problems with cache but that is a unique situation occuring in combination with the inablility to run VSS. Syncrify is being used by hundreds and thousands of other location where caching is saving a lot of time during backup. In fact, we use cache backup our files and have never run into this problem.
Imran.
Dear Imran,
besides the fact that I do see not the slightest interrogation between VSS and the cache (because /you/ write the cache data and you would do so /only/ after /successfully/ trasferring the /complete/ data of a file/directory /and/ after /verifying that MD5 on client and server are identical, wouldn't you? You wouldn't blindly trust that is 'has worked'?!
Yours, Frank
P.S. The funny thing in my life is that whenever I run in such issues the vendors support claims I was the only one (BTW: you forget about Sash) out of thousands or millions of satisfied users.
well, Imran,
I knew it when I faced the issue!
http://synametrics.com/SynametricsWebApp/Forums?operation=4&msgID=3797
Regards, Frank