Sounds like you’ve never actually worked in IT at all.
“It’s just data migration, it’s easy!”
Until whatever they’re using to do it, dies, or bugs out, and you suddenly need to restore from backups.
Unless blizzard just merrily spends the money for heavy redundancy, to where they can just switch to the mirror server, a big oopsie could definitely lead to super long recovery times.
Given that they’re a corporation, it’s probably significantly cheaper for them to give the finger to redundancy, and just have a combination of live backups, and tape backups to back that up.
No idea what they’re using, but my experience with this was that it took nearly 18 hours for our ~4 TB exchange server to revert back to an earlier backup state, when I was having all sorts of fun dealing with that on-premise exchange exploit.
This is all well and good but we’re talking about activision blizzard, and they’ve had months of preparation time to figure it out. They were the ones who decided to rush into tbc launch, and the ones who decided on only two weeks of pre-patch time. The bed was made.
So, I am currently a database developer and went to OIT for software engineering. I can honestly say that sometimes $hit just happens. The sheer number of things that can go wrong in any of the processes, from code to hardware, is insane.
I can almost guarantee you Blizzard tested this process on test servers, which is how they gave the 3PM guestimate in the first place.
I can guarantee you the employees are freaking the heck out, trying to get this $hit fixed.
I wouldn’t care much about this if we didn’t have a 2 week pre-patch. The reality is we do though, and I truly do question some of the people on this forum that are still trying to defend it. We needed more time.
Holy crap your ignorance is showing, you have no idea how complicated implementing unique network / database solutions are. This isn’t just migrating data. Jeeeeeeeeze people, go to bed or something.
Do you guys not remember that there are like max 2 devs working right now cause blizz fired the rest.
So basically for EST people, their release date is already off. It’ll be 5/19 for them. Ready to see the extension push to 11:00 PDT just so they can say it “made release” for one time zone LOL
it’s almost like people expect competence from a multi billion dollar company (looking at blizzard as a whole)…this is so common with them and the only constantly repeated excuse you have is “iTs sO hArD”