First 10GB of photos moved
Tar, split, scp, cat, md5sum – the first 10GB of photos are now moved up to the new hosting server.
Slow business – but now it’s a job to re-knit the gallery2 database and see how that all performs.
Tar, split, scp, cat, md5sum – the first 10GB of photos are now moved up to the new hosting server.
Slow business – but now it’s a job to re-knit the gallery2 database and see how that all performs.
Strictly a console guy – I’ve been struggling to get the big blog database dumps up to the new hosting. phpMyAdmin claims to support zipped dumps – but that doesn’t work. There are also timeouts in the console for the upload and import.
I finally fixed it by using scp to move the non-compressed dump to the hosting server; and then using the Hosting Control Center to restore the dump as if it was a backup.
It’s running right now – so hopefully I’ll have happy blogs again soon.
More testing of the server migration to the cloud – and also to note that WordPress 3.1 beta 1 is now live.
Some nice features – I’ll be kicking the tyres some more on this in the coming weeks.
A trio of projects before the year-end – all interwined.
Moving the mail isn’t that hard – it’s just making sure that mail doesn’t get dropped while the new MX and CNAMEs are propagating. The old mail will live on in Google Apps – the new stuff in hosted Exchange. The trickier part is making sure that ‘my customers’ get the right service – and can keep getting mail in Outlook or the web. Users eh.
Moving the DNS is part of the mid-term strategy to change ISP. Covad have been great to me since I moved to the US; sadly they are starting to show signs of decay. I need to support additional DNS records than the A, CNAME and MX records – no plans from Covad.
The final push is to move the blog servers out of the ‘home data centre’ and to a reliable, faster provider.
The ultimate aim is to divorce myself from Covad and the Static IP business DSL that has worked so well – and move to something that is much faster – but maybe without the SLA on the line itself.
I’ve been testing out xCache for a while – primarily as a PHP accelerator.
Early results were really promising – reducing page load times dramatically; and also reducing CPU load as common pages (i.e. the latest blog post and photos) were fed directly from the cache.
There seems to be some kind of memory leak/cache clean up issue with xCache 1.3 – I allocate some amount of RAM for cache (16MB, 64MB, 256MB – it really doesn’t matter) and at some point Apache/PHP starts eating up RAM, then starting to swap – and finally the server grinds to a halt.
xCache is off for now – I’ll keep investigating.
Recent Comments