yeah, the same config for nightly run is the exact same as the one for manual
run,
only difference is that it's scheduled.
ssh tunnel is opened for each job.
as additional info, I have multiple jobs, but it's only the SSH jobs that fail.
+---
just noticed there is this following error in addition to the above
Fatal error: Bad response to Storage command: wanted 2000 OK storage, got 2902
Bad storage
+--
|This was sent by to...@tomse.dk via Backup Central.
|Forward SPA
The above message is now shown after upgrading from 5.1.x to 5.2.6
Doing a manual backup using same jobs etc it works perfectly.
So keys are good.
This only occurs with the automatic backup running through a SSH Tunnel
(following the ssh tunnel guide in the manual)
anyone has any ideas to fix t
did you label the tapes ? other than the barcode I mean.
it looks like you've replaced an old tape with this new one, but kept the name
of the old one on the label.
if you are sure the tape is brand new, and there are no data on it, just delete
the tape from bacula, and
use the label command on
0
own nsa1.0 root:bacula
perm nsa1.0 0660
though I could probably exclude ch1.
then restarted the devfs
worked like a charm now.
cheers
Tomse
+--
|This was sent by to...@tomse.dk via Backup Central.
|Forward SPAM
Hello.
I've just setup 2 autoloaders on the same server
the first autoloader works fine when doing "update slots" in the console
doing the same on the second, it responds with "Device has 0 slots"
bacula-sd.conf
autochanger {
name = my1dev-library
changer command ="/usr/local/share/bacula/mt
