From: Gordon Henderson <gordon@drogon.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM & snapshots
Date: Tue, 20 Feb 2007 15:02:37 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0702201452390.27267@lion.drogon.net> (raw)
In-Reply-To: <45DAFBE8.2040009@gmail.com>
On Tue, 20 Feb 2007, Les Mikesell wrote:
> You might want to look at backuppc (http://backuppc.sourceforge.net/) to
> manage the on-line backups. It uses a scheme of compression and hard-linking
> duplicate files to greatly reduce the storage space you need when keeping a
> long history - especially if many files are unchanged over that time. With
> something that size you might still have to play some tricks with snapshots
> or break it down into smaller directory runs. It uses tar, smb, or rsync to
> do the actual copies, then has some extra overhead for the compression and
> linking jobs. If it is too slow, you might run it against your existing
> uncompressed copy so it has all day to make the long-term archive version.
Interesting, especially for the Win side of things, thanks!
However one of the things I may need is to use the backup server as a
"live" server, should the original server ever catch fire (or whatever),
so pull the backup from the bunker, drive it across town and with minimal
changes, have it take the place of the live server (turn on nfs/samba on
the appropriate locations) until we get a new one installed... So it's
compression would be of minimal use, but it may have other uses...
Thanks,
Gordon
next prev parent reply other threads:[~2007-02-20 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 12:58 [linux-lvm] LVM & snapshots Gordon Henderson
2007-02-20 13:40 ` Lars Ellenberg
2007-02-20 15:05 ` Gordon Henderson
2007-02-20 13:47 ` Les Mikesell
2007-02-20 15:02 ` Gordon Henderson [this message]
2007-02-20 19:12 ` Greg Freemyer
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=Pine.LNX.4.64.0702201452390.27267@lion.drogon.net \
--to=gordon@drogon.net \
--cc=linux-lvm@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).