Transfers


From Another Provider to BCA (External)

If you are transferring your existing website to BCA WebServices, please study the following:


From an Old to a New BCA Server (Internal)

Generally an internal transferred is done to upgrade to newer versions of the system software (OS, Apache, PHP, MySQL, etc.).

BCA will clone your existing account onto the newer server where you can test it before it becomes live. In the mean time your existing site will continue to work and be available for the world to see. This presents a good opportunity to upgrade your website, if you so desire.

Please study the following:


Should I transfer my domain name?

It is important to realise that your domain name (eg cscc.co.uk) is different from your webserver. The domain name is held by your Registrar and points to the server which hosts your webserver. Often these two jobs are done by the same provider but they can be done by two different providers.

  • Option 1. Transfer your domain to BCA WebServices
    • BCA makes any necessary updates to your domain name such as DNS entries 1) or contact details at your request.
    • Some work is involved in making the transfer to BCA WebServices
    • The domain name registration is charged separately from the webhosting. You should check our Pricing verses your existing provider to see that we are competitive.
    • We use FastHosts as our Registrar.
  • Option 2. Leave your domain where it is
    • You make any necessary updates to your domain name.
      • Check that your provider will allow you to make updates (of the DNS records in particular). This is usually done by logging into your account. If not you will have to ask their customer support to do it for you.
      • The DNS records will need to be changed to ns1.memset.com, ns2.memset.com and ns3.memset.com.
    • The hassle of the transfer is avoided.
    • The domain name registration is charged separately from the webhosting. You should check our Pricing verses your existing provider to see that we are not competitive.


Connecting to the New Webserver

For a time you will have two webservers one new and one old. That will allow you to test that the new server is working correctly and that you have copied everything you require. When you are happy the DNS record will be updated and the new server will become live and your old server redundant.

You will have been sent your Account Name and Password. With these you can logon to the various services that allow you to create and manage your website.

Before the DNS Update

Before the DNS is updated your domain name will point to the old website, so the following must be used instead.

cPanel

FTP

  • The host is server.british-caving.org.uk. Use the same Username and Password as for the cPanel.
  • NOTE your website files belong in the /www directory (which is linked to, same as the /public_html directory).

Website

There are two options here.

  1. Browse to server.british-caving.org.uk/~your-user-name. E.g. server.british-caving.org.uk/~cscc.
    • This is the quickest option but might cause problems if you have any absolute URL links on your website.
  2. Update your local /etc/hosts file to fool your computer thinking the domain's IP address is that of the new webserver's.
    • This is generally a better test and will not suffer from the absolute URL links problem.
    • To do this you need to edit your /etc/hosts (Linux) or /windows/system32/drivers/etc/hosts (Windows).
      • Make a backup of the file before you change anything!
    • Then add the line below, substituting the domain name for your own domain name.
    • When you have finish don't forget to restore the original file.
    • NB 31.25.186.126 is the IP address of server.british-caving.org.uk
31.25.186.126   cscc.org.uk

After the DNS Update

Once the DNS is updated your domain name will point to the new website, so the following will now work.

cPanel

  • Browse to your-domain-name/cpanel and enter your Username and Password.
    E.g. cscc.org.uk/cpanel.

FTP

  • The host is your-domain-name. Use the same Username and Password as for the cPanel.
    E.g. cscc.org.uk.

Website


Steps To Transfer From Another Provider

The steps are:

  1. BCA will let you know your new account is ready and give you your logon details.
  2. Take a backup of the existing website.
  3. Browse to the control panel (cPanel) of the new server.
    1. Create the email accounts and forwarders as they are on the old server.
    2. Create a database if you had one previously.
      1. Backup the database from the old server and restore to the new server.
  4. Connect to the new server with FTP
    1. Copy all of the web files from the old server to the new server.
  5. Browse to the website on the new server and check it thoroughly.
    1. The new server is case-sensitive. Are all the directories, file names and URLs the proper case?
    2. The new server observes permissions. Are the directory and file permissions correct?
    3. Can the database be accessed? Make sure you are accessing the new database and not the old.
    4. Check software generated emails are still sent.
  6. Once all the checks are done the name servers (DNS) will be updated to make the new website live.
    1. Updates to the old site should be prevented. So Forums and similar should be disabled.
    2. It can take up to 72 hours for the DNS changes to propagate around the world. In that time a user might arrive at either the new or the old site.
  7. After 72 hours check the new site again. If all is OK the old site can be removed (although you might want to wait a little longer).


Steps To Upgrade From Old To New BCA Webserver

The steps are:

  1. BCA will clone your account on the new webserver and inform you that it is ready.
  2. Browse to the website on the new webserver and check it thoroughly.
    1. Can the database be accessed?
    2. Make sure you are accessing the new database and not the old.
    3. Check software generated emails are sent.
  3. Once all the checks are done let BCA know.
  4. The name servers (DNS) will be updated to make the new website live.
    1. Updates to the old site should be prevented. So Forums and similar should be disabled.
    2. It can take up to 72 hours for the DNS changes to propagate around the world. In that time a user might arrive at either the new or the old site.
  5. After 72 hours check the new site again. If all is OK the old site can be removed (although you might want to wait a little longer).


1) The DNS entry is like an index and points the domain name at the webserver
Last modified: 2017/07/22 17:56