This is a bit scary; I've moved my recordings data between mythtv instances (I have a single NFS filestore for the recordings) several times before, without problems. I'm normally not *EVER* restoring the entire database, just the recordings info, by dumping the following tables into its own file with mysqldump:<br>
<br>record recorded oldrecorded recordedprogram recordedrating recordedmarkup recordedseek<br><br>And then restoring them on the new instance with mysql.<br><br>In fact, I dump this to a file on a weekly basis, and export it to a safe place. I'm also doing this with my dtv_multiplex and channel tables (less useful, but has come in handy)<br>
<br>I'm normally running a production and test instance master backends. I'm in the midst of migrating my "Old" production (svn 20028 with the original S2 patches in ticket 5882) to the new production (svn 21731). A straight backup/restore was not possible ("hacks" to the DB to support the original S2 implementation). So I've already got a "new" database instance with some recordings in it on the new production backend, and just want to merge in the recordings from the old backend. Using the orphans script is definitely *NOT* an option!<br>
<br><br>Are you suggesting this will not work any longer, or that I was lucky to have it work at all ?<br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Message: 13<br>
Date: Wed, 09 Sep 2009 13:04:02 -0400<br>
From: "Michael T. Dean" <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>><br>
Subject: Re: [mythtv-users] [mythtv] Tagging recordings....<br>
To: <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
Message-ID: <<a href="mailto:4AA7E002.8080700@thirdcontact.com">4AA7E002.8080700@thirdcontact.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
<Moving to the -users list><br>
<br>
On 09/09/2009 09:41 AM, Gary D Walborn wrote:<br>
> I suppose that this has been mentioned before, but MythTV should tag<br>
> files with enough info to import the file into the system (and the<br>
> database). I'm not sure if the nuppelvideo format support tags. I'm<br>
> quite sure that all the mpeg formats do. I suppose a separate file with<br>
> tags would be better than nothing, but that should be an option. I ran<br>
> MythTV for a couple of years and recently upgraded the system, skipping<br>
> several versions. I backed up my database but have been unable to get<br>
> hundreds of recordings in the new version. If I try to import just the<br>
> recording info (not the entire database), I get a message that columns<br>
> are missing.<br>
<br>
That's because, as described at<br>
<a href="http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup" target="_blank">http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup</a><br>
:<br>
<br>
Note, however, that it will only work if the backup schema version is<br>
identical to the schema version used by the currently-installed mythbackend.<br>
<br>
I added additional information and instructions for how to do a partial<br>
restore when also changing versions. (But it's probably too late for<br>
you, now.)<br>
<br>
> If I import the whole database, the new version does not<br>
> seem to be able to upgrade the database to the new version (I get<br>
> repeated upgrade messages even though I select "Upgrade" from the<br>
> dialog. It MUST be easier to import pre-existing files into MythTV.<br>
> This is very frustrating.<br>
<br>
Please show me exact errors from the log file. You should see 2 prompts<br>
asking if you want to upgrade. The first before the backup, the 2nd<br>
after the backup (and allowing you to stop if the backup failed).<br>
Therefore, depending on how many "multiple prompts" you see, everything<br>
may be working fine. (Note, also, that you'll get a prompt for<br>
upgrading the MythMusic DB schema version when you start<br>
mythfrontend--we haven't got prompts for other plugins, yet, though.)<br>
<br>
I recommend going back to your old-version database backup and doing a<br>
full restore. Also, and *most importantly* the upgrade to current<br>
trunk's database schema version takes a *long* time. (<br>
<a href="http://www.gossamer-threads.com/lists/mythtv/users/396252#396252" target="_blank">http://www.gossamer-threads.com/lists/mythtv/users/396252#396252</a> ). Do<br>
not stop it mid upgrade or you will corrupt/break your data.<br>
<br>
Note, also, that there is no difference going between 0.21-fixes and<br>
trunk or going between 0.18 and trunk--the same path is followed, but in<br>
the former case, it's just been done in gradual steps. Therefore, it's<br>
highly unlikely there are problems with the procedure used in the Myth<br>
code as it's been very well tested by a lot of users.<br>
<br>
Mike<br>
<br>
<br></blockquote></div>