I have no clue what the consequences would be, but I am somewhat afraid for it. The third party program synced the sync.ffs_db file as well, either to the left or to the right. When in a subsequent FFS sync attempt files are to be mirrored in the "detect moved files" mode, problems occur.Įven when folder contents left and right are completely equal, FFS starts to delete all files on the left, and than copies all from left to right. Total Commander, or just by windows explorer doing the same at two locations). The db is just keeping record of where files are and what they are named.The problem: folders can be synced by another application (say e.g. Instead of deleting y and copying x, which may be a large file, just move y in the destination to the new location". It is so FFS can see "Oh, this new file x in the source is actually the same as file y in the destination but just got moved to a different folder. They don't store anything relevant to the data itself. You could delete them, it won't hurt anything other than waste some time if you moved or renamed files before your next sync.īasically, you can restore from an image that was made months ago, simply open FFS to run a backup, and nothing bad will happen from "old" db files. The only way a db file could get transferred from a source to destination is if you do it manually, so you are fine if you didn't do that. They contain a "snapshot" of the state of the directory they are in so you don't have to delete and copy files when they are simply moved or renamed, saving time. They only pertain to where they exist, so the one on your internal drive is not the same as the one in your backup. I'm wondering if it is better to delete all the db files and restart.įFS doesn't copy, move, or overwrite its db files. One strange thing is that the db file on the D disk (which I didn't restore) dates back to the first installation of ffsync, two years ago, while the one on the external disk is updated to today and half the size! I really don't understand why they are not identical as for disk C. In any case I don't know if I did the right thing to overwrite the old db files of the restored image with the backup ones. Now - after some backups - checking the db files, I see they all have been updated at least to the first backup made after the restore, with identical date and size between source and destination, which makes me think that hypothesis 2 is right. When I restored the C disk using a Reflect image, obviously I found myself with old db files from the time of the image and - without thinking that they could have had different functions from those of the destination dirs in the external disk created by ffsync - when I updated the old restored files with those of the last ffsync backup I overwrote also the old db files. When you write that they are location specific, do you mean that 1 - the db files in the source dirs (in C) are different from those in the identical target dirs (in the external disk) because they have different functions, or 2 - that they are identical (because they are backups) and are specific obviously for the different C dirs? Hi xCSxXenon, glad you and Zenju answered me! I messed up something.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |