<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/19/2013 02:36 PM, Karl Newman
wrote:<br>
</div>
<blockquote
cite="mid:CAOOwNtL0vr3-gyAu6ovEc+6DPv1bBkvT3b_iLJ7ohBUFn_bUkw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Dec 19, 2013 at 10:50 AM,
Rich West <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:Rich.West@wesmo.com" target="_blank">Rich.West@wesmo.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
12/19/2013 12:52 PM, Matthias Thyroff wrote:<br>
> On 19.12.2013 18:01, Jon N wrote:<br>
>> On Thu, Dec 19, 2013 at 11:56 AM, Jon N <<a
moz-do-not-send="true"
href="mailto:jdnandroid@gmail.com">jdnandroid@gmail.com</a>>
wrote:<br>
>>> Hi,<br>
>>><br>
>>> I am planning on moving my MythTV
frontend/backend (it's the only<br>
>>> backend I have) to a new machine. I have
been reading backend<br>
>>> migration page on the wiki on Mythtv.org, but
still have at least one<br>
>>> question about passwords.<br>
>>><br>
>>> I set up Mythtv so long ago I don't remember
much about it, but I do<br>
>>> seem to remember there is a password
associated with it, I think it'<br>
>> ...oops, somehow I managed to send that before it
was done. Picking<br>
>> up where I left off...<br>
>><br>
>> was for access to the mysql database. Is this a
factor in moving<br>
>> things to the new computer? I don't see it
mentioned on the database<br>
>> migration page, but I admit moving this makes me
a little nervous (I<br>
>> am not what I would call a power user), so I
would just like to<br>
>> verify before I start.<br>
>><br>
>> BTW, if anyone knows of an alternate guide to
doing this please pass<br>
>> it along. I often find having more than one
perspective on doing<br>
>> something helps.<br>
>><br>
>> Thanks,<br>
>> Jon<br>
>> _______________________________________________<br>
>> mythtv-users mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
>> <a moz-do-not-send="true"
href="http://www.mythtv.org/mailman/listinfo/mythtv-users"
target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
> Hello Jon,<br>
><br>
> I have moved my backend many times already from one
machine to the<br>
> next one... starting on a PII, Athlon, Athlon X2, and
now I am on an<br>
> ivy bridge celeron, I think, always complete with the
underlaying<br>
> linux installation, either just taking the hard disk
to the new<br>
> computer or copying the whole system to to a new disk
(there are<br>
> instructions on the internet to do that, you might
have to boot from a<br>
> CD to reconfigure grub). This saved me from
reconfiguring, not only<br>
> myth, but also the web server, the mail system, the
users, the cloud,<br>
> the pbx (at that time)...<br>
><br>
> This is also why I am still running 32bit on 64bit
hardware, but I do<br>
> not see the need to change to 64bit at all (maybe a
tiny little<br>
> technology itch, but I can live in peace with that.)<br>
><br>
> That is one of the great things about linux: Changing
the platform<br>
> does not mean automatically that you have to
reinstall. It is quite<br>
> cool to see the old installation booting the first
time on new hardware.<br>
><br>
> It sometimes needs some tweaking, removing old
network adaptors,<br>
> tweaking powersaving, minor things that you have to
tweak manually<br>
> anyway.<br>
><br>
> And when everything is running, you still should go
and recover your<br>
> passwords, maybe.<br>
><br>
> Good luck and fun for your holidays project!<br>
><br>
> Matthias<br>
<br>
I've copied the entire /root/.mythtv directory and the<br>
entire /var/lib/mysql directory over (perhaps not the best
practice, but<br>
it has worked well) to the remote host.</blockquote>
<div><br>
Don't do that. The fact that it worked just means you've
been lucky.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Not lucky at all. When you are in the process of moving a system,
definitely make sure you DO NOT have mysqld running. In all cases
of migrations, I have mythbackend off, mysql off. Attempting to
move a database when it is running.. well, that's just silly talk.
:)<br>
<br>
<blockquote
cite="mid:CAOOwNtL0vr3-gyAu6ovEc+6DPv1bBkvT3b_iLJ7ohBUFn_bUkw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> You
could always do a mysqldump<br>
mythconverg > mythconverg.sql, copy the file over to
the new host and<br>
run mysql < /root/mythconverg, <br>
</blockquote>
<div><br>
</div>
<div>Don't do that either. You should use the <a
moz-do-not-send="true"
href="http://mythconverg_backup.pl">mythconverg_backup.pl</a>
and <a moz-do-not-send="true"
href="http://mythconverg_restore.pl">mythconverg_restore.pl</a>
scripts (in the /usr/share/mythtv directory in most
distros) to ensure you get the correct command line
switches to avoid a corrupted database.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Sorry.. I sent that out too quickly.. I should have clarified that I
always run "mysqldump --add-drop-table --complete-insert
--extended-insert mythconverg" when backing up my databases nightly,
and I've used that backup in the past to do restores locally and to
test hosts (when testing a new revision). Looks like
mythconverg_backup.pl is a cool wrapper around that (although it
looks like the mythconverg_backup.pl command has a --no-create-db
option, which doesn't give the warm-n-fuzzy, and it has
--add-drop-table in there twice).<br>
<br>
The mythconverg_backup.pl and mythconverg_restore.pl scripts are a
good way to go as well, especially if you don't have a lot of linux
experience. Personally, I didn't know they existed (probably didn't
when I first started with myth), so now I have something to
investigate in order to modernize my backup process. :) Thanks!<br>
<br>
-Rich<br>
<br>
</body>
</html>