Trevor Vaughan typed, at or about 7/6/2005 12:09 PM, ...
> Basically, what I am asking is if a hot backup site can be configured.
> I.e. Site A has the main OTRS service and Site B has a backup that
> must be synchronized with Site A.
>
> In the case that Site A fails, Site B should be able to pick up from
> where Site A left off with no major problems (I understand that
> e-mails may be forced into queues).
> Finally, when Site A comes back online, it should synchronize with
> Site B and resume the primary server function.
> I believe that the setup you describe would work but it may be
> interesting getting the heartbeat metrics correct at distributed
> sites.
Not at all! heres an idea:
All the main data is in a centralized database. OTRS runs on multiple
webservers, all talking to the same database, that way theres no need to
synchronize. Just make sure the Database machine is rock solid.
The only thing you need to really worry about is both websesrvers
replicating work with their cron jobs
You can do one of two things:
A) Make a "WhichServer" table in your database, each webserver gets a
script to check and see whis supposed to be the main server, and who is
still alive, and who needs to be running the cron jobs
B) Let BOTH webservers run the cronjobs, just stagger them a little. You
wouldnt even need heartbeats, then.
--
-Tony
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support oder Consulting für Ihr OTRS System?
=> http://www.otrs.de/
