The place where your backups will be saved is called a “repository”. This chapter explains how to create (“init”) such a repository. The repository can be stored locally, or on some remote server or service. We’ll first cover using a local repository; the remaining sections of this chapter cover all the other options. You can skip to the next chapter once you’ve read the relevant section here.
For automated backups, rustic accepts the repository location in the environment
For the password, several options exist:
Setting the environment variable
Specifying the path to a file with the password via the option
--password-fileor the environment variable
Configuring a program to be called when the password is needed via the option
--password-commandor the environment variable
init command has an option called
--set-version which can be used to
explicitly set the version for the new repository.
The below table shows which rustic version is required to use a certain repository version and shows new features introduced by the repository format.
|Minimum rustic version
|Major new features
Moreover, there are different options which can be set when initializing a repository:
Options to specify the target pack size:
--set-datapack-sizespecify the default target pack size for tree and data pack files. Arguments can given using TODO For example, valid sizes are “4048kiB”, “2MB”, “30MiB”, etc. If not specified, the default is 4 MiB for tree packs and 32 MiB for data packs.
--set-datapack-growfactorspecify how much the target pack size should be increased per square root of the total pack size in bytes of the given type. This equals to 32kiB per square root of the total pack size in GiB.
Note that larger pack sizes have advantages, especially for large repository or
remote repositories. They lead to less packs in the repository and transfer
larger datasets to the repository which can increase the throughput. But there
are also disadvantages. Rustic keeps the whole pack in memory before writing it
to the backend. As writes are parallelized, multiple packs are kept. So larger
pack sizes increase the memory usage of the
backup command. Moreover larger
pack sizes lead to increased repack rates during