OTRS at multiple locations

[thunter28]

I am looking to implement OTRS at 2 separate physical locations. We will have a 10g link between the locations, but I am more concerned about how to set this up is a failure occurs in the link. Both locations will need to receive the same tickets and can even respond to them, but location 1 will have the original system and database. Location 2 would have no ticketing system if the link were to go down. Has anyone else had this type of setup, or does anyone have any idea on how this would be best accomplished?

Thanks in advance!

[crythias]

It's a website...

[thunter28]

Site 1 is the primary site where the server is located. Devices on the network can access the server via the web server from location 1 and location 2, as this is on our private network. The link between the sites (a 10g PTP) breaks, site 2 is no longer connected to the OTRS server in location 1, thus it cannot connect to the web server. Even though it is a "website", site 2 is now unable to act on its own for ticketing.

[crythias]

How would this work in any other environment not related to OTRS? If you had a financial software that required transaction-safe processing, what would happen? This isn't just distributed file system or database folder sync. You're talking about potential collisions of data if you separate them and attempt to merge them back.

Your question needs to be answered by a paid professional who can handle your drop in service, not merely a quick answer on a free forum.

Or, host in an environment that would be likely *always* available on the Internet.