Re: "Keepuptodate" behaviours
You have to use both
synchronize
and keepuptodate
.
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
synchronize
and keepuptodate
.
I'm not sure I understand what you ask for/what your problem is.
Does/can the "keepuptodate" command start with a "synchronize" to make sure the directory is up-to-date and then keep monitoring the directory for any further changes?
Not in scripting - in GUI it does (optionally) - in scripting you can do the same by explicitly runningsynchronize
.
synchronize remote -delete -criteria=time D:\<Destination> /<source>
on the destination server at 01:00 it would act like keepuptodate -delete D:\<Destination> /<source>
, so if I added a file at 01:30 it would still be copied across? or would I have to write the script as:
option batch on
option confirm off
open ftps://<FTPUser>:<FTPPassword>@<FTPServer> -explicit -certificate="<Thumbprint>"
synchronize remote -delete -criteria=time D:\<Destination> /<source>
keepuptodate -delete D:\<Destination> /<source>
Does/can the "keepuptodate" command start with a "synchronize" to make sure the directory is up-to-date and then keep monitoring the directory for any further changes?
synchronize
.