Mailing List Archive: MythTV: Users

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data

Index | Next | Previous | View Threaded

mythtv at american-hero

Jul 3, 2008, 7:27 PM

Post #1 of 8 (478 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data

John Drescher wrote:
> On Thu, Jul 3, 2008 at 10:12 PM, Larry Roberts <mythtv[at]american-hero.com> wrote:
>> I managed to get some new to me hardware so I'm in process of migrating
>> from an FC6 box running .20 to a Centos 5.2 running .21.
>>
>> I have an export of the mysql DB, and had planned to just do a reimport,
>> but with the new features of .21 and things like storage groups I'm a
>> little concerned that its not that easy.
>>
>> What if anything do I have to do to import the data? Is there a field
>> that I will need to populate in the DB for each recording to tell it
>> what storage group (or rather file system location within the SG) I used?
>>
> No. Myth automatically finds the files as long as you setup the
> recordings folder to be in the storage group.
> John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Great. I was concerned that some field had been added that would cause
the import to fail.

I'm at the point of importing the file so here goes nothing! (or
hopefully EVERYTHING!)

Thanks

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

drescherjm at gmail

Jul 3, 2008, 7:33 PM

Post #2 of 8 (450 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data [In reply to]

On Thu, Jul 3, 2008 at 10:27 PM, Larry Roberts <mythtv[at]american-hero.com> wrote:
> John Drescher wrote:
>> On Thu, Jul 3, 2008 at 10:12 PM, Larry Roberts <mythtv[at]american-hero.com> wrote:
>>> I managed to get some new to me hardware so I'm in process of migrating
>>> from an FC6 box running .20 to a Centos 5.2 running .21.
>>>
>>> I have an export of the mysql DB, and had planned to just do a reimport,
>>> but with the new features of .21 and things like storage groups I'm a
>>> little concerned that its not that easy.
>>>
>>> What if anything do I have to do to import the data? Is there a field
>>> that I will need to populate in the DB for each recording to tell it
>>> what storage group (or rather file system location within the SG) I used?
>>>
>> No. Myth automatically finds the files as long as you setup the
>> recordings folder to be in the storage group.
>> John
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users[at]mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> Great. I was concerned that some field had been added that would cause
> the import to fail.
>
> I'm at the point of importing the file so here goes nothing! (or
> hopefully EVERYTHING!)
>
I believe when you first start the backend the schema will be updated.

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

mythtv at american-hero

Jul 3, 2008, 7:47 PM

Post #3 of 8 (452 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data [In reply to]

John Drescher wrote:
> On Thu, Jul 3, 2008 at 10:27 PM, Larry Roberts <mythtv[at]american-hero.com> wrote:
>> John Drescher wrote:
>>> On Thu, Jul 3, 2008 at 10:12 PM, Larry Roberts <mythtv[at]american-hero.com> wrote:
>>>> I managed to get some new to me hardware so I'm in process of migrating
>>>> from an FC6 box running .20 to a Centos 5.2 running .21.
>>>>
>>>> I have an export of the mysql DB, and had planned to just do a reimport,
>>>> but with the new features of .21 and things like storage groups I'm a
>>>> little concerned that its not that easy.
>>>>
>>>> What if anything do I have to do to import the data? Is there a field
>>>> that I will need to populate in the DB for each recording to tell it
>>>> what storage group (or rather file system location within the SG) I used?
>>>>
>>> No. Myth automatically finds the files as long as you setup the
>>> recordings folder to be in the storage group.
>>> John
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users[at]mythtv.org
>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>> Great. I was concerned that some field had been added that would cause
>> the import to fail.
>>
>> I'm at the point of importing the file so here goes nothing! (or
>> hopefully EVERYTHING!)
>>
> I believe when you first start the backend the schema will be updated.
>
> John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

SUCCESS!

For those following along at home I followed the directions found here:

http://www.mythtv.org/docs/mythtv-HOWTO-23.html for moving your data to
a new server. If I had been staying with the same version of the DB I
believe I could have gotten away with just dropping the old db and
restoring the old one, but given the schema changes this way made sense.

I had to restart the backend to have it reflect my upcoming recordings
but all appears well now.

Last thing to figure out is how to get the tv-out of the PVR-350. I
wouldn't be surprised to see a message about that coming up next. :) I
vaguely remember some ivtvfb stuff in the xorg.conf that had to be
changed and fb drivers I had to update only to find out .20 didn't
support it on the new format.

thanks for the quick response to my overly concerned email!

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

mtdean at thirdcontact

Jul 3, 2008, 8:59 PM

Post #4 of 8 (439 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data [In reply to]

On 07/03/2008 10:47 PM, Larry Roberts wrote:
> SUCCESS!
>
> For those following along at home I followed the directions found here:
>
> http://www.mythtv.org/docs/mythtv-HOWTO-23.html for moving your data to
> a new server.

Just a note to anyone else trying this, database backups and restores,
including 23.5 (full restore), 23.7 (new hardware restores), and 23.15
(change hostname) are supported by the backup restore scripts that (I
hope) will be part of 0.22. They work with any version of MythTV and
are available (for now--until they're in the MythTV source) at
http://misc.thirdcontact.com/MythTV/database_mythconverg_backup.pl and
http://misc.thirdcontact.com/MythTV/database_mythconverg_restorep.pl

> If I had been staying with the same version of the DB I
> believe I could have gotten away with just dropping the old db and
> restoring the old one, but given the schema changes this way made sense.
>

Since your approach seems to have worked, I'm sure you did it this way,
but to make things clearer for anyone else reading, the "new hardware
restore" (23.7) can only be used when the exported data comes from the
same version of MythTV that's used to create the database into which the
data is imported--i.e. if doing a new-hardware restore /and/ upgrading,
you must do the upgrade first, then backup the DB, then drop the DB,
create the DB (with mc.sql), then start mythtv-setup, then restore the
DB. The only other option is to do everything described except doing
the upgrade last (i.e. backup the DB, drop the DB, create the DB (with
mc.sql), then start mythtv-setup, then restore the DB, then upgrade the DB).

In other words, you should /not/ do a partial/new-hardware restore
across DB schema versions.

The scripts mentioned above will take care of checking to ensure you do
things properly. See the --help output for more info (than you probably
want ;).

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

mythtv at american-hero

Jul 4, 2008, 6:50 AM

Post #5 of 8 (418 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data [In reply to]

Michael T. Dean wrote:
> On 07/03/2008 10:47 PM, Larry Roberts wrote:
>> SUCCESS!
>>
>> For those following along at home I followed the directions found here:
>>
>> http://www.mythtv.org/docs/mythtv-HOWTO-23.html for moving your data to
>> a new server.
>
> Just a note to anyone else trying this, database backups and restores,
> including 23.5 (full restore), 23.7 (new hardware restores), and 23.15
> (change hostname) are supported by the backup restore scripts that (I
> hope) will be part of 0.22. They work with any version of MythTV and
> are available (for now--until they're in the MythTV source) at
> http://misc.thirdcontact.com/MythTV/database_mythconverg_backup.pl and
> http://misc.thirdcontact.com/MythTV/database_mythconverg_restorep.pl
>
>> If I had been staying with the same version of the DB I
>> believe I could have gotten away with just dropping the old db and
>> restoring the old one, but given the schema changes this way made sense.
>>
>
> Since your approach seems to have worked, I'm sure you did it this way,
> but to make things clearer for anyone else reading, the "new hardware
> restore" (23.7) can only be used when the exported data comes from the
> same version of MythTV that's used to create the database into which the
> data is imported--i.e. if doing a new-hardware restore /and/ upgrading,
> you must do the upgrade first, then backup the DB, then drop the DB,
> create the DB (with mc.sql), then start mythtv-setup, then restore the
> DB. The only other option is to do everything described except doing
> the upgrade last (i.e. backup the DB, drop the DB, create the DB (with
> mc.sql), then start mythtv-setup, then restore the DB, then upgrade the DB).
>
> In other words, you should /not/ do a partial/new-hardware restore
> across DB schema versions.
>
> The scripts mentioned above will take care of checking to ensure you do
> things properly. See the --help output for more info (than you probably
> want ;).
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

I wish that I could say that I did the upgrade as you described, but in
fact I just did an export of the .20 data, filtered for the specific
info I needed and then did a reimport of the new data. While all seemed
ok, what I'm finding now is that my upcoming recordings are all off by a
couple channels.
My source is the same as before so there is no difference in the
channels that I'm aware of...
If i go in and delete and redo the recording schedule would I loose all
the saved history of recorded programs? I dont see any way of changing
the channel in the upcoming recordings and I dont want to do a record on
any channel at any time as that will also catch all the episodes that
started prior to my recording them with myth (Think 3 or 4 seasons of
CSI that I have watched, but not via Myth...)

My thoughts are that I could go into the mysql database and adjust the
channel there, but I wanted to throw it out for group consensus before I
do anything.

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

drescherjm at gmail

Jul 4, 2008, 8:12 AM

Post #6 of 8 (421 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data [In reply to]

> I wish that I could say that I did the upgrade as you described, but in
> fact I just did an export of the .20 data, filtered for the specific
> info I needed and then did a reimport of the new data.

Hmm. I have never filtered the data on any upgrade or hardware change.
I just restore a mysql dump and all is well.

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

mythtv at american-hero

Jul 4, 2008, 8:16 AM

Post #7 of 8 (421 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data [In reply to]

John Drescher wrote:
>> I wish that I could say that I did the upgrade as you described, but in
>> fact I just did an export of the .20 data, filtered for the specific
>> info I needed and then did a reimport of the new data.
>
> Hmm. I have never filtered the data on any upgrade or hardware change.
> I just restore a mysql dump and all is well.
>
> John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

My "fix" if you will was to go in and set the program to record at any
time on any channel, then go into the upcoming recordings and pick one
on the channel I wanted and set it to "record at any time on this channel"

Everything else I tried created new recording schedules.

The wierd part was that every channel was off by 2, some 2 channels
high, some 2 channels low, but always off by 2 channels.

Wierd stuff.

Thanks for the help.
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Jul 4, 2008, 11:06 AM

Post #8 of 8 (410 views)
Permalink

Re: Migrating HW and from .20 to .21. Concerned about storage groups and import of data [In reply to]

On 07/04/2008 11:16 AM, Larry Roberts wrote:
> John Drescher wrote:
>
>>> I wish that I could say that I did the upgrade as you described, but in
>>> fact I just did an export of the .20 data, filtered for the specific
>>> info I needed and then did a reimport of the new data.
>>>
>> Hmm. I have never filtered the data on any upgrade or hardware change.
>> I just restore a mysql dump and all is well.
>>

That works, also. The only real benefit to the "new hardware"/partial
restore is that it serves as a "spring cleaning" of your DB. In other
words, it resets everything to defaults so you don't have to undo the
configuration you did for your previous hardware before configuring for
your new hardware.

> My "fix" if you will was to go in and set the program to record at any
> time on any channel, then go into the upcoming recordings and pick one
> on the channel I wanted and set it to "record at any time on this channel"
>

That works.

> Everything else I tried created new recording schedules.
>

That works, too. In other words, deleting the recording rule has no
effect on recording history or anything.

> The wierd part was that every channel was off by 2, some 2 channels
> high, some 2 channels low, but always off by 2 channels.

All the per-channel rules are configured via callsigns, not by channel
number. However, they're referenced in the recording rules by chanid,
which means that the channels you created have different channel ID's
from those used in your previous setup.

Or, put another way, the partial restore pretty much assumes that you're
using "any channel" rules.

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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com