<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;">
1) Use the /exact/ same hostname for the new system as you used for the old.<br>
</blockquote><div><br>I can vouch for this hostname issue. I just used the --partial restore option to move my recordings over to some new hardware and I've had terrible problems. I now fiund that my new backend shows up as <unknown> when a frontend UPNP's it. I'm therefore going to rebuild the new frontend using the old name and migrate again.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If you can't use the same hostname, make sure you do a hostname change ( <a href="http://www.mythtv.org/wiki/Database_Backup_and_Restore#Change_the_hostname_of_a_MythTV_frontend_or_backend" target="_blank">http://www.mythtv.org/wiki/Database_Backup_and_Restore#Change_the_hostname_of_a_MythTV_frontend_or_backend</a> ) using the restore script /at the right time/... I.e. right after you restore the DB (without specifying the hostname change), do the hostname change. Do *not* run /any/ mythtv programs (mythtv-setup, mythbackend, mythfrontend) against the restored database before doing the hostname change or you will make a mess that will require a /lot/ of work to clean up.<br clear="all">
<br></blockquote></div><br>Defo keep the old drive - I've rolled back so many times on a new frontend trying to get a stable VDPAU install I just cant imagine what I'd have done without it!<br><br>Cheers,<br>Steve.<br>
<br>