Skip to content

Commit

Permalink
Update content/docs/1.6.0/best-practices.md
Browse files Browse the repository at this point in the history
Co-authored-by: Jillian <[email protected]>
  • Loading branch information
james-munson and jillian-maroket authored Oct 31, 2023
1 parent a9399e1 commit 83c1182
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/docs/1.6.0/best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -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. 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.
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.

Expand Down

0 comments on commit 83c1182

Please sign in to comment.