Thorsten Dannhausen wrote:
Well thank you Ron for this information as I'm not really familiar whith replacating databases. But the single hosted solution is something my bosses don't want at all. Our internet connection in our headquarters is reliable and redundant so that wouldn't be the problem. But what pretty often occurs is that one of our other locations are loosing there internet connectivity. As you might know it is hard to get redundancy at a payable price in some places of the world. But the location should still be able to use OTRS when there line is down as they would need it for the daily work. So any other ideas out there besides hosting a single system.
If a location needs to be able to use OTRS even when the network connection is down, you won't really be able to use one database for all locations, as Ron pointed out. Having all tickets available at all locations is not going to be possible if connections are down from time to time. You could set up separate OTRS installs at every location and maybe have different email-addresses for the different queues at the different locations, but then you wouldn't have one central system (database) that holds all tickets and you might have to forward tickets to other locations. As we don't have any more info about how the business works I don't know if that would work for you. Nils Breunese.