Server move incoming

Hey all,

I can't put a precise moment on it yet, but in the coming hours/days, Guild Wars Legacy will be down for a few hours for a server migration (yes, again).

This is the big one. Legacy is moving to a way beefier server and several other servers will be merged to this single server (hello, archive servers!).

I'll keep you up to date, but if you can't access Guild Wars Legacy for a while, this is the reason.

- Kevin

Unfortunately, we run into issues with our new server and we had to perform a rollback.

A new attempt will be made in the next few days once our investigation is completed.

- Kevin

Quote from trademeimfamous

since reforged the site has been feeling slower / less responsive. is that because of servers or just more people being on here?

There is a limit of 30 days on my metrics, but we have gone from 35.77k unique visitors a month ago to 108.56k, or from 443.3k requests to 1.42m requests (these are daily metrics).

So yes, the amount of visitors has gone up drastically and it is one of the reasons for the server move - the new server is orders of magnitudes faster. I'm testing behind the scenes and hope to finish it today.

And the server move has just been completed - if you can read this, the server move was a success and you are now visiting Guild Wars Legacy on the new server, Ashford.

As explained in my previous post, we saw a huge increase in users so a bigger server was warranted and Legacy has never had such a beefy server as this one - we have 8 times as much memory and have moved to dedicated cores, so Legacy should remain smooth for years to come!

Now, with every migration, there is a risk of issues so should you encounter something strange, please feel free to let me know and I'll take a look at it.

Kevin

By the way, the reason why the migration failed last time: it didn't fail, but the new security system was a bit too eager and banned me while debugging the issues. That caused a whole lot of other issues which led me to roll-back to our previous server. Ofcourse it only took a few more minutes after before I realized what was really happening. I spent a lot of time confirming the issue and fixing another issue.

The new security system is also VERY thorough and completely banned me on all fields, so it looked like the server had crashed. Ah, the joys of being a system administrator.

Quote from Looney

Quote from Iaerah

By the way, the reason why the migration failed last time: it didn't fail, but the new security system was a bit too eager and banned me while debugging the issues. That caused a whole lot of other issues which led me to roll-back to our previous server. Ofcourse it only took a few more minutes after before I realized what was really happening. I spent a lot of time confirming the issue and fixing another issue.

The new security system is also VERY thorough and completely banned me on all fields, so it looked like the server had crashed. Ah, the joys of being a system administrator.

Can we then assume it's name was HAL and it was afraid you can't do that...

M.O.X. 9000!