Hello.
I'm admin of about 60 win (some 98 still) computers and 2 linux servers. We
plan to install new server under fc5 + bacula for backup all other
computers.
The main problem for me while I test computers (1 fc5 server +
1.38.11-1.39.24 bacula-dir-sd-fd, 1 winxp+fd and 1 win98+fd) is to shutdown
them only when it previously switched on by bucula-fd by RunBefore job by
etherwake but not user and skiping of Full backup Job if it is scheduled on
Sunday but something has wrong so Full Backup will wait until next Sunday
(but something again wrong and so on).
My thoughts are:
1) Improve window's fd ability to recognize is anybody logged in to system
or there's safely to shutdown computer. Moreover, I think it's a good idea
(for window's workstations) to display messagebox with message that backup
is running on this computer (better with localization of message). It's
extremely needed for security persons who has came in room at middlenight
and seeing working workstation and for users to who came at his workplace at
8:05 and see running computer because bacula has started backup job at 8:00.
Then user can press ok button in this dialog and login to system so bucula
will not shutdown the computer after finish the job (a big surprise for user
finishing to input 2nd page of text!) or he can press cancel and bacula
break its current job but user can make his urgent job (go to www.xxx.com
for example) or he can go to nearest pub to drink a lot of beer with
sysadmin while backup has finished.
I understand that it is not simple modification but would you give me at
least an external tool that give me ability to send command to fd client
outside bacula. For example:
run job
Run Before Job = scriptRBJ that:
ping computer Client1 (is it alive?)
set some EXTERNAL flag Client1.on/off
possible switch it on (throw etherwake for example)
make job
Run After Job = scriptRAJ (not Client Run After Job! because bacula don't
know who switch on client's computer user or bacula-dir, It's know only
Client1.on/off flag) that:
look for flag Client1.on/off
if : shutdown it sending "shutdown -h 60" to Client1's fd.
end job.
Indeed, why I must send commands to client throw some other client's daemon
(RPC for example) in my scripts while I already have fd with this
possibility? All I need to be happy is only "bscript -c config_file -d
client -s command" or Bacula::RunScript.
2)2nd idea is to start jobs not (or not only) by scheduling but by Count or
Rating.
Let's every Job (I,D,F) has its own basket and every timebit (hour or 5 min)
it's added with token. At every timebit director checks is basket full? If
yes it runs job and empts basket on success finish. Jobs can be arranged by
token count. This count can be multiplied by VIP, normal or lower
coefficient. It can be 0 if client's computer on so backup will run only on
off computer but on some value dir can be forced to run backup and so on. On
the other hand if some backup job does not finish successfully it will rerun
at nearest timebit. I think it's extremely client-friendly option if you
have many computers with unpredicted work time.
Sorry for my English.
Alexey Serebryakov
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
