Quoted from "choujiaki;587396"
GM CM SUPPORT all that other crap is based in EU now, but if the US servers are based in the states, shouldnt they be able to fix the problem by now....
Quoted from "timthum;587411"
this is a normal day on reni
http://www.youtube.com/watch?v=316AzLYfAzw
Okay that one was a good one
Quoted from "timthum;587411"
this is a normal day on reni
http://www.youtube.com/watch?v=316AzLYfAzw
Quoted from "timthum;587411"
this is a normal day on reni
http://www.youtube.com/watch?v=316AzLYfAzw
Quoted from "Southern;587412"
*IF* they're typical, the servers themselves are housed in a data center with 24/7 support that only supports hardware - actual software maintenance is performed remotely (from anywhere in the world) and includes limited hardware abilities (such as they can reboot the servers, but little else). Onsite support is limited to replacing hardware and power cycling hardlocked servers.
So if the problem is a hardware problem, they have to work with the data center to get that resolved.
And considering that the IPs for the servers terminate within a VaultNetworks data center, I'm going to assume this is how they're operating.
Quoted from "vfwiffo;587419"
Indeed. Data center can only perform limited recovery, and with only some of the servers being down, indications are it is not a hardware issue. Data centers might be little understaffed on weekends (especially superbowl one), but they are 24/7 and so will repair hardware problems.
Software issues and database integrity are far more likely culprits. You do not want those resolved quickly if the problem is not simple. I've had more than one occasion in my IT career where there was a pressure to do it fast or to have people who are available working on resolving the problem, regardless of their ability and understanding of systems involved. It never ends well. Any time right people can't work on the issue, it causes far more problem than it solves. Heck, I myself have created quite a few problems because I had no clue what I was doing, trying to repair the system I had no business repairing.
Quoted from "vfwiffo;587419"
Indeed. Data center can only perform limited recovery, and with only some of the servers being down, indications are it is not a hardware issue. Data centers might be little understaffed on weekends (especially superbowl one), but they are 24/7 and so will repair hardware problems.
Software issues and database integrity are far more likely culprits. You do not want those resolved quickly if the problem is not simple. I've had more than one occasion in my IT career where there was a pressure to do it fast or to have people who are available working on resolving the problem, regardless of their ability and understanding of systems involved. It never ends well. Any time right people can't work on the issue, it causes far more problem than it solves. Heck, I myself have created quite a few problems because I had no clue what I was doing, trying to repair the system I had no business repairing.
Quoted from "Choralone42;587423"
All of that is probably 100% what's going on in this case. However, having someone actually say "Yes this is happening and it may take some time to fix" would be nice.
However, the following link accurately describes what I'm talking about...
http://imgur.com/ug3Yo
Quoted from "Southern;587425"
Actually, with both Reni AND Osha down, I'm leaning toward a hardware issue. Maybe a router that feeds these 2 worlds, or a common power supply. Since the issue affected identical zones on two different worlds (housing, mail, auction house, guild castles), I don't see how that could be strictly database related -- but without knowing more about their server structure/topology, it's hard to be sure. Do the 2 worlds share a database on a single server? Are Zones housed on multiple physical servers, or a single VM?