I'm using brew, personally, and letting it compile on each machine -- I wrote a script to do the entire deployment I can share if you'd like. It handles installing brew and the necessary dependencies.
This seems like a good time to mention that I recently attended a presentation about macOS Catalina, and it sounds like brew and macports will probably not be workable going forward -- Gatekeeper is being tightened up so that only binaries signed by Apple will run, even if they're compiled locally. There's no provision for turning this off, although individual unsigned apps can be whitelisted if you have an MDM server. In addition, even more of the user's home directory will now be blocked by SIP, including Documents and Downloads. On Thu, Jul 11, 2019 at 6:39 AM Andrea Brancatelli via Bacula-users < bacula-users@lists.sourceforge.net> wrote: > OK thanks for the pointers. > > Tomorrow I'll test it with a few clients. > > The next problem on my roadmap is the Mac OS X Binary client... > > On the test machine I just installed it with Brew but compiling it from > scratch on the CEO machine seems complicated. > --- > > > *Andrea Brancatelli > * > > On 2019-07-11 13:12, Heitor Faria wrote: > > Hello Andrea, > > > 1. The scheduling - you can certainly schedule backups for a working > hour and hope that the guy's is working at that moment, but hey... Is there > any way to "invoke" a backup from client side (I don't know, like on system > startup) -- "Hey, I'm ready, backup me!" :-) > > You can schedule on the Director, and have these directives: > > "*Reschedule On Error = yes|no* If this directive is enabled, and the job > terminates in error, the job will be rescheduled as determined by the > *Reschedule > Interval* and *Reschedule Times* directives. If you cancel the job, it > will not be rescheduled. The default is *no* (i.e. the job will not be > rescheduled). > > This specification can be useful for portables, laptops, or other machines > that are not always connected to the network or switched on. > > > *Reschedule Incomplete Jobs = yes|no* > > If this directive is enabled, and the job terminates in incomplete status, > the job will be rescheduled as determined by the *Reschedule Interval* > and *Reschedule Times* directives. If you cancel the job, it will not be > rescheduled. The default is *yes* (i.e. Incomplete jobs will be > rescheduled). > > > *Reschedule Interval = time-specification* If you have specified *Reschedule > On Error = yes* and the job terminates in error, it will be rescheduled > after the interval of time specified by *time-specification*. See the > time specification formatsTime in the Configure chapter for details of time > specifications. If no interval is specified, the job will not be > rescheduled on error. The default Reschedule Interval is 30 minutes (1800 > seconds). > > > *Reschedule Times = count* This directive specifies the maximum number of > times to reschedule the job. If it is set to zero (the default) the job > will be rescheduled an indefinite number of times." [ > https://www.bacula.org/9.2.x-manuals/en/main/Configuring_Director.html#10256 > ] > > It will retry in case machine is not on. > Instead of all this, you could have a console in each client and/or tray > monitor to start jobs from the Client machine, via script or user action. > > > 1. The IP addresses - again one could try to fix client's IP address > or have DHCP automatically update a fixed name, like > desktop-jon.company.com but that seems pretty flaky. Is there any way > to, maybe, update the client IP from client side? > > You could use Static DNS which uses the MAC address to fix an IP for each > client machine. > There is also a setip console command: > > "*setip* Sets new client address - if authorized. > > A console is authorized to use the *SetIP* command only if it has a > Console resource definition in both the Director and the Console. In > addition, if the console name, provided on the *Name =* directive, must > be the same as a Client name, the user of that console is permitted to use > the *SetIP* command to change the Address directive in the Director's > client resource to the IP address of the Console. This permits portables or > other machines using DHCP (non-fixed IP addresses) to "notify" the Director > of their current IP address." [ > https://www.bacula.org/9.0.x-manuals/en/console/Bacula_Console.html] > > Is it totally unfeasible to use Bacula in such scenario? > > It is possible, go for it. > > Thanks in advance > > Regards, > > -- > > *Andrea Brancatelli > * > > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > -- > > MSc Heitor Faria > CEO Bacula LATAM > mobile1: + 1 909 655-8971 > mobile2: + 55 61 98268-4220 > [image: linkedin icon] > <https://www.linkedin.com/in/msc-heitor-faria-5ba51b3> > [image: logo] <Http://www.bacula.com.br> > América Latina > bacula.lat | bacula.com.br <http://www.bacula.com.br> > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- David Brodbeck System Administrator, Department of Mathematics University of California, Santa Barbara
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
