Never mind. My bad. When I upgraded, I installed into a new version
specific directory. The original person who installed bacula used / as
the install prefix, so out of habit, I went to /etc/bacula/ to make the
config edits, rather than the version specific directory where I had
moved the con figs and updated them.
Apologies all.
--
/^^^\ Craig Dupree, Systems Analyst
/~O~O~\ [EMAIL PROTECTED] ITS, User Services
\ U / (512)471 - 5358 UNIX Tech. Support
-oOo-------oOo- (512)625 - 0321(pg) The University of Texas at
Austin
[EMAIL PROTECTED](pg email)
Democracy is two wolves and a sheep voting on what to have for dinner.
Liberty is two wolves attempting to have a sheep for dinner and
finding a well-informed, well-armed sheep.
Rowdy wrote:
Craig Dupree wrote:
From looking at the Docs, and through the archives I think I can
disable a client's backup by commenting out the Schedule line like this:
Job {
Name = "frodo"
Type = Backup
Level = incremental
Client = frodo
FileSet = "windows"
Storage = tape0
# Schedule = "WeeklyCycle-FRODO"
Pool = Default
Messages = Standard
}
Am I wrong, or perhaps am I supposed to doing something else in
addition to this? I'd like to disable this client while I re-build it
as a Linux system. The client continues to be backed up, and I'm
afraid that if I proceed with the upgrade, all of my other systems
will be delayed in backing up.
I found that I had to comment the Job and the Client sections for the
machine to be excluded.
Rowdy
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
