Syncovery Support Forum

Is there any word on this? The problem seemed to go away for awhile, but it comes back sometimes.

Last night's backup was a mix, some failed, some succeeded. One of them gave up after only two minutes:

Still Working At 10/21/2021 03:42:15
Still Working At 10/21/2021 03:42:45
Still Working At 10 ...

I don't remember anymore what changed, but this specific problem hasn't recurred since my last post in this thread.

The tips you gave in this thread, about managing the background process and GUI, have been very useful in other situations.

I did now upgrade to v9.39f.

OK, just sent.

Yes, both are Linux. Same version of Syncovery.

I have a profile in which Syncovery backs up a local source, over wifi, to destination drives attached to another machine via USB. I'm using block-level copying, with the remote service running on the destination machine.

Sometimes this works well. But sometimes I have large files skipped because ...

For anyone reading who wants to automate pausing of VirtualBox VMs before the profile runs, using a bash script, here are the problems I ran into and solved...

VirtualBox's "VBoxManage" command, when run as root (as Syncovery does, I believe) doesn't see VMs that were started as an ordinary user ...

I'm glad to hear the UTC thing is a known phenomena, because that's certainly what seemed to be happening. This drive is indeed NTFS.

I remember now, Windows' shadow copying of open files. Makes sense. I can simply add pause/resume of the VMs using Syncovery's before/after scripts.

I found ...

I think I finally have it working. I mounted the SMB volume locally using cifs-utils, which got rid of the 2026 mod date problem.

I then ran into a separate timestamp problem that was probably contributing as well. A few times, I temporarily moved the destination drives to a local USB connection ...

That seems to have worked! In limited testing so far, anyway. Tomorrow I'll work with it more, apply it to my actual profile, and close back here.

The version is actually v9.38e. (I've been waiting to buy until I feel more sure this setup is going to work.)

For the first test today, I did a backup of this same 4GB file, but with block-level copying disabled; it still used a 2026 mod date.

Then I did the backup with a new, zero-byte file ...

Also, I did a manual copy of this same file (using the file system), to the same destination drive. That file has a correct modification date.