Hi to all. I'm running Bacula 11.0.6 on docker, using images built in-house over CentOS7, using the RPMs from https://www.bacula.org/packages
The Storage is configured with some AWS S3 devices with a local cache. Some of the Jobs have a only-Full schedule, and in certain moments, those jobs got stuck. Their status is running, but no data is written to the device cache. On the status storage command, the device is listed as: Device Cloud (S3 Plugin): "AWSS3-VTL-D1" (/var/bacula/awss3-cache) is not open. Device is being initialized. Drive 0 is not loaded. Available Cache Space=13.36 TB == When this occurs, the affected job keeps the running state, and any job that starts execution after it gets the same status: Running state and "Device is being initialized". We're treating this by setting all jobs to a Full+Incr schedule, even if those schedules make no sense to our environment. Even so, in the last month we started to see this behaviour on Incr jobs. Any help on this matter? Any log I should post? -- Humberto Fraga Ribeiro _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
