Star Wars Galaxies: More info on Galaxies downage

Greetings...

Something we struggle with is providing an ETA. In some cases, we have no idea what the ETA is, because we don't know what the root problem is. In this case, an ETA would be a complete guess and therefore not very valuable. The best I can do is post the relevant information as it happens, give you any data you request, and hope you have patience with us while we work to solve the problem as quickly as possible.
_____________________________________________________________________________

Blair wrote:

In some cases, we have no idea what the ETA is, because we don't know what the root problem is. In this case, an ETA would be a complete guess and therefore not very valuable.

Let me correct this. We know the root problem is the database machine containing the login services. We don't know why it won't come up at the moment.

_____________________________________________________________________________

Drysander wrote:

A database problem in the login server is a serious issue. Of course they will have backups and all that. But there is always a problem with backups.. There will be a rollback.

At this time, this appears to be a hardware problem. There is no indication of a problem with data integrity. The login server controls only the servers you have access to, and a list of servers you have created characters on. It does not store character data or account information for that matter. Rollbacks occur when the game cluster can't save data to the database.

Blair
Producer
_____________________________________________________________________________

Many people asked:

Where isn't there a back up system for these servers.

Greetings...

Every system architecture has single points of failure. During your architecture design phase, you work very hard to eliminate as many as possible to provide redundancy where you can. In our case, we have multiple login servers running on multiple machines. What we don't have is multiple instances of the login server DB data. Thus, if the DB machine for the login server goes down, no one can log in. This is where we stand at this moment.

We have a couple of ideas for how to address this, but there is a lot of trickiness. If it were as easy as adding a few more machines, it would have been solved long ago.

Thanks for your patience here.

Blair
Producer

____________________________________________________________________________