I use Coreftp to do my offsite backups. I have a Buffalo Drive sitting at my in-laws' house. Nightly I use the a series of commands to backup important (to me) directories to the remote Buffalo Drive.
The basic command looks like (normally on one long line):
C:"\Program Files\CoreFTP\coreftp.exe"
-site offsite_backup -u z:11us
-p "/disk1/share/_Z drive/" -recurse -ON -OG -s
-output c:\output\%%Y%%m%%d-%%H%%M_Z_11us.out
-log c:\output\%%Y%%m%%d-%%H%%M_Z_11us.log
Most directories don't change night to night yet every night COREFTP will spend several hours on a directory coping files that I don't think has changed.
BTW the site "offsite_backup" is a encrypted via CoreFTP.
CoreFTP Pro v2.1 build 1650
So what I'm looking for but haven't found in the logs or output is the reason why CoreFTP decided to overwrite the given remote file. Is there a way to log the size and date CoreFTP found on the remote file that it used for the test to see if it should overwrite the file?
Todd