> Victor,
>
> Thanks for the response and I apologize for the confusing language.
Don't worry... probably it's my fault as I haven't sleeped enough...
> 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.
Ok but... Site A and Site B are different locations? (different
internet addresses,
different ISP's, and so on) If they are, things will be a bit more complicated.
In my setup,
OTRS is accessed using an internal IP address (192.168.0.23) that "floats"
between my
two servers (it's on the master until it fails or I take it down). That will
work exactly the
same using Internet IP's of the same range, but not if they're of different
ranges.
> I believe that the setup you describe would work but it may be
> interesting getting the heartbeat metrics correct at distributed
> sites.
When making this kind of resilient setups is important to know exactly
what kind
of circumstances you want to survive: server hardware failures, network
hardware
failures, OS failures, network/ISP failures. Some are easier/cheaper to
accomplish, but
others are really difficult. Which ones do you need to survive? If I know
exactly what you
need maybe I can help you a bit more ;-)
Regards,
Victor.
---
Victor R. Rodriguez
Departamento de Sistemas
Valoraciones del Mediterraneo, S.A.
---
_______________________________________________
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/
