<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 17, 2023, 3:45 PM Bill Meek <<a href="mailto:keemllib@gmail.com">keemllib@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 1/17/23 14:17, James Abernathy wrote:<br>
> <br>
> <br>
> On Tue, Jan 17, 2023 at 2:43 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank" rel="noreferrer">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank" rel="noreferrer">jfabernathy@gmail.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On Tue, Jan 17, 2023 at 2:13 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank" rel="noreferrer">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank" rel="noreferrer">jfabernathy@gmail.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On Tue, Jan 17, 2023 at 11:48 AM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank" rel="noreferrer">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank" rel="noreferrer">jfabernathy@gmail.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On Tue, Jan 17, 2023 at 11:10 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank" rel="noreferrer">stephen_agent@jsw.gen.nz</a> <mailto:<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank" rel="noreferrer">stephen_agent@jsw.gen.nz</a>>> wrote:<br>
> <br>
> On Tue, 17 Jan 2023 09:07:44 -0500, you wrote:<br>
> <br>
> >I want to confirm what I think I need to do to create a duplicate backend<br>
> >so I can take it with me.<br>
> ><br>
> >My production backend has a lot of TV recordings that I have not<br>
> >watched yet. I thought I would take a snapshot of my production backend<br>
> >with me.<br>
> ><br>
> >Both my production backend and traveling backend are v32 on Ubuntu 22.04<br>
> >derivative Distro's.<br>
> ><br>
> >I think all I have to do is move the contents of the production backend<br>
> >Storage Group directories to the same relative directories on the traveling<br>
> >backend and then take a backup of the production mythconverg database and<br>
> >restore that to the traveling backend's database.<br>
> ><br>
> >Since the tuner hardware on the production backend is a Hauppauge WinTV<br>
> >Quad PCIe card and the traveling backend is HDHomeRun tuners, I have some<br>
> >setup work to do but am I missing anything else?<br>
> ><br>
> >Jim A<br>
> <br>
> If you want fully identical duplication, you can backup the production<br>
> database and restore it on the traveling machine. But that means that<br>
> you will need to have both machines using the same hostname and<br>
> possibly also the same IP address. This makes it difficult to have<br>
> both machines on the same network. It is better to use different<br>
> hostnames and use the --change_hostname option of<br>
> <a href="http://mythconverg_restore.pl" rel="noreferrer noreferrer" target="_blank">mythconverg_restore.pl</a> <<a href="http://mythconverg_restore.pl" rel="noreferrer noreferrer" target="_blank">http://mythconverg_restore.pl</a>> to change the hostname when doing the database<br>
> restore.<br>
> <br>
> Personally, I use my laptop as my traveling machine, and it has two<br>
> hard drives in an external dual USB mount that I just transfer<br>
> recordings onto to take with me. I use mythexport/mythimport to do<br>
> that. So the laptop has an independent setup and just gets imported<br>
> recordings added to its database. There is no way I would want to<br>
> take my production box's hard drives away with me, as I need them on<br>
> that box doing recordings while I am away. My laptop is capable of<br>
> recording using a couple of USB tuners, but I rarely do that as two<br>
> drives of recordings is quite enough for a few weeks away from home.<br>
> And if I am staying somewhere there is decent enough Internet, I can<br>
> just download some new recordings from home and import them. I run an<br>
> OpenVPN server on my home network and VNC servers on each PC so I have<br>
> full control of the PCs at home as long as I have even a basic<br>
> Internet connection. The four drives that store my videos, photos,<br>
> music and so on are on a quad SATA/USB drive carrier that I can just<br>
> disconnect from the production system SATA port and plug into the<br>
> laptop via its USB port, so I also take that with me. One of the USB<br>
> tuners has an IR receiver onboard, so I can use an IR remote just like<br>
> at home, and I have a long HDMI cable to plug into any big screen that<br>
> is available. But the laptop has a 17" screen anyway, so it is fine<br>
> for a couple of people to watch at the same time.<br>
> <br>
> <br>
> So does the mythexport/mythimport preserve metadata for the recordings?<br>
> <br>
> I might do that next time as this was more work than I had anticipated. Since the backends had different names and different<br>
> hardware, mythtv-setup after the restore did the usual crash 3 times until I got serious and ran mythtv-setup.real -v most:debug and<br>
> that scared it into working. But I did have to do a complete setup to get all the parameters right.<br>
> <br>
> But in the end I have all the recordings with metadata, and schedules on my travel backend. They will run in parallel for a few<br>
> weeks before I leave and I'll move the travel BE to my RV and set up the antenna system to the HDHR. I use Mobile Data and a<br>
> tethered AP/Router.<br>
> <br>
> I'll have all the recordings on my production BE when I return, but can delete the ones I've already seen on the travel BE.<br>
> <br>
> Thanks, all,<br>
> <br>
> Jim A<br>
> <br>
> <br>
> Here's an odd one. So I have the duplicate backend up and running on my travel BE which is an Intel NUC. Everything I've tested works<br>
> and I can play all those recordings I did on the production BE. However, I installed Kodi and Kodi-pvr-mythtv and it can launch livetv,<br>
> but it can't play any of the previous recordings from the old backend. mythfrontend can but not kodi. I looked in the log and it can't<br>
> connect with the backend. However, it connects fine for all the new stuff. Even new recordings that get setup on the travel BE. Just<br>
> can play the ones brought over from the Production backend. I wonder what in the database is confusing the Kodi system.<br>
> <br>
> Not a big deal since I'll probably use mythfrontend or Leanfront on a FireTV most of the time, but Kodi is nice for videos and music.<br>
> <br>
> Jim A<br>
> <br>
> <br>
> It appears that the Recording Host is kept in the database. If I look at the information "I" key twice in the List of recordings, my new<br>
> recording on the travel BE has its correct name. The recordings brought over had the Production BE name. mythfrontend doesn't care but<br>
> Kodi does. Interesting. <br>
> <br>
> <br>
> For those playing along at home:<br>
> mysql> UPDATE recorded SET hostname = "den-pc";<br>
> <br>
> This set the hostname of all the old recordings to the new hostname and now kodi works as well as mythfrontend.<br>
<br>
Did you use the --change_hostname option of <a href="http://mythconverg_restore.pl" rel="noreferrer noreferrer" target="_blank">mythconverg_restore.pl</a>?<br>
<br>
-- <br>
Bill<br>
<br>
____________________________<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Unfortunately I not smart enough to have done that. But I think I recovered nicely 😀</div><div dir="auto"><br></div><div dir="auto">Jim A</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>