mirror of
https://github.com/restic/restic.git
synced 2024-12-23 16:26:11 +00:00
Document access time handling
This commit is contained in:
parent
eddb8549ef
commit
ffbc68aa2e
1 changed files with 8 additions and 2 deletions
|
@ -127,8 +127,8 @@ args:
|
||||||
|
|
||||||
$ restic -r /tmp/backup backup --files-from /tmp/files_to_backup /tmp/some_additional_file
|
$ restic -r /tmp/backup backup --files-from /tmp/files_to_backup /tmp/some_additional_file
|
||||||
|
|
||||||
Backing up special items
|
Backing up special items and metadata
|
||||||
************************
|
*************************************
|
||||||
|
|
||||||
**Symlinks** are archived as symlinks, ``restic`` does not follow them.
|
**Symlinks** are archived as symlinks, ``restic`` does not follow them.
|
||||||
When you restore, you get the same symlink again, with the same link target
|
When you restore, you get the same symlink again, with the same link target
|
||||||
|
@ -140,6 +140,12 @@ If there is a **bind-mount** below a directory that is to be saved, restic desce
|
||||||
archived as a block device file and restored as such. This also means that the content of the
|
archived as a block device file and restored as such. This also means that the content of the
|
||||||
corresponding disk is not read, at least not from the device file.
|
corresponding disk is not read, at least not from the device file.
|
||||||
|
|
||||||
|
By default, restic does not save the access time (atime) for any files or other
|
||||||
|
items, since it is not possible to reliably disable updating the access time by
|
||||||
|
restic itself. This means that for each new backup a lot of metadata is
|
||||||
|
written, and the next backup needs to write new metadata again. If you really
|
||||||
|
want to save the access time for files and directories, you can pass the
|
||||||
|
``--with-atime`` option to the ``backup`` command.
|
||||||
|
|
||||||
Reading data from stdin
|
Reading data from stdin
|
||||||
***********************
|
***********************
|
||||||
|
|
Loading…
Reference in a new issue