transferring a web site
Im having to undertake a risk assessment of a possible site transfer from one server to another.
The site consists of html, dynamic elements (forms and calculators) in coldfusion, some flash and email contacts.
The third party content which shoulds be fine as this resides on other servers.
My question is what risks need to be considered with transferring a site that is not just html? Such as server configuration, email set up, any coldfusion considerations.....etc etc
Any comments much appreciated,
Thanks
tuffy posted this at 22:48 — 6th August 2002.
They have: 39 posts
Joined: Jul 2002
Hi,
This is just a suggestion...
Probably, one of the first things you should do is figure out where you are going to move to, and then start finding out what the differences will be for paths and such. Most of the things you mentioned will have very minimal risk if you get your account setup a day or two before you move and get it ready ahead of time. Don't forget about your domain... if you have to change dns information, it can take several hours to propogate.
Check with the host you plan to move to as they may offer you some other options to help you out.
Leah | Idologic.com
Reseller, Dedicated, and Co-Lo Solutions
The Webmistress posted this at 07:42 — 7th August 2002.
She has: 5,586 posts
Joined: Feb 2001
As tuffy says the best thing to do is set up the new webspace before you initiate the transfer so that you can find out the new configurations and be able to prepare in advance what you are going to need to change. As long as you have local copies of everything then it really shouldn't be too much hassle to change things.
Julia - if life was meant to be easy Michael Angelo would have painted the floor....
evvo posted this at 11:39 — 7th August 2002.
They have: 26 posts
Joined: Nov 2001
Thanks, in particular, I was wondering about consequences of any coldfusion server, database (oracle) connection issues, java, performance and security.
Suzanne posted this at 17:21 — 7th August 2002.
She has: 5,507 posts
Joined: Feb 2000
There are huge consequences if you don't have the same set up.
Ergo, set up the new server first, make sure it's functioning properly, then move it over. That advice is sound.
As for problems you might encounter?
1. Cold Fusion server -- find out if the new server has the same version or not. If it has a higher version (do not get a server with a lower version), then check with your programmers to see if there is any code revision needed.
2. Different db setup/connections -- get the specs ahead of time and have your programmers evaluate the time needed to make the modifications, if needed.
3. Java -- well this is easy -- make sure the new server has the same version, or if it has a higher version, talk to your programmers about whether any code will be affected.
4. Performance issues -- if the new server has less RAM, a different connection to the Internet backbone, sure, you'll have issues. This is really just a matter of making sure your new server will meet your requirments. Evaluating the risk of this is just evaluating whether your current server meets your needs. Where it doesn't, make sure the new server does.
5. Security -- you'll need a sysadmin to evaluate the security of the new server to make sure it's at the same level or higher as the old one. This is something really only a sysadmin can do properly.
I'm sure you see a trend. You need to determine what you need. To do that, talk to ... the programmers!
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.