From 024006f4c03a3b31c221f106effc59202e3b9e5e Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Sat, 1 Mar 2025 20:56:40 -0800 Subject: [PATCH] Title case Borg. --- docs/how-to/snapshot-your-filesystems.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/how-to/snapshot-your-filesystems.md b/docs/how-to/snapshot-your-filesystems.md index 1041dc05..bd569957 100644 --- a/docs/how-to/snapshot-your-filesystems.md +++ b/docs/how-to/snapshot-your-filesystems.md @@ -205,12 +205,12 @@ 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 +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.) +KVM that contains an MBR, partitions, etc.). -In those cases, you can omit the `lvm:` option, and use borg's own support for +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.