On 6/27/24 2:54 AM, Chris Wilkinson wrote:
I made the additional changes you suggested.

*Removed FD port open on remote router
*Set storage resource 'Address=<local address of SD host>'
*Set storage resource 'FDStorageAddress=<public FQDN of remote site>'

I re-tested local and remote backups and these seem to be working fine.

Excellent! \o/

Next up.... Client Initiated Backups!   heh


These changes were not absolutely required as local backups continued to work when I had storage resource 'Address=<public FQDN of remote site>' and without the 'FDStorageAddress=' directive. I presume this was because I had opened ports 9101-9103 to the DIR/SD host on the local router as part of my previous attempts and I haven't undone any of them.

I didn't say it yesterday, but I was suspecting that if local and remote FD -> SD connections for backups were all still working after you set the Storage's Address to the external IP of the firewall, then it mu st be that NAT reflection was set/enabled on your firewall.

Yes sure, that will work, but do you really want all of your backup data 
traversing your firewall? :)


Thanks for your help

-Chris-

You're welcome!

I am glad that my curiosity to set this exact configuration up last week (for 
fun) was well timed.  :)


Best regards,
Bill

--
Bill Arlofski
w...@protonmail.com

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to