j k <[email protected]> writes:
> Hi,
>
> I'm running s3ql 2.x with Google Cloud Storage as my backend. I'm running a
> cloud based storage front-end for users where their data is stored on the
> s3ql mounted drive. I have two questions about versioning and s3ql:
>
> 1) Would enabling versioning allow me to recover files that were
> accidentally deleted (user error, application error, malicious user, etc) ?
> It would be fairly simple to restore the deleted object in the bucket with
> versioning enabled, but I'm wondering how s3ql would handle having a data
> block file suddenly re-appear. I'm guessing it would just ignore it and
> there would be no way to re-incorporate it back into the meta-data.
Correct.
> 2) If versioning as described above is a sufficient mechanism for
> recovering lost files with s3ql, would enabling versioning on an
> in-production bucket affect my data in any way?
No. However, if you undelete storage objects, you'll get warnings from
fsck.s3ql.
A much better way to protect against accidential deletion is to
periodically run s3qlcp + s3qllock. s3qlcp creates a snapshot of a
directory tree, and s3qllock makes the snapshot immutable.
Best,
-Nikolaus
--
Encrypted emails preferred.
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
»Time flies like an arrow, fruit flies like a Banana.«
--
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.
