The ITIL Weblog has moved to another hoster. We think that the new hoster provides a faster platform and has a better control panel. Moving to another hoster also is a nice test case to see how ITIL minded this change was performed. To be very short: it could be much better, but also much worse…..
In order to move the ITIL Weblog (and with it also the Prince2 Weblog, the MSP Weblog and the Free Online Health Check….) a plan was made. The plan consisted of 3 separate changes to be performed by 3 diffent parties.
- Prepare the new ‘healthcheck-online.com’ environment by putting a backup from the ‘old’ environment up-and-running;
- Inform the ‘old’ provider that the Weblogs have to be moved and that the contract will be ended;
- Adjust the DNS setting so the ‘old’ provider will point to the ‘new’ location and the ‘old’ websites will not be used even before the move.
So far so good. Step 1 was performed by requesting a move from the domain at the new provider. The webserver was adjusted so it would recognize requests for healthcheck-online.com. The files were copied and the databases partially moved at day 1. Day 2 would be the day to finish this job.
Step 2 was also started by sending a letter and requesting the move and an EPP code (needed to transfer the domain). The provider responder very fast and the EPP code was sent to the new provider.
Meanwhile step 3 was performed. The old DNS entries were edited and 1 of the weblogs was tested (the MSP weblog, since it has less viewers….). The Weblog seemed to work fine so the other two weblog entries were changed too.
So far everything was planned fine: risk and impact analysis performed, steps in a controlled way performed and always checked. It felt good to be in control with this change!
But then….
Just to make sure that everything was working fine I tried to read a post: a 404 error appeared!
An incident was created and right away escalated (in my head…..) I started working as a problem manager taking control of the situation and performing the fall-back scenario: Adjust the DNS settings so the old Weblogs would be up and running again…..did it, everything under control. Damage: a short period of 404′s when people tried to read posts, front page worked fine though.
Analysing the problem the cause for the problem was found and adjustments to the new environments was made. The Weblogs needed 1 configuration file extra. This was created and added to the weblogs and so the DNS settings were switched back again. Phew….it is fun to be a rapid reaction team by yourself…..it’s time for a break so step one can be continued and the Free Online Health Check can be put online too.
The next day the new provider adjusted his DNS settings and was given control to the domain….meaning that the ‘old’ DNS settings were no longer active…… But hey: I wasn’t ready with putting the backups on the new environment!!!!
You can guess that I stressed again and had to rapidly copy the files and put the database online in the new environment. And the…everything worked fine…but I realised that I wasn’t in control pro-active but reactive. The plan was good, the fall-back worked but I had no control of the two providers who worked both surprisingly fast….
In the end my service to you was interrupted two times. Creating 404 pages and confusing for people looking for sample exams or information. I really apologize for the inconvenience!
Good luck with ITIL and let’s hope that the new enviroment will serve us better and faster.
Lessons learned
- Prepare a move like this and also think of fall back scenarios;
- Perform the steps faster then the webhoster. Stay ahead!
- Test the sites after moving really good. It’s not enough to just see the frontpage. All separate posts could not be found….
- Created information pages so the visitor doesn’t get a 404 page…but a maintenance page.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
Recent Comments