That makes sense...so you check the block checksum against the local DB
first, if it has a match, you add a reference to the same block for the
"new file" and continue on. If not, you add the checksum/block details
to the DB, compress it, encrypt it and send it for storage?
On 3/14/2014 12:04 PM, Nikolaus Rath wrote:
On 03/14/2014 08:11 AM, aweber1nj wrote:
Do all the features in the subject work well together? That is, can I
enable all three options and assume:
1. All my data will be stored encrypted.
2. Data is compressed before storing.
3. Identical blocks (of original content, pre-compression and
encryption I would assume) are only stored once (correctly
de-duplicated)?
Yes, they all work together. The order is: (1) deduplication, (2)
compression, (3) encryption.
Best,
-Nikolaus
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
