Page 1 of 1

Copy from NAS to a temporary/volatile destination

Posted: Tue Jun 24, 2025 11:32 am
by Jean-Michel
Hello

For a new project, we are looking if the following is possible with Syncovery:

Copy the files from a local NAS to a S3 bucket which would only be temporary: that destination is not the final destination but a watchfolder from where our cloud application would "consume" the file and move it somewhere else.
That means that from Syncovery the file would disappear from the right-side destination but should not be copied again from the the left side unless it is modified on the left-side.

So it requires to have a "memory" (database ?) of files that have already been copied (fpath, size, date) instead of relying on the right side directory.

Is there an option for such behavior ?

Note that I don't know yet if the host would be Linux/Windows or Mac. I'm asking there because our latest projects were Linux based.

Thanks

Re: Copy from NAS to a temporary/volatile destination

Posted: Tue Jun 24, 2025 11:50 am
by tobias
Hello,
yes, you can use the SmartTracking mode, which defaults to not re-copying deleted files. It uses a database.

Even better could be using checkmarks under "Filters". On Windows, you would use the two archive-flag checkmarks.

On Mac/Linux, Syncovery can mark copied files as copied and not re-copy them.

It depends on whether the NAS implements these file system features.

You can also install Syncovery on many NAS types directly.

Re: Copy from NAS to a temporary/volatile destination

Posted: Tue Jun 24, 2025 12:25 pm
by Jean-Michel
Hi Tobias

So it looks like I could use the following :
SmartTracking options:
Detection of moved files: Off
Deleted files: Ignore
Conflicting: Do nothing (although this should not happen)
Options: nothing checked
General options
Masks/Filters: General filters: [X] Copy Only Files That Have Not Previously Been Marked As Copied (or Have Changed Since)

What do you mean by "marking the files as copied" ?
Are you talking about the Syncovery managed database ?
Or something on the filesystem layer such as the "Archive" bit on Windows (which I wouldn't consider as super reliable)
In that project, the NAS cannot host Syncovery so we need to rely on a separated computer on which the NAS is mounted.


A question: what happens if we have a problem with Syncovery database such as:
- database get damaged for any reason (not necesseraly by Syncovery)
- we have to re-install on another computer
How can we export the history of files already copied and re-import that ?

Thanks