[mythtv-users] Mythbuntu - database not backing up

[Michael T. Dean]

On 02/10/2009 01:58 PM, Nick Rout wrote:
> Had a database go wrong yesterday, luckily the optimize script fixed it (phew).
>
> But it brought to my attention that database backups don't seem to be
> working. I have a series of files in /var/backups,
>
> nick at media:/var/backups$ ls -l /var/backups/mythconverg.sql.gz*
> -rw-r--r-- 1 root root 331 2009-02-08 06:47 /var/backups/mythconverg.sql.gz
> -rw-r--r-- 1 root root 329 2009-02-01 06:47 /var/backups/mythconverg.sql.gz.0
> -rw-r--r-- 1 root root 329 2009-01-25 06:47 /var/backups/mythconverg.sql.gz.1
> -rw-r--r-- 1 root root 329 2009-01-18 06:47 /var/backups/mythconverg.sql.gz.2
> -rw-r--r-- 1 root root 329 2009-01-11 06:47 /var/backups/mythconverg.sql.gz.3
> -rw-r--r-- 1 root root 329 2009-01-04 06:47 /var/backups/mythconverg.sql.gz.4
> -rw-r--r-- 1 root root 329 2008-12-28 06:48 /var/backups/mythconverg.sql.gz.5
> -rw-r--r-- 1 root root 329 2008-12-21 06:47 /var/backups/mythconverg.sql.gz.6
>
>
> all of which (when unzipped) say:
>
> -- MySQL dump 10.11
> --
> -- Host: localhost    Database: mythconverg
> -- ------------------------------------------------------
> -- Server version       5.0.51a-3ubuntu5.4
>
> /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
> /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
> /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
> /*!40101 SET NAMES utf8 */;
> /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
> /*!40103 SET TIME_ZONE='+00:00' */;
> /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
> /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0
> */;
> /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
> /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
>
>
> and thats it.
>
> What am i missing?

My recommendation is to disable the distro-provided*** backup script and 
use http://www.mythtv.org/wiki/Database_Backup_and_Restore .

Mike

***My guess is it's Gentoo because--assuming the above is from a 
0.21-fixes DB backup attempt--your DB config is broken in the way many 
Gentoo users' DB's are, but you (or Gentoo) will fix it before 0.22, so 
don't worry about it, now.  (If that's from a trunk DB backup attempt, 
it's not broken.)