If "verbose" is checked, there will be one (or more) line(s) for each file. That's too much information if you are working with a number of files.
The "starting job xxx" and "job xxx completed" messages should be a "non-verbose" message, that would …
As described above, the problem is that the log is incomplete in that respect: There is no indication there that a job has started and is currently running, until either a file has been completly transferred or the job has ended. If the first file t…
I've been looking at the status line as a progress indicator, but this is confusing as well:
Currently, a job is active and has been running for about three hours. Yet, the status is still "Snapshotting [path]". "Snapshotting" on a Windows system w…
In the first place, I want to know if it ran at all. Otherwise, it might have failed even to start and not actually performed the backup I would be counting on.
Ideally I would like an entry like this:
started at X, scanned X files, transferred X…
Good tip, thank you. I'll watch that.
On a related note: When "Verbose Logging" is DISabled, the log does not even contain a "task started/task finished" mark. Could those be added?
Regards
I'm still not clear about this:
Yesterday morning, a big job was started.
This morning (around 5 AM), the connection was broken and reestablished a few seconds later. The job was interrupted and did not continue.
Two hours later (around 7 AM), th…
So to make sure the long, weekly profile gets completed eventually, I should still schedule it daily to make sure it has a chance to continue when interrupted, even though it doesn't do anything on most days?
This is a problem when using the snapsh…
Thank you.
BTW: The Date format used in filenames (also with snapshots) is a little unusual. Instead of
Year-MonthDay-Hour
a format of
Year-Month-Day-Hour
would seem more familiar. Could that be modified or is there a reason for the present f…