Backup recommendation
in [UK Linux]
|
Prev: Compaq NS5000...
Next: Backup to DVD
From: Martin Gregorie on 19 Dec 2008 20:45 On Fri, 19 Dec 2008 23:54:17 +0000, Ian Rawlings wrote: > That's down to what you have a pressing need for I suppose, either > storing encrypted data in a database or running an encrypted filesytem! > After a quick scan of the LUKS website, it looks like the simplest approach. I've been fairly careful to concentrate sensitive items in one directory on my main server. Managing reference information on my LAN via an internal website has really helped to make this approach simple, so in fact my best move is simply to put that directory in a tiny encrypted partition and then nuke free space on its current partition with one of the free-space mungers. I've bookmarked the LUKS site - thanks for the pointer. > If you have a linux laptop then I'd be tempted to pursue LUKS first and > move the laptop across to it (not hard to do) as the risk of losing the > laptop or it getting stolen can be high and the consequences dire so > that would be a useful driver for the pretty short learning curve > involved. > I have one, but it almost never travels anywhere - its primarily used as a quiet terminal for the server. It contains nothing vital that isn't also replicated on the server. If I do go anywhere with it, it gets a copy of the reference pages loaded on it, so it should be equally easy to copy the sensitive stuff to an encrypted partition on it. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
From: Gordon Henderson on 20 Dec 2008 09:02 In article <slrngkno3b.jhj.news06(a)desktop.tarcus.org.uk>, Ian Rawlings <news06(a)tarcus.org.uk> wrote: >On 2008-12-19, Gordon Henderson <gordon+usenet(a)drogon.net> wrote: > >> I know what a hard link is and what it does, and the difference >> between that an a symbolic link, and I've never said that backup up >> to the same server is anything other than accidental deletion >> prevention. > >Certainly, but there are people taking hints from this thread so best >watch ourselves ;-) Advice is worth what you pay for it :) Gordon
From: Theo Markettos on 21 Dec 2008 08:51 Martin Gregorie <martin(a)see.sig.for.address.invalid> wrote: > After a quick scan of the LUKS website, it looks like the simplest > approach. I've been fairly careful to concentrate sensitive items in one > directory on my main server. Managing reference information on my LAN via > an internal website has really helped to make this approach simple, so in > fact my best move is simply to put that directory in a tiny encrypted > partition and then nuke free space on its current partition with one of > the free-space mungers. Is LUKS the most widespread Linux disc encryption? There seem to be plenty of old HOWTOs out there, but it's difficult to find out what's the mainstream. I must have a read about the crypto (key management etc) at some point. I went to a talk by Poul Henning-Kemp who did FreeBSD's GBDE disc encryption which sounds vaguely sane. But it's a pity that each platform has their own approach. Theo
From: Ian Rawlings on 21 Dec 2008 09:58 On 2008-12-21, Theo Markettos <theom+news(a)chiark.greenend.org.uk> wrote: > Is LUKS the most widespread Linux disc encryption? There seem to be plenty > of old HOWTOs out there, but it's difficult to find out what's the > mainstream. It seems to be the most popular or most supported, it's part of cryptsetup now, I think the main advantage of LUKS over other systems is that it's largely plug and play to the extent that a LUKS partition can be read by other linux boxes with mainly just the password being the missing bit of information, all the details such as the encryption type and key lengths etc are stored in the partition itself. Gentoo linux even has LUKS as an option in its auto-generated initrd setup so it's easy to make full disc encrypted systems. -- Blast off and strike the evil Bydo empire! http://youtube.com/user/tarcus69 http://www.flickr.com/photos/tarcus/sets/
From: Nix on 21 Dec 2008 10:13
On 19 Dec 2008, Martin Gregorie told this: > - I have a 120 GB 3.5" drive that lives on top of the PC and gets > a daily .TGZ compressed backup of the whole system from a daily > cron job. This takes 75 minutes and requires a fairly elaborate > script that automatically deletes enough of the oldest backups to > leave room for the next, does the backup and mails me a run report. > These backups are there to provide protection against finger trouble > or disk failure. If there's a fire or a major power spike these > backups will be toast along with the PC. I'd like to do something similar to this, only keeping it shut down except when needed. I haven't paid any attention to hardware for nearly a decade so I have no idea if this is possible, but is there a way to automatically cut/restore power to something like this under software control? (I know I could do it with a wall timer, but that can't be told to turn *off* at the right time, so either it'll run for too long or cut power in the middle of a backup!) |