[mythtv-users] Full or Partial Database restore?

Michael T. Dean mtdean at thirdcontact.com
Tue Sep 14 17:18:50 UTC 2010


  On 09/14/2010 09:04 AM, John Haywood wrote:
> After much instability going from Mythbuntu 9.10 to 10.04, even trying a database backup, clean install and restore the inevitable finally happened:
> 0.23.1 fixes, PPA repo
>
> I was experiencing several freezes and lockups, usually one or two per day.
>
> Finally the whole box just started up to a setup screen - and refused to update the schema from<blank>  to 1025 (i.e. no value to current)
> I ran the db optimise script to check, then the mysqlcheck, as per the wiki
> mysqlcheck found problems which it repaired
>
> I then thought I'd check the xfs filesystem on which the recordings are stored and found quite a few orphaned files, which it placed in Lost + Found
>
> I'm now faced with reinstalling the OS, and restoring the db from a backup. I'd like to keep my database of recordings, videos and schedules if possible, but if I have to lose the rest, I can live with setting the combined fe/be up again
>
> Should I try a full restore from a couple of days before the final crash first - or am I just prolonging the agony given the previous issues?
>
> Or should I just do a partial restore from the last backup

There's really no benefit to doing a partial restore if you have a good 
backup of a non-corrupt schema.  The partial restore can be useful if 
someone broke the schema.  Otherwise, it's just the same end result as a 
full restore, except you have to reconfigure /everything/ after the 
fact, and you lose some useful data.

http://www.mythtv.org/wiki/Database_Backup_and_Restore#Database_Restore

In all the cases where people claim that their systems run faster/better 
after a partial restore, it's either a) they had never used 
optimize_mythdb.pl in their lives or--far more likely--b) they did a 
complete operating system re-install, and /that/ made things run 
faster/better.

Mike


More information about the mythtv-users mailing list