diff --git a/content/docs/1.4.0/best-practices.md b/content/docs/1.4.0/best-practices.md index 024d82063..462eb0a65 100644 --- a/content/docs/1.4.0/best-practices.md +++ b/content/docs/1.4.0/best-practices.md @@ -94,7 +94,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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.4.1/best-practices.md b/content/docs/1.4.1/best-practices.md index 024d82063..462eb0a65 100644 --- a/content/docs/1.4.1/best-practices.md +++ b/content/docs/1.4.1/best-practices.md @@ -94,7 +94,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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.4.2/best-practices.md b/content/docs/1.4.2/best-practices.md index 024d82063..462eb0a65 100644 --- a/content/docs/1.4.2/best-practices.md +++ b/content/docs/1.4.2/best-practices.md @@ -94,7 +94,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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.4.3/best-practices.md b/content/docs/1.4.3/best-practices.md index ef9ca2170..31cec6105 100644 --- a/content/docs/1.4.3/best-practices.md +++ b/content/docs/1.4.3/best-practices.md @@ -94,7 +94,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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.4.4/best-practices.md b/content/docs/1.4.4/best-practices.md index ef9ca2170..31cec6105 100644 --- a/content/docs/1.4.4/best-practices.md +++ b/content/docs/1.4.4/best-practices.md @@ -94,7 +94,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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.5.0/best-practices.md b/content/docs/1.5.0/best-practices.md index 43accd09e..71ca4088a 100644 --- a/content/docs/1.5.0/best-practices.md +++ b/content/docs/1.5.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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.5.1/best-practices.md b/content/docs/1.5.1/best-practices.md index 82e4eeeda..d6c9cafd8 100644 --- a/content/docs/1.5.1/best-practices.md +++ b/content/docs/1.5.1/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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.5.2/best-practices.md b/content/docs/1.5.2/best-practices.md index 82e4eeeda..d6c9cafd8 100644 --- a/content/docs/1.5.2/best-practices.md +++ b/content/docs/1.5.2/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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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. diff --git a/content/docs/1.6.0/best-practices.md b/content/docs/1.6.0/best-practices.md index 82e4eeeda..d6c9cafd8 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. +Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 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.