Server availibility blog post I made.

Red Squirrel · Post by **Red Squirrel** » Fri Dec 19, 2008 12:06 am

I wrote a blog post that may interest computer geeks / IT admins with this subject:

http://www.redsquirrel.me/2008/12/uptim ... ume-2.html

What triggered me to write this post is I've seen so many instances where I've seen people bring a service down when really, it could be avoided.

Discuss.

Archived topic from AOV, old topic ID:3962, old post ID:25482

Anonymous · Post by **Anonymous** » Fri Dec 19, 2008 12:18 am

geeze get bored on that blog lol

Archived topic from AOV, old topic ID:3962, old post ID:25483

dprantl · Post by **dprantl** » Fri Dec 19, 2008 3:28 pm

1) People don't always have test servers on hand that they can try the upgrade on.

2) Some applications/situations require the upgrade of massive amounts of data that take a very long time. It is also not feasible to make a separate system with a mirror of all this data.

3) Sometimes the people administering the upgrade are retards and/or don't know wtf they are doing.

Archived topic from AOV, old topic ID:3962, old post ID:25487

Red Squirrel · Post by **Red Squirrel** » Fri Dec 19, 2008 9:56 pm

A test environment is a must though. In fact that should be the first thing to be setup before the actual live one, as the whole thing has to be tested ahead of time anyway and be developed. It can't really be done in thin air. So you keep test environment afterwards then use it to do your development on and test new changes/updates without impacting possible customers (depending on the system in question). Like when I make a website from scratch I always do it on my local server and test it from there so before it's even gone live I already have a test environment for it.

Even large sums of data should not take THAT long to transfer/change if the process is well coded.

Archived topic from AOV, old topic ID:3962, old post ID:25490

dprantl · Post by **dprantl** » Sat Dec 20, 2008 1:11 am

Red Squirrel wrote:A test environment is a must though. In fact that should be the first thing to be setup before the actual live one, as the whole thing has to be tested ahead of time anyway and be developed. It can't really be done in thin air. So you keep test environment afterwards then use it to do your development on and test new changes/updates without impacting possible customers (depending on the system in question). Like when I make a website from scratch I always do it on my local server and test it from there so before it's even gone live I already have a test environment for it.

Even large sums of data should not take THAT long to transfer/change if the process is well coded.

Squirrel you still have a lot to learn.

Archived topic from AOV, old topic ID:3962, old post ID:25495