diff --git a/docs/advanced/csidriver.md b/docs/advanced/csidriver.md index 6e48e7c38e..ae195ca14b 100644 --- a/docs/advanced/csidriver.md +++ b/docs/advanced/csidriver.md @@ -23,7 +23,7 @@ These validated CSI drivers have the following capabilities: | Storage Solution | VM Image | VM Rook Disk | VM Data Disk | Volume Export To VM Image | VM Template Generator | VM Live Migration | VM Snapshot | VM Backup | | --- | --- | --- | --- | --- | --- | --- | --- | --- | -| Longhorn v2 Data Engine | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |✖ | ✖ | +| Longhorn v2 Data Engine | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | LVM | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✔ | ✖ | | NFS | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | | Rook (RBD) | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | @@ -70,7 +70,7 @@ Before you can make use of Harvester's **Backup & Snapshot** features, you need :::note -Backup currently only works with the Longhorn v1 Data Engine. If you are using other storage providers, you can skip the **Backup VolumeSnapshot Class Name** configuration. +Backup currently only works with the Longhorn v1 Data Engine (and V2 provided they're not the root disk). If you are using other storage providers, you can skip the **Backup VolumeSnapshot Class Name** configuration. For more information, see [VM Backup Compatibility](https://docs.harvesterhci.io/v1.4/advanced/csidriver#vm-backup-compatibility). @@ -175,7 +175,7 @@ Avoid changing the storage profile or CDI directly. Instead, allow the Harvester ### Limitations -- Backup support is currently limited to Longhorn V1 Data Engine volumes. Harvester is unable to create backups of volumes in external storage. +- Backup support is currently limited to Longhorn volumes. Harvester is unable to create backups of volumes in external storage. - There is a limitation in the CDI which prevents Harvester from converting attached PVCs to virtual machine images. Before exporting a volume in external storage, ensure that the PVC is not attached to workloads. This prevents the resulting image from getting stuck in the *Exporting* state. diff --git a/docs/advanced/longhorn-v2.md b/docs/advanced/longhorn-v2.md index 2985447a0d..0514b74faf 100644 --- a/docs/advanced/longhorn-v2.md +++ b/docs/advanced/longhorn-v2.md @@ -33,14 +33,11 @@ Every node with an active Longhorn V2 Data Engine requires the following dedicat The Longhorn V2 Data Engine currently does not support the following operations: - Backing image creation and usage -- Volume cloning - Volume encryption -- Volume expansion +- Volume expansion (TODO: check if this is still true, see https://longhorn.io/docs/1.10.0/v2-data-engine/features/volume-expansion/) ::: -- Snapshots of V2 volumes cannot be created because snapshot and restoration functionality in Harvester relies on volume cloning. - - SSDs and other non-NVMe disks are managed using the SPDK AIO bdev driver, which does not support the unmap operation. If you are using non-NVMe disks, avoid trimming the filesystem because this results in I/O errors and paused virtual machines. For example, when creating an ext4 filesystem on a Linux virtual machine, use `mkfs.ext4 -E nodiscard /dev/vdb` (assuming `/dev/vdb` is your device path). On Windows virtual machines, you can disable trimming for NTFS by running the command `fsutil behavior set disabledeletenotify NTFS 1`. ## Using the Longhorn V2 Data Engine diff --git a/docs/vm/backup-restore.md b/docs/vm/backup-restore.md index 13164eaf21..d873f6531b 100644 --- a/docs/vm/backup-restore.md +++ b/docs/vm/backup-restore.md @@ -26,7 +26,7 @@ VM backups are created from the **Virtual Machines** page. The VM backup volumes A backup target must be set up. For more information, see [Configure Backup Target](#configure-backup-target). If the backup target has not been set, you’ll be prompted with a message to do so. -Backup support is currently limited to Longhorn V1 Data Engine volumes. Harvester is unable to create backups of volumes in external storage. +Backup support is currently limited to Longhorn volumes. Harvester is unable to create backups of volumes in external storage. :::