Jump to content

Restic: Difference between revisions

From Official NixOS Wiki
Wo2wz (talk | contribs)
improve wrapper example config
Phobos (talk | contribs)
m Added note for creating htpasswd file
Tags: Mobile edit Mobile web edit Advanced mobile edit Visual edit
Line 22: Line 22:


Passing the <code>htpasswd</code> file should be done using one of the [[Comparison of secret managing schemes|secret management methods]].
Passing the <code>htpasswd</code> file should be done using one of the [[Comparison of secret managing schemes|secret management methods]].
==== Creating a htpasswd file ====
A htpasswd file must be created using the <code>apacheHttpd</code> package. Assuming that you do not already have this package, you may run the following to generate the file using nix shell. Note that the file will be hidden due to the "." at the start of the file.
<syntaxhighlight lang="console">
$ nix shell nixpkgs#apacheHttpd -c htpasswd -B -c .htpasswd YOUR_USERNAME
</syntaxhighlight>


== Security Wrapper ==
== Security Wrapper ==

Revision as of 20:24, 24 March 2026

Restic is a fast and secure backup program. NixOS packages both restic client (program used to make backups) and restic-rest-server (one of the backends to store the backups remotely, "repositories" in restic parlance).

Installing

If you want to manually create restic backups, add restic to environment.systemPackages like so:

environment.systemPackages = with pkgs; [
  restic
];

Configuring

Restic

NixOS provides options to create a systemd timer and a service that will create the backups. See services.restic.backups options and "Backing up" in the restic documentation.

Note that NixOS includes an option to automatically create the repository by specifying    services.restic.backups.<name>.initialize = true;, as well as a wrapper to run restic in the same environment as the systemd jobs in services.restic.backups.<name>.createWrapper

Restic Rest Server

Restic Rest Server is one of the options for a remote repository[1]. It can be installed by enabling the services.restic.server.enable option. By default the server requires either providing it with htpasswd file or running it without authentication. If provided, the username and password pairs htpassd file will be used to authenticate the restic clients connecting to the server. To run the server without authentication, you can pass the flag using the extraFlags option like this: services.restic.server.extraFlags = [ "--no-auth" ];

Passing the htpasswd file should be done using one of the secret management methods.

Creating a htpasswd file

A htpasswd file must be created using the apacheHttpd package. Assuming that you do not already have this package, you may run the following to generate the file using nix shell. Note that the file will be hidden due to the "." at the start of the file.

$ nix shell nixpkgs#apacheHttpd -c htpasswd -B -c .htpasswd YOUR_USERNAME


Security Wrapper

If you want to back up your system without running restic as root, you can create a user and security wrapper to give restic the capability to read anything on the filesystem as if it were running as root. The following will create the wrapper at /run/wrappers/bin/restic

users = {
  users.restic = {
    group = "restic";
    isSystemUser = true;
  };
  groups.restic = {};
};

security.wrappers.restic = {
  source = lib.getExe pkgs.restic;
  owner = "restic";
  group = "restic";
  permissions = "500"; # or u=rx,g=,o=
  capabilities = "cap_dac_read_search+ep";
};

Note that you will have to set your Restic configuration to use the wrapper using the services.restic.backups.<name>.package option, for example [2],

services.restic.backups.foo = {
  # ...
  user = "restic";
  package = pkgs.writeShellScriptBin "restic" ''
    exec /run/wrappers/bin/restic "$@"
  '';
};