On 6/26/24 3:31 PM, Chris Wilkinson wrote: >
Your tips were bang on. I implemented this and it is working.
Excellent! \o/
The other steps required were to forward ports on the routers at each end
This should not be necessary at the remote site(s). The remote clients will be making outbound calls to the Internet, unless you have NAT inside NAT or something "interesting" going on at the remote site(s). :)
> and change the DIR storage resource Address= from a local lan address to the public FQDN. Uff yes, sorry, I missed a step! :)The part I missed (which you solved differently, but not the best way if this Storage is needed to be used by other internal Clients) is to instead leave the SD's `Address = ` alone and set the `FDStorageAddress = <FQDN or IP of your Main site firewall>` in the Director's configuration resource for this (and any other external) Clients.
This way, all your normal internal backups/clients that use this same SD can connect to it using its normal `Address = <SD's internal IP or FQDN>` and only these external clients will have the FDStorageAddress set to connect to the Main site's external firewall IP or FQDN.
Thank you. -Chris-
You're welcome! Hope these additional tips help to clean things up even more. Best regards, Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
