Web Services
  Home arrow Web Services arrow Page 4 - A Step-By-Step Guide to Changing Web Hosts
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
WEB SERVICES

A Step-By-Step Guide to Changing Web Hosts
By: HostVoice.net
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 2 stars2 stars2 stars2 stars2 stars / 3
    2003-11-04

    Table of Contents:
  • A Step-By-Step Guide to Changing Web Hosts
  • Backup, Backup, Backup
  • Gathering the Odds
  • Finalizing

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    A Step-By-Step Guide to Changing Web Hosts - Finalizing


    (Page 4 of 4 )

    Inform Your Visitors

    It is common and good practice to inform your visitors and customers of the server move. If you run an e-store, this helps assure your customers you have not fled with their money if there is any downtime. Also give an alternate email so you don’t lose emails in the transfer. You might also want to give periodic updates prior, during (if there is downtime), and after. If your site is large, doing this is helpful because your visitors can alert you whenever there is a section of the site that is not working.

    Moving Day

    Try to schedule the move at a time where there’s the least amount of traffic. Perform a backup again just before you do the move, so you’ll have the latest data. Start by first copying or creating your custom error pages onto the new host server. Put a small note in there about the move. You can always remove it later. Then, upload the most visible parts of the site first i.e the main pages then move on to the less critical parts of the site. If you have a large site with many divisions you might want to split them across different days and instead move the least critical first. Just ensure you always do a backup before you do any moving. Use the temporary URL to check your site, visiting as many pages as you can.

    Changing DNS

    Once you’re satisfied, change your DNS over. This typically takes about 24-48 hours so you have time to make some minor changes if need be. You might want to also take this time to modify your old site’s error pages to inform your visitors of the move and give a new URL if there are URL changes. To help you determine if the DNS has resolved, make a small change on the new pages to differentiate between the old and the new.

    Monitor

    After you’ve moved and the DNS have resolved, do not release your old hosting account yet. Keep it as long as two weeks running concurrently. Go back and check the old servers for activity. Check your old email account and if you have a web based contact method on the old server check to see if any communication is left there. Once you’re comfortable all email and traffic is correctly directed to the new host server, you can cancel that account.


    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

     

    WEB SERVICES ARTICLES

    - Getting Started with Flex
    - Automated Billing and Faxing for the Web
    - An Introduction to Web Services
    - The Foundations of Web Services: From Novice...
    - Web Services Reengineering: Finishing Touches
    - Fault Handling with Web Services
    - Flow and Web Services
    - Process Lifecycles and Web Services
    - Business Processes and Web Services
    - Orchestrating Web Services
    - Notifications and Resources in the WS-Resour...
    - WS Notification and WS Topics in the WS Reso...
    - Introducing the Implied Resource Pattern
    - Web Services and Stateful Resources
    - Deploying an EJB Application






    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 3 hosted by Hostway
    Stay green...Green IT