Sooooooo. The upgrade this weekend. It did not go so well. In fact, it pratically hasn't gone at all. We started with the backup server and the initial testing did not go well. I was up until 2 a.m. last night restoring the backup server so that we could retry today.
We retried today. It worked more than it did yesterday; but not 100%. Now I'm accepting the risk of not having a backup server so that super-helpful vendor support guy can work with software company to fix.
There were some dicey moments along the way. Like last night when I thought I'd figured out why it wasn't working, redid the install without super-helpful vendor support guy (without shutting down the primary, functioning server) and then freaked out because I thought I had somehow inadvertently broken our only functioning server. I literally called my boss and told him that I had fracked (I didn't say frack) everything up and it was all my fault. He told me to wait for the server to reset. Everything was fine. Then he told me to stop working on it, do the server restore and to go sleep. I have such an awesome boss.
Even though I did all the testing I know how to do to make sure our primary server is still happy and functioning, I still need to check with our Romanian call center to make sure they are able to take calls when they come online at 9 a.m. their time. They are eight hours ahead right? I only have to stay up until 1 a.m., right? um, right? WRONG! They don't care about our time change. They are now only seven hours ahead and I have to be awake and on the computer at 2 a.m. As an aside, if you ever need to know the time somewhere other than where you are, or even where you are, www.worldtimeserver.com is awesome. I like. So many times during my day I need to know what time it is in Aukland, NZ and is that the same time as in Sydney or Bombay?
No comments:
Post a Comment