On 20100906 14:50, David Nicol wrote:
Only off-topic if BTRFS isn't ever going to ooze into the space
currently occupied by the likes of
http://en.wikipedia.org/wiki/Global_File_System
that is, file systems that have multiple nodes simultaneously
accessing block devices and tolerating faults.
On Mon, Aug 30, 2010 at 11:14:51AM -0700, K. Richard Pixley wrote:
On 20100830 10:59, Roy Sigurd Karlsbakk wrote:
I think drbd does precisely what you want.
It's not useful for fault tolerance, nor for load balancing, but it
will
produce a remote block copy that can be used as a sort of
On Tue, Aug 31, 2010 at 07:07:29AM +0200, Fred van Zwieten wrote:
Hmmm, maybe, but rsync would take a lot of time to find the changes.
the actual blocks of a snap _are_ the changes, that's why SnapMirror
is very efficient. And, I don't see how rsync will retain the snap's
between both sites.
On Tuesday, 31 August, 2010, Simon Kirby wrote:
[...]
Anyway, there _is_ this interface:
btrfs subvolume find-new path last_gen
List the recently modified files in a filesystem.
Eg:
btrfs sub find-new /mnt 0
This should print all files on the file system,
Thinking about this a bit more, would a setup with btrfs on top of
DRBD be a setup that comes in the neighboorhood of what SnapMirror
provides? DRBD does replication at the blocklevel, without any notion
of a filesystem on top of it (as I understand this). So, if I make a
snapshot on a DRBD'ed
Hi there,
I would like to know if there is something functionally equivalent to
NetApp's SnapMirror in the works or planning? It would require block
level access to a snap and the ability to rebuild (subvolumes
including it's) snap's on another machine.
If not, what would be the best way to
LVM Snapshot.
lvm -s -n SnapShotName /dev/VolumeGroup/SourceLogicalVolumeName
you may need to pass -l or -L to give an initial size for the COW.
(as for rebuilding on another machine, that would require shared
storage or additional LVM tricks to export/import - or good old
fashioned dd)
that
- Original Message -
Hi there,
I would like to know if there is something functionally equivalent to
NetApp's SnapMirror in the works or planning? It would require block
level access to a snap and the ability to rebuild (subvolumes
including it's) snap's on another machine.
If
On 20100830 10:07, Fred van Zwieten wrote:
Hi there,
I would like to know if there is something functionally equivalent to
NetApp's SnapMirror in the works or planning? It would require block
level access to a snap and the ability to rebuild (subvolumes
including it's) snap's on another
I think drbd does precisely what you want.
It's not useful for fault tolerance, nor for load balancing, but it
will
produce a remote block copy that can be used as a sort of hot
backup.
drbd with heartbeat/pacemaker can provide fault tolerance...
Vennlige hilsener / Best regards
roy
--
On 20100830 10:59, Roy Sigurd Karlsbakk wrote:
I think drbd does precisely what you want.
It's not useful for fault tolerance, nor for load balancing, but it
will
produce a remote block copy that can be used as a sort of hot
backup.
drbd with heartbeat/pacemaker can provide fault tolerance...
I just glanced over the DRBD/LVM combi, but I don't see it being
functionally equal to SnapMirror. Let me (try to) explain how
snapmirror works:
On system A there is a volume (vol1). We let this vol1(A) replicate
thru SnapMirror to vol1(B). This is done by creating a snap vol1sx(A)
and replicate
On Mon, Aug 30, 2010 at 2:15 PM, Fred van Zwieten fvzwie...@gmail.com wrote:
I just glanced over the DRBD/LVM combi, but I don't see it being
functionally equal to SnapMirror. Let me (try to) explain how
snapmirror works:
On system A there is a volume (vol1). We let this vol1(A) replicate
If you can put the db into a consistent state, then rsync will do
this. Rsync does changed block transfers.
--rich
On 8/30/10 14:15 , Fred van Zwieten wrote:
I just glanced over the DRBD/LVM combi, but I don't see it being
functionally equal to SnapMirror. Let me (try to) explain how
Hmmm, maybe, but rsync would take a lot of time to find the changes.
the actual blocks of a snap _are_ the changes, that's why SnapMirror
is very efficient. And, I don't see how rsync will retain the snap's
between both sites. It would be great if a tool like rsync could have
access to the changed
15 matches
Mail list logo
