On 5/1/07, Jim Dunham <[EMAIL PROTECTED]> wrote:

Brian,


I am aware that Sun just open sourced SVVR, which is volume based
replication. I however, am interested in near real time asyncronous
filesystem aware replication. (Think rsync, but near real time)


What is SVVR? Do you mean SNDR?


I meant SSAS.

Availability Suite, specifically SNDR supports; Time-Fixed Replication,
Synchronous (real time) replication, Asynchronous (near real time), the
latter of which is support with either memory or disk based queues.



I know, I had initially been very excited that this was what I wanted. (I am
still excited, but it just isn't exactly what I need right now). So that you
can understand what I am looking for, I will give you a sample aplication
for the replication tool I am trying to describe. You have ten servers in
your main datacenter. each of them have a filesystem that is 50GB. There is
a directory that has certain key information that I need replicated on each
of these filesystems. I want to replicate these directories from all ten
servers to a single server and to a single file system, housed in another
data center. From this datacenter, I need to replicate these directories to
other servers that are housed in local datacenters.

Assuming that something like this doesn't already exist in OpenSolaris, is
there any interest in a project like this? If so, is there anyone who would
be interested in implementing this? (I can discuss algorithms, and
architecture, but coding this is outside of my knowledge domain.)


Have you seen - http://www.opensolaris.org/os/project/avs/ ?


Yes. This is not what I am seeking.

.Availability Suite is both file system and storage volume agnostic, and is
Solaris kernel code.

My understanding is that SSAV is a volume/LUN level replication tool. While
this is great for many applications, I am looking for a file level
replication tool. (Keep this directory in sync with that.) Many might say
that rsync does this, but Rsync is not real-time asynchronous. To do this
you would have to intercept file writes, and log them to a transaction log
on a local file system. You would then drain these logs off to one or more
replication targets, that are running the syncronization client.

In the ideal world, you would have a compatibility mode that would support
any target that can run rync.

-Brian
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to