<div class="gmail_quote">On Thu, Nov 3, 2011 at 1:37 PM, <span dir="ltr"><<a href="mailto:lothar.subscribe@comcast.net">lothar.subscribe@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="font-family:Arial;font-size:12pt;color:#000000"><div style="font-family:Arial;font-size:12pt;color:#000000"><div style="font-family:Arial;font-size:12pt;color:#000000"><div style="font-family:Arial;font-size:12pt;color:#000000">
<div class="im">>I know how to<br>>back up the database, install a new 64 bit version of Natty or Oneric, and<br>>then restore the database, but if I do that, it forces the upgrade to 0.24,<br>>and that is the part I am not so sure of. I know that the database schema<br>
>changes with each version, and I am worried about importing a 0.23 database<br>>into a 0.24 installation.<br>><br></div><div class="im">>Does anybody have experience? I have a very high WAF (my current system<br>
>has been stable for 3 years, and the one before that was good for about 2<br>>years), and I don't want to ruin it.<br>><br>>Matthew Asplund<br><div>></div></div><div><hr> </div><div>I recently upgraded from 0.21 to 0.24 (three times because it kept recording new shows before I had time to migrate all of my systems) using the mythconverg_backup and mythconverg_restore scripts. The process went very smoothly each time. In my case, I used a separate hard drive to do the new installation on so I was guaranteed to not lose data, but it wasn't a problem in the end anyway. I wrote up the experience here if you want to take a look: <a href="http://www.missingremote.com/guide/migrating-mythtv-database-between-installations" target="_blank">http://www.missingremote.com/guide/migrating-mythtv-database-between-installations</a></div>
</div></div></div></div></div></blockquote><div><br>I did a quick read through and my only comment is Myth's database doesn't like it if the name of your backend changes (assuming you are retiring one and replacing it with a new one). You can either jump through the hoops needed to fix the problems or change the name of your new backend to be the same as your old one before you start MythFrontend or run Myth_Setup.<br>
<br>See <a href="http://www.mythtv.org/wiki/Backend_migration" target="_blank">http://www.mythtv.org/wiki/Backend_migration</a> for details on how to do these. </div></div>