On Wed, Jan 7, 2015 at 9:49 AM, John Florian 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 instal
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...@
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 s
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
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 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
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.f
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
