Re: [Bacula-users] Windows (FD v2.0.1): ClientRunBeforeJob
Agreed Troy! Add the .exe to the path name. I ran into this very same issue 'assuming' the extension would otto-magically be added. So much for assuming Erich On Jan 19, 2007, at 12:40 AM, Troy Daniels wrote: Hi Scott, I might be completely wrong but have you tried to append .exe to the ntbackup command? On my systems at least the full path is c:\WINDOWS\system32 \ntbackup.exe Microsoft normally tries to be nice and append the .exe extension automatically, but something may have changed in the latest version that interferes with that. However, it also hides the extension in by default in Explorer which leads to confusion more often than not in my experience. What version were you running before upgrading? And what version of Windows are you running? The answers to the above might help others answer your original question. Hope this helps, Troy Daniels. Perth Systems Admin. iTouch Australia (pty) ltd. Scott Ruckh wrote: I am trying to call a .BAT file using ClientRunBeforeJob. The config used to work fine before upgrading the Windows FD 2.0.1. It looks like the syntax in my bacula-dir.conf file is correct. It looks like the .BAT file is being called, and for some reason there is a problem with the .BAT file. Taking Bacula out of the equation, running the .BAT file works without any problem. 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. Perhaps someone can lend some assistance. Here is what is reported from Bacula's messages. ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 Yes, C:\WINDOWS\system32\ntbackup, does exist and is the correct PATH. Thanks. -- --- 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - 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.phpp=sourceforgeCID=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
This is what you said Erich Prinz Agreed Troy! Add the .exe to the path name. I ran into this very same issue 'assuming' the extension would otto-magically be added. So much for assuming Erich On Jan 19, 2007, at 12:40 AM, Troy Daniels wrote: Hi Scott, I might be completely wrong but have you tried to append .exe to the ntbackup command? On my systems at least the full path is c:\WINDOWS\system32 \ntbackup.exe Microsoft normally tries to be nice and append the .exe extension automatically, but something may have changed in the latest version that interferes with that. However, it also hides the extension in by default in Explorer which leads to confusion more often than not in my experience. What version were you running before upgrading? And what version of Windows are you running? The answers to the above might help others answer your original question. Hope this helps, Troy Daniels. Perth Systems Admin. iTouch Australia (pty) ltd. To answer Kern, it was working with version 1.39.27. I can not remember what the actual version of the Windows FD was at that time. Both director and FD were upgraded at the same time when version 1.39.27 was installed. Now the Window FD is version 2.0.1. I will definitely give adding the extension (.EXE) a try, but I am not sure why that would make a difference. The .BAT file, which calls the ntbackup.exe, program works fine (from an windows command prompt). This leads me to believe the syntax in the .BAT file is correct. I assume the bacula-dir.conf file is correct because the .BAT file IS being called (or so appears from bacula's messages). The messages show the commands from the .BAT file. The problem is that what is in the .BAT does not run (when executed from bacula). The results are the same if I add the .EXE extension to the command line in the .BAT file. Below are the results: ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup.exe backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup.exe' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 I do not doubt the problem could be me, but this used to work in earlier versions of bacula. I started using this .BAT file in version 1.38.11. Thanks. Scott - 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.phpp=sourceforgeCID=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.phpp=sourceforgeCID=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
On Friday 19 January 2007 16:30, Scott Ruckh wrote: This is what you said Erich Prinz Agreed Troy! Add the .exe to the path name. I ran into this very same issue 'assuming' the extension would otto-magically be added. So much for assuming Erich On Jan 19, 2007, at 12:40 AM, Troy Daniels wrote: Hi Scott, I might be completely wrong but have you tried to append .exe to the ntbackup command? On my systems at least the full path is c:\WINDOWS\system32 \ntbackup.exe Microsoft normally tries to be nice and append the .exe extension automatically, but something may have changed in the latest version that interferes with that. However, it also hides the extension in by default in Explorer which leads to confusion more often than not in my experience. What version were you running before upgrading? And what version of Windows are you running? The answers to the above might help others answer your original question. Hope this helps, Troy Daniels. Perth Systems Admin. iTouch Australia (pty) ltd. To answer Kern, it was working with version 1.39.27. I can not remember what the actual version of the Windows FD was at that time. Both director and FD were upgraded at the same time when version 1.39.27 was installed. I wouldn't be surprised if there are differences between 1.39.27 and 2.0.x since, if I am not mistaken, the code was changed during that period. You can check the ChangeLog, which should explain what was done. Now the Window FD is version 2.0.1. I will definitely give adding the extension (.EXE) a try, but I am not sure why that would make a difference. The .BAT file, which calls the ntbackup.exe, program works fine (from an windows command prompt). This leads me to believe the syntax in the .BAT file is correct. I assume the bacula-dir.conf file is correct because the .BAT file IS being called (or so appears from bacula's messages). The messages show the commands from the .BAT file. The problem is that what is in the .BAT does not run (when executed from bacula). The results are the same if I add the .EXE extension to the command line in the .BAT file. Below are the results: ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup.exe backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup.exe' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 I do not doubt the problem could be me, but this used to work in earlier versions of bacula. I started using this .BAT file in version 1.38.11. Thanks. Scott - 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - 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.phpp=sourceforgeCID=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
On Thu, 18 Jan 2007 20:23:38 -0700 (MST), Scott Ruckh said: Importance: Normal I am trying to call a .BAT file using ClientRunBeforeJob. The config used to work fine before upgrading the Windows FD 2.0.1. It looks like the syntax in my bacula-dir.conf file is correct. It looks like the .BAT file is being called, and for some reason there is a problem with the .BAT file. Taking Bacula out of the equation, running the .BAT file works without any problem. 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. Perhaps someone can lend some assistance. Here is what is reported from Bacula's messages. ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 Yes, C:\WINDOWS\system32\ntbackup, does exist and is the correct PATH. This is a 64-bit Windows system, right? If so, then I think you are being hit by the way that 64-bit Windows hacks file names when running 32-bit programs. Basically what happens is that a 32-bit program accessing C:\WINDOWS\system32 actually accesses C:\WINDOWS\SysWOW64, which contains files that a 32-bit Windows installation would provide. The real C:\WINDOWS\system32 contains 64-bit Windows. The problem is that Bacula runs C:\WINDOWS\system32\cmd.exe to execute your .BAT file. Because Bacula is a 32-bit program, it ends up runing the 32-bit cmd from C:\WINDOWS\SysWOW64\cmd.exe. Then when this cmd runs C:\WINDOWS\system32\ntbackup, it actually tries to run C:\WINDOWS\SysWOW64\ntbackup, which doesn't exist. To make it work, you'll have to put a copy of C:\WINDOWS\system32\ntbackup.exe is some other directory. __Martin - 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.phpp=sourceforgeCID=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 [RESOLVED]
This is what you said Martin Simmons On Thu, 18 Jan 2007 20:23:38 -0700 (MST), Scott Ruckh said: Importance: Normal I am trying to call a .BAT file using ClientRunBeforeJob. The config used to work fine before upgrading the Windows FD 2.0.1. It looks like the syntax in my bacula-dir.conf file is correct. It looks like the .BAT file is being called, and for some reason there is a problem with the .BAT file. Taking Bacula out of the equation, running the .BAT file works without any problem. 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. Perhaps someone can lend some assistance. Here is what is reported from Bacula's messages. ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 Yes, C:\WINDOWS\system32\ntbackup, does exist and is the correct PATH. This is a 64-bit Windows system, right? If so, then I think you are being hit by the way that 64-bit Windows hacks file names when running 32-bit programs. Basically what happens is that a 32-bit program accessing C:\WINDOWS\system32 actually accesses C:\WINDOWS\SysWOW64, which contains files that a 32-bit Windows installation would provide. The real C:\WINDOWS\system32 contains 64-bit Windows. The problem is that Bacula runs C:\WINDOWS\system32\cmd.exe to execute your .BAT file. Because Bacula is a 32-bit program, it ends up runing the 32-bit cmd from C:\WINDOWS\SysWOW64\cmd.exe. Then when this cmd runs C:\WINDOWS\system32\ntbackup, it actually tries to run C:\WINDOWS\SysWOW64\ntbackup, which doesn't exist. To make it work, you'll have to put a copy of C:\WINDOWS\system32\ntbackup.exe is some other directory. __Martin Martin is right on! Thanks! Great find as I forgot to mention I was trying to run script on x64 system and originally I was running it on x32. It is still completely insane and does not make sense. Why can't the other command interpreter locate the fully qualified path to the ntbackup executable. Is that other directory structure unavailable when launched from the other cmd.exe interpreter? G!!! I am not a fan of Windows x64. Everyday I find something new I do not like. Thanks for the help. I hope this thread will educate others with similar situations. Maybe a 64bit Windows bacula FD would help? Now back to x32 where drivers worked and programs functioned as expected. Scott - 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.phpp=sourceforgeCID=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
On Friday 19 January 2007 22:55, Martin Simmons wrote: On Thu, 18 Jan 2007 20:23:38 -0700 (MST), Scott Ruckh said: Importance: Normal I am trying to call a .BAT file using ClientRunBeforeJob. The config used to work fine before upgrading the Windows FD 2.0.1. It looks like the syntax in my bacula-dir.conf file is correct. It looks like the .BAT file is being called, and for some reason there is a problem with the .BAT file. Taking Bacula out of the equation, running the .BAT file works without any problem. 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. Perhaps someone can lend some assistance. Here is what is reported from Bacula's messages. ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 Yes, C:\WINDOWS\system32\ntbackup, does exist and is the correct PATH. This is a 64-bit Windows system, right? If so, then I think you are being hit by the way that 64-bit Windows hacks file names when running 32-bit programs. Basically what happens is that a 32-bit program accessing C: \WINDOWS\system32 actually accesses C:\WINDOWS\SysWOW64, which contains files that a 32-bit Windows installation would provide. The real C:\WINDOWS\system32 contains 64-bit Windows. The problem is that Bacula runs C:\WINDOWS\system32\cmd.exe to execute your .BAT file. Because Bacula is a 32-bit program, it ends up runing the 32-bit cmd from C:\WINDOWS\SysWOW64\cmd.exe. Then when this cmd runs C:\WINDOWS\system32\ntbackup, it actually tries to run C:\WINDOWS\SysWOW64\ntbackup, which doesn't exist. Egads, what a mind-boggling horror. To make it work, you'll have to put a copy of C: \WINDOWS\system32\ntbackup.exe is some other directory. __Martin - 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - 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.phpp=sourceforgeCID=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
Hi Scott, I might be completely wrong but have you tried to append .exe to the ntbackup command? On my systems at least the full path is c:\WINDOWS\system32\ntbackup.exe Microsoft normally tries to be nice and append the .exe extension automatically, but something may have changed in the latest version that interferes with that. However, it also hides the extension in by default in Explorer which leads to confusion more often than not in my experience. What version were you running before upgrading? And what version of Windows are you running? The answers to the above might help others answer your original question. Hope this helps, Troy Daniels. Perth Systems Admin. iTouch Australia (pty) ltd. Scott Ruckh wrote: I am trying to call a .BAT file using ClientRunBeforeJob. The config used to work fine before upgrading the Windows FD 2.0.1. It looks like the syntax in my bacula-dir.conf file is correct. It looks like the .BAT file is being called, and for some reason there is a problem with the .BAT file. Taking Bacula out of the equation, running the .BAT file works without any problem. 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. Perhaps someone can lend some assistance. Here is what is reported from Bacula's messages. ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 Yes, C:\WINDOWS\system32\ntbackup, does exist and is the correct PATH. Thanks. - 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.phpp=sourceforgeCID=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
On Friday 19 January 2007 04:23, Scott Ruckh wrote: I am trying to call a .BAT file using ClientRunBeforeJob. The config used to work fine before upgrading the Windows FD 2.0.1. Are you saying that this worked in version 2.0.0 and is broken in 2.0.1? There was a change in the finding the default path for the conf files, but I don't remember anything affecting execution of programs. If you are saying that it worked on 1.38.x and not on 2.0.x, that is quite possible as a lot of code has been changed, and I think (hope) that it is just a matter of getting your syntax correct -- e.g. as someone suggested, include the .bat, ... It looks like the syntax in my bacula-dir.conf file is correct. It looks like the .BAT file is being called, and for some reason there is a problem with the .BAT file. Taking Bacula out of the equation, running the .BAT file works without any problem. 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. Perhaps someone can lend some assistance. Here is what is reported from Bacula's messages. ClientRunBeforeJob: run command C:/Program Files (x86)/Bacula/bin/backup_systemstate.bat ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32C:\WINDOWS\system32\ntbackup backup systemstate /F C:\SystemState\systemstate.bkf ClientRunBeforeJob: 'C:\WINDOWS\system32\ntbackup' is not recognized as an internal or external command, ClientRunBeforeJob: operable program or batch file. ClientRunBeforeJob: ClientRunBeforeJob: C:\WINDOWS\system32exit 0 Yes, C:\WINDOWS\system32\ntbackup, does exist and is the correct PATH. Thanks. -- Scott - 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
