I have a secondary backend that always loses connection to the master backend whenever one system gets rebooted for whatever reason. Is there a setting I am missing that will make the two communicate with each other so that they maintain their connection?

TIA

Huh? Must be missing something. When you reboot, the system is supposed to lose the connection. But it should come back up once the reboot is complete. At least mine do.

So there is no setting that you have to enable to make the reconnection automatic? What kind of time frame should the reconnect happen? Maybe I am checking on it too soon after the disconnect?? After a reboot or power flicker, I pull up Mythweb and check the status and the tuner in the secondary backend always shows disconnected.

I don't know of any settings for it. I have UPS's on all my boxes, so I don't have power hits. When I boot/reboot the secondary, the tuner in it comes available after boot sometime. Couldn't say exactly when, but not long. It's the 5th tuner, so doesn't get used much. If I stop and restart the master, then the secondary is seen during the restart sometime. Haven't timed it cause it's never been an issue. I don't use mythweb, so maybe the problems there.

most times my secondary backends just eventually get recognized. I haven't timed it either. but as mentioned, restarting the master usually make them visible when I'm in a hurry during testin or something.

Another question for those using secondary backends:

How do you have your recordings stored? Do you store them locally on the secondary backend or does the recording get stored on the master backend?

I have my recording folder on my master backend shared via NFS. I then mount this share on the secondary backend. In the backend setup for the secondary backend I set this mounted share as the recording location. I have just recently started using NFS, previously I used Samba. Is my setup correct or am I making it too difficult?

TIA

Another question for those using secondary backends:

How do you have your recordings stored? Do you store them locally on the secondary backend or does the recording get stored on the master backend?

I have my recording folder on my master backend shared via NFS. I then mount this share on the secondary backend. In the backend setup for the secondary backend I set this mounted share as the recording location. I have just recently started using NFS, previously I used Samba. Is my setup correct or am I making it too difficult?

TIA

It's a personal choice, based partially on your hardware and where you have the storage. I store all my recordings local to the backend that records it. I have a fair amount of other network traffic from time to time, and only have a 100Mbps network (haven't bothered to upgrade all my switches) so I don't want to record over the network. And I have an appropriate amount of storage on each secondary backend. Heck, my master backend has no tuners or recordings.

One benefit of keeping all the storage on your master is that you can watch recordings from the slaves even when they are off or not connected.

If you do use central storage, to cut down on network traffic, I recommend you use the Master Backend override in mythtv-setup.

I'm sure others will have other thoughts...

So if I store locally on the recording machine will the master backend, which is also my main frontend, automatically know where the recording is? How do I set this up? I'd rather have it this way because I have noticed some flaky recordings. That is why I switched from Samba to NFS, but that hasn't seemed to help.

So if I store locally on the recording machine will the master backend, which is also my main frontend, automatically know where the recording is? How do I set this up? I'd rather have it this way because I have noticed some flaky recordings. That is why I switched from Samba to NFS, but that hasn't seemed to help.

Yes it the master backend will know. You don't have to do anything special to set it up. You'd just have set up the storage group on your secondary backend to be on a local drive. Your master backend will know where to get the recording.
You don't even have to share the drive where the recordings are via NFS or SAMBA. Myth has it's own streaming protocol for recordings and liveTV that doesn't require setup.

I switched the secondary to save locally and everything seems to be working correctly. In the secondary setup should I have "mater backend override " selected or unselected?

I switched the secondary to save locally and everything seems to be working correctly. In the secondary setup should I have "mater backend override " selected or unselected?

I'd unselect it - it's for if you have centralized storage - it helps lessen network traffic in some cases if you have centralized storage.

Ok...Thanks for your help....once again!!!