We have it implemented using and external, redundant , load balancer. It really comes down to your budget.
John On Mon, Feb 15, 2016 at 8:58 AM, Bob <bobnli...@gmail.com> wrote: > Hello, > > Thanks for the valuable suggestions. > > What can be done to assure the high-availability of the reverse proxy > itself ? > What about the latency if the master and hot standby located in two > different data center ? > > > > On Sunday 14 February 2016 10:43 PM, Yehuda Katz wrote: > > We use three different methods: > 1. Content on NFS server > 2. Content auto-committing and auto-pulling over git about every 15 minutes > 3. Separate database server - with replication for backup. > > - Y > > Sent from a device with a very small keyboard and hyperactive autocorrect. > On Feb 14, 2016 5:28 PM, "Rose, John B" <jbr...@utk.edu> wrote: > >> What is your preferred approach to keeping content in sync? >> >> Sent from my iPad >> >> On Feb 14, 2016, at 3:47 PM, Daniel < <dferra...@gmail.com> >> dferra...@gmail.com> wrote: >> >> with a reverse proxy in front of both, you use balancer setup specifying >> the second web server as hot standby >> >> El dom., 14 feb. 2016 a las 16:49, Bob (<bobnli...@gmail.com>) escribió: >> >>> Hello list, >>> >>> I have two servers. One is already up with apache, mysql etc.. >>> Now I wonder if I can configure the second server as a fallback web >>> server. >>> The idea is.. if first web server is down , the second one will serve >>> the requests. >>> >>> Any suggestion / idea is very much welcome. >>> >>> Thanks and regards, >>> Bob >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >>> For additional commands, e-mail: <users-h...@httpd.apache.org> >>> users-h...@httpd.apache.org >>> >>> >
