I am trying to do remote self-contained incremental backups using WinSCP.
Several places (<invalid hyperlink removed by admin>) advocate the use of rsync & the UNIX
However, in order to do so, new backups must make sure they do not over-write hard-linked files. For example, if I:
1. upload a file b.txt to the directory remote:latest/b.txt (using WinSCP in SFTP mode)
2. do a
cp -al latest old
3. Screw up the b.txt file locally
4. Upload the (corrupted) b.txt file to the directory remote:latest/b.txt again (using WinsCP in SFTP mode)
Then: What is WinSCP's behavior? It can either over-write the file directly (therefore over-writing both latest/b.txt and old/b.txt which references/hard-links-to it). Or, it can de-link (delete) latest/b.txt before uploading.
The reason I ask is that rsync does de-link the file before writing the new version. That's the behavior that I want with (the much-better-than-rsync) WinSCP.
I've spent about 15 minutes looking through the manual. So, I admit that there might be an option there that I missed. My apologies if this is the case. However, I did make an effort. :D[/b]
P.S. Excellent software. I recently battled with rsync for the last couple of days. Finding WinSCP has already saved me a bunch of heartache.