I don't think I have used unmount after removing old state files and nuking
all data in sql database.
I had started afresh and backup ran smoothly and created about 30 volumes
(256MB each) and then stopped with following message.
Running Jobs:
Console connected at 28-Jun-11 18:45
JobId Level Name Status
======================================================================
1 Full FileShare.2011-06-28_10.04.46_03 is waiting for a mount
request
When I checked the storage status I got the following info.
Device status:
Device "FileStorage" (/home/backups/fileshare) open but no Bacula volume is
currently mounted.
Device is BLOCKED waiting for mount of volume "FileShare0037",
Pool: File
Media type: File
Total Bytes Read=0 Blocks Read=0 Bytes/block=0
Positioned at File=0 Block=0
I tried to look up in mailing lists and could not find any post similar to
problem I am facing.
Thanks,
Venkatesh K
On Wed, Jun 29, 2011 at 8:13 AM, John Drescher <dresche...@gmail.com> wrote:
> On Tue, Jun 28, 2011 at 10:36 PM, Venkatesh K Reddy
> <venkat...@kaevee.com> wrote:
> > I had used unmount. But, I nuked the whole configuration.
> >
>
> If you ever use umount then the next volume that bacula will want you
> will have to mount it since umount takes the storage device out of
> bacula's control. If you just want to unload a volume without bacula
> giving up control on the storage device use the release command
> instead.
>
> John
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
