From a9399e1af2e7bcd7ad997fccb3819b63431f2fd8 Mon Sep 17 00:00:00 2001 From: James Munson Date: Fri, 22 Sep 2023 15:45:53 -0600 Subject: [PATCH] Add a note about best practice for choice of a backup store. Signed-off-by: James Munson --- content/docs/1.6.0/best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/1.6.0/best-practices.md b/content/docs/1.6.0/best-practices.md index 82e4eeeda..4a7a5c7d1 100644 --- a/content/docs/1.6.0/best-practices.md +++ b/content/docs/1.6.0/best-practices.md @@ -95,7 +95,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li ## Volume Maintenance -We highly recommend using the built-in backup feature of Longhorn. +We highly recommend using the built-in backup feature of Longhorn. A backup can be saved to an object store (S3, Azure, etc), to an NFS server, or to a SMB/CIFS server, although an object store is the preferred method. For each volume, schedule at least one recurring backup. If you must run Longhorn in production without a backupstore, then schedule at least one recurring snapshot for each volume.