From 114f5702b281d7d894ce45b71ac52a902d2cf358 Mon Sep 17 00:00:00 2001 From: lingfish Date: Sun, 2 Mar 2025 14:22:57 +1100 Subject: [PATCH] Expand a little on the specifics of backups of an LVM volume. --- docs/how-to/snapshot-your-filesystems.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/how-to/snapshot-your-filesystems.md b/docs/how-to/snapshot-your-filesystems.md index f1b6f8e2..1041dc05 100644 --- a/docs/how-to/snapshot-your-filesystems.md +++ b/docs/how-to/snapshot-your-filesystems.md @@ -205,6 +205,14 @@ Volume Manager) and sending those snapshots to Borg for backup. LVM isn't itself a filesystem, but it can take snapshots at the layer right below your filesystem. +Note that, due to borg being a file-level backup, this feature is really only +suitable for filesystems, not whole disk or raw images containing multiple +filesystems (for example, if you're using a LVM volume to run a Windows +KVM that contains an MBR, partitions, etc.) + +In those cases, you can omit the `lvm:` option, and use borg's own support for +[image backup](https://borgbackup.readthedocs.io/en/stable/deployment/image-backup.html). + To use this feature, first you need one or more mounted LVM logical volumes. Then, enable LVM within borgmatic by adding the following line to your configuration file: