From: Nganon <nganon+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to build a time machine on Gentoo
Date: Mon, 16 Aug 2010 13:27:38 +0300 [thread overview]
Message-ID: <AANLkTimOLteya7ni-7FLH+xZ_MfsHtY7C_2YQ=zAtXMN@mail.gmail.com> (raw)
In-Reply-To: <201008160215.55382.wonko@wonkology.org>
[-- Attachment #1: Type: text/plain, Size: 3916 bytes --]
On 16 August 2010 03:15, Alex Schuster <wonko@wonkology.org> wrote:
> Nganon <nganon+gentoo@gmail.com <nganon%2Bgentoo@gmail.com>> writes:
>
> > Hello all,
> >
> > My first post on the list. I thought I would start with something
> > that I started
> > to think of as 'essential' after losing 90GB of data. Now I have two
> > main questions in mind: what to and how to back up on gentoo most
> > efficiently.
> >
> > 1. Apart from users' home directories and the followings, what should
> > be backed
> > up on a gentoo machine?
> > /etc/portage/
> > /root
> > /var/lib/portage
> > ...?
>
> Wouldn't it be easier to just backup the whole / directory?
> Excluding /home, /usr/portage and /var/tmp/portage?
>
> Yes but that would not solve my huge backup file problem, would it?
> > 2. Erm..okay, I am gonna say, what magic I want and then ask your way.
> > I first started making gzipped tar balls as follows:
> >
> > tar czpf /media/backups/userA-`date +%Y.%m.%d`.tgz -X
> > userA-excludelist /etc
> >
> > But these can get huge especially for home dirs. I also want safe dvd
> > copies.
> > Though I can find enough space on the external drives, I don't trust
> > them any more. See above..sigh..(No I recovered about one third of it
> > with testdisk/photorec
> > which names them as file000001 file00002.. and half them are zero
> > sized.. which
> > quite justifies my agony)
>
> Okay, but I don't trust DVDs. Although DVD-RAM is quite safe I heard.
> But external disks are flexible, offer more space, and if you want more
> security, just use yet another drive, so you are safe even if your main
> drive and a backup drive fails.
>
> I did not give a thought to DVD-RAM before. Will give it a try. Thanks.
I suggest you have a look at rdiff-backup. It gives you a 1:1 copy of
> the source directory, but also does incremental backups, which are
> stored (in compressed form) in an additional folder in the destination
> directory. I would use this at least for things like /etc, where I
> sometimes might want to retrieve an old version of a file. Similar to
> your approach with big tar files and small ones containing the
> increments.
>
> I just emerged and tried it. Seems like incremental backups was what I
was looking for. But from what I see, it is mirroring the src to dist and
storing the metadata/stats of increments as archived. Maybe there is an
option to archive increments along side their metadata as well. I will keep
playing with it.
I use a script for my backups, which I mentioned here on 2010-05-07,
> subject 'Snackup'. It optionally creates LVM snapshots so I can make
> backups from the running system, even if the source directory is
> altered during the backup. This works on LVM only, though, and also
> allows the volume to be LUKS-encrypted. It does backups by rdiff-backup,
> rsync, cp, tar or dd. It may be overkill when not using the LVM
> features, but still I suggest to use some script for backups, so one
> does not always have to remember the backup commands. When I want to
> update my backup, I enter something like 'snackup boot root home src',
> and the script backs up my boot, root and home partition in the
> background, and creates tar files each directory in /usr/src.
>
> I found the thread and script. I am gonna take a look at it. Once I decide
on
how to backup, I am gonna cron a script for it.
> > By the way, since I want dvd backups as well, and I want to use +rw
> > dvds so I can overwrite old backup after a while, what is best way of
> > ensuring the integrity and safety of them. Is it a good idea to use
> > truecrypt containers? Or nothing tops signing and encrypting with gpg?
>
> I'd use DVD-RAM. The media is a little more expensive, but AFAIK they
> were made with long-time backups in mind. And access is much easier,
> you just copy the files as to an external drive, no need to burn ISOs.
>
> Wonko
>
>
Thanks for the advises.
[-- Attachment #2: Type: text/html, Size: 5263 bytes --]
next prev parent reply other threads:[~2010-08-16 10:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 23:11 [gentoo-user] How to build a time machine on Gentoo Nganon
2010-08-16 0:15 ` Alex Schuster
2010-08-16 10:27 ` Nganon [this message]
2010-08-16 8:36 ` Marco
2010-08-16 10:30 ` Nganon
2010-08-16 21:37 ` Mick
2010-08-16 23:53 ` Thomas Yao
2010-08-17 11:34 ` Nganon
2010-08-17 11:29 ` Nganon
2010-08-17 12:14 ` Maximilian Bräutigam
2010-08-17 12:33 ` Alex Schuster
2010-08-18 11:04 ` Nganon
2010-08-18 11:34 ` Neil Bothwick
2010-08-18 11:53 ` Nganon
2010-08-18 14:53 ` Bill Longman
2010-08-18 18:03 ` Nganon
2010-08-18 18:37 ` Bill Longman
2010-08-18 18:49 ` Joerg Schilling
2010-08-18 19:04 ` Nganon
2010-08-18 19:28 ` Joerg Schilling
2010-08-18 19:09 ` Bill Longman
2010-08-18 19:29 ` Alan McKinnon
2010-08-18 20:03 ` Joerg Schilling
2010-08-19 9:30 ` Joerg Schilling
2010-08-18 18:53 ` Nganon
2010-08-17 19:34 ` Enrico Weigelt
2010-08-18 11:09 ` Nganon
2010-08-18 11:59 ` William Kenworthy
2010-08-18 17:56 ` Nganon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimOLteya7ni-7FLH+xZ_MfsHtY7C_2YQ=zAtXMN@mail.gmail.com' \
--to=nganon+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox