Notes From the Latest Move
This latest server/hosting company move was different than
others we did.
Only once before did we move all of our domains from one
hosting company to another. At that time, there were less
domains and they were smaller in size.
Several of our sites are now so big that moving to a
different server just isn't easy anymore. Over time, the
sites get bigger and bigger and bigger.
For example, in December of year 2000, willmaster.com had
1796 files. During this latest move, the domain had 7 times
as many, 13176 files.
In anticipation of moving willmaster.com, the largest of our
domains, I made a batch file processing tool. It automated
some things that could otherwise have required many days of
work. The tool was designed to scan files and search/replace
text and/or change file permissions.
The search/replace was used to change perl location, file
module names, and directory paths. The permission change
feature was used to give Perl scripts 755 permissions.
The tool worked so well I used it for the other domains,
also. It is so effective it could be dangerous in the wrong
hands. It was removed from the server after I was done with
it.
This was our procedure:
-
For each domain, zip up the web site files on the
old server. (Or, zip up sections of the domain if
very large.)
-
Download the zipped files from the old server.
-
Unzip the files on the local drive to remove logs
and other files that don't need to be on the new
server.
-
Zip the files back up.
-
Upload the zipped files to the new server.
-
Unzip the files on the new server.
-
Change the domain's DNS values at the domain
registrar.
-
Run the new batch file processing tool.
-
Test.
That final step, testing, takes the longest of all. We're
still not done.
Link checkers help. We recommend
http://validator.w3.org/checklink for cross-platform
availability.
The w3.org link checker is rather verbose, even in "Summary
only" mode. So I made a little script to extract the
information I was interested in; namely, 404's and the URL
of the page with the broken link.
After links are checked, much is left to do. Every form
needs to be used, every product purchase cycle completed,
every software generator tried out. In short, manual
application of each domain's functions is still required.
It was worth it. We're now on a virtual server, perfect for
one like me who likes to tweak things.
Before closing, let me list some previously published
articles and blog posts on this subject that may be useful
to you.
Moving CGI Scripts to a New Server
Backup/Restore & Export/Import & Server Move Perl DBM
Database Tools
Moving Our Sites To a New Server
Site Moving Tips; Orderly or Emergency Moves; Things To
Consider When Moving From One Server To Another
Those should be read, or at least scanned, if you think you
might be moving your domains to a different server.
Question:
Did you find this article interesting and understandable? How can it be improved?
Your response is anonymous.
When done typing, click anywhere outside the box. [more info]
Will Bontrager
©2007 Bontrager Connection, LLC Bontrager Connection, LLC
Please note:
Articles on this website are presented "as is". However -
If you have a question about a CGI script, HTML, CSS, PHP, or JavaScript
Ask one of our Experts and you'll have your answer!
Click here for details.
