My back up fails on verify everytime. Where can I look to see what is the problem?

rkshack


Correction: I answered this question. I used checkbackup from root. When I did I got the following error. Any suggestions?

Checking for the existance of the DB dump file...
Using file /myth/backup/mythconverg.sql.gz
DB dump file exists. Checking the compression...
Compression looks OK. Checking DB dump contents...
Generating a list of tables and record counts in the DB dump...
Generating a list of tables and record counts in the live DB...
Comparing live versus saved tables...
23c23
< jobqueue 18
---
> jobqueue 17
58c58
< recorded 200
---
> recorded 199
63c63
< recordedseek 1140342
---
> recordedseek 1140076
Warning, table lists are not identical!


rkshack

_________________
5.5
6150k8ma-8ekrs
Athlon64 3200+
1gb ram
250gb hda
750gb sda
nvidia 6200
central time

It looks like another recording occurred between the end of the backup and the check.

- Do you have an auto-restart script running to restart the backend if it "dies"? You must disable that somehow for the duration of the backup.

- Do you have a slave BE running against the same DB? You must also stop that for the duration of the backup.

- Are you doing something like continuously watching live TV? You must stop that for the duration of the backup.

Please try disabling the things mentioned above and rerunning the backup from a root shell session. That will let you tee the output into a log file.

Basically you need to to ensure that the system is idle before running the backup. Auto restarting the backend is bad. Having a remote system accessing the DB is bad. ... The backup script does what it can by shutting down the local backend for the duration, but unfortunately it's nearly impossible to anticipate and prevent all the ways you could violate the "idle system" requirement. I'll write myself a note to see about disabling remote DB access while the backup is running. Disabling all networking would probably be easier, but it would also prevent running backups from an ssh session.

I did not change anything but when I did your command the backup worked fine. Since then I have been able to do several backups without problem. Did the command you told me to do, do anything except port the output from the backup command to a file?

Rkshack

_________________
5.5
6150k8ma-8ekrs
Athlon64 3200+
1gb ram
250gb hda
750gb sda
nvidia 6200
central time

It just captures the output. This bit: /usr/local/bin/mythbackup is the backup script proper. This bit: 2>&1 sends stderr to the same place as stdout. This bit | tee /var/log/mythtv/mythbackup.log pipes stdout (and stderr too) into the "tee" program which records a duplicate of the output to the named file and passes it along to stdout so that you can see it.

We could have also used:

but then you wouldn't have been able to watch the progress.