Chris Cruft

The Proliant 5500 and 3000 are pretty similar.  I’m considering replacing bmw, my older 2×550MHz Proliant 3000 (with the old-style drives) with a Proliant 5500.  I will be able to migrate the IMD, power supplies, and PCI cards, but not the drives or the memory.  The memory will be a problem as the 5500 I am looking at only comes with 1GB of RAM.  I just upgraded bmw to 2GB last weekend…  The 5500 uses EDO ECC DIMMs, either 50ns or 60ns.
This upgrade process was actually supported by Compaq, so it gives me some confidence in the ability to recycle the power supplies, IMD and cards.
References:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=61709&admit=-682735245+1162309574428+28353475

Given the growing amount of important data I now have in MySQL, I figured it was time to get familiar with backing up MySQL on the fly. I see that there is an open source package, Zmanda Recovery Manager [ZRM] for MySQL (reference 1), that seems to do the job. But to get started, I am going to use the built-in database dumper. Later, I might just graduate to better tools.  Here is an example for backing up all databases (with compression) from the command line:

# mysqldump –add-drop-table –all-databases -h localhost -u root -p | bzip2 -c > /tmp/mysql.hotcopy

But here is the script I run from cron:

#!/bin/sh
mysqldump –add-drop-table -h localhost -u root -pSecret wordpress | bzip2 -c > $HOME/wordpress.hotcopy
mysqldump –add-drop-table -h localhost -u root -pSecret MemoryMiner_development | bzip2 -c > $HOME/MemoryMiner_development.hotcopy

References:

http://wiki.zmanda.com/index.php/MySQL_Backup_and_Recovery

As this is my first blog post to this new blog, it deserves a witty title and thought-provoking content indicative of the pearls of wisdom that will certainly be found here in the future.

Currently I am suffering from blogger’s block, so this will have to do.

Keep in mind that chronologically this site is a bit twisted because I converted a journal I have been keeping for several years into retroactive postings.