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. What I'm confused about is why a disk volume ties
itself to one specific storage resource when there are numerous
clients from different VLANs. Ultimately, I don't really care
where it looks to get it's data from, but it was something that
didn't make sense to me.
Did I answer your questions? Any other thoughts?
Thanks,
Kevin B. Zimmerman
On 09/20/2013 01:31 PM, Ana Emília M. Arruda wrote:
Hi
Kevin,
Just trying to understand... The error bellow:
Restore-public-Disk.2013-09-20_12.43.48_32
is waiting
for
Client to connect to Storage daemon
...
It means
that your client "public-fd" have problems to connect to
storage daemon. In the case, for the restore job, bacula is
asking for:
Storage
{
Name = File_20
Address = 192.168.120.35
...
}
So,
probably, public-fd has network problems in communicating
with 192.168.120.35...
Are
you using the correct JobId for the restore? When you say
that it should ask for File_5 storage, maybe you are
misunderstanding the JobId information for the restore you
want.
Best
regards,
Ana
|
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|