Hardware change and upgrade
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:5a37577da4091ec0058eebf9ec88ce75' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Hi all,</p>\n<p>I\'m putting in some new hardware and thought I\'d take the opportunity to upgrade as well. </p>\n<p>I\'m currently running 10.21 ol the old box and thought that building the new machine with 12.23 and then bringing the database across would be the way to go. My two drives full of recordings should simply unplug from the old box and get mounted up on the new.</p>\n<p>My question to the list is around the database. Is there a set of scripts or something that I can run on a copy of the database to upgrade its schema so that it can be used on the new machine? I\'d like to leave the old machine in play as long as possible given my currently high WAF and then switch over once I am confident that the new machine is fully sorted.</p>\n<p>Is this a direction others have gone down before? Would appreciate your input if you have.</p>\n<p>Regards<br />\nMarty </p>\n<p>(running Myth for 7 years now in various flavours!)</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:5a37577da4091ec0058eebf9ec88ce75' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:dded86c945a93746588c2a9fc1d37653' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>You can take a dump of the database by simply doing a mysqldump mythconverg >mythconverg.sql</p>\n<p>Or you can alternatively run /usr/share/mythdora/dorabackup -dump to create a copy on /storage/dorabackup/</p>\n<p>The only caveat may be that you need to get to 0.22 first on the DB, then to 0.23. I\'m not sure you can go right from 0.21 schema to 0.23, I\'ve never tried. </p>\n<p>At any rate, you just port the db backup to the new host, and import it with either dorabackup or mysql</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:dded86c945a93746588c2a9fc1d37653' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:1eb8f2e950a4e0a0e911bde8d30df2b3' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>My question is really one of how do you go about upgrading the database?</p>\n<p>Can this be done without upgrading the whole of MythTV?</p>\n<p>I\'d rather take a abckup of the database, upgrade this and then put it into place with the new machine rather than have to upgrade the current one (along with the software and risk breaking it).</p>\n<p>Or am I being overly paranoid? I\'ve had varying levels of success with previous upgrades.</p>\n<p>Are there any recommended backup and / or rollback strategies for upgrading my current system so that if it does break I can go back (reliably).</p>\n<p>Regards<br />\nMarty</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:1eb8f2e950a4e0a0e911bde8d30df2b3' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:2c8cd43169b51d2f5551de0ce31bb877' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>No, you can\'t upgrade the data base without the schema changes. Those are embedded in the mythtvsetup / frontend, etc programs. *technically* you could get the source and update the database with the sql code that\'s in there. But the easy way to do it is just update the app.</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:2c8cd43169b51d2f5551de0ce31bb877' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:fd70106db1a12e8cf926888d7ee26bc7' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Then I guess the question becomes \'what is the best way to backup a system prior to an upgrade so that it can be rolled back in case there are issues with the update?\'</p>\n<p>Maybe I am being overly cautious. Have been stung before, shy of the pain again.</p>\n<p>The WAF is high at the moment and has been for some time. Would like to keep it that way.</p>\n<p>Regards<br />\nMarty</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:fd70106db1a12e8cf926888d7ee26bc7' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:1a85722b4a66259beb84956761f8e817' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>I would;</p>\n<p>1 - back up the database<br />\n2 - Copy it onto a usb /dvd etc<br />\n3 - Upgrade the old box<br />\n4 - Back up that DB and keep it separate from the first one</p>\n<p>Now you have two versions of the DB, old and new.</p>\n<p>5 - install the new version on the new box.<br />\nYou will need to make sure that you have the same system name (and i would stick with the same IP) - they are linked to the recordings in the DB.</p>\n<p>6 - Connect all the hardware etc.<br />\n7 - Reinstall the DB from the new version.<br />\n8 - Cross fingers and dance backwards....</p>\n<p>Somewhere in there i would go through and get copies of all your custom configs, xorg, samba, etc. I run mine as a samba share for the family, and as a Time Machine backup for me, so i have nsswitchand afpd, new firmware for cards, so options,as well as Lirc, Lircrc, Lircd and VLC customisation to play videos.</p>\n<p>If it goes pear shaped, you can fall back to reinstalling 10.21 on the old box, or try it on the new box, with the 10.21 DB.</p>\n<p>I think this keeps the most options open for you.</p>\n<p>I hope this helps.</p>\n<p>AN</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:1a85722b4a66259beb84956761f8e817' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:0502fd227ffdc02c7149aeba8218a042' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>If I understand you correctly you are advocating running the new software against the old database.</p>\n<p>Don\'t think that there is even a vague chance that this will work.</p>\n<p>If anything I think installing the old version on the new box, swapping in the database from the old machine and then upgrading it to the current version is more likely to work.</p>\n<p>Had been hopin gthat I could just find the database upgrade scripts instead which would have let me install the new version on the new box, take a backup of the old database, upgrade it using the scripts and then use that.</p>\n<p>Regards<br />\nMarty</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:0502fd227ffdc02c7149aeba8218a042' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:e4eb8aae41f63deca0ea5c1df5c6245c' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>No. that\'s how it works. You import your old database, then you let the new application update that schema.</p>\n<p>But like I originally mentioned, you probably should go to 10.22 first. I\'m not 100% certain that you can schema jump from 0.21 to 0.23. </p>\n<p>Ryan</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:e4eb8aae41f63deca0ea5c1df5c6245c' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:b6b34c753b00b0e9e913ff85480635dd' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>\n<div class=\"quote-msg\">\n<div class=\"quote-author\"><em>pisani</em> wrote:</div>\n<p>But like I originally mentioned, you probably should go to 10.22 first. I\'m not 100% certain that you can schema jump from 0.21 to 0.23. </p>\n<p>Ryan</p></div>\n</p>\n<p>Actually I went from 0.20 to 0.23 directly. You get prompted multiple times for the schema update as each update script runs in turn.</p>\n<p>I would recommend you enable mythdora-updates (IIRC) repo during the install though. </p>\n<p>Then I went and installed 0.24 :-)</p>\n<p>Cheers<br />\nIan</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:b6b34c753b00b0e9e913ff85480635dd' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:0eb222027ba40a8125733d9d061e797a' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>There is some code to detect the old version and automatically run the update scripts? </p>\n<p>Nice!</p>\n<p>BTW. The 12.23 Release Notes have:</p>\n<p>Upgrading from 10.21:<br />\nBeta testing confirmed that upgrading via the DVD does work from 10.21 to 12.23.</p>\n<p>Might give it a shot, would cut out a step at least.</p>\n<p>Regards<br />\nMarty</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:0eb222027ba40a8125733d9d061e797a' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:73fc8bf76fc79c54137c613e24980351' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Yeah, guess that\'s true. I actually may have tested a clean build of 10.21 to go to 12.23. Either way, you can try it and see.</p>\n', created = 1369144243, expire = 1369230643, headers = '', serialized = 0 WHERE cid = '1:73fc8bf76fc79c54137c613e24980351' in /var/www/mythdora/html/includes/cache.inc on line 109.
Submitted by mravell on February 18, 2011 - 2:30pm
Hi all,
I'm putting in some new hardware and thought I'd take the opportunity to upgrade as well.
I'm currently running 10.21 ol the old box and thought that building the new machine with 12.23 and then bringing the database across would be the way to go. My two drives full of recordings should simply unplug from the old box and get mounted up on the new.
My question to the list is around the database. Is there a set of scripts or something that I can run on a copy of the database to upgrade its schema so that it can be used on the new machine? I'd like to leave the old machine in play as long as possible given my currently high WAF and then switch over once I am confident that the new machine is fully sorted.
Is this a direction others have gone down before? Would appreciate your input if you have.
Regards
Marty
(running Myth for 7 years now in various flavours!)
You can take a dump of the
You can take a dump of the database by simply doing a mysqldump mythconverg >mythconverg.sql
Or you can alternatively run /usr/share/mythdora/dorabackup -dump to create a copy on /storage/dorabackup/
The only caveat may be that you need to get to 0.22 first on the DB, then to 0.23. I'm not sure you can go right from 0.21 schema to 0.23, I've never tried.
At any rate, you just port the db backup to the new host, and import it with either dorabackup or mysql
But how?
My question is really one of how do you go about upgrading the database?
Can this be done without upgrading the whole of MythTV?
I'd rather take a abckup of the database, upgrade this and then put it into place with the new machine rather than have to upgrade the current one (along with the software and risk breaking it).
Or am I being overly paranoid? I've had varying levels of success with previous upgrades.
Are there any recommended backup and / or rollback strategies for upgrading my current system so that if it does break I can go back (reliably).
Regards
Marty
No, you can't upgrade the
No, you can't upgrade the data base without the schema changes. Those are embedded in the mythtvsetup / frontend, etc programs. *technically* you could get the source and update the database with the sql code that's in there. But the easy way to do it is just update the app.
Then I guess the question
Then I guess the question becomes 'what is the best way to backup a system prior to an upgrade so that it can be rolled back in case there are issues with the update?'
Maybe I am being overly cautious. Have been stung before, shy of the pain again.
The WAF is high at the moment and has been for some time. Would like to keep it that way.
Regards
Marty
Not that i have done it......but
I would;
1 - back up the database
2 - Copy it onto a usb /dvd etc
3 - Upgrade the old box
4 - Back up that DB and keep it separate from the first one
Now you have two versions of the DB, old and new.
5 - install the new version on the new box.
You will need to make sure that you have the same system name (and i would stick with the same IP) - they are linked to the recordings in the DB.
6 - Connect all the hardware etc.
7 - Reinstall the DB from the new version.
8 - Cross fingers and dance backwards....
Somewhere in there i would go through and get copies of all your custom configs, xorg, samba, etc. I run mine as a samba share for the family, and as a Time Machine backup for me, so i have nsswitchand afpd, new firmware for cards, so options,as well as Lirc, Lircrc, Lircd and VLC customisation to play videos.
If it goes pear shaped, you can fall back to reinstalling 10.21 on the old box, or try it on the new box, with the 10.21 DB.
I think this keeps the most options open for you.
I hope this helps.
AN
If I understand you correctly
If I understand you correctly you are advocating running the new software against the old database.
Don't think that there is even a vague chance that this will work.
If anything I think installing the old version on the new box, swapping in the database from the old machine and then upgrading it to the current version is more likely to work.
Had been hopin gthat I could just find the database upgrade scripts instead which would have let me install the new version on the new box, take a backup of the old database, upgrade it using the scripts and then use that.
Regards
Marty
No. that's how it works. You
No. that's how it works. You import your old database, then you let the new application update that schema.
But like I originally mentioned, you probably should go to 10.22 first. I'm not 100% certain that you can schema jump from 0.21 to 0.23.
Ryan
0.20 to 0.23 is possible in one leap
But like I originally mentioned, you probably should go to 10.22 first. I'm not 100% certain that you can schema jump from 0.21 to 0.23.
Ryan
Actually I went from 0.20 to 0.23 directly. You get prompted multiple times for the schema update as each update script runs in turn.
I would recommend you enable mythdora-updates (IIRC) repo during the install though.
Then I went and installed 0.24 :-)
Cheers
Ian
There is some code to detect
There is some code to detect the old version and automatically run the update scripts?
Nice!
BTW. The 12.23 Release Notes have:
Upgrading from 10.21:
Beta testing confirmed that upgrading via the DVD does work from 10.21 to 12.23.
Might give it a shot, would cut out a step at least.
Regards
Marty
Yeah, guess that's true. I
Yeah, guess that's true. I actually may have tested a clean build of 10.21 to go to 12.23. Either way, you can try it and see.