[mythtv-users] Planning upgrade to 0.26 including hardware reorganisation
Russell Gower
mythtv at thegowers.me.uk
Fri Mar 15 16:52:49 UTC 2013
Hi,
I'm planning to upgrade from 0.25/fixes to 0.26/fixes this weekend, as part of the process I wish re-organise the hardware used, I though i'd put it to the list, to make user I'm not doing anything stupid or missing a trick.
First off this is my current setup
mytht01 (master backend) - HP Micro Server running Centos 6.3, containing 2 dual dvb-s2 cards and a network attached dual dvb-t tuner, with one SSD for OS and 2 1.5TB disks for Recordings.
mythtv02 Frontend (i3-2100T CPU @ 2.50GHz) with 4GB ram, Nvidia GeForce GT 430, currently diskless with NFS root on the master backend.
Proposal (interim state)
mythth01
Stop mythbackend
Backup database
Remove the dvb-t tuners with mythtv-setup
Backup database
Stop and disable mysql
mythtv02
Install two new SSD disks with the following partitions (This will allow me to boot in to the A or B OS to allow for future upgrades.)
sda1 - 500mb /boot - Live boot partition
sda2 - LVM volume group vgA
/dev/vgA/root 1GB /
/dev/vgA/home 1GB /home
/dev/vgA/usr 6GB /usr
/dev/vgA/var 2GB /var
/dev/vgA/log 1GB /var/log
/dev/vgA/swap 2GB
/dev/vgA/mythtv 200GB /mythtv/A (will create a Recordings subdirectory and and this to the default storage group)
sdb1 - 500mb /boot - spare boot partition
sdb2 - LVM volume group vgB
/dev/vgB/root 1GB /
/dev/vgB/home 1GB /home
/dev/vgB/usr 6GB /usr
/dev/vgB/var 2GB /var
/dev/vgB/log 1GB /var/log
/dev/vgB/swap 2GB
/dev/vgB/mythtv 200GB /mythtv/B (will create a Recordings subdirectory and and this to the default storage group)
Install Fedora18 into vgA and with the hostname "master"
Install mythtv0.26 (from packages built by me using the packaging repository)
restore last database backup
run myth-setup to upgrade database and configure dvb-t tuners
copy the XMLTV config files from mythtv01
Testing
At this stage livetv should work and I should be able to record from the dvb-t tuners but not access previous recordings
Verify that mythfilldatabase is working
if it goes badly wrong, I can restore the first DB backup on mythtv01 and reinstate it as the master backend.
mythtv01
uninstall mythtv0.25 packages
install mythtv0.26 packages (from packages built by me using the packaging repository)
start mythbackend
Testing
mythtv01 should now be available as a slave backend with access to all previous recordings
dvb-s2 tuners should be available for recordings and livetv
End game
To replace mythtv01 with a pair of network attached dvb-s2 tuners (TBS moj are on order) and move the 1.5TB recordings disks into master, leaving me with a single combined master backend and frontend system.
So does this sound like a sensible plan?
Regards
Russell
More information about the mythtv-users
mailing list