From: Brian Neu <proclivity76@yahoo.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] snapshot pools, lvm roadmap
Date: Fri, 7 Jan 2011 11:01:56 -0800 (PST) [thread overview]
Message-ID: <963006.39922.qm@web39303.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1101061943130.14845@bmsred.bmsi.com>
> I'm not sure what "Volume Shadow Copy" actually does, but we use DRBD (Data
> Replicating Block Device) to remotely mirror block devices - which could be
> marketed as "Volume Shadow Copy".
MS's VSS is their implementation of snapshots at the fs level. For instance,
you can set the C drive to back up to a D drive, allocating 80GB for all C drive
snapshots. Snapshots are removed automatically on a First-In, First-Out basis
as the storage ceiling is reached. Because the storage is shared, they can also
be deduplicated for speed and storage efficiency. Again, this has been in place
since 2003.
As I understand LVM now, each snapshot must have individual storage allocated.
When that ceiling is reached, the snapshot must still be manually removed.
Since snapshot storage can't be shared, copied blocks must be written to every
active snapshot, causing both a space and speed inefficiency.
I'm familiar with DRBD and have implemented it on HA systems. It's great, but
has nothing to do with the shared snapshots storage I desire for Linux.
next prev parent reply other threads:[~2011-01-07 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 7:11 [linux-lvm] snapshot pools, lvm roadmap Brian Neu
2011-01-05 18:34 ` Brian Neu
2011-01-06 11:59 ` Joe Thornber
2011-01-07 19:33 ` Brian Neu
2011-01-07 20:27 ` Phillip Susi
2011-01-07 20:41 ` Alasdair G Kergon
2011-01-10 10:15 ` Joe Thornber
2011-01-10 15:30 ` Phillip Susi
2011-01-05 18:45 ` Stuart D. Gathman
2011-01-05 20:56 ` Brian Neu
2011-01-06 16:15 ` Phillip Susi
2011-01-07 1:09 ` Stuart D. Gathman
2011-01-07 19:01 ` Brian Neu [this message]
2011-01-08 16:17 ` Stuart D. Gathman
-- strict thread matches above, loose matches on Subject: below --
2011-01-18 15:39 Brian Neu
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=963006.39922.qm@web39303.mail.mud.yahoo.com \
--to=proclivity76@yahoo.com \
--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 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.