What version is your Windows FD?
File type 26 is a Windows Junction point. It is hard to
understand how you could get that type with an FD that does not
know what it is. This indicates that you might have mixed
different versions of the FD at various time
On 06/12/2014 05:38 PM, Thomas Lohman wrote:
> I've seen this error before on and off on one particular client.
> Nothing changes with regard to the configuration and yet the error will
> crop up. Usually a combination of the following "fixes" it -
> cancel/restart the job, restart the Bacula c
On 06/11/2014 08:18 PM, Larry A. Rosen wrote:
> Is there a way to do "update all volumes from pool" specifying the pool
> without being prompted to use the menu to select the operation?
>
> i.e. I want to update the retention period of all volumes in the Archive
> pool so I'd like to do somethin
Hello,
Thanks for the feedback.
Best regards,
Kern
On 06/10/2014 08:28 PM, Stephen Thompson wrote:
>
>
> ver 7.0.4 does not appear to have the canceling job issue I saw in
> 7.0.2. yay! ...and thanks.
>
>
>
> On 5/22/14 8:37 AM, Bill Arlofski wrote:
>> On 05/22/14 11:28, Kern Sibbald wrote:
>>>
Hi at all,
since two weeks I got problem with my HP MSL4048, a two reader library
connected by SAS to my Centos 5 (32bit) Bacula server.
Randomly the s.o. is not able to see the library, but this one return no
error (on the web managemente): the only signs of problem could be seen
into dmesg output
26 is a junction point. Are you trying to restore onto a Linux machine? That
can't work unless you made a portable backup.
__Martin
> On Fri, 13 Jun 2014 17:07:54 +0200, Florian Baumgartner said:
>
> While doing a restore of a Windows backup I'm receiving *** Restore Error
> *** as termin
While doing a restore of a Windows backup I'm receiving *** Restore Error
*** as termination status.
There are many files being restored but it is not obvious to me what is
failing. Looking at the logs of the fd I'm restoring with I'm seeing many
lines resembling the one below which I assume is wh
