Hello. I have problem with this.
Job {
Name = "Flows"
Client = prodisz-fd
JobDefs = "FlowsJob"
Max Wait Time = 3h
}
It's should cause canceling job if job flows stuck for more than 3h (for eg. if
no volume).
But... backup id canceled if previous backup is running for long time and flows
backup is waiting for free robot more than 3h. I's not started yes, it have
status "created, but not yet running". How to fix this?
I'm trying to make config that cancel all backups are hangs for more than 3h
but no waiting for first start.
+----------------------------------------------------------------------
|This was sent by prze...@tkk.net.pl via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+----------------------------------------------------------------------
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
