https://505-merge.resticprofile.pages.dev/usage/index.htmlHere are a few examples how to run resticprofile (using the main example configuration file) See all snapshots of your default profile: resticprofile See all available profiles in your configuration file (and the restic commands where some flags are defined): resticprofile profiles Profiles available (name, sections, description): root: (backup, copy, forget, retention) self: (backup, check, copy, forget, retention) src: (backup, copy, retention, snapshots) Groups available (name, profiles, description): full-backup: [root, src] Backup root & src profiles (using full-backup group shown earlier)Hugoen-gbhttps://505-merge.resticprofile.pages.dev/usage/version/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://505-merge.resticprofile.pages.dev/usage/version/index.htmlThe version command displays resticprofile version. If run in verbose mode (using --verbose flag) additional information such as OS version, golang version and modules are displayed as well. resticprofile --verbose versionhttps://505-merge.resticprofile.pages.dev/usage/keyfile/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://505-merge.resticprofile.pages.dev/usage/keyfile/index.htmlGenerating random keys resticprofile has a handy tool to generate cryptographically secure random keys encoded in base64. You can simply put this key into a file and use it as a strong key for restic. On Linux and FreeBSD, the generator uses getrandom(2) if available, /dev/urandom otherwise. On OpenBSD and macOS, the generator uses getentropy(2). On other Unix-like systems, the generator reads from /dev/urandom. On Windows systems, the generator uses the uses the RtlGenRandom API. On JS/Wasm, the generator uses the Web Crypto API. On WASIP1/Wasm, the generator uses random_get from wasi_snapshot_preview1. Reference from the Go documentationhttps://505-merge.resticprofile.pages.dev/usage/memory/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://505-merge.resticprofile.pages.dev/usage/memory/index.htmlMinimum memory required restic can be memory hungry. I’m running a few servers with no swap and I managed to kill some of them during a backup. For that matter I’ve introduced a parameter in the global section called min-memory. The default value is 100MB. You can disable it by using a value of 0. It compares against (total - used) which is probably the best way to know how much memory is available (that is including the memory used for disk buffers/cache).https://505-merge.resticprofile.pages.dev/usage/locks/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://505-merge.resticprofile.pages.dev/usage/locks/index.htmlrestic is already using a lock to avoid running some operations at the same time. Since resticprofile can run several commands in a profile, it could be better to run the whole batch in a lock so nobody can interfere in the meantime. For this to happen you can specify a lock file in each profile: ​ toml yaml hcl json version = "1" [src] lock = "/tmp/resticprofile-profile-src.lock" [src.backup] check-before = true exclude = [ "/**/.git" ] source = [ "~/go" ] [src.retention] after-backup = true before-backup = false compact = false keep-within = "30d" prune = true version: "1" src: lock: "/tmp/resticprofile-profile-src.lock" backup: check-before: true exclude: - /**/.git source: - ~/go retention: after-backup: true before-backup: false compact: false keep-within: 30d prune: true "src" = { "lock" = "/tmp/resticprofile-profile-src.lock" "backup" = { "check-before" = true "exclude" = ["/**/.git"] "source" = ["~/go"] } "retention" = { "after-backup" = true "before-backup" = false "compact" = false "keep-within" = "30d" "prune" = true } } { "version": "1", "src": { "lock": "/tmp/resticprofile-profile-src.lock", "backup": { "check-before": true, "exclude": [ "/**/.git" ], "source": [ "~/go" ] }, "retention": { "after-backup": true, "before-backup": false, "compact": false, "keep-within": "30d", "prune": true } } } For this profile, a lock will be set using the file /tmp/resticprofile-profile-src.lock for the duration of the profile: check, backup and retention (via the forget command)https://505-merge.resticprofile.pages.dev/usage/noroot/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://505-merge.resticprofile.pages.dev/usage/noroot/index.htmlInfo This section is mostly copied from the restic documentation: Backing up your system without running restic as root Backing up your system without running resticprofile as root Creating a complete backup of a machine requires a privileged process that is able to read all files. On UNIX-like systems this is traditionally the root user. Processes running as root have superpower. They cannot only read all files but do also have the power to modify the system in any possible way.