Re: [Bacula-users] Backing Up a Remote Client

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 outboun

Re: [Bacula-users] Backing Up a Remote Client

Your tips were bang on. I implemented this and it is working. The other steps required were to forward ports on the routers at each end and change the DIR storage resource Address= from a local lan address to the public FQDN. Thank you. -Chris- On Wed, 26 Jun 2024, 18:18 Bill Arlofski via Bacula

Re: [Bacula-users] Backing Up a Remote Client

That's very helpful. On reflection, the storage being a cifs share shouldn't be a show stopper as I first thought. The SD (and thus the storage) should be contactable via a port opening. I'll look at my current attempt again in the light of your explication. -Chris- On Wed, 26 Jun 2024, 18:18 Bil

Re: [Bacula-users] Backing Up a Remote Client

On 6/26/24 10:44 AM, Chris Wilkinson wrote: I'm seeking some advice on configuring the backup of a remote client. Up till now all clients were located on the same local lan that hosts the Director, File and Storage Daemons. The whole lan is behind a nat'd router. One of these clients has now mo

[Bacula-users] Backing Up a Remote Client

I'm seeking some advice on configuring the backup of a remote client. Up till now all clients were located on the same local lan that hosts the Director, File and Storage Daemons. The whole lan is behind a nat'd router. One of these clients has now moved to a remote site, also behind a nat'd route

Re: [Bacula-users] volumes, pools, media types and labels

Am 21.06.24 um 16:31 schrieb Radosław Korzeniewski: Hello, czw., 20 cze 2024 o 17:46 Stefan G. Weichinger > napisał(a): Well, it looks for a volume named "Vol-xxx" in the tape loader, which is wrong. Any chance you can share your job log here? Sure ... q