, when used with a standard FTP server, provides an option to alter the timestamp of the Working file (the file you're backing up) to match the time of the backup copy. That's the only way incremental backup can work with standard FTP, because the FTP server will write the backup copy with the current time and date. Compared to the original file, the backup copy appears to be newer. Letting MultiBackup change the timestamp of the Working file to match that of the backup fixes this problem but there are many reasons why changing the Working file timestamp may be undesirable.

provides ftp servers that can modify the backup timestamp to match that of the original Working file. This means that incremental backups can be achieved without changes to the Working file set. Note that MultiBackup itself, the backup program, is Windows-only, but by accessing FTP servers can do backups between non-Windows machines

MultiBackup ftp servers come in Windows and Unix versions. They implement commands to control file timestamps on the backup server. Their default directory listing is in EPLF to provide high-resolution time information.

The MultiBackup FTP servers may be usefule in some variety of situations, but are designed specifically for use with MultiBackup or any other application that cares to implement this timestamp protocol.

When used in conjunction with MultiBackup, these servers also encode user passwords passed over the network. Standard FTP servers accept only "clear-text" (un-encoded) passwords. Encryption-based FTP client/servers, such as SSH, encrypt files as well as passwords.

See some discussion and details regarding these FTP servers.

Availability

MultiBackup ftp servers, for Windows and Unix, are available by writing to me.