I encountered a problem when I created a backup copy of my data disk and then decided to reorganize some files on the original disk. When I switch on synchronous directory change, it nicely keeps track of my browsing, but when I rename a file in original disk ( while in synchronous directory change mode ) it would be a nice optional feature to automatically rename the file in the backup drive too ( if the file exists in the backup drive ). As it is difficult to track those changes for any backup tool later on, it is wise to do synchronous rename on both, original and backup drives simultaneously. The same applies when I move ( crtl-x ctrl-v ) a file or directory in the original disk pane, this move could also be optionally executed in the other pane provided the backup drive is a plain file system mirror of the data disk and it is not any kind of archive.
I was not successful in discovering such functionality in TC, so my question goes, does it yet exist or should I post to TC suggestions thread?
thank you
synchronous directory change, rename/move for disk backup
Moderators: Hacker, petermad, Stefan2, white
synchronous directory change, rename/move for disk backup
Last edited by matus on 2011-10-30, 13:23 UTC, edited 6 times in total.
Hello, matus.
No, such a feature "synchronous rename" does not exist.
I am not sure whether it can be implemented.
E.g.: I often synchronize the (original) source foldertree to the (backup) archive. If I rename an object in the source foldertree automatically renaming the object in the archive would involve a lot of overhead work, I assume.
Anyway, what I do in a situation like the one you explained is this:
Karl
No, such a feature "synchronous rename" does not exist.
I am not sure whether it can be implemented.
E.g.: I often synchronize the (original) source foldertree to the (backup) archive. If I rename an object in the source foldertree automatically renaming the object in the archive would involve a lot of overhead work, I assume.
Anyway, what I do in a situation like the one you explained is this:
- Rename all the objects which I want to rename in the source foldertree
- Use "Synchronize Directories" in "Asymmetric mode" from the source foldertree (left panel) towards the backup foldertree (right panel).
Press [Compare], next press [Synchronize].
First T.C. will remove all the renamed objects from the backup foldertree.
Next T.C. will transfer all the renamed objects from source foldertree to the backup foldertree. - Task accomplished.
Karl
Yes, that'd be what I'd do too if the data disk would not contain 2TB of data. That would take ages to transfer over after each change in directory structure. Currently I manually mirror all rename/move changes to the backup disk immediately after each change in original disk, so I do not forget some changes, but this approach is error prone.
Why are you having doubts regarding the implementability of this feature?
Why are you having doubts regarding the implementability of this feature?
Hello, matus.
I expressed my doubts only for cases where the target (backup) is an archive, because renaming / moving inside an archive requires partially rewriting the archive file. Renaming / moving on the same disk, however, just requires rewriting some folder object.
The job should be much easier in your case where source and target both are foldertrees on different disks.
In the end, it is the programme author, Christian Ghisler, who will be able to tell whether your suggestion can be implemented.
So whatever I think is irrelevant in the end and must not prevent you from promoting your request.
Cheers,
Karl
I expressed my doubts only for cases where the target (backup) is an archive, because renaming / moving inside an archive requires partially rewriting the archive file. Renaming / moving on the same disk, however, just requires rewriting some folder object.
The job should be much easier in your case where source and target both are foldertrees on different disks.
In the end, it is the programme author, Christian Ghisler, who will be able to tell whether your suggestion can be implemented.
So whatever I think is irrelevant in the end and must not prevent you from promoting your request.
Cheers,
Karl