Do you have LabelMedia = yes; set in the device section of your sd config?
Luca Ferrari wrote:
> Looking in the messages I found this:
>
> 25-Jul 08:58 backup-dir: Start Backup JobId 761,
> Job=sede_Vol2Samba_job.2007-07-25_08.58.35
> 25-Jul 08:58 backup-dir: Created new
> Volume "sede_Vol2Samba_job-2007-07-25--8-58" in catalog.
> 25-Jul 08:58 backup-sd: End of Volume "sede_Vol2Samba_job-2007-07-25--8-58"
> at
> 0:0 on device "sede_Vol2Samba_storage" (/backup/sede/vol2). Write of 240
> bytes got -1.
> 25-Jul 08:58 backup-sd: Marking Volume "sede_Vol2Samba_job-2007-07-25--8-58"
> in Error in Catalog.
> 25-Jul 08:58 backup-dir: sede_Vol2Samba_job.2007-07-25_08.58.35 Error:
> sql_create.c:384 Volume "sede_Vol2Samba_job-2007-07-25--8-58" already exists.
> 25-Jul 08:58 backup-dir: sede_Vol2Samba_job.2007-07-25_08.58.35 Error:
> sql_create.c:384 Volume "sede_Vol2Samba_job-2007-07-25--8-58" already exists.
> 25-Jul 08:58 backup-sd: Job sede_Vol2Samba_job.2007-07-25_08.58.35 waiting.
> Cannot find any appendable volumes.
> Please use the "label" command to create a new Volume for:
>
>
> but the volume does not exists and I don't know what the above error "got -1"
> means....just I'm not running out of space.
>
> Any idea/suggestion?
>
> Luca
>
>
> On Tuesday 24 July 2007 Luca Ferrari's cat, walking on the keyboard, wrote:
>> Hi all,
>> I've got several job definitions that are similar, but the following is not
>> working:
>>
>> Job {
>> Name = sede_Vol2Samba_job
>> Enabled = no
>> Type = Backup
>> Level = Incremental
>> Client = sede-fd
>> FileSet = sede_Vol2Samba_fileset
>> Storage = sede-samba-sd
>> Messages = Daemon
>> Pool = sede_vol2_pool
>> Schedule = Night-Incremental
>> }
>>
>>
>>
>> Pool {
>> Name = sede_vol2_pool
>> Pool Type = Backup
>> Recycle = yes
>> AutoPrune = yes
>> Volume Retention = 365 days
>> Accept Any Volume = yes
>> Label Format
>> = "${Job}-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}--${Hour}-${Minute}"
>> Maximum Volume Jobs = 1
>> Use Volume Once = yes
>> }
>>
>>
>> in fact the job stay blocked waiting for media, and in particular there is
>> no label for the volume:
>>
>> Running Jobs:
>> Writing: Full Backup job sede_Vol2Samba_job JobId=749 Volume=""
>> pool="sede_vol2_pool" device=""sede_Vol2Samba_storage"
>> (/backup/sede/vol2)"
>> Files=0 Bytes=0 Bytes/sec=0
>> FDReadSeqNo=6 in_msg=6 out_msg=4 fd=5
>>
>>
>> Other jobs with an identical pool get labeled right, why this is not?
>> Any suggestion?
>>
>> Thanks,
>> Luca
>>
>> -------------------------------------------------------------------------
>> 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
>
>
>
> -------------------------------------------------------------------------
> 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
>
-------------------------------------------------------------------------
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
