No subject

ythtv/users/525478#525478" target=3D"_blank">http://www.gossamer-threads.<u=
></u>com/lists/mythtv/users/525478#<u></u>525478</a> ), the reason you don&=
#39;t have an automatically-created database backup is:<div class=3D"im">
<br>
<br>
2012-05-13 21:31:48.041371 C [342/342] CoreContext dbutil.cpp:217 (BackupDB=
) - Database backups disabled. Skipping backup.<br>
<br></div>
i.e. you explicitly disabled them with the mythtv-setup setting:<br></block=
quote><div>=A0</div><div>Yes.=A0 I belatedly realized that when I got thing=
s running. One of my reasons for doing so might suggest something that coul=
d be clarified: I may have thought the backup would backup all my video fil=
es, not just the mysql database.=A0 I realize that&#39;s not so.<br>
<br>More at the bottom.<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Disable automatic database backup<br>
If enabled, MythTV will not backup the database before upgrades. You should=
 therefore have your own database backup strategy in place.<br>
<br>
IMHO, you should really consider re-enabling the automatic, for-your-own-pr=
otection database backups so even if you don&#39;t manually create a backup=
, you have options when things go wrong.<br></blockquote><div>Yes, <br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<br>
I&#39;ll try to get a chance, soon, to look into the DB upgrade process for=
 users without MythVideo schema, but last I tested, it worked fine. =A0I&#3=
9;m thinking if there was a problem, it was external to MythTV (i.e. someth=
ing killed and restarted mythbackend during the upgrade because it wasn&#39=
;t responding or whatever...), but I will run a test, again, of a 0.24-0.25=
 upgrade of a DB schema without MythVideo schema.<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
Mike<br></div></div></blockquote><div><br>Thanks for your help.=A0 I&#39;m =
not sure any checking is warranted; the only explanation I can see of how t=
hings got this way required two odd things: first, the file system filled i=
n the middle of an install, leaving the mythvideo tables in a very old stat=
e (since the code creates the tables by making a very old version and then =
upgrading it).=A0 Second, after I made space I did not reinstall the mythvi=
deo package (partly to save space), and so it never had a chance to complet=
e updating the tables.<br>
<br>If anyone has ideas about the segfault, or information on mysql 5.5 com=
patibility,=A0 that would be great.<br><br>Ross<br></div></div>

--20cf307f39aae2643404c766c4b3--