[consulting] Distributed Loads, Failover and Dynamic Content

[Michael Haggerty]

Right now, we are using rsync to keep our servers synchronized. 

We tried unison, and found it had too many limitations despite the fact it
is really a wrapper for rsnyc.

There are technical reasons why we cannot take the following approach which
I have used in other clustering situations. There is a way to have multiple
clustered servers use a single, common filesystem. Mount a share from a
separate server to each of your Web servers and point the DocRoot on each to
the mount. This works really well and may be the best option available.
Makes backups a breeze.

M 

> -----Original Message-----
> From: Hugh Esco [mailto:he at reclaimedcomputers.ca] 
> Sent: Friday, July 14, 2006 5:41 PM
> To: consulting at drupal.org
> Subject: [consulting] Distributed Loads, Failover and Dynamic Content
> 
> I'm working with folks who would like to physically 
> distribute their server load so that they might be prepared 
> for peak demand as well as to provide for fail-over as part 
> of a disaster recovery plan.  
> 
> We're looking at rsync and such for static content.  But I'm 
> curious what strategies others might be pursuing for syncing 
> two or more servers which are hosting mirrored content on 
> dynamic platforms which are subject to local manipulation 
> between changes.  
> 
> I'm imagining some sort of hourly flatfile datadumps, which 
> would be diff'd and merged together with hourly restores.
> With DNS round-robin being used to distribute the load.  
> 
> Or I'm wondering if there is some way to put a trigger on 
> every database which is being mirrored, so that every 
> transaction against the db that inserted or updated a record 
> was logged and simultaneously run against the mirror data 
> sets on the remote hosts.  
> 
> Has anyone done something like this before?  Any clues on 
> potential strategies would be appreciated.  
> 
> --
> Hugh Esco
> RCK Computer Services
> http://reclaimedcomputers.ca/
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
> 
>