<div class="gmail_quote">On Wed, Feb 1, 2012 at 2:29 PM, Kevin Johnson <span dir="ltr"><<a href="mailto:dabears_rule@yahoo.com">dabears_rule@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<table cellspacing="0" cellpadding="0" border="0"><tbody><tr><td valign="top" style="font:inherit">I have a dedicated backend with multiple frontends.<br>I use a hdhr for two of the four tuners.<br>I am running mythbuntu 24.2 fixes. (separate backend and frontends)<br>
<br>I travel quite frequently and my house is occupied by people who know little or nothing about computers or mythtv.<br>I want to have a spare backend setup to run in case my main backend goes down.<br>I will only use the spare backend in case the main backend goes down. It will only be used for sending the hdhr signal to the frontends scattered around the house. No recordings or movies or anything. (the frontends are low powered machines)<br>
Basically I want something that can be easily turned on in case of a server crash so people at the house can at least watch tv using the hdhr to the frontends. <br>What would be the simplest way to do this? <br>1. Setup a backend
on one of my frontends and "turn it on" in case the main backend fails?<br>2. Setup a slave backend?<br>3. Other options?<br><br>I would like something that is easily switched on by a novice user.<br><br>Thanks<br>
<br><br></td></tr></tbody></table><br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></blockquote></div><br><div>Do you have access to a ssh client from wherever you may be? For example, I have one on my smartphone and have on many occasions run simple stuff such as reboots or scripts while I was away from home. You should be able to setup a few scripts on your frontend/emergency backend that will kick off the backend process, and remotely run a script on each of the frontends to update the IP of the master backend and restart the frontend process. The emergency backend must have a hard drive large enough for the live TV buffers and a decent NIC (gigabit) since you will have to double the bandwidth of the number of the live TV streams (coming in from the HDHR and going out to the frontends). The user must also know not to schedule any recordings or they may fill up your live TV buffer disk rather quick. You may also need to keep the passwords in sync for at least the database.</div>
<div><br></div><div>There may be something I have not thought of, but this is probably a good start.</div><div><br></div><div>-Tom</div>