forked from TrueCloudLab/restic
docs: Explain recognizing modified files
This commit is contained in:
parent
0882aca3a8
commit
0c0a8e3d2b
1 changed files with 6 additions and 1 deletions
|
@ -121,7 +121,12 @@ can compute which parts of the files need to be saved. When you backup
|
||||||
the same directory again (maybe with new or changed files) restic will
|
the same directory again (maybe with new or changed files) restic will
|
||||||
find the old snapshot in the repo and by default only reads those files
|
find the old snapshot in the repo and by default only reads those files
|
||||||
that are new or have been modified since the last snapshot. This is
|
that are new or have been modified since the last snapshot. This is
|
||||||
decided based on the modify date of the file in the file system.
|
decided based on the following attributes of the file in the file system:
|
||||||
|
|
||||||
|
* Type (file, symlink, or directory?)
|
||||||
|
* Modification time
|
||||||
|
* Size
|
||||||
|
* Inode number (internal number used to reference a file in a file system)
|
||||||
|
|
||||||
Now is a good time to run ``restic check`` to verify that all data
|
Now is a good time to run ``restic check`` to verify that all data
|
||||||
is properly stored in the repository. You should run this command regularly
|
is properly stored in the repository. You should run this command regularly
|
||||||
|
|
Loading…
Reference in a new issue