[mythtv-users] Myth not autoexpiring since upgrade to 0.22RC1

[Michael T. Dean]

On 10/28/2009 02:03 AM, Nick Rout wrote:
> On Mon, Oct 26, 2009 at 9:25 PM, Duncan Brown wrote:
>   
>> Thought the upgrade to 0.22 had gone fairly smoothly until last night when
>> my recordings disk completely filled up. It is a upgrade from 0.21-fixes,
>> done using the backup script upgrade method in the wiki (i.e clean database
>> then --partial restore from backup)
>>     
> can you please refer me to that wiki page? I haven't been able to find
> the one you are looking for. (Doesn't help that *.mythtv.org has been
> down part of today)

By the way, a partial restore isn't really recommended.  There's no real 
advantage to doing a partial restore.

When upgrading, just do a full backup, then upgrade MythTV and let the 
new version of MythTV upgrade the complete database.  If you move the 
MySQL server to a new host, do a full restore of the full backup on the 
new MySQL server, then let MythTV upgrade the complete database.

The only catch is that you should use the same hostname for your all 
your MythTV frontend and backend hosts or use the restore script to 
change the hostname /before/ running any mythtv apps on the host with 
the new name.  ( 
http://www.mythtv.org/wiki/Database_Backup_and_Restore#Change_the_hostname_of_a_MythTV_frontend_or_backend 
)

The backup and restore page is at 
http://www.mythtv.org/wiki/Database_Backup_and_Restore .

Mike