Scratch

Here you will find older scratches, musings and other detritus that once were located on the front pages, but have now faded.

Filed away here to collect dust and cobwwwebs in perpetuity, links may break, facts may change and data may corrupt.

On occasion I may come down here to tidy, but for the most, I prefer to leave the past where it lies.

Upgrades

Ok. So far so good.

Hopefully if you can read this, then the webserver/data migration and configuration is complete.

All I need now is to start on the mailserver.

Last night I finally managed to install most of the hardware components into my 'new' server. Most bits worked fine, although a few old scsi disks I had wanted to RAID and use as a backup refused to work with any of the others. At some point I will have to replace the ide and scsi cables as there is literally no room for airflow, but hopefully this shouldn't cause many problems in the interim.

This morning I have successfully installed new versions of apache, perl, php, mysql, phpMyAdmin and analog, although in the case of the latter I have no idea why as I rarely (read never) use it. The new version of apache no longer seems to throw errors up every few hours which is good (and yes I know its early days). Saying that it seems to have dutifully passed on this role to the anti virus software, which is bad. There appear to be a few glitches but I am sure these will be sorted out by going through the http.conf file.

As of just now, I have managed to migrate all the old data across, and the only problems are making sure all the users passwords for the different tables are altered, as both these and the cms system have changed locations. Where these are stored in ini files and cfg files this should be fine. The problem will come where I have hard-coded these into the pages or network apps, but hopefully these should be few and far between and any disruption minimal.

It is because of this that hopefully, by using a dedicated, non-system drive, that in the future things should be much easier. I should just be able to port the databases across next time, tweak the config fies to bring them up to date, and that should be it. No worrying about breaking code. From a resilience point of view, it also means that if the PC fails, in the short term I can just change the routing table to point to a machine with a cloned disk on it and then the disk out and put it in another machine with minimal problems. Not that I am paranoid or anything.

I know I will have missed bits, so let me know if there are any problems.

And on that note, just the mailserver to go.

21 Aug 2005 12:34 | (0) comments | site

Related Entries

By Date

Monthly Archive for August 2005

Previous entry: « Migrating Server Data

Next entry: » Upgrades (2)

By Category

Category Index: site

Previous entry: « How Did I...