Hi Arno,
> Ok, so this looks like the SD is kind of confused.
>
> I assume you do have volumes for both pools, and all the volumes are
> heoreticall (from Baculas point of view) available to the SD. This
> depends mainly on the media type, I think, but the storage the media is
> assigned to might also be important.
The Default pool only contains tapes. The NAS is not equipped with a
tapestreamer...
> So you should have the existing
> volume files for the pool you want to use in the directory /data/bacula
I've got one, but I want it to create a volume automagically for each job.
> (your configuration, though, shows this as /path/bacula, which might be
> related to this problem...)
In my configfile, it is set correctly. I went through the config files and
replaced some values with bogus ones to mislead potential hackers. I
should've been more consequent.
> What I would do, after checking the setup and possibly restarting he
> daemons: Try unmounting the storage device and mounting again. The SD
> should try to access the right volume then.
I did, and it didn't... Got this lovely message instead ;)
--------------------------%<---------------------------
mount
The defined Storage resources are:
1: File
2: FileNAS
3: DDS-4
Select Storage resource (1-3): 2
3001 OK mount. Device="FileStorageNAS" (/data/bacula)
21-Mar 08:01 nas-sd: Job ntserv2NAS.2006-03-20_23.05.05 waiting. Cannot find
any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: "FileStorageNAS" (/data/bacula)
Media type: File
Pool: Default
--------------------------%<---------------------------
> If this doesn't work, try running the SD with debug output and see what
> that reports. Your problem description is a little similar to one I
> observed with a beta version, by the way, but I'm using tape volumes.
Here's the output:
--------------------------%<---------------------------
nas-sd: dircmd.c:187 Message channel init completed.
nas-sd: dircmd.c:513 Found device FileStorageNAS
nas-sd: dircmd.c:710 Device already unmounted
nas-sd: cram-md5.c:52 send: auth cram-md5 <[EMAIL PROTECTED]> ssl=0
nas-sd: cram-md5.c:68 Authenticate OK [EMAIL PROTECTED]@[EMAIL PROTECTED]
nas-sd: cram-md5.c:114 sending resp to challenge: [EMAIL PROTECTED]@[EMAIL
PROTECTED]
nas-sd: dircmd.c:187 Message channel init completed.
nas-sd: dircmd.c:513 Found device FileStorageNAS
--------------------------%<---------------------------
> The current -beta6 might resolve this problem, but I will know more
> tomorrow after my more difficult schedules are run...
Eh.. This is used in a production environment... Is the beta6 version safe to
use?
Thanks again,
Ger.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
