[mythtv-users] Upgrading from old versions and preserving the database
two.bits.11 at gmail.com
Fri Jul 29 19:27:57 UTC 2011
On Fri, Jul 29, 2011 at 3:16 PM, DFishburn <dfishburn.mythtv at gmail.com>wrote:
> On 7/25/2011 2:57 PM, mythtv-users-request at mythtv.org wrot
> > Because you'll be getting a different MySQL version, you'll want to do
> > a full backup ( http://www.mythtv.org/wiki/Database_Backup_and_Restore
> > ) on your 0.21-fixes system. Note that the backup script will work
> > with any version of MythTV, so even though it's not shipped with
> > 0.21-fixes, you can download it (as described in the wiki page), then
> > use it to make a backup. Then, after re-installed the operating
> > system, you'll restore the database, while replacing the existing
> > database (
> > ).
> On my Myth 21 box I downloaded a new backup script and ran it, copied
> over the file to my "test" machine.
> I just tried this out on Mythbuntu 11-04 (which should be MythTV 24 at
> I essentially used this command line:
> mythconverg_restore.pl --drop_database --create_database --filename
> Ran myth-setup, it asked if I wanted to upgrade my database.
> The upgrade succeeded, restarted myth backend and the frontend.
> Now, I get a message box on the FE startup:
> "The server uses network protocol version 40,
> but this client only understands version 63.
> Make sure you are running compatible versions
> of the backend and frontend."
> Now that I am typing this up, am I just realized I am "switching hosts",
> since I am trying it on a test machine.
> Mike also mentioned this:
> > I highly recommend using the same host name and IP address for your
> > machine, so that you don't have to change the host names in the
> > database, but if you must use a different host name, see
> > . If you change the IP address, you'll need to re-run mythtv-setup and
> > update the IP address setting for "this backend" and possibly for the
> > master backend.
> So I am assuming I can simply run this:
> mythconverg_restore.pl --change_hostname --old_hostname="192.168.0.40"
> And then restart the frontend.
> I will try this later tonight, but if there are other things to try or
> check first, I am double checking.
> mythtv-users mailing list
> mythtv-users at mythtv.org
I just had this happen last night with my migration from .22 to .24-fixes.
My problem is that my old production backend was still up and running. The
frontend on my new backend was talking to my old backend. Doh! It only
took an hour to figure that out. The hostname does not equate to IP address
in the backup/restore scripts. The simplest thing I did, was shutdown the
old backend temporarily and update the mythtv-setup -> General -> IP address
on the new backend, and re-ran the frontend on my new backend with the -p
option to have ask where the backend is located. I probably didn't need to
do every step, but I was up and running after that.
I hope this helps.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users