public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Writing a bash script or thinking about it anyway.
Date: Tue, 22 Dec 2009 15:39:49 +0000	[thread overview]
Message-ID: <20091222153949.5c4865d2@digimed.co.uk> (raw)
In-Reply-To: <c1c10dab0912220708i1ae645bbk593896d42d68401b@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

On Tue, 22 Dec 2009 16:08:18 +0100, Ward Poelmans wrote:

> You should take a look at rsnapshot ( http://rsnapshot.org/ ). I use
> it and it works perfectly. But it's written in perl and not bash, i'm
> afraid.

That misses the point. This isn't really about making backups, it's about
learning to write shell scripts. Backing up is just the project that Dale
has chosen for this first effort, at least that's how I read it.

Having said that, you need an underlying program to perform the backups,
and the main choices are tar and rsync. Rsync has all the advantages
already mentioned, but it does need a lot of space and needs the
filesystem to be used for backups to support all the metadata of the
source. Tar handles both of these issues, but incremental backups are
more complicated to make and restore. On the other hand, you do get
history, while rsync only has the most recent copy of the file. If you
found the file was corrupt just after an rsync backup, touch!

I really like BackupPC, but that's totally irrelevant to the original
question.


-- 
Neil Bothwick

We all know what comes after 'X', said Tom, wisely.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-12-22 15:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22  3:22 [gentoo-user] Writing a bash script or thinking about it anyway Dale
2009-12-22  3:53 ` Francisco Ares
2009-12-22  4:16   ` Dale
2009-12-22  4:32     ` Francisco Ares
2009-12-22  5:02 ` Neil Walker
2009-12-22  5:09   ` Dale
2009-12-23  1:45     ` Francisco Ares
2009-12-25 23:21       ` Dale
2009-12-22 10:34 ` Jesús Guerrero
2009-12-22 11:20   ` Christian Könitzer
2009-12-22 12:11     ` Jesús Guerrero
2009-12-22 14:21       ` Christian Könitzer
2009-12-22 14:51         ` Alan McKinnon
2009-12-22 15:36           ` Jesús Guerrero
2009-12-22 19:01             ` Stroller
2009-12-23  6:58               ` Dirk Heinrichs
2009-12-22 18:56   ` Stroller
2009-12-22 23:25   ` Willie Wong
2009-12-22 11:16 ` Stroller
2009-12-22 23:30   ` Willie Wong
2009-12-22 15:08 ` Ward Poelmans
2009-12-22 15:39   ` Neil Bothwick [this message]
2009-12-22 15:57     ` Ward Poelmans
2009-12-23  0:33 ` [gentoo-user] " »Q«
2009-12-25 23:19   ` Dale
2009-12-27 21:09     ` »Q«
2009-12-23 12:29 ` [gentoo-user] " Alex Schuster

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=20091222153949.5c4865d2@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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