Change Details

cloudservices2005-dev are, apparently, failing. However, they do not fail fast, they have been "producing a backup" for 3 days already, causing clogging on the general backup system. The most likely cause is that the pre-script is failing and getting stuck, causing a huge amount of queuing on general backups, as concurrency is limited to avoid killing the storage system for too many writes. I am going to kill the non-finishing backup process and then remove the 2 configured backups out of rotation to prevent more bacula issues and delay to other hosts, but the host should be checked (or the pre script reviewed).

cloudservices2005-dev are, apparently, failing. However, they do not fail fast, they have been "producing a backup" for 3 days already, causing clogging on the general backup system. The most likely cause is that the pre-script is failing and getting stuck, causing a huge amount of queuing on general backups, as concurrency is limited to avoid killing the storage system for too many writes. Alternatively, the host is in a bad state, network-wise, causing huge timeouts. I am going to kill the non-finishing backup process and then remove the 2 configured backups out of rotation to prevent more bacula issues and delay to other hosts, but the host should be checked (or the pre script reviewed).

cloudservices2005-dev are, apparently, failing. However, they do not fail fast, they have been "producing a backup" for 3 days already, causing clogging on the general backup system. The most likely cause is that the pre-script is failing and getting stuck, causing a huge amount of queuing on general backups, as concurrency is limited to avoid killing the storage system for too many writes. Alternatively, the host is in a bad state, network-wise, causing huge timeouts. I am going to kill the non-finishing backup process and then remove the 2 configured backups out of rotation to prevent more bacula issues and delay to other hosts, but the host should be checked (or the pre script reviewed).