Mailing List Archive: MythTV: Users

Testing 0.22 before full backend upgrade

Index | Next | Previous | View Threaded

chris at westnet

Nov 7, 2009, 9:09 AM

Post #1 of 3 (373 views)
Permalink

Testing 0.22 before full backend upgrade

I would like to do some testing of the 0.22 frontend before springing the
whole thing on my family. Assuming a 0.22 frontend won't talk to a 0.21
backend, even in a half-arsed way to test out the menus, I am thinking of
this strategy

Run a test install on my desktop, as a combined front/backend. Load up the
database from my live backend and upgrade it. This test backend wouldn't
have any tuners -- if that REALLY is a drop dead problem I can stick an old
PVR-500 in it.

Mount the real backend's media drives via read-only NFS, so I can't muck
them up.

Anything I am missing ?

==========================================================
Chris Candreva -- chris [at] westnet -- (914) 948-3162
WestNet Internet Services of Westchester
http://www.westnet.com/
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarpublic at gmail

Nov 7, 2009, 9:40 AM

Post #2 of 3 (351 views)
Permalink

Re: Testing 0.22 before full backend upgrade [In reply to]

> I would like to do some testing of the 0.22 frontend before springing the
> whole thing on my family. Assuming a 0.22 frontend won't talk to a 0.21
> backend, even in a half-arsed way to test out the menus, I am thinking of
> this strategy
>
> Run a test install on my desktop, as a combined front/backend. Load up the
> database from my live backend and upgrade it. This test backend wouldn't
> have any tuners -- if that REALLY is a drop dead problem I can stick an old
> PVR-500 in it.
>
> Mount the real backend's media drives via read-only NFS, so I can't muck
> them up.

Definitely backup the database, and you may want to choose a time when
the old backend isn't doing anything and shutdown mythbackend and
mysql initially. I have read threads where there were issues having
separate backends on the same network because of the auto discovery
features. I have seen people inadvertently connecting to or updating
the wrong backend or mysql database.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv-list at dinkum

Nov 9, 2009, 2:17 AM

Post #3 of 3 (318 views)
Permalink

Re: Testing 0.22 before full backend upgrade [In reply to]

On 7 Nov 2009, at 17:40, Johnny wrote:
>
> Definitely backup the database, and you may want to choose a time when
> the old backend isn't doing anything and shutdown mythbackend and
> mysql initially. I have read threads where there were issues having
> separate backends on the same network because of the auto discovery
> features. I have seen people inadvertently connecting to or updating
> the wrong backend or mysql database.

That happened to me some time ago!

Even if you specify which database to upgrade, MythTV knows better,
well in an old svn version quite some time ago anyway.
After I'd restored the database from a backup I added a couple of
firewall rules to prevent mythtv & mysql access from the test
frontend. I now have a 0.22 system running on the same network as my
0.21, supposedly if you turn of uPnP it doesn't auto detect but I use
only uPnP for playback so that wasn't really an option.

Andre
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads