The Bacula dbcheck is basically a program that looks for consistent irregularities in your data set's Bacula tables and alternatively corrects them. It's a data set support routine, as it can recognize and eliminate unused lines, nonetheless it's not a catalogue restoration schedule.
After numerous long stretches of utilization or customizations on Bacula, it is likely that your inventory has orphaned entries: data that stays in the data set but doesn't have linking indexes to prevailing reserved backups.
Something very similar may end up re-establish occupations data that might be not, at this point, required in the event that you could approve the restored contents. This conduct can leave the more intricate administration of Bacula and welcome some effect on the list execution.
Luckily, the Bacula dbcheck appl is introduced with the Bacula Director and can be utilized to clean those sections. The fundamental necessity for this order is to inform the Bacula working catalogue, set in the bacula-dir.conf.
It won't fix your info base if it is broken. To fix a data set, see the devices outfitted by the info base merchant. Generally, the Bacula dbcheck should never need to be launched. Still, If Bacula has crashed, it could be useful.
Bacula Dbcheck Logical Inconsistencies
Spare Filename Records
This can occur if you inadvertently run two duplicates of Bacula dbcheck simultaneously, and they are mutually totalling file titles at the same time. It is an uncommon event. However, it will make a conflicting data set.
If so, you will get error texts during Jobs notice of copy information base records. There’s no motivation to launch this scan on the off chance that you are not getting these blunder messages.
Orphaned Document Records
This ensures when a Work record is erased (maybe by a client allotted SQL), yet the comparing document record (a single for every Volume utilized in the Job) was not erased.
Note, looking for these accounts can be really tedious (for instance, it might require hours) for a vast data set. Typically, this ought not to occur as Bacula takes care to forestall it. Nonetheless, this scan can eliminate any stranded document records.
It is suggested that you launch this once per year since stranded document records can take a lot of room in your data set. You should guarantee that you have records on FilenameId, JobId, and PathId for the Folder chart in your list prior to running this order.
Orphaned JobMedia Records
This ensues when a Work record is erased (maybe by a client-issued SQL); however, the JobMedia account (a single for every Volume utilized in the Job) was not erased.
Regularly, this ought not to occur, and regardless of whether it does, these accounts, by and large, don't take a lot of room in your information base. Be that as it may, by running this check, you can take out any such vagrants.
Orphaned Path Accounts
This occurs when a registry is erased from your framework, and all related Work accounts have stood cleansed. During standard cleansing (or trimming) of Job accounts, Bacula dbcheck doesn't check for stranded Path accounts.
As a result, throughout some undefined time frame, old fallow Path accounts will, in general, amass and utilize storage in the information base. This scan will dispose of them. It’s suggested that you launch this scan-in any event once every year.
Orphaned File Records
This happens when a Job record is erased (maybe by a client who gave SQL explanation), yet the comparing File record (one for every Volume utilized in the Trade) remains unerased.
Note, looking for these records can be very tedious (for example, it might require some time) for a vast data set. Ordinarily, this ought not to occur as Bacula dbcheck makes sure it doesn’t forestall it. Nevertheless, this check can eliminate any stranded File accounts.
It's suggested you launch once every year since stranded File accounts can occupy a lot of room in your information base. You should guarantee that you hold records on JobId, PathId and FilenameId for the File table in your index before running this order.
Orphaned Work Records
In the event that no customer is characterized at a trade or you don't run work for quite a while, you can gather old occupation records. This alternative permits you to eliminate occupations not linked to any customer.
Final Thought
All in all, you should only run the Bacula dbcheck for the inconsistencies illustrated above if you have interfered with the data set with bugs developing in the code. These inconsistencies are here so that you don't need to keep running dbchecks regularly.
