Hi Ana -
Thanks for responding.
I currently have no issues communicating between the public-fd client
and the storage daemon at 192.168.120.35. I'm able to connect between
both addresses on ports 9102 and 9103.
As far as the JobID, I pass the specific job to the console during the
restore.
On Sat, Sep 21, 2013 at 2:20 AM, Greg Woods wrote:
> I'm having some trouble getting vchanger to work, partly because the
> documentation that comes with it seems not to be up to date. For
> instance, the keywords described in the howto HTML file that comes with
> the source are invalid keywords.
I apologize for yet another posting, but I am just having a HELL of a
time trying to get vchanger to work. I have been following the
instructions in the Howto that came with the source code. I have the
automounting working, and the permissions are all correct (the "bacula"
user owns the work_dir an
On 2013-09-21 09:53, Greg Woods wrote:
...
> Ugh, never mind. I've been spending so much time on this and doing so
> many searches that I got my versions of the Howto confused. It looks
> like the one that actually comes with the source code is not the one I
> was actually reading. Now that I have
On Fri, 2013-09-20 at 19:20 -0600, Greg Woods wrote:
> I'm having some trouble getting vchanger to work, partly because the
> documentation that comes with it seems not to be up to date.
Ugh, never mind. I've been spending so much time on this and doing so
many searches that I got my versions of t
On 09/19/2013 10:35 AM, Ralf Brinkmann wrote:
> We are using now Bacula on Linux servers for years with great success.
>
> On Windows clients we start Bat via Putty and XMing.
>
> Now I found on SourceForge there is a "Bat" for Windows available -
> unfortunately a little bit outdated.
>
> Is it sa
