[dm-crypt] Protection against data failure

Sun_Blood sblood at gmail.com
Wed Aug 10 14:44:38 CEST 2011

Thanks. That is a great idea. I was thinking on to advance solutions
to realize that what you say a secondary disk with its own LUKS header
and some crafty snapshot or normal backup procedure is probably the
easiest and best.

Thanks for all your answers. I feel I have a much clearer look on how
LUKS works(and some lvm too :-))

A final question that is more LVM but it sounds like you have some
knowledge in this area. My setup is LVM -> LUKS -> Filesystem.
If I use LVM snappshots on the LVM will the LUKS header also be
backuped because it's on top of LVM?


On Wed, Aug 10, 2011 at 2:12 PM, Marc Ballarin <ballarin.marc at gmx.de> wrote:
> Hi,
>> ...
>> What I'm looking for is a way to protect the system from myself.
>> Hardware is one way and with that I can protect myself against
>> hardware failure good enough with raid and SMART disk.
>> But if I accidental overwrite the first part of the disk or some other
>> important part can I protect myself from that?
> Just make complete backups. Instead of putting your second hard disk in a
> mirror-RAID, put it in an eSATA or USB chassis or in some NAS device.
> RAID-1 does not replace backups. Its primary purpose isn't even data safety
> but high system availabilty - and unless you really need this, it is rather
> pointless.
> As you (unlike many others) recognized, you are the biggest danger yourself
> and the only way to protect against this, is regular backups. Either
> incremental/differential backups or - in my opinion ans experience much
> preferable at home: simple backups in combination with some snapshotting
> mechanism (LVM, btrfs, ZFS, ...).
> (You can use snapshots at your backup source to get consistent data, but
> also at the target to keep old versions.)
> Simply encrypt your backup disk using its own LUKS header and don't even
> bother with special header backups.
> Regards,
> Marc

More information about the dm-crypt mailing list