Re: [Bacula-users] Catalog "Filename" empty
Kern - thanks. Perhaps foolishly I didn't try any "one file test" jobs; my comfort level with installing bacula on this distro with these tape drives has become second-nature to the point that I didn't feel the need (so I got bit), and of course with the weekend, trying to get it running to have time to attend to other chores. To be honest, I don't recall ever having looked at the catalog tables until after jobs. Cheers, Ted. On 11/12/2017 12:44 PM, Kern Sibbald wrote: Hello Ted, This is probably perfectly normal if you have not yet finished any jobs. By default the Filename entries are put in the catalog at the end of each Job. The one entry you did find is a "blank" filename which is used when putting Directory entries into the catalog (i.e. for a Directory the Filename is empty). If your job finishes normally the Filename table should be filled with the names of files that were backed up. Best regards, Kern On 11/12/2017 05:53 PM, Ted Hyde wrote: Greets - I have a new installation of Bacula on Debian Jessie (5.2.6+dfsg-9.3) with a postgres backend. This is not my first bacula installation (I have 5 other separate instances running on different tape units, some single TL2000, some library changers - all happy) -- except for this new one (maybe). I never noticed exactly when bacula writes data to the file and filename tables - I figured it did it on the fly. -- 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 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- 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
Re: [Bacula-users] Feature Request - job complete status of with warnings on zero files zero bytes
Hi everyone, Personally I think this is something that should be kept out the core code of Bacula, but the topic interested me so last night I emailed Jim directly (off list) and then wrote a script. I have the script mostly completed which I will release shortly. I am just working out the final logic test details. :) The idea: - Call this script from a RunScript (RunsWhen = after) "Command =" - Pass the script the current jobid (%i) and a few other variables: - allow_zero_files - allow_zero_bytes - zero_incremental_ok So, my idea is that each backup job can call this script, the script calls bconsole and runs a "list joblog jobid=" then determines the FD (Files|Bytes) written, determines if the level is Full or Inc of Diff and then send a warning email if the files and/or bytes are zero and if they should not have been (for example, when the Level=full), or if the Level=inc|diff and zero files for these levels are not to be considered OK (zero_incremental_ok not set). I am of course accepting comments and idea/feature requests etc. Hope this will be useful, and hope to release it in the coming day(s). Best regards, Bill -- Bill Arlofski http://www.revpol.com/bacula -- Not responsible for anything below this line -- -- 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
Re: [Bacula-users] Catalog "Filename" empty
Hello Ted, This is probably perfectly normal if you have not yet finished any jobs. By default the Filename entries are put in the catalog at the end of each Job. The one entry you did find is a "blank" filename which is used when putting Directory entries into the catalog (i.e. for a Directory the Filename is empty). If your job finishes normally the Filename table should be filled with the names of files that were backed up. Best regards, Kern On 11/12/2017 05:53 PM, Ted Hyde wrote: Greets - I have a new installation of Bacula on Debian Jessie (5.2.6+dfsg-9.3) with a postgres backend. This is not my first bacula installation (I have 5 other separate instances running on different tape units, some single TL2000, some library changers - all happy) -- except for this new one (maybe). I never noticed exactly when bacula writes data to the file and filename tables - I figured it did it on the fly. In this current instance, I am running a 4TB+ job on a single TL2000 SAS drive, and I'm currently on tape 2 of probably 5 or 6 (depending on compression). However, there are only 7 entries in the "file" table: 1;1;5;4;1;0;0;"GgB ZgAI EHt C A A A BAA BAA I BaB4NI BaB4NI BaB4NI A A C";"0" 2;2;5;7;1;0;0;"gC B EHt B A A A BAAA BAA IA A A A A A C";"0" 3;3;5;3;1;0;0;"gy B EHt B A A A BAAA BAA IA A A A A A C";"0" 4;4;5;6;1;0;0;"gR B EHt B A A A BAAA BAA IA A A A A A C";"0" 5;5;5;5;1;0;0;"gi B EHt B A A A BAAA BAA IA A A A A A C";"0" 6;6;5;2;1;0;0;"GgB ZgAH EHt C A A A BAA BAA I BaB4NE BaB4NE BaB4NE A A C";"0" 7;7;5;1;1;0;0;"GgB ZgAC EHt I A A A BAA BAA I BaB4eL BaB4NI BaB4NI A A C";"0" and only one entry in the "filename" table: 1;"''" Which I find rather odd. I compared against my other sites, and they have plenty of entries, all as expected (filenames, hashes, etc). I am using a simplified job referencing against a pool of pre-labeled tapes in "Default", the catalog "MyCatalog", 5 specific folders in Full backup mode, and it was started manually in bconsole. The database on the whole is functioning as there are plenty of log entries, it updates the media and status tables (my favorite), but no data of value in file and filename. Tests listed in the FAQ show the database and sequences (indexes for the mysql-peeps) are in ok shape and all exist. The dbase log and verbose log don't show any dbase errors or errors related to "MyCatalog". There are no other tables or dbases visible that seem to show temporary storage info. Is this normal behavior, or is my large backup slated to be an orphan? If I need to make a fix, I'd prefer to fix it before running another large backup, or into the scheduled daily backups (I'd rather not have to bextract every job afterwards). I have another day-ish of this job running (hey, its 4TB of usb-attached storage going into the vault, no speed records to be broken), so any thoughts would be appreciated. Regards, Ted. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- 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 -- 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
[Bacula-users] Catalog "Filename" empty
Greets - I have a new installation of Bacula on Debian Jessie (5.2.6+dfsg-9.3) with a postgres backend. This is not my first bacula installation (I have 5 other separate instances running on different tape units, some single TL2000, some library changers - all happy) -- except for this new one (maybe). I never noticed exactly when bacula writes data to the file and filename tables - I figured it did it on the fly. In this current instance, I am running a 4TB+ job on a single TL2000 SAS drive, and I'm currently on tape 2 of probably 5 or 6 (depending on compression). However, there are only 7 entries in the "file" table: 1;1;5;4;1;0;0;"GgB ZgAI EHt C A A A BAA BAA I BaB4NI BaB4NI BaB4NI A A C";"0" 2;2;5;7;1;0;0;"gC B EHt B A A A BAAA BAA IA A A A A A C";"0" 3;3;5;3;1;0;0;"gy B EHt B A A A BAAA BAA IA A A A A A C";"0" 4;4;5;6;1;0;0;"gR B EHt B A A A BAAA BAA IA A A A A A C";"0" 5;5;5;5;1;0;0;"gi B EHt B A A A BAAA BAA IA A A A A A C";"0" 6;6;5;2;1;0;0;"GgB ZgAH EHt C A A A BAA BAA I BaB4NE BaB4NE BaB4NE A A C";"0" 7;7;5;1;1;0;0;"GgB ZgAC EHt I A A A BAA BAA I BaB4eL BaB4NI BaB4NI A A C";"0" and only one entry in the "filename" table: 1;"''" Which I find rather odd. I compared against my other sites, and they have plenty of entries, all as expected (filenames, hashes, etc). I am using a simplified job referencing against a pool of pre-labeled tapes in "Default", the catalog "MyCatalog", 5 specific folders in Full backup mode, and it was started manually in bconsole. The database on the whole is functioning as there are plenty of log entries, it updates the media and status tables (my favorite), but no data of value in file and filename. Tests listed in the FAQ show the database and sequences (indexes for the mysql-peeps) are in ok shape and all exist. The dbase log and verbose log don't show any dbase errors or errors related to "MyCatalog". There are no other tables or dbases visible that seem to show temporary storage info. Is this normal behavior, or is my large backup slated to be an orphan? If I need to make a fix, I'd prefer to fix it before running another large backup, or into the scheduled daily backups (I'd rather not have to bextract every job afterwards). I have another day-ish of this job running (hey, its 4TB of usb-attached storage going into the vault, no speed records to be broken), so any thoughts would be appreciated. Regards, Ted. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- 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
Re: [Bacula-users] Feature Request - job complete status of with warnings on zero files zero bytes
On Saturday 2017-11-11 12:21:22 Phil Stracchino wrote: > If implemented at all it should be implemented as an option, because > there are many kinds of possible admin jobs (and even incremental > backups) for which it is *perfectly normal* to complete with 0 files/0 > bytes backed up. If implemented it would have to be implemented only for the jobs of the type that could have number of files bigger than 0, like backup and copy job for example. Or it could be implemented for all the job types and leave the user to decide whether to use it or not but I don't see the point to fail the job because of the zero-files if the particular type of job is always going to have zero files. I believe that sometimes this feature could be useful if people are sure that there has to be non-zero files on particular backup jobs they have defined. If they start to get false positives it's on them. :-) Then again sometimes false positive is better than undetected incident. Of course. the check could be done outside the bacula directly on the database but then again we could say the same for many features already implemented into bacula. -- Josip Deanovic -- 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
