Thank you very much. Excellent analysis!
1. My bad, I concluded that sync.ffs_db and sync.ffs_lock were directly correlated (that they both contributed to file move/rename/delete detection, and that both warnings related to them are due to the same reason).
2.1. (G:\) is my Google Drive mounted to ...
Search found 2 matches
- 14 May 2024, 16:48
- Forum: Help
- Topic: The difference in FFS' behaviour when there's a database file (sync.ffs_lock) vs When there's not.
- Replies: 3
- Views: 1990
- 14 May 2024, 05:21
- Forum: Help
- Topic: The difference in FFS' behaviour when there's a database file (sync.ffs_lock) vs When there's not.
- Replies: 3
- Views: 1990
The difference in FFS' behaviour when there's a database file (sync.ffs_lock) vs When there's not.
In a Mirror Job that's set to version deleted files .
If there's a database file to keep track of file movement, this should mean that when a file is moved, it is not deleted, but instead it is moved accordingly, replicating the action and folder structure of the backup source, right?
So, does ...
If there's a database file to keep track of file movement, this should mean that when a file is moved, it is not deleted, but instead it is moved accordingly, replicating the action and folder structure of the backup source, right?
So, does ...
