<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><br>
<br>
Hi Mike!<br>
<br>
</div>
<blockquote type="cite"
cite="mid:mailman.5.1523016002.16257.mythtv-users@mythtv.org">
<pre wrap="">The anomalies you list in switching should not be happening if your network and host names are setup correctly. I?m going to assume you have two databases (one on each backend), and each of those databases will hold settings for each of your frontend machines. If you switch from one backend to another and you?ve never configured that frontend on that backend, then yes, all the settings will default because backend 2 has never seen backend 1. However, if you configure all of your settings also on backend 2 the same as backend 1, changing backends should be transparent as long as the settings are identical.</pre>
</blockquote>
<br>
Agree: if I configure the two backend to have the same name and
password I should be able to switch between the two with a change of
the address to select the Backend. Not so sure can be done all that
easily by the 'non Geek' people here. Good tip for Klaus however.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:mailman.5.1523016002.16257.mythtv-users@mythtv.org">
<pre wrap="">Hope this helps you make your system a tad bit more elegant, because it?s myth? and it should be. :)
</pre>
</blockquote>
<br>
No disagreement! Some of the 'sloppiness' here has been done on
purpose to make it easier to troubleshoot. The original intention
was for the new Backend to replace the aging existing Backend when
discovered there are intermittent issues with reception (OTA). As
this is Klaus's thread I don't want to insert my problems. ...Hope
that's not sounding rude or unappreciative.<br>
<br>
Barry<br>
</body>
</html>