Hello,
I'm a IT major at Rutgers University and am working on installing Bacula
on my personal network. It's made up of 8 Linux boxes, mainly used for
email, web, and development - not exactly "critical". I've been
experimenting with Bacula for the past day (about 20 hours by now)
mainly trying to figure out the config files, with the aid of Webmin at
times. Right now I'm doing manual weekly tapes, and my tape drives are
listed on the known-to-work list, so I decided to try disk-only for now.
I'm working on 2 machines. The director is on STOR1, running OpenSuSE
10.2 with Bacula installed via the OpenSuSE "bacula-mysql-2.2.4-1" RPM.
My storage daemon is installed on "janus", running SuSE 9.3 (yeah, I
know, upgrade is coming soon, but it's running fine and internal only)
with the "bacula-1.36.3-3.2"
and "bacula-server-1.36.3-3" RPMs installed. I crossed my fingers on the
lower version because the bacula 2.x RPMs would require massive
dependency upgrades, and probably braking some other stuff along the way.
I thought I had everything configured properly.
I ran bconsole on the director (STOR1) in an attempt to label a volume
on janus, the storage machine.
Output:
Connecting to Director STOR1:9101
1000 OK: STOR1-dir Version: 2.2.4 (14 September 2007)
Enter a period to cancel a command.
*label
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
The defined Storage resources are:
1: STOR1-sd-home
2: janus-sd
Select Storage resource (1-2): 2
Enter new Volume name: JANUS-HDD-BACULA1
Automatically selected Pool: DiskVolume
Connecting to Storage daemon janus-sd at janus.jasonantman.com:9103 ...
Sending label command for Volume "JANUS-HDD-BACULA1" Slot 0 ...
3000 OK label. Volume=JANUS-HDD-BACULA1 Device=/mnt/hdd/BACULA
Label command failed for Volume JANUS-HDD-BACULA1.
Do not forget to mount the drive!!!
*exit
Now the problem:
if I run "list media", the volume "JANUS-HDD-BACULA1" doesn't show up.
However, if I re-run the label command:
*label
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
The defined Storage resources are:
1: STOR1-sd-home
2: janus-sd
Select Storage resource (1-2): 2
Enter new Volume name: JANUS-HDD-BACULA1
Automatically selected Pool: DiskVolume
Connecting to Storage daemon janus-sd at janus.jasonantman.com:9103 ...
Sending label command for Volume "JANUS-HDD-BACULA1" Slot 0 ...
3911 Cannot label Volume because it is already labeled: "JANUS-HDD-BACULA1"
Label command failed for Volume JANUS-HDD-BACULA1.
Do not forget to mount the drive!!!
*exit
it appears to think that the volume is already labeled.
If I try to delete media, the volume is also not shown as an option.
Any suggestions on how to get out of this seemingly infinite loop? It's
telling me that all label commands on that daemon return 3000 OK and
then says failed, so it's telling me that the labels exist yet they're
not showing up as valid media.
Thanks,
Jason Antman
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
