[Typo3-dev] Mirroring typo3.org etc.

Jan-Hendrik Heuing [netfielders] jh at netfielders.de
Thu Feb 5 14:58:08 CET 2004


It's of course  both... If it would be just a mirror, I don't think it's a
problem, there are nice solutions for static files out there. Search for
Eddie on sourceforge (or just eddi ?), loadbalancing with dns and so on...

But here again, no live replication of files or anything else.

With the coming MySQL-Cluster, the pages should be fairly stable. The
bottleneck has been the database a few times. So if the mysql-cluster is
running, I don't think it's worth spending the time in these solutions, as
it should not be a serious problem anymore. And if it happens to fail at
some point again... Bad luck, and it should be back up soon again in no time
in nearly any case. Of course in the event of fire... ;)

JH

"Rutger Meekers" <rutger at akku.be> schrieb im Newsbeitrag
news:mailman.1.1075984477.23530.typo3-dev at lists.netfielders.de...
> yes, that's true, but are we talking only about mysql that requires sync?
Or
> also about static files?
>
> When it's only mysql, you can attach a slave to the main mysql db. that
> should not give a problem.
> when there are also static files, i had to agree that there is not an open
> source solution known to me.
>
> "Christoph Moeller" <moeller at network-publishing.de> schreef in bericht
> news:mailman.1.1075983819.22291.typo3-dev at lists.netfielders.de...
> > Rutger Meekers schrieb:
> >
> > > i discussed with some people, and i was wrong about that mirror tool,
> it's
> > > only used for local mirrors in the same datacenter.
> > > but they said that rsync is no problem, because when de whole site is
> > > mirrored once, rsync will only tranfer the files that are changed. so
> this
> > > reduces useless traffic. php.net uses also rsync to keep theirs
mirrors
> up
> > > to date, and we are talking over lot's of mirrors and huge db's.
> >
> > Thanks for your investigation. rsync is a nice tool indeed, but this
> > doesn't solve any of the two-way syncing problems that were pointed out
> > in other previous mails.
> >
> > We'd need to build not only a "dump-to-the-slaves" setup, but also a
> > "merge-back-changes-from-slaves-to-master" solution - and this is where
> > (IMO) all open tools fail due to lack of algorithm.
> >
> > Chris
> >
> > -- 
> > network.publishing
> > internet & network service
> > moeller westbunk gbr
> >
> > ### now available: TYPO3 Lanyards :-)
> > ### -> http://www.network-publishing.de/lanyards.html
> >
>
>






More information about the TYPO3-dev mailing list