Hello,
I'm running Bacula 5.2.6 on Debian linux.
A dry run of dbcheck has revealed the following.
dbcheck -v -c /etc/bacula/bacula-dir.conf
Hello, this is the database check/correct program.
Modify database is off. Verbose is on.
Please select the function you want to perform.
1) Toggle modify database flag
2) Toggle verbose flag
3) Check for bad Filename records
4) Check for bad Path records
5) Check for duplicate Filename records
6) Check for duplicate Path records
7) Check for orphaned Jobmedia records
8) Check for orphaned File records
9) Check for orphaned Path records
10) Check for orphaned Filename records
11) Check for orphaned FileSet records
12) Check for orphaned Client records
13) Check for orphaned Job records
14) Check for all Admin records
15) Check for all Restore records
16) All (3-15)
17) Quit
Select function number: 16
Checking for Filenames with a trailing slash
Found 0 bad Filename records.
Checking for Paths without a trailing slash
Found 0 bad Path records.
Checking for duplicate Filename entries.
Found 0 duplicate Filename records.
Checking for duplicate Path entries.
Found 0 duplicate Path records.
Checking for orphaned JobMedia entries.
Checking for orphaned File entries. This may take some time!
Note. Index over the PathId column not found, that can greatly slow down
dbcheck.
Create temporary index? (yes/no): yes
Create temporary index... This may take some time!
CREATE INDEX idxPIchk ON File (PathId)
Temporary index created.
Checking for orphaned Path entries. This may take some time!
Found 300000 orphaned Path records.
Print them? (yes/no): no
Drop temporary index.
DROP INDEX idxPIchk ON File
Temporary index idxPIchk deleted.
Note. Index over the FilenameId column not found, that can greatly slow down
dbcheck.
Create temporary index? (yes/no): yes
Create temporary index... This may take some time!
CREATE INDEX idxFIchk ON File (FilenameId)
Temporary index created.
Checking for orphaned Filename entries. This may take some time!
Found 300000 orphaned Filename records.
Print them? (yes/no): no
Drop temporary index.
DROP INDEX idxFIchk ON File
Temporary index idxFIchk deleted.
Checking for orphaned FileSet entries. This takes some time!
Found 12 orphaned FileSet records.
Print them? (yes/no): no
Checking for orphaned Client entries.
Found 0 orphaned Client records.
Checking for orphaned Job entries.
Found 31 orphaned Job records.
Print them? (yes/no): no
Checking for Admin Job entries.
Found 0 Admin Job records.
Checking for Restore Job entries.
Found 23 Restore Job records.
Print them? (yes/no): no
A yearly job is scheduled to run "dbcheck -c /etc/bacula/bacula-dir.conf -f -b"
every December.
This lead to a db corruption in December 2015.
"Mysqladmin processlist" revealed one INSERT job with a state "Waiting for table level
lock" followed by SELECT stuck with "executing".
A series of check and repair table command made Bacula run again but the
problem with excessive number of records remained.
In 2016 the service didn't stop working but an email report returned:
Checking for orphaned Path entries. This may take some time!
Query failed: SELECT DISTINCT Path.PathId,File.PathId FROM Path LEFT
OUTER JOIN File ON (Path.PathId=File.PathId) WHERE File.PathId IS
NULL LIMIT 300000: ERR=Server shutdown in progress
So I'm bracing myself for 2017.
I'm planning to take a full db dump beforehand and run dbcheck manually under
supervision which I'm expecting to fail again :(
Any advise on how to resolve the 300k record issue?
Is it a good idea to increase this limit in the database?
Or maybe a different (and fairly safe) SQL command that can fix it before
dbcheck is executed?
Thanks
Adam
------------------------------------------------------------------------------
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
