Thanks for that tip. I didn't see anything in the joblog about retries so
assumed it wasn't doing that.
I added a runafter runscript to the cloud job.
Runscript {
RunsOnFailure = yes
RunsOnClient = no
FailJobOnError = no
RunsWhen = "After"
Console = "cloud storage=cloud-sd all
On 11/30/23 03:29, Chris Wilkinson wrote:
I use Backblaze B2. It is S3 compliant but about the lowest cost I could find,
certainly a fraction of the price of AWS.
It works mostly OK except for errors of the kind in the log below. The "no tomes" error is from B2 when there are no upload
slots a
Não sei se isso resolve para o seu caso, mas no meu caso resolveu.
Autochanger {
Name = Bacula-SD1
Device = Bacula-SD1-Dev1, Bacula-SD1-Dev2
Changer Command = ""
Changer Device = /dev/null
}
Device {
Name = Bacula-SD1-Dev1
Media Type = Diretorio-Local
Archive Device = /tmp/bacula
Thanks, Chris.
My company is looking to align with companies who are not in the 5/9/14 eyes
alliances, hence I'm now looking at Koofr (Slovenia).
Backblaze is domiciled in the USA.
Best,
On 2023-11-30 5:29 a.m., Chris Wilkinson wrote:
> I use Backblaze B2. It is S3 compliant but about the l
I use Backblaze B2. It is S3 compliant but about the lowest cost I could
find, certainly a fraction of the price of AWS.
It works mostly OK except for errors of the kind in the log below. The "no
tomes" error is from B2 when there are no upload slots available
temporarily. B2 says that the user ap
