Hi,
On 26.09.2005 17:00, Russell Howe wrote:
Arno Lehmann wrote:
I've been thinking about that lately...
http://www.wpkg.org/ may be one way. You also might be able to package
up bacula into an MSI file and install that way (perhaps even using
Active Directory for the deployment).
I never tried building and preparing for noninteractive install a msi
file, which is probably one of the reasons I tried to restrice myself to
something simple, and staying inside bacula where possible...
Failing that, stop the bacula service remotely, copy the bacula files to
\\servername\c$\bacula (need to have administrative rights to do this,
usually),
That is one of the problems, because I wouldn't like to require more
access rights than necessary. (In fact I *do* know that doing backups
and restores requires about all the rights possible, but still... :-)
and start the bacula service remotely. Test that the fd is up
and running by doing an estimate or something. Should be fairly
scriptable. I don't think there's any fancy registry keys which need
creating once you've installed it once, although you can't really rely
on this being the case forever.
Well, the main reason for my suggestion to copy files during windows'
start-up is to avoid problems with locked files. Recently, there was
some problem with the win-FD installation package where one part of the
installation (wx-console?) complained because it couldn't install a dll
in use by the previously-installed and already running other part (FD).
Now, if I understand that situation correctly, his is definitely a bug
in the installation program, but as long as we can't be sure that
something similar can happen with other libraries I'd try to use the
file replacement during startup stuff windows supplies.
Of course, this might lead to trouble when a) a client is seldom
restarted, and b) bacula's inter-daemon protocoll changes, because in
that case you might need the manual intervention, i.e. restart, anyway.
Remote service stop/start can be done either via the Services thing, or
via the 'net' command in a script, I think.
I think you think right, though I forgot that...
In this case, I would use a client run after job script that forks (or
windows' equivalent), waits some seconds or minutes, stops the FD,
replaces the files, and restarts the FD. Easier than first damaging the
registry and then having to load your backup ;-)
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
