Update docs/docs/backups.md

Co-authored-by: Florent BEAUCHAMP <[email protected]>
vatesfr · Jan 24, 2025 · 98369f8 · 98369f8
1 parent 4d784b0
commit 98369f8
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/docs/docs/backups.md b/docs/docs/backups.md
@@ -48,7 +48,8 @@ Encryption is opt-in and requires configuring an encryption key on the remote.
 
 #### What is AES-256-GCM?
 
-Currently, backups use the [`AES-256-GCM`](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) encryption algorithm. While this is a highly secure option, it does have a file size limitation of 64 GiB. This isn't an issue when working with Amazon S3, as the data is split into smaller blocks, making it fully compatible with the platform. 
+Currently, backups use the [`AES-256-GCM`](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) encryption algorithm. While this is a highly secure option, it does have a file size limitation of 64 GiB. This isn't an issue when working with incremental backups, as the data is split into smaller blocks, making it fully compatible with any remote ( S3 compatible or file based). 
+Full backups creates one file per backup with all the data , that can go over 64GB, even when using xcp-ng zstd encryption
 
 #### Authentication