Sync starting too soon, possibly causing reboots?

[ldeveraux]

I have duplicate external HDDs that I powerup, transfer long term storage files to, then have it run SyncBackPro. I've currently set the When and Changes section to check for changes to the right or left, then wait 60 seconds for no changes. The problem is, sometimes I'll transfer large 25GB folders that take a couple minutes. The sync starts before the files are done transferring. Am I using the setting correctly? Hopefully a pic of the settings is below:

Untitled.jpg (82.99 KiB) Viewed 4825 times

[petroben]

It seems like you are using SyncBackPro for syncing files between external HDDs, and you're concerned about the sync starting before the files finish transferring. Unfortunately, I don't have the capability to view or analyze images, but I can offer some advice based on your description.

If you're experiencing issues with SyncBackPro starting the sync before the file transfer completes, consider adjusting the synchronization settings:

Sync When Changes Detected:

Set the "When" option to "Manually."
Scheduled Jobs:

Instead of relying on the automatic sync, schedule the synchronization job to run at specific times when you know the file transfers will be complete.
Post-Transfer Trigger:

If there's an option to trigger the sync automatically after the file transfer is complete, utilize that feature. This can ensure that the sync only starts once all files are present.
Delay Option:

Check if there's an option to introduce a delay before starting the sync, giving your file transfer sufficient time to complete.
Remember to consult the SyncBackPro documentation or support resources for specific guidance on your version's settings. If the issue persists, reaching out to SyncBackPro support may provide more tailored assistance.

[ldeveraux]

What? You can't see the pic I added in my post? I have the trigger set for 60 seconds after the latest change. This is an option in the software, I think I should be able to utilize it and not make concessions.

[mmullins_98]

I see a few possibilities that may be causing a problem, I am not suggesting all are your situation.

Not knowing exactly how your external drives are connected (NAS etc.).
Changes cannot be detected on FTP, email servers, MTP, Touch or cloud servers. It will probably also fail to detect changes on NAS devices that are not running Windows (many NAS devices use a version of Linux) and on networked drives that are not running Windows.

"The problem is, sometimes I'll transfer large 25GB folders that take a couple minutes."
A common problem with running a profile when files are changed is that there is no way for SyncBack to know when a program has finished writing to or updating a file.

You state you "then run SyncBackPro".
SyncBack must be running for it to be able to detect changes. (this may also imply a transfer started before syncback cannot wait 60 seconds) You may want to configure SyncBack to start with Windows (see Global Settings in the burger menu burger). Important: It actually starts after you login to Windows and not before login.

Since you are syncing between Left and Right and detecting any changes on Left and Right then of course there will be changes on the Left or Right by the sync operation. Perhaps you should be running the profile only when any files or directories are changed on the Left.

[ldeveraux]

Thank you for this. My 2 drives are external HDDs attached to my Windows 11 PC by USB 3.0.
But why wouldn't SBP know when the file is done writing? FWIW I'm using Teracopy as my file copying method, not windows innate file copying.
I think i misspoke; SBP is always running in my system tray. So when i say I run it, I mean manually through SBP, pressing the triangle play button.
I disabled the "When" check on the right side, then copied over a 20GB file. When it was done (less than a few seconds later, definitely under 60) I copied another 20GB file. It started automatically syncing during the second file. I don't know why this had never happened before a few months ago, it was waiting the 60 seconds for it to be complete previously.

[ldeveraux]

Anybody have other suggestions? I feel it's still happening