[mythtv-users] 2Backends

Mark Perkins perkins1724 at hotmail.com
Mon Dec 5 14:06:41 UTC 2016


On 5 December 2016 11:16:59 PM James Linder <jam at tigger.ws> wrote:

> There is lots of mumble on google but little clear answer
>
> I want to run 2 backends on the same network:
> 1 x 0.27 with it’s own machine, db
> 1 x 0.28 with it’s own machine, db
>
> Never the twain shall meet - a 0.27 frontend will goto the 0.27 backend and 
> ditto for the 0.28 suite.
>
> From my user point of view what words of wisdom can I get here?
>
> Thanks
> James
> _______________________________________________

I have just setup an 0.27, 0.28 and master backend on a single machine and 
it seems to work mostly fine.  The main points are:
-set the pin on each backend to be blank so that frontends (or other 
backends if you accidentally type in a wrong IP address somewhere) can only 
connect if they already have the right credentials.
-give each backend its own network ports (not needed if separate IP addresses)
-give each database a different name to aid in remembering which one you 
are working on at the time (I have a single mariadb server for all 3 
databases).
-i created 3 separate mysql users with each one only having permission to 
access a single database as an extra layer of safety.
-use the environment variables / paths as described in the wiki (there are 
4, mythconfdir, python bindings, libraries and bin iirc). I have created 
wrapper scripts for everything to simplify.
-mythtv-setup will see the other local backends running even though it 
can't connect to them so best to shut all backends down before running 
mythtv-setup for changes.
-you will need to think about how to manage tuners so the backends are not 
fighting over them.  I have started to use mumudvb to rebroadcast the 
streams as http unicast.
-create separate storage groups for each backend for default recordings and 
livetv as a minimum otherwise you could end up with the backends fighting 
over recording files.
-will need to tweak build environment to handle qt4 versus qt5 etc but they 
all seem to mostly happily coexist. If you have separate machines managing 
the dependencies should be simpler.
-double check your backups are working because it doesn't take much of a 
typo to make a mess when they are so close together.




More information about the mythtv-users mailing list