[Csync2] cysnc2 vs linking hackery
Giampaolo Tomassoni
g.tomassoni at libero.it
Tue Dec 5 21:05:37 CET 2006
From: csync2-bounces at lists.linbit.com
> Hi Rafiu,
>
> > Hi all,
> >
> > I've been reading about csync2 and want to find out whether it can
> > be recommended for use in DRBD+HA setup instead of the metadata
> > volume + FS links method. I've never liked the latter way of doing
> > it and if csync2 is an option it certainly would solve a heck of a
> > number of configuration problems for me.
>
> I'm not sure I full understand your requirements but I currently
> use csync2
> in a DRBD+HA environment without any issues.
>
> The clustering software I use is linuxha.net, which handles all the
> heartbeat, failover, drbd, etc while csync2 just synchronises
> config files
> between the machines.
>
> Have been using this for well over a year now with no dramas.
I guess Rafiu would like to sync metadata with it. If this is the case, I'm not shure csync2 can help.
Don't know what's supposed to be in /var/lib/nfs (it's years I don't use it anymore), but the content of /var/cache/samba looks like a lot of BDBs, which are not safe to be syncd through csync2.
giampaolo
> Michael.
>
> > I read in an ML post that csync2 is only recommended for slow
> > changing config files. How would that apply to metadata for services
> > like nfs , Samba/winbind etc. Could I use csync2 to replicate
> > /var/lib/nfs and /var/cache/samba for instance?
> >
> > If csync2 is not the way to go, how about a cross between the
> > metadata volume and some other [d|i]notify based solution where
> > local changes (on active primary) are synced to the metadata volume
> > and then synced back to place (on passive secondary), controlled as
> > a heartbeat resource, when a failover occurs.
> >
> > TIA
> >
> > R.
>
> _______________________________________________
> Csync2 mailing list
> Csync2 at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/csync2
More information about the Csync2
mailing list