public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Back up a server in real-time
Date: Sun, 16 Nov 2008 11:54:04 +0200	[thread overview]
Message-ID: <200811161154.04361.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <200811160008.58417.michaelkintzios@gmail.com>

On Sunday 16 November 2008 02:08:42 Mick wrote:
> On Saturday 15 November 2008, Dale wrote:
> > Mick wrote:
> > > Without gentoo-wiki my knowledge level is rather poor (just like my
> > > memory!)
> > >
> > > What would you use to back up a running server without taking it off
> > > line?
> >
> > I keep mine simple, cp -auv paths/you/want/to/backup back/up/to  It has
> > works so far.  Thought about doing a cron job but that complicates
> > things.  :/
>
> Thank you all for the suggestions and for the link to the wiki!  I've got
> some reading to do.  ;-)
>
> Whenever I have used tar to back up a whole OS I used it with a LiveCD. 
> This was to make sure that files and their metadata were not being changed
> while I was tar'ing them.
>
> Are you saying that I can actually fire up tar/rsync and back up in real
> time?

Yes. Unix does some RealSmartThings(tm) when using files. The name is just a 
pointer to the actual file, represented by an inode. Once you have an inode 
open, it stays open until everything using it closes it. So you can 
add/delete/copy/move files by name with impunity as you then just move names 
around. Contrast this with other inferior systems, like say Windows for 
example, which has a built-in self-destruct button when you try this...

> I was gravitating towards using LVM snapshot and then tar'ing that to an
> external USB drive.

This is the preferred way, as you get a consistent snapshot frozen at a point 
in time. This deals nicely with inconsistencies caused by files changing 
while you are backing up other ones.

-- 
alan dot mckinnon at gmail dot com




  parent reply	other threads:[~2008-11-16  9:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 19:45 [gentoo-user] Back up a server in real-time Mick
2008-11-15 20:13 ` Volker Armin Hemmann
2008-11-15 20:23 ` Alan McKinnon
2008-11-15 20:29 ` Jerry McBride
2008-11-15 20:38 ` Dale
2008-11-16  0:08   ` Mick
2008-11-16  0:42     ` Dale
2008-11-16  2:58     ` Jerry McBride
2008-11-16  9:54     ` Alan McKinnon [this message]
2008-11-16 11:51       ` Mick
2008-11-16 13:08         ` Alan McKinnon
2008-11-16 17:12     ` Jorge Peixoto de Morais Neto
2008-11-16  5:16 ` jaeyoung lee
2008-11-16  9:04 ` William Kenworthy
2008-11-16  9:36   ` Volker Armin Hemmann
2008-11-16  9:58   ` Alan McKinnon
2008-11-16 10:31     ` William Kenworthy
2008-11-16 10:39       ` Alan McKinnon
2008-11-16 12:36         ` William Kenworthy
2008-11-16 13:15           ` Alan McKinnon
2008-11-17 16:07   ` Joerg Schilling
2008-11-30 22:56     ` Mick
2008-11-30 23:04       ` Joerg Schilling
2008-11-16 10:35 ` Dirk Heinrichs
2008-11-19 16:59 ` Mark Somerville
2008-11-19 17:15   ` [gentoo-user] " Harry Putnam
2008-11-20  7:15     ` Dirk Heinrichs

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=200811161154.04361.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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