On 05/05/18 12:00, Ken Mandelberg wrote: > Well the backup I was counting on doesn't exist. I Duplicated the Ubuntu > 16.04 filesystem in another slice before doing the OS upgrade, assuming > I would have a copy of everything pre-update. It was a big surprise to > find that the update updated both the live slice and the backup slice > to 18.04. > > Furthermore looking at the mysql bacula database post install, it looks > corrupted. See below.
...Yeah, that looks like a mess. You did *stop* mysql before cloning the filesystem, right? it is NOT safe to hot-copy MySQL database files. > I didn't do anything that isn't default for a mysql or a bacula saved > copy of the mysql bacula database. Presumably I can extract one from the > volumes (which are actually files not tapes). I could use some advise on > how to do that. > > I had planned just to fix up the database I had by manually doing what > the update script does, but when I ran into what must be corruption > shown below, it seems like I should start over from a backup. I would definitely restore the Bacula database from a recent DB dump (you *do* run regular DB dumps, right...?) and rerun the upgrade script. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
