> tir, 03,.05.2005 kl. 12.49 -0400, skrev David Clymer: >> On Tue, 2005-05-03 at 18:40 +0200, Christopher Rasch-Olsen Raa wrote: >> > Hi, >> > >> > Just a quick question, arrest me if I have misunderstood the doc's. :p >> > >> > Why is Bacula written so that the Director is the one who contacts the >> > clients with the data for backup, instead of the Clients contacting >> the >> > Director whenever they need to do the backup? >> > >> >> I'm guessing that it's because it allows for centralized scheduling and >> control of backup jobs. >> >> -davidc > > Good point, though maybe bad news for us. > > At the office we are going to have 20+ clients that are to be taken > backup of regularly. These clients recieve their ip's via DHCP. Offsite > we will have our backupserver (in case of fires etc). In the case of the > Director contacting each and every client, won't I have to manually > reroute ports to each of the machines internally, every time they change > ip, for the Director to be able to find them? > > - Christopher >
I would suggest putting your director inside your [internal] network and placing your storage daemon off-site. That will take care of your problem with NAT, but unfortunately, I can't think up anything to get around the fact that you're fully DHCP. -- Alan Gerber ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
