Re: [Bacula-users] Is this an Inter-version Compatibility Issue???
On Wed, Jan 7, 2015 at 9:49 AM, John Florian john.flor...@dart.biz wrote: My Fedora 21 workstation has: bacula-client-7.0.5-2.fc21.x86_64 bacula-common-7.0.5-2.fc21.x86_64 bacula-libs-7.0.5-2.fc21.x86_64 I ran into the same problem. I solved it by removing the bacula packages, then installing the fc20 RPMs. You probably will have to download the RPMs, then installl them from the local RPM files you downloaded. My problem is that my SD server is a Raspberry Pi, and there are no Bacula 7 packages for it. I'd have to compile from source. It was easier to downgrade the f21 system than to do this. Eventually I may try it, because the system that the Bacula director runs on is going to need upgrading soon too (for reasons having nothing to do with Bacula). --Greg -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Is this an Inter-version Compatibility Issue???
I recently rebuilt my workstation from Fedora 20 to 21 and am now having issues with Bacula that may stem from incompatibilities between Bacula versions. I'm hoping somebody can confirm my suspicion. At present, I have: Dir and SD are on the same Fedora 20 host with: bacula-client-5.2.13-18.fc20.x86_64 bacula-common-5.2.13-18.fc20.x86_64 bacula-console-5.2.13-18.fc20.x86_64 bacula-director-5.2.13-18.fc20.x86_64 bacula-libs-5.2.13-18.fc20.x86_64 bacula-libs-sql-5.2.13-18.fc20.x86_64 bacula-storage-5.2.13-18.fc20.x86_64 My Fedora 21 workstation has: bacula-client-7.0.5-2.fc21.x86_64 bacula-common-7.0.5-2.fc21.x86_64 bacula-libs-7.0.5-2.fc21.x86_64 If I try to run a simple incremental backup job for my workstation, the log emits: 07-Jan 11:35 mdct-bacula-dir JobId 32287: Start Backup JobId 32287, Job=Florian_Workstation.2015-01-07_11.35.23_23 07-Jan 11:35 mdct-bacula-dir JobId 32287: Using Device FileStorage to write. 07-Jan 11:35 mdct-dev12.dartcontainer.com- JobId 32287: Fatal error: Authorization key rejected by Storage daemon. Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. 07-Jan 11:35 mdct-bacula-dir JobId 32287: Fatal error: Bad response to Storage command: wanted 2000 OK storage, got 2902 Bad storage I am quite familiar with Bacula's authorization requirements and have confirmed everything is correct. (In fact, I've had puppet managing these aspects for years to reduce the probability of human error.) It's for these reasons I suspect there must be a version compatibility issue here. I've checked the release notes but find them lacking detail in this regard. (The last time compat is mentioned goes all the way back to the 5.2.11 release and that only talks about having older FDs - nothing about newer FDs.) -- John Florian -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula bug? Expanding my NAS size (Adding disk)-Redoes Full
On 01/06/2015 01:31 PM, philhu wrote: ok, tried to do that, seems to have failed, but list volumes shows retention is now correct: Select parameter to modify (1-18): 14 Error updating Volume records: ERR=sql_update.c:451 Update failed: affected_rows=0 for UPDATE Media SET ActionOnPurge=0, Recycle=1,VolRetention=63072000,VolUseDuration=0,MaxVolJobs=0,MaxVolFiles=0,MaxVolBytes=53687091200,RecyclePoolId=0 WHERE PoolId=1 Error updating Volume records: ERR=sql_update.c:451 Update failed: affected_rows=0 for UPDATE Media SET ActionOnPurge=0, Recycle=1,VolRetention=63072000,VolUseDuration=0,MaxVolJobs=0,MaxVolFiles=0,MaxVolBytes=53687091200,RecyclePoolId=0 WHERE PoolId=2 Error updating Volume records: ERR=sql_update.c:451 Update failed: affected_rows=0 for UPDATE Media SET ActionOnPurge=0, Recycle=1,VolRetention=31536000,VolUseDuration=0,MaxVolJobs=0,MaxVolFiles=0,MaxVolBytes=0,RecyclePoolId=0 WHERE PoolId=3 All Volume defaults updated from LTO4Tapes Pool record. * Hi Phil... Just a quick note regarding your mention of the command failing. If you notice, the last line says: 'All Volume defaults updated from LTO4Tapes Pool record.' Which means that the SQL query that Bacula sent to the DB successfully updated the records for all of the volumes in the LTO4Tapes pool. However, the three lines above it are a bit misleading in that they are not really errors in the true sense of an error. What actually happened was that there were no volumes in those pools to update. To verify this, type List Pools in bconsole. You should see four pools listed, and the first three; PoolId 1, 2, and 3 will have NumVols = 0. Hope this helps. Bill -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/ -- Not responsible for anything below this line -- -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Is this an Inter-version Compatibility Issue???
That's kind of what I thought/remembered, but I couldn't find it written in stone anywhere. Thank you for the confirmation. -- John Florian -Original Message- From: John Drescher [mailto:dresche...@gmail.com] Sent: Wednesday, January 07, 2015 12:28 To: John Florian Cc: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Is this an Inter-version Compatibility Issue??? The server versions need to be equal to or higher than the client versions. John On Wed, Jan 7, 2015 at 11:49 AM, John Florian john.flor...@dart.biz wrote: I recently rebuilt my workstation from Fedora 20 to 21 and am now having issues with Bacula that may stem from incompatibilities between Bacula versions. I’m hoping somebody can confirm my suspicion. At present, I have: Dir and SD are on the same Fedora 20 host with: bacula-client-5.2.13-18.fc20.x86_64 bacula-common-5.2.13-18.fc20.x86_64 bacula-console-5.2.13-18.fc20.x86_64 bacula-director-5.2.13-18.fc20.x86_64 bacula-libs-5.2.13-18.fc20.x86_64 bacula-libs-sql-5.2.13-18.fc20.x86_64 bacula-storage-5.2.13-18.fc20.x86_64 My Fedora 21 workstation has: bacula-client-7.0.5-2.fc21.x86_64 bacula-common-7.0.5-2.fc21.x86_64 bacula-libs-7.0.5-2.fc21.x86_64 If I try to run a simple incremental backup job for my workstation, the log emits: 07-Jan 11:35 mdct-bacula-dir JobId 32287: Start Backup JobId 32287, Job=Florian_Workstation.2015-01-07_11.35.23_23 07-Jan 11:35 mdct-bacula-dir JobId 32287: Using Device FileStorage to write. 07-Jan 11:35 mdct-dev12.dartcontainer.com- JobId 32287: Fatal error: Authorization key rejected by Storage daemon. Please see http://www.bacula.org/en/rel- manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. 07-Jan 11:35 mdct-bacula-dir JobId 32287: Fatal error: Bad response to Storage command: wanted 2000 OK storage, got 2902 Bad storage I am quite familiar with Bacula’s authorization requirements and have confirmed everything is correct. (In fact, I’ve had puppet managing these aspects for years to reduce the probability of human error.) It’s for these reasons I suspect there must be a version compatibility issue here. I’ve checked the release notes but find them lacking detail in this regard. (The last time “compat” is mentioned goes all the way back to the 5.2.11 release and that only talks about having older FDs – nothing about newer FDs.) -- John Florian -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- John M. Drescher -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula backup obsessed with a specific tape
I would, except I reloaded the auotloader after manually loading tapes to make the backup in progress finish. After the reload, it is now working as expected Still think it is a bug, but not ffecting me anymore. +-- |This was sent by p...@isone.biz via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Chged NAS size, now all files are written during first incr
Actually, what happened is I had forgotten to set retention to 2 years, so the default, 60 days was hit the same day the nas expanded...coincidence! +-- |This was sent by p...@isone.biz via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Is this an Inter-version Compatibility Issue???
The server versions need to be equal to or higher than the client versions. John On Wed, Jan 7, 2015 at 11:49 AM, John Florian john.flor...@dart.biz wrote: I recently rebuilt my workstation from Fedora 20 to 21 and am now having issues with Bacula that may stem from incompatibilities between Bacula versions. I’m hoping somebody can confirm my suspicion. At present, I have: Dir and SD are on the same Fedora 20 host with: bacula-client-5.2.13-18.fc20.x86_64 bacula-common-5.2.13-18.fc20.x86_64 bacula-console-5.2.13-18.fc20.x86_64 bacula-director-5.2.13-18.fc20.x86_64 bacula-libs-5.2.13-18.fc20.x86_64 bacula-libs-sql-5.2.13-18.fc20.x86_64 bacula-storage-5.2.13-18.fc20.x86_64 My Fedora 21 workstation has: bacula-client-7.0.5-2.fc21.x86_64 bacula-common-7.0.5-2.fc21.x86_64 bacula-libs-7.0.5-2.fc21.x86_64 If I try to run a simple incremental backup job for my workstation, the log emits: 07-Jan 11:35 mdct-bacula-dir JobId 32287: Start Backup JobId 32287, Job=Florian_Workstation.2015-01-07_11.35.23_23 07-Jan 11:35 mdct-bacula-dir JobId 32287: Using Device FileStorage to write. 07-Jan 11:35 mdct-dev12.dartcontainer.com- JobId 32287: Fatal error: Authorization key rejected by Storage daemon. Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. 07-Jan 11:35 mdct-bacula-dir JobId 32287: Fatal error: Bad response to Storage command: wanted 2000 OK storage, got 2902 Bad storage I am quite familiar with Bacula’s authorization requirements and have confirmed everything is correct. (In fact, I’ve had puppet managing these aspects for years to reduce the probability of human error.) It’s for these reasons I suspect there must be a version compatibility issue here. I’ve checked the release notes but find them lacking detail in this regard. (The last time “compat” is mentioned goes all the way back to the 5.2.11 release and that only talks about having older FDs – nothing about newer FDs.) -- John Florian -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- John M. Drescher -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
