Alan Orth
131420be17
One less thing to do manually after server provisioning, and there is nothing sensitive in here anyways.
48 lines
1.3 KiB
Plaintext
48 lines
1.3 KiB
Plaintext
### Recommended options
|
|
|
|
# Tarsnap cache directory
|
|
cachedir /root/.tarsnap-cache
|
|
|
|
# Tarsnap key file
|
|
keyfile /root/.tarsnap.key
|
|
|
|
# Don't archive files which have the nodump flag set
|
|
nodump
|
|
|
|
# Print statistics when creating or deleting archives
|
|
print-stats
|
|
|
|
# Create a checkpoint once per GB of uploaded data.
|
|
checkpoint-bytes 1G
|
|
|
|
### Other options, not applicable to most systems
|
|
|
|
# Aggressive network behaviour: Use multiple TCP connections when
|
|
# writing archives. Use of this option is recommended only in
|
|
# cases where TCP congestion control is known to be the limiting
|
|
# factor in upload performance.
|
|
#aggressive-networking
|
|
|
|
# Exclude files and directories matching specified patterns
|
|
#exclude
|
|
|
|
# Include only files and directories matching specified patterns
|
|
#include
|
|
|
|
# Attempt to reduce tarsnap memory consumption. This option
|
|
# will slow down the process of creating archives, but may help
|
|
# on systems where the average size of files being backed up is
|
|
# less than 1 MB.
|
|
#lowmem
|
|
|
|
# Try even harder to reduce tarsnap memory consumption. This can
|
|
# significantly slow down tarsnap, but reduces its memory usage
|
|
# by an additional factor of 2 beyond what the lowmem option does.
|
|
#verylowmem
|
|
|
|
# Snapshot time. Use this option if you are backing up files
|
|
# from a filesystem snapshot rather than from a "live" filesystem.
|
|
#snaptime <file>
|
|
|
|
humanize-numbers
|