The metadata every 24h hours to the backend. Keeps several backups in the backend storage. If the worst case happens and you will loose your local metadata, S3QL ) and regular scrubs to secure the metadata (put it on its own sub-filesystem). If you only have one drive, you could use Kinds of problems and do regular scrubs to detect and correct bitrod or If you use ZFS anyways, use Z1 or Z2 to protect your data against these Sync allows you to you to choose folders from your PC and have them available on all devices. I would guess that this has a high change of successįor a single bit-flip (bitrod). But you can of course use the SQLite tools to try to recover aĬorrupt database. The metadata of S3QL is a SQLite database. However files are of course fast to access. Which is not pretty space efficient, locally Rechunk,mtime (all files are considered modified - rechunk, cache mtime)ĭisabled (disable the files cache, all files considered modified - rechunk)Īt the moment, as said, I use a very large cache on my S3QL files. Rechunk,ctime (all files are considered modified - rechunk, cache ctime) Mtime,size,inode (default behaviour of borg versions older than 1.1.0rc4) This comparison can operate in different modes as given by -files-cache: The detection of unmodified files is done by comparing multiple file metadata values with previous values kept in the files cache. To create a borg repo, there are 4 options (man borg create)īackup speed is increased by not reprocessing files that are already part of existing archives and weren’t modified.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |