Re: [Bacula-users] ClientRunBeforeJob fails, Windows 2000 client
Silver Salonen wrote: > I have the same problem with 2.0.0 on Windows 2003 server :( > The directive is: Client Run Before Job = "C:/Program > Files/Bacula/systemstate.bat" I have a problem that may or may not be related. winbacula-2.0.0.exe (from sourceforge) installed as Administrator under Windows 2000 Professional. C:\baculascript.bat contains the line ntbackup backup systemstate /L:n /F C:\systemstate.bkf and works if executed manually. Via ClientRunBeforeJob, however (from Director on a separate Linux system), runs but does not generate systemstate file; if /L:n (no logfile) switch removed, produces error message "Error opening the log file C:\\Microsoft\Windows NT\NTBackup\data\backup08.log." (The number 08 increases each time, although there are no other files in this data folder.) I can't trace the problem to access permissions under the Security tab of folder Properties: Administrator has Full Control all the way down this path, but it's as if writes fail when running from the Bacula FD. -- View this message in context: http://www.nabble.com/ClientRunBeforeJob-%28XP-Client%29-CrashesMe-Too-tf2562274.html#a8415721 Sent from the Bacula - Users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows (FD v2.0.1): ClientRunBeforeJob
Scott Ruckh wrote: > Possibly the environment/context that the Bacula FD runs under is > different then the user I am using to run the .BAT file. The security on > the actual files appears to be correct for the SYSTEM user, which is what > I believe is the context for the Bacula FD. In another thread (message quoted below) I reported a different privilege-related problem with the Windows FD. I have managed to work around this by changing the user under which the Bacula FD service runs (via compmgmt.msc) from the default LocalSystem to Administrator. It has the negative side-effect that the tray icon doesn't appear. On the other hand, it has the positive side-effect that the user logged in when the backup runs doesn't see ntbackup opening and can't interfere with it. In my .bat file I just have "ntbackup" (no path, no .exe). Yours, Greg. Earlier, I wrote (Re: ClientRunBeforeJob fails, Windows 2000 client): > Silver Salonen wrote: > >>I have the same problem with 2.0.0 on Windows 2003 server :( >>The directive is: Client Run Before Job = "C:/Program >>Files/Bacula/systemstate.bat" > > > I have a problem that may or may not be related. > > winbacula-2.0.0.exe (from sourceforge) installed as Administrator under > Windows 2000 Professional. > C:\baculascript.bat contains the line > > ntbackup backup systemstate /L:n /F C:\systemstate.bkf > > and works if executed manually. Via ClientRunBeforeJob, however (from > Director on a separate Linux system), runs but does not generate systemstate > file; if /L:n (no logfile) switch removed, produces error message "Error > opening the log file C:\\Microsoft\Windows NT\NTBackup\data\backup08.log." > (The number 08 increases each time, although there are no other files in > this data folder.) I can't trace the problem to access permissions under the > Security tab of folder Properties: Administrator has Full Control all the > way down this path, but it's as if writes fail when running from the Bacula > FD. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] "unwanted" feature in winbacula
Miki Lewinger wrote: > Currently any user (even non-admins) can stop the bacula file server > service on winnt-2k-xp workstations at will. This is a very unusual > "unwanted feature". Can it be fixed in later versions ? If not what is > the rational behind such behavior ? Using compmgmt.msc you can change the user under which the service runs from LocalSystem to Administrator. For me this has the side-effect of making the tray icon disappear, which may help you. I, on the other hand, would like to know why I have to do this to get ntbackup backup systemstate to work at all... (See the ClientRunBeforeJob threads.) - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
