[mythtv-users] Restoring old database to newer version install

[Ian Evans]

On Aug 11, 2016 6:25 PM, "Michael T. Dean" <mtdean at thirdcontact.com> wrote:
>
> On 08/11/2016 04:33 PM, Bill Meek wrote:
>>
>> On 08/11/2016 02:29 PM, Ian Evans wrote:
>>>
>>> So all I need to do after that is run mythconverg_restore.pl? It
handles the mismatched schemas?
>>
>>
>> No. mythconverg_restore.pl restores a backup you made
>> earlier. Probably/recently on 0.27 in your case.
>>
>> The schema upgrade happens when you run a 0.28 mythtv_setup
>> (and mythfrontend.) mythbackend will do the upgrade too, but
>> mythtv_setup is preferred.
>
>
> Right, so make sure you do a complete restore, and to be safe (in case
your package manager creates a schema), use the
>
> --drop_database --create_database
>
> arguments, as at
>
https://www.mythtv.org/wiki/Database_Backup_and_Restore#Replacing_an_existing_database
> (which will work fine, even if there is no existing database, given a
user with proper permissions--so you should really always use those
arguments).
>
> You cannot do a partial restore--but, on the bright side, there's no good
reason to ever do a partial restore unless you have some database
corruption in some of the tables (but not in any of the partial-restore
tables).
>

Still a bit confused here. Okay, if I can't use the restore because the
schemas are mismatched, how do I get the 0.27 database onto the new 0.28
system?

Again I am talking about a completely fresh, reformat the drive upgrade
from 12.04/0.27 to 16.04/0.28.

Am I just cp'ing the mythtv mysql files over to another drive, doing the
fresh installation and then mv'ing the files over again so that myth-setup
will then do the schema upgrade when I start it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160811/fa59492c/attachment.html>