[mythtv-users] Channel Line-up Export

Panachoi panachoi at gmail.com
Tue Feb 24 06:13:30 UTC 2009


>
> Message: 16
> Date: Mon, 23 Feb 2009 21:18:39 -0500
> From: "Michael T. Dean" <mtdean at thirdcontact.com>
> Subject: Re: [mythtv-users] Channel Line-up Export
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <49A358FF.6040505 at thirdcontact.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 02/23/2009 09:11 PM, MrVining wrote:
> > On Feb 23, 2009, at 7:49 PM, Nick Rout wrote:
> >> On Tue, Feb 24, 2009 at 10:15 AM, MrVining wrote:
> >>> I'm building a new MythTV master backend as we speak.  I've done some
> >>> googling and searched the wiki a bit, but I not really finding
> >>> much.  Is
> >>> there a somewhat simple way to export/backup my channel line-up?
> >> just the channel line up or the whole database?
> >>
> >> http://www.mythtv.org/wiki/Database_Backup_and_Restore
> > Just the Line-up.  Partly because I want to do a sort of perm. backup
> > of some of my setup.
>
> There's a section on that wiki page that talks about backing up
> xmltvid's.  I'm planning to rewrite the backup/restore support to make
> it easier (will be a normal full backup instead of a special backup).
> The restore will then take a look at the old channels and try to match
> them up with the new channels and try to modify the settings of the new
> channels to match what you had previously (i.e. things like xmltvid,
> useeit, visible, ...).
>
> However, I doubt there will /ever/ be a (safe/reliable) way to just
> backup up and then restore the channels (and all associated channel
> info) themselves.  Instead, you'd have to do a backup, fetch channels
> from listings provider or scan for channels, then "restore" channel
> settings on top of the new channels.
>
> The best backup--for now or after I finish the channel restore
> rewrite--is a full backup.
>


Is there something special about the xmltvids ? I'm only using them for my
analog source, as everything else has EIT (DVB-S/S2 and DVBC). I have
actually setup test backends by dumping my channel information and then
importing it into the new backend, as I've had lots of problems with the
scanner in the past (crashing, inserting bogus multiplexes, associating
services with wrong multiplex ids), so it was quicker for me to create a
fresh database, and then just reload my channel information, and then from
within setup add the cards/inputs  and associate the already defined
sources/channels with them.

Here's my simple script which I run from cron on a weekly basis (I also dump
the recordings information, but you may not want that, so I've left that
out), that I've used to move the channel information to the new backend.

---------------------
#!/bin/sh
#

BACKUPDIR=/recordings/backup
DBHOST=d925
DBUSER=mythtv
DBPASS=mythtv
DBNAME=mythconverg_s2


mysqldump --no-create-db --add-drop-table -h $DBHOST -u $DBUSER -p$DBPASS
$DBNAME dtv_multiplex channel | gzip -9 -c >
$BACKUPDIR/channelmultiplex-`date +%Y%m%d%H%M`.gz
----------------------

I also run a script which deletes all of the backups older than 1 month,
since I'm not likely to be interested in anything bu the latest backups.

Unfortunately, in the DVB world, transponders are constantly changing with
new serviceids, so theres not really a way around rescanning every once in
awhile.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090224/b651156b/attachment.htm>


More information about the mythtv-users mailing list