It appears to me that somehow, you have a space in your volume name.
Instead of it being "Vol-0007" it is "Vol-0 007" so Bacula will
actually be looking for Vol-0, which obviously does not exist. Volume
names should never have a space in them, and Bacula attempts to avoid
that, so the "space
On Wed, Jun 22, 2016 at 12:31:59PM +0300, Daniel wrote:
> Hello Vanush
> I think i have found the problem
>
> volume Vol-0007 is located in /mnt/backup/week/i don't know if have
> configured correctly my device storage
>
> Device {
> Name = FileStorage-Month
> Media Type = File
> Arch
Hello Vanush
I think i have found the problem
15-Jun 12:15 akula-sd JobId 257: Warning: mount.c:220 Open of file
device "FileStorage-Month" (/mnt/backup/month) Volume "Vol-0
007" failed: ERR=file_dev.c:185 Could not
open(/mnt/backup/month/Vol-0007,OPEN_READ_WRITE,0640): ERR=No such file
or dire
On Wed, Jun 22, 2016 at 10:16:28AM +0300, Daniel wrote:
> Hello everyone
>
> I have problem with one of my pools (Weekly pool) . I can't figure out
> what triggers the creation of new volume and why it appears as VolStatus
> error.Any ideas what could be wrong in my config ??? here is my config
Hello everyone
I have problem with one of my pools (Weekly pool) . I can't figure out
what triggers the creation of new volume and why it appears as VolStatus
error.Any ideas what could be wrong in my config ??? here is my config
http://pastebin.com/raw/LxkQ2ZjP
---
