Hi,
On 6/30/2006 8:51 AM, Przemysław Staniszewski wrote:
> Arno Lehmann wrote:
>
>>I have tried to help you, but you did not supply any useful informaton.
>>
>>Debug logs from bacula-dir and actual console output, together with
>>configuration samples would be useful. Without these, I don't think
>>anybody can help you any further.
>>
>
> I happens one again (1.38.9). In log's there no information about it.
Today, I tested 1.38.11 and the problem that rescheduled jobs end in
some inconsistent state has disappeared. (Still I get no job report for
them, but that is something I won't investigate now.)
> All it happens it was something like that: when I look after 2 days to
> bconsole and
> run status directory i can see only:
>
> Running Jobs:
> something like _job_name_ is waiting on _client_name_ to connect to
> storage file.
> all jobs scheduled after this one was canceled.
Try 1.38.11 - there are some fixes to the scheduler in there. I don't
understand how they are related to what you observed, but at least here,
the problem has disapperaed.
> (I couldn't paste output from console - maybe next time :( )
> And in my director con'f file there was SD Connect Timeout = 4 minutes.
> So the entry should not bee there ?
> Right? Then I realize if another jobs scheduled in this time to - take
> more then 4 minutes the first one be canceled.
Erm. I never needed to modify the timeout values, so I have no
experiences there. I know the default timeouts are quite long, but that
never bothered me.
> So it's my new config file for director:
>
> Director { # define myself
> Name = backup-dir
> DIRport = 9101 # where we listen for UA connections
> QueryFile = "/usr/lib/bacula/query.sql"
> WorkingDirectory = "/var/lib/bacula"
> PidDirectory = "/var/run"
> Maximum Concurrent Jobs = 1
> FD Connect Timeout = 1 minutes
I would comment out this setting, too, and rather use a run before job
script to ensure the clients are up and the FD is running. But that
might be a matter of taste.
> #SD Connect Timeout = 4 minutes
> # jesli beda 2 na ten sam czas to jedno po 4 minutach
> # sie przeterminuje
> Password =
> Messages = Daemon
> }
>
> Schedule {
> Name="KopiaZLanu"
> Run = Incremental mon-thu at 08:30
> Run = Full fri at 08:30
> #Run = Incremental fri at 12:26
> }
>
> Storage {
> Name = File
> Address =
> SDPort = 9103
> Password =
> Device = FileStorage
> Media Type = File
> }
>
> Catalog and Messages of course...
>
> Pool {
> Name = Default
> Pool Type = Backup
> Recycle = yes # Bacula can automatically recycle
> Volumes
> AutoPrune = yes # Prune expired volumes
> Volume Retention = 60 days # one year
> Maximum Volume Bytes = 102949672960
> #Maximum Volume Files = 2 #
> Accept Any Volume = yes # write on any volume in the pool
> # Label Format = "BackupFile-"
> # Use Volume Once = yes
> }
>
> Console..
> Client {
> Name = DanielKaminski
> Address =
> FDPort = 9102
> Catalog = MyCatalog
> Password =
> File Retention = 30 days # 30 days
> Job Retention = 30 days # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
> Job {
> Name = "xxBackup"
> JobDefs = "JobDefxx"
> Write Bootstrap = "/var/lib/bacula/xx.bsr"
> Client = xx
> FileSet = "FileSetxx"
> Rerun Failed Levels = yes
> Reschedule On Error = yes
> Reschedule Times = 5
> Reschedule Interval = 1 hours
> Max Run Time = 220 minutes
> #Max Wait Time = 2 minutes
> #Max Start Delay = 2 minutes
> }
>
> JobDefs {
> Schedule = "Schedulexx"
> Name = "JobDefxx"
> Type = Backup
> Storage = File
> Messages = Standard
> Pool = Default
> Priority = 10
> Level = Full
> }
>
>
> Job {
> Name = "RestoreFilesxx"
> Type = Restore
> Client = xx
> FileSet="Filexx"
> Storage = File
> Pool = Default
> Messages = Standard
> Where = /tmp/bacula-restores
> #Max Wait Time = 2 minutes
> }
>
> FileSet {
> Name = "FileSetxx"
> Include {
> Options {
> signature = MD5
> }
> File =
> }
> Exclude {
> File =
> }
> }
>
> So, from line with !!! to here, for any client in my lan its only copy
> of that with another Client Name, File Set , Schedule Time and Password.
> I start 2 client and the same time. for example for that Schedule
> "KopiaZLanu" another job is planned.
>
> In logs is only information about successfully complete previous jobs.
>
> Is there any option to get more verbose logs?
Yes, you can run the DIR with debug output, for example like 'bacula-dir
-c /etc/bacula/bacula-dir.conf -d 200 2>&1 >>/tmp/bacula-dir.debuglog'
or similar.
> If you don't understand some part of it please write me, I will try to
> be more clearly.
>
> I will be unhappy to buy some commercial programs to backup 30
> computers. :(
Understandable...
Arno
> Best regards.
>
> ps. I think because host was down.
>
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
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
