Web Hosting Website Migration Process - enthralling From One Web Hosting enterprise to someone else

on Wednesday, November 30, 2011

This description provides a detailed step by step process for migrating a website from one web hosting provider to the next without disrupting the delivery of either the website or email services linked with the domain.

A summary of the steps complicated in the process are:

Cloud Hosting

Make sure you have all significant information Request set up of the hosting inventory with the new provider Replicate Dns with the new provider Re-delegate the domain name Copy the site content Test the site on the temporary domain Configure email services Change Dns records. Migration completed

Before you begin make sure you have all you will need to unblemished the migration. This includes, among other things:

Domain password or registry keys Access to the web hosting inventory on the existing web hosting provider Ability to perform database dumps on the existing web hosting provider All Ssl certificate files (if there is one) Checked that the hosting platform is compatible (i.e. Versions of applications, Linux vs windows). List of all existing email addresses Setup the web hosting inventory with the new web host

Make sure that the website hosting inventory is setup with the new web hosting provider. Setting up the inventory will not interfere with the performance of the existing live site. When the web hosting inventory is configured with the new host, you should receive all the access details for adding article to the account.

Dns Configuration

We very propose redelegating the domain name to the name servers of the new hosting firm in advance of thoughprovoking any other services, this is ordinarily referred to as the Dns.

Dns is usually handled by the same firm that handles either website or email hosting or both. It is any way technical independent and is a service that can be handled by distinct companies.

Dns is where the convert is made made when a website is switched from one hosting provider to another.

We propose changing the Dns to be hosted by the new provider but set the Dns records to continue to point all services at the existing hosting service provider. Once the Dns records are hosted by the new provider, convert the Ttl (Time To Live) attribute to sell out it from the suitable 24 hours to 10 minutes. This allows us to make changes in the middle of providers in as itsybitsy as 10 minutes once the services are ready to be migrated. This is a big correction on the suitable 24 hours since the level of disruption is greatly minimised and the risk of users being spread in the middle of old and new sites is so much lower.

We first need to make sure we have an spoton copy of the records from the existing host. The best way to do this is to ask a copy of the records from the current host or Dns provider. If this is not possible, with a reasonable knowledge of the services in use on the domain name, it is usually inherent to derive most of the significant information that you need using tools such as dig or nslookup.

Site Copying

Once Dns migration has been initiated we have approximately 24-48 hours before the domain can be redelegated to the new hosting providers name servers. This will give us ample time to move the article across to the new servers. There are essentially two ways this can be completed depending on what information we have. If you have Ftp/Ssh details then you will be able to log in and copy the files across. Foremost things to note:

Databases? Make sure a dump is taken and saved in the home directory Provided you have Ssh access, the easiest way to copy the article across is to tar up the whole home directory and then Scp it across.

A easy way of copying an whole website if you have Ftp access is using Lftp. Login to the server the inventory is on as root and:

$ su - $ cd public_html $ lftp lftp:~> user Password: lftp:/> ls (just to make sure you're in the spoton folder, otherwise cd to the folder containing the website) lftp:/> mirror

This will mirror the whole contents of the website into your current folder. You still need to manually copy any databases across.

Without Ssh/Ftp access you can copy the site using Wget if you keep in mind a few caveats: Wget will only work when there is static article on the webpage, no dynamic pages (eg php, asp, shtml), no databases. If the site contains Javascript or Flash you might find you miss parts of the content.

Site Testing

Once the website has been copied test it on the temporary Url (as in case,granted in the initial email) for the hosting inventory setup and assess against traditional website to ensure all is working correctly. If anything is not working, make sure it is fixed at this stage.

It is Foremost that you confirm with the new hosting provider that you have completed your testing of the website.

Email Configuration

Assuming that all email services are to be migrated, a full list of email addresses that are required must be in case,granted to your hosting company. If mail services are remaining with the existing host, or they are already handled externally it is Foremost that you let your hosting firm know.

Once they have been in case,granted your web host should provide you with new username and passwords.

Note that if email services are to be migrated in most cases you will be changing the username and password details for email services. This convert is the one that will have the most consequent on the end user of the hosting services and it's Foremost that it is communicated properly. If peoples email breaks these days, it's often more disruptive to their work than cutting of their telephone.

We've found that the best way to ensure no email is lost in the migration process is to leave the existing configuration in place, so that the mail client continues to check the old mail server, then add a new profile that checks the new mail server concurrently. This should usually be left in place for up to 7 days after the convert over. It will ensure that any mail that still does make its way to the old location will be collected.

Finalise Migration

Once all has been checked and rechecked we can switch the site across our servers for web and email hosting (by switching the Dns).

You should sense your hosting provider to confirm a time to make the change.

If the website uses a database it may be significant to unblemished a final synchronisation of database immediately prior to changing the Dns.

Complete!

That's it, you're all done. You site migration should be unblemished and all traffic flowing to the new host with a minimum of disruption.

Web Hosting Website Migration Process - enthralling From One Web Hosting enterprise to someone else

2 comments:

Anonymous said...

sharing many points of the hosting website of the Cloud computing very useful for starters

Anonymous said...

Good helping & informative stuff define.Thanks for sharing.. web hosting services

Post a Comment