[Bacula-users] Renamed and moved files are backed up again
Hello, is it normal to back up bacula moved files or renamed files over and over again? I have created a test configuration with base jobs but the files are backed up again and again. Does anyone have a solution to the problem or a working configuration file? To the procedure: 1. I'm starting a backup as a base job OK 2. a full backup using a base job OK 3. rename or move a file 4. Full Backup with Base Job The renamed or moved file is saved with every job again and again Part of the logfile: 30-Aug 14:13 debian-dir JobId 137: Start Backup JobId 137, Job=BaseData.2017-08-30_14.13.33_03 30-Aug 14:13 debian-dir JobId 137: Using Device "usb-vchanger-1-drive-0" 30-Aug 14:13 debian-sd JobId 137: Volume "vchanger-1_3_0" previously written, moving to end of data. 30-Aug 14:13 debian-sd JobId 137: Ready to append to end of Volume "vchanger-1_3_0" size=6983211129 30-Aug 14:13 debian-sd JobId 137: Job write elapsed time = 00:00:10, Transfer rate = 76.43 M Bytes/second 30-Aug 14:13 debian-sd JobId 137: Sending spooled attrs to the Director. Despooling 9,331 bytes ... 30-Aug 14:13 debian-dir JobId 137: Bacula debian-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu debian jessie/sid JobId: 137 Job: BaseData.2017-08-30_14.13.33_03 Backup Level: Base Client: "debian-fd" 5.2.6 (21Feb12) x86_64-pc-linux-gnu,debian,jessie/sid FileSet: "BaseFS" 2017-08-22 15:14:24 Pool: "File" (From Job resource) Catalog: "MyCatalog" (From Client resource) Storage: "vchanger-1" (From Job resource) Scheduled time: 30-Aug-2017 14:13:31 Start time: 30-Aug-2017 14:13:35 End time: 30-Aug-2017 14:13:45 Elapsed time: 10 secs Priority: 10 FD Files Written: 36 SD Files Written: 36 FD Bytes Written: 764,366,752 (764.3 MB) SD Bytes Written: 764,370,589 (764.3 MB) Rate: 76436.7 KB/s Software Compression: None VSS: no Encryption: no Accurate: no Volume name(s): vchanger-1_3_0 Volume Session Id: 57 Volume Session Time: 1503407574 Last Volume Bytes: 7,748,149,958 (7.748 GB) Non-fatal FD errors: 0 SD Errors: 0 FD termination status: OK SD termination status: OK Termination: Backup OK 30-Aug 14:13 debian-dir JobId 137: Begin pruning Jobs older than 6 months . 30-Aug 14:13 debian-dir JobId 137: No Jobs found to prune. 30-Aug 14:13 debian-dir JobId 137: Begin pruning Files. 30-Aug 14:13 debian-dir JobId 137: No Files found to prune. 30-Aug 14:13 debian-dir JobId 137: End auto prune. 30-Aug 14:15 debian-dir JobId 138: Start Backup JobId 138, Job=BackupClient1.2017-08-30_14.15.06_04 30-Aug 14:15 debian-dir JobId 138: Using Device "usb-vchanger-1-drive-0" 30-Aug 14:15 debian-dir JobId 138: Using BaseJobId(s): 122,137 30-Aug 14:15 debian-dir JobId 138: Sending Accurate information. 30-Aug 14:15 debian-sd JobId 138: Volume "vchanger-1_3_0" previously written, moving to end of data. 30-Aug 14:15 debian-sd JobId 138: Ready to append to end of Volume "vchanger-1_3_0" size=7748149958 30-Aug 14:15 debian-fd JobId 138: Space saved with Base jobs: 728 MB 30-Aug 14:15 debian-sd JobId 138: Job write elapsed time = 00:00:01, Transfer rate = 3.377 K Bytes/second 30-Aug 14:15 debian-sd JobId 138: Sending spooled attrs to the Director. Despooling 6,509 bytes ... 30-Aug 14:15 debian-dir JobId 138: Bacula debian-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu debian jessie/sid JobId: 138 Job: BackupClient1.2017-08-30_14.15.06_04 Backup Level: Full Client: "debian-fd" 5.2.6 (21Feb12) x86_64-pc-linux-gnu,debian,jessie/sid FileSet: "FullFS" 2017-08-30 09:23:05 Pool: "File" (From Job resource) Catalog: "MyCatalog" (From Client resource) Storage: "vchanger-1" (From Job resource) Scheduled time: 30-Aug-2017 14:15:05 Start time: 30-Aug-2017 14:15:09 End time: 30-Aug-2017 14:15:10 Elapsed time: 1 sec Priority: 10 FD Files Written: 36 SD Files Written: 36 FD Bytes Written: 0 (0 B) SD Bytes Written: 3,377 (3.377 KB) Rate: 0.0 KB/s Software Compression: 100.0 % Base files/Used files: 71/36 (50.70%) VSS: no Encryption: no Accurate: yes Volume name(s): vchanger-1_3_0 Volume Session Id: 58 Volume Session Time: 1503407574 Last Volume Bytes: 7,748,154,163 (7.748 GB) Non-fatal FD errors: 0 SD Errors: 0 FD termination status: OK SD termination status: OK Termination: Backup OK 30
Re: [Bacula-users] Deduplication Optimized Volumes. Lookup of symbol "BaculaSDdriver" undefined
Hello, You cannot fix it. The aligned plugin driver is not yet distributed with Bacula and without the driver, you cannot use it. You must use "File" rather than "Aligned". Due to vacations (mine is coming up) the Bacula binary project for distribution of binaries including the Aligned plugin will probably be delayed another month. Best regards, Kern On 08/31/2017 01:26 AM, Pedro Luis Balcázar wrote: Hello everyone. I am with version 9.0.3 and following the document "DeduplicationOptimized Volumes" I have encountered the error, see debug: localhost.localdomain-sd: stored.c:609-0 calling init_dev Aligned-Disk localhost.localdomain-sd: init_dev.c:116-0 init_dev dev_type=9 localhost.localdomain-sd: init_dev.c:152-0 Num drivers=15 localhost.localdomain-sd: init_dev.c:165-0 loadable=1 type=9 loaded=0 name=aligned handle=0 localhost.localdomain-sd: init_dev.c:430-0 loadable=1 type=9 loaded=0 name=aligned handle=0 localhost.localdomain-sd: init_dev.c:435-0 Open SD driver at /opt/bacula/plugins/bacula-sd-aligned-driver-9.0.3.so localhost.localdomain-sd: init_dev.c:438-0 Driver=aligned handle=7f62cc005120 localhost.localdomain-sd: init_dev.c:440-0 Lookup "BaculaSDdriver" in driver=aligned localhost.localdomain-sd: init_dev.c:442-0 Driver=aligned entry point=0 localhost.localdomain-sd: init_dev.c:448-0 Lookup of symbol "BaculaSDdriver" driver=/opt/bacula/plugins/bacula-sd-aligned-driver-9.0.3.so failed: ERR=/opt/bacula/plugins/bacula-sd-aligned-driver-9.0.3.so: undefined symbol: BaculaSDdriver localhost.localdomain-sd: stored.c:611-0 SD init done Aligned-Disk localhost.localdomain-sd: stored.c:613-0 Could not initialize SD device "Aligned-Disk" Does anyone know what I can do to fix this error? -- 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
Re: [Bacula-users] [Non-DoD Source] Re: database upgrade problem
Sorry, I see that Phil has answered this in detail. On 09/03/2017 09:03 AM, Kern Sibbald wrote: For both of you with this issue: it is not possible to respond correctly if you do not provide the following information: 1. What database server are you using (MySQL, MariaDB, PostgreSQL)? 2. What version of that database server are you using? 3. Have you modified any of the default parameters of the database server, such as requiring strict SQL default specifications. Note, if you look through the archives of several months ago concerning MySQL in particular you will see that some users have modified the basic install parameters of the server and run into trouble. Best regards, Kern On 09/01/2017 11:04 PM, Hicks, Daniel CTR OSD DMEA wrote: Davide, I am having this same issue. Can you clarify how to make sure the catalog upgrade is done. I did the update to tables without error but am not sure it is the same. Thank you Dan Hicks | 916-999-2711 From: Davide Franco [mailto:bacula-...@dflc.ch] Sent: Friday, September 1, 2017 12:11 PM To: Jerry Lowry ; bacula-users@lists.sourceforge.net Subject: [Non-DoD Source] Re: [Bacula-users] database upgrade problem Hi Jerry, Make sure the catalog upgrade has been done without issue. This seems to be related to Mariadb. Good luck Davide On Fri, 1 Sep 2017 at 17:38, Jerry Lowrywrote: Hi, I finally got my backup server upgraded to 9..0.3. I have run the database update and it succeeded with out any errors. But I get this error any time I start a job: 01-Sep 00:20 kilchis-dir JobId 0: Fatal error: sql_create.c:84 Create DB Job record INSERT INTO Job (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate,ClientId,Comment) VALUES ('BackupCatalog.2017-09-01_00.20.18_03','BackupCatalog','B','F','C','2017-09-01 00:20:16',1504250416,15,'') failed. ERR=Field 'StartTime' doesn't have a default value Does this mean the update did not work? thanks for the help! jerry -- 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 -- 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] [Non-DoD Source] Re: database upgrade problem
For both of you with this issue: it is not possible to respond correctly if you do not provide the following information: 1. What database server are you using (MySQL, MariaDB, PostgreSQL)? 2. What version of that database server are you using? 3. Have you modified any of the default parameters of the database server, such as requiring strict SQL default specifications. Note, if you look through the archives of several months ago concerning MySQL in particular you will see that some users have modified the basic install parameters of the server and run into trouble. Best regards, Kern On 09/01/2017 11:04 PM, Hicks, Daniel CTR OSD DMEA wrote: Davide, I am having this same issue. Can you clarify how to make sure the catalog upgrade is done. I did the update to tables without error but am not sure it is the same. Thank you Dan Hicks | 916-999-2711 From: Davide Franco [mailto:bacula-...@dflc.ch] Sent: Friday, September 1, 2017 12:11 PM To: Jerry Lowry ; bacula-users@lists.sourceforge.net Subject: [Non-DoD Source] Re: [Bacula-users] database upgrade problem Hi Jerry, Make sure the catalog upgrade has been done without issue. This seems to be related to Mariadb. Good luck Davide On Fri, 1 Sep 2017 at 17:38, Jerry Lowrywrote: Hi, I finally got my backup server upgraded to 9..0.3. I have run the database update and it succeeded with out any errors. But I get this error any time I start a job: 01-Sep 00:20 kilchis-dir JobId 0: Fatal error: sql_create.c:84 Create DB Job record INSERT INTO Job (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate,ClientId,Comment) VALUES ('BackupCatalog.2017-09-01_00.20.18_03','BackupCatalog','B','F','C','2017-09-01 00:20:16',1504250416,15,'') failed. ERR=Field 'StartTime' doesn't have a default value Does this mean the update did not work? thanks for the help! jerry -- 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 -- 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