diff --git a/content/docs/1.4.0/best-practices.md b/content/docs/1.4.0/best-practices.md index 462eb0a65..fa910754a 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 462eb0a65..fa910754a 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 462eb0a65..fa910754a 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 31cec6105..f15124480 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 31cec6105..f15124480 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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.5/best-practices.md b/content/docs/1.4.5/best-practices.md index ef9ca2170..f15124480 100644 --- a/content/docs/1.4.5/best-practices.md +++ b/content/docs/1.4.5/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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 71ca4088a..09fb80941 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 d6c9cafd8..fd4fae90f 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 d6c9cafd8..fd4fae90f 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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.3/best-practices.md b/content/docs/1.5.3/best-practices.md index 82e4eeeda..fd4fae90f 100644 --- a/content/docs/1.5.3/best-practices.md +++ b/content/docs/1.5.3/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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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.4/best-practices.md b/content/docs/1.5.4/best-practices.md index 82e4eeeda..fd4fae90f 100644 --- a/content/docs/1.5.4/best-practices.md +++ b/content/docs/1.5.4/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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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 d6c9cafd8..fd4fae90f 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 -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. +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, if possible, because it generally has better performance and reliability. There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades. 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.