>rename a folder with gigabytes of files
>next rsync copies the whole thing over again instead of just renaming the folder
Windows never did this with my backup utility. Why does Linux have to act so retarded?
theres no renaming support in linux. it moves the files to another folder with mv
>>55466003
Do you even know how mv works? It just messes with directory structure while retaining the inodes. That IS rename.
>>55465113
Your problem is using simple tools and expecting complex behavior. You get what you ask for. A git tree wouldn't fuck this up, for example, but few people are crazy enough to use git everywhere.
>>55466003
mv literally calls rename(2)
>using rsync locally
What the hell are you doing?
>>55465113
Using rsync to rename shit... are you retarded!?
I think the point is, how do you make backups that are easily accessible and automatable while keeping bandwith changes down?
i.e. how can you use git with rsync or the like?
>>55465113
>>55469217
The point is rsync isn't a dedicated backup tool — it is a tool for copying or syncing files between systems efficiently. It doesn't automagically know when a file has been renamed.
If you want something that does that then use a dedicated backup tool (which will more than likely use rsync for copying under the hood anyway). Otherwise you need to manually rename the backup file yourself.
>>55469217
There are other backup utilities than rsync, look into that.
>git with rsync
look into git-annex