Migration from one webserver to another can be problematic.
Environmental variables change, software versions vary and paths no longer exist.
This can be a difficult thing to troubleshoot, particularly if you do not have experience in Linux troubleshooting.
Adding to this, the pressure of ensuring this works in a timely fashion does not help.
Avoid Uneccessary DowntimeWithout proper planning or experience, a migration from one server to another will incur problems.
Avoid unneccessary downtime, get the job done right first time.
Murphy's LawWhat can go wrong, will go wrong
Moving web sites from one server to another has an infinate number of potential pitfalls to avoid.
A few examples include:
- Change of MySQL version
- Change of PHP version
- Apache environment
- Change of platform
- Different paths
- Environmental variables
If you need advice on how to successfuly move from one server to another with the minimum disruption, contact one of our consultants. We can help you to create a migration action plan.
Migration Action Plan
Migrating to Linux, Apache, MySQL and PHP
LAMP is the platform of choice for the development and deployment of high performance web applications. It is solid and reliable, and if Apache is any indicator, then LAMP sites predominate. If you take a look at the Netcraft website, you will see that many run Apache on Linux, usually running perl and/or PHP.
With the majority of Web 2.0 being developed on the LAMP stack, many new web design companies that previously worked on the Windows platform are moving to Linux. They are also benefitting from the reliability of Linux. As of August 2008, the most reliable hosting companies with the least amount of downtime are dominated by companies that run Linux or variants of BSD.
Migrating to BlueQuartz
There are many reasons why you may want to migrate to BlueQuartz.
Easy to manage, easy to configure, simple to add new sites.