public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Back up a server in real-time
Date: Sun, 16 Nov 2008 19:31:16 +0900	[thread overview]
Message-ID: <1226831476.21629.33.camel@rattus.localdomain> (raw)
In-Reply-To: <200811161158.01059.alan.mckinnon@gmail.com>

It actually does a very fast, space efficient backup management.

As for restore, each backup is effectively an uncompressed fully
accessible mirror image so you can manually copy/tar/... etc back for
the full system, or individual files.  The developers basically say we
have a working backup system where you can restore using standard tools
if needed, but we'll make it easier when we can get around to it.

Having versioned backups can be REALLY handy at times.  Space efficiency
typically stabilises at 2x archive size depending on delta.

Downside it can hammer a disk - reiserfs is fine but ext2/3 was flaky.

moriah ~ # esearch dirvish
[ Results for search key : dirvish ]
[ Applications found : 1 ]

*  app-backup/dirvish
      Latest version available: 1.2.1
      Latest version installed: 1.2.1
      Size of downloaded files: [no/bad digest]
      Homepage:    http://www.dirvish.org/
      Description: Dirvish is a fast, disk based, rotating network
backup system.
      License:     OSL-2.0

Its worth a read on how its done - using smarts rather than brute force!

BillK

On Sun, 2008-11-16 at 11:58 +0200, Alan McKinnon wrote:
> On Sunday 16 November 2008 11:04:41 William Kenworthy wrote:
> > dirvish is in portage.
> >
> > tar/rsync/cp are not really backups but manual copies.  If you want true
> > backup you need scripts to handle the extra functionality for things
> > like versioning, archive management and the all important restore.
> >
> > Dirvish is excellent on all but restore.
> 
> Which raises the question:
> 
> What's the point of it then?
> 
> OTOH, it has to be better than legato. Nothing could be worse than legato.
> 
> 
-- 
William Kenworthy <billk@iinet.net.au>
Home in Perth!




  reply	other threads:[~2008-11-16 10:31 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
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 [this message]
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=1226831476.21629.33.camel@rattus.localdomain \
    --to=billk@iinet.net.au \
    --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