[mythtv-users] Backend upgrade question

Matthew Asplund mattasplund at gmail.com
Sat Nov 5 05:25:49 UTC 2011

So, I came up with a plan that I thought would work.  I built my new
machine, ran a bunch of tests to make sure that there were not hardware
problems.  Then I transferred my drives from the old machine to the new
machine.  I figured to get it working with the old installation on the new
hardware. Then I would do the upgrades from there.

So, I transferred the disks to the new machine, changed the dhcp entry on
my router to give it the same IP address as my old server, and booted it
up.  It came up fine, and everything worked, and was in the right place.
 But when I tried to connect to the backend from one of my front ends, it
connected just fine, but it couldn't find the files.  It had the recordings
in the database, but when I tried to play any of them, it said that the
files for the shows could not be found.  I checked, and the recordings
directories were mounted in the right places, and the files were there.
 When I checked out the mythbackend log file, it said that it was looking
for files that weren't there, and sure enough, the files weren't there.

So, is there something funny about moving the database like this.  Does the
filename somehow depend on some id field from the machine?  WIll this be
fixed by doing a backup and restore of the database?


On Fri, Nov 4, 2011 at 7:49 AM, Roger H <mythtvuser1818 at gmail.com> wrote:

> On Thu, Nov 3, 2011 at 1:37 PM, <lothar.subscribe at comcast.net> wrote:
>>  >I know how to
>> >back up the database, install a new 64 bit version of Natty or Oneric,
>> and
>> >then restore the database, but if I do that, it forces the upgrade to
>> 0.24,
>> >and that is the part I am not so sure of.  I know that the database
>> schema
>> >changes with each version, and I am worried about importing a 0.23
>> database
>> >into a 0.24 installation.
>> >
>> >Does anybody have experience?  I have a very high WAF (my current system
>> >has been stable for 3 years, and the one before that was good for about 2
>> >years), and I don't want to ruin it.
>> >
>> >Matthew Asplund
>> >
>> ------------------------------
>> 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:
>> http://www.missingremote.com/guide/migrating-mythtv-database-between-installations
> 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.
> See http://www.mythtv.org/wiki/Backend_migration for details on how to do
> these.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20111104/8e874485/attachment-0001.html 

More information about the mythtv-users mailing list