Do we need to exclude the sync.ffs_db file from the filter?

[Heluojiang]

I am a donor user and I would like to discuss two questions about sync.ffs_db, as I have not found the relevant answers in the forum; this is causing me a lot of trouble with my 321 principle backup:

1. If I use the "mirror function" and "use database file to detect changes" to clone the contents of folder A to mirror B, corresponding sync.ffs_db files will be generated in both directories A and B. If I then clone the contents of folder A to mirror C, do I need to add \sync.ffs_db\ or \*.ffs_db\ to the "filter" to exclude similar database files?

2. If I use the "mirror function" and "use database file to detect changes" to clone the contents of folder A to mirror B, corresponding sync.ffs_db files will be generated in both directories A and B. If I then clone the contents of folder B (not A) to mirror C, do I need to add \sync.ffs_db\ or \*.ffs_db\ to the "filter" to exclude similar database files?

I want to know if our software processes database files like sync.ffs_db.

[xCSxXenon]

1) No, it is excluded by default
2) No, same reason

[Heluojiang]

1) No, it is excluded by default
2) No, same reason

Thank you!!!

[Plerry]

There is a clear reason why sync.ffs_db files are excluded by default.
The contents of the sync.ffs_db files is specific to each of the base locations involved in a sync.
Copying such file to another location could mess up expected/intended sync results.