CE rsync backup

[fakuivan]

Seafile stores file contents in blocks, these blocks are never modified, only deleted or added, except for when the garbage collector is not running, in this case blocks will only be added, not deleted or modified. These blocks comprise the bulk of the storage used by the server, so you can sync the directory where these blocks are stored (I don’t recall the path at the moment), and then take the server down for a moment to backup the databases, the library indexes and seahub related stuff.

For more info on this, I suggest you read the data model page on the manual.

Related post:

Seafile data model: will objects ever change on storage?

As Seafile’s data model is similiar to GIT’s, object IDs seem to be based on the hash value of the object content, for commits, fs and blocks alike. However, is there any possibility that seafile will change an object’s content after creation? For backup purposes, it would be much more efficient to rely only on object IDs instead of stating every single object on storage.