redundant transfer

[Dmitry]

How to setup redundant data transfer?
I have several tasks to copy large media files from several file-servers to other file servers.
Source media files moved to subfolders when transfers are done.
(Move files to destination + move deleted files into specified folder).
How to setup second server with Syncovery tasks to continue transfer tasks in case of main Syncovery server fault? (on-line redundancy)

[superflexible]

You need to write some scripts yourself. You can use Execute before/after in the profile to invoke scripts from Syncovery. You could use one such script to update a heartbeat file somewhere. Or use a separate profile just for the "live" sign.

On the other server, your scripts would need to check if the main server is alive and updating its hearbeat file regularly. If not, your script can start the Syncovery Service with
net start Syncovery_Service

Of course when the main server resumes, both will be running. Depending on how your profiles work, this might be entirely OK - depending on the protocols and server software used, one instance would just error out because the other is already copying the file.