Linux LVM users
 help / color / mirror / Atom feed
From: "Wolfgang Weisselberg" <uzx87lvfmukwc001@sneakemail.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Block-Level Backup
Date: Fri Aug  8 08:46:02 2003	[thread overview]
Message-ID: <10920-38778@sneakemail.com> (raw)
In-Reply-To: <3F328E3A.6070203@conterra.de>

Dieter Stueken wrote 67 lines:

> But seriously: there is some other interesting possibility. After you
> made the snapshot, don't try do save it elsewhere. Instead just keep it!
> I use a similar system since a year now. It holds a full mirror of
> all my data, thus its some kind of full backup. Each night I
> synchronize all modified files, but keep the previous state, too.
> Its like a  snapshot. As all unchanged data is shared between the
> snapshots, the whole thing grows quite moderately compared to its
> total size (200Gb).

> Thus I have a snapshot of all my data for each day. I save them daily
> for about a week. Then I thin them out, keeping the Sundays only.
> After a few weeks I keep one snapshot per month etc. This is equivalent
> to dealing with a bundle of tapes, but much much easier.

Sounds interesting.  How does defend against:
- hard disk head crashes 
- a lightning striking your PC, roasting your HDs (and any tape
  drive, and all the rest)
- software errors (e.g. in LVM, in your scripts)
- operator errors (removing the wrong snapshot(s))
- cracker attacks
- corrupted main file system (even fdisk giving up), due to
  some software/hardware problem (e.g. cable came half off)

With a backup which migrates/copies the data to tapes, I can at
least:
- replace broken HDs/computers
- know the data was at least readable at the time of the
  backup, and any later accidents are recoverable
- it's much harder to nuke 2+ tapes/backup sets by operator
  error.

-Wolfgang

  reply	other threads:[~2003-08-08  8:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07  4:14 [linux-lvm] Block-Level Backup Rocky Lee
2003-08-07  4:28 ` Frank Van Damme
2003-08-07  4:34 ` Jose Luis Domingo Lopez
2003-08-07  4:37 ` Joe Thornber
2003-08-07  7:48   ` Christophe Saout
2003-08-07  8:45     ` Herbert Pötzl
2003-08-07 10:12       ` Bill Rugolsky Jr.
2003-08-07 10:55         ` Joe Thornber
2003-08-07 11:33           ` Bill Rugolsky Jr.
2003-08-07 12:39             ` Dieter Stueken
2003-08-08  8:46               ` Wolfgang Weisselberg [this message]
2003-08-07  8:28 ` Mark H. Wood
  -- strict thread matches above, loose matches on Subject: below --
2003-08-07  3:02 Rocky Lee
2003-08-07  3:29 ` Markus Schiltknecht

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=10920-38778@sneakemail.com \
    --to=uzx87lvfmukwc001@sneakemail.com \
    --cc=linux-lvm@sistina.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