From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Automatic snapshot system?
Date: Fri Nov 30 02:53:01 2001 [thread overview]
Message-ID: <20011130082244.A379@btconnect.com> (raw)
In-Reply-To: <ufa667ts3zh.fsf@epithumia.math.uh.edu>; from tibbs@math.uh.edu on Thu, Nov 29, 2001 at 02:42:58PM -0600
On Thu, Nov 29, 2001 at 02:42:58PM -0600, Jason L Tibbitts III wrote:
> >>>>> "p" == petro <petro@auctionwatch.com> writes:
>
> p> We have a home-brewed perl script called from cron that does a
> p> snap, rsync's out the data, then releases the snapshot.
>
> Interesting, but not quite what I'm trying to do. Essentially I'd
> like to use snapshots as a sort of quick online backup to guard
> against users nuking their files. Of course we do backups nightly,
> but restoring from a snapshot is much quicker than messing with tapes.
>
> So, depending on how snapshots actually work and the performance
> penalty they incur and various other bits, I was thinking of doing a
> daily or twice-daily snapshot, keeping them around for a few days,
> then deleting them. But that entails having around 100 snapshots
> sitting around, and I don't know if there are performance problems
> with doing that.
It's a nice idea, but with the current implementation there's no way
I'd want 100 snapshots of the same origin hanging around.
- Joe
next prev parent reply other threads:[~2001-11-30 2:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 1:07 [linux-lvm] Automatic snapshot system? Jason L Tibbitts III
2001-11-29 2:46 ` Petro
2001-11-29 14:41 ` Jason L Tibbitts III
2001-11-29 14:58 ` Petro
2001-11-29 15:16 ` Jason L Tibbitts III
2001-11-30 2:53 ` Joe Thornber [this message]
2001-11-30 9:11 ` Jason L Tibbitts III
2001-12-03 8:18 ` Heinz J . Mauelshagen
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=20011130082244.A379@btconnect.com \
--to=thornber@btconnect.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.