From 6ae5c259d303d0ba558fa3bec04da69d40589bd3 Mon Sep 17 00:00:00 2001 From: Dan Date: Wed, 18 May 2022 09:12:57 -0400 Subject: [PATCH] Add small section for local usage --- Home.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Home.md b/Home.md index 006875c..08ecb03 100644 --- a/Home.md +++ b/Home.md @@ -208,6 +208,18 @@ It also possible to use a 3rd server that pulls backups from the source and push To do this, you have to install zfs-autobackup on a 3rd server and use both `--ssh-source` and `--ssh-target` to specify the other servers. +### Local Usage + +It is also possible to run zfs-autobackup locally, where you could backup snapshots to a different pool on the same server. This is done by simply omitting the `--ssh-source` and `--ssh-target` parameters. + +For example, let's say you have an additional pool for local backups called `backups`, that's on separate device(s) from your data pools. In this pool, you have a dataset called `autobackup`. You could run the following command (assuming you set the zfs group name to `autobackup:local` on your data filesystems): + +> zfs-autobackup -v local backups/autobackup + +Combining this with a remote push or pull backup, you could then set the zfs group name on your backup filesystems to something like `autobackup:remote`, then have a second zfs-autobackup job that backs up these snapshots to your remote storage like: + +> zfs-autobackup -v --ssh-target root@backupserver remote data/backup/pve01 + ### Automatic backups Now every time you run the command, zfs-autobackup will create a new snapshot and replicate your data.