PIMSYNC-STATUS(7)

NAME
pimsync-status - Status database for pimsync(1).

DESCRIPTION
pimsync(1) uses an internal database to track metadata of each storage between one execution and the next. After the initial synchronisation, whenever items in both storages don't align, the status database is used to determine which of the two has changed.

The status database is considered internal, and should not be altered directly without clear understanding of the risks.

The location of the status database is expected to be an absolute path; using a relative path in a user-wide configuration file can easily result in ignoring the existing status database, and performing an unexpected sequence of operations.

DELETION
After deleting the status database, the next execution of pimsync(1) will run as if it were the first execution. Items which exist on both sides and are identical shall be considered in sync. Items which have been modified in either side shall be considered in conflict. Items which have been deleted on one side shall be restored from the other side — all items shall be considered new, since there is no record of them having been seen before.

If all items are deleted from a storage (e.g.: by the user or some other local process), then pimsync(1) shall treat the storage as "deliberately emptied". Protections exist and are enabled by default such that this scenario does not immediately delete all entries on the opposite storage. Typically, users delete all items with an expectation that they shall be restored from the other side. See on_delete in pimsync.conf(5) for how to disable these protections. In cases where one storage was deleted entirely with the expectation that pimsync(1) will restore all items from the other storage, the status database for this pair needs to be deleted, such that the next synchronisation is considered the first, and all items are treated as new.

SEE ALSO
pimsync(1), pimsync.conf(5)