This is the script I use in a run after clause in the cloud backup job.
This does all cloud volumes without bothering to check what went and what
didn't. Most of the time it does nothing, just resending parts when there
is an upload error.
#!/bin/bash
#upload to cloud
sleep 10 #wait 10secs
echo "c
replies inline below.
A lot of things can affect reliability, and who knows, maybe there are
> intermittent issues during backup jobs and cloud
> volume part uploads which are out of your control causing some parts to
> fail to be uploaded during the backup job itself, but
> those issues do not
I had exactly that problem with S3/Backblaze. I would sometimes get a "no
tomes available" error message. I run a script after to upload the part
files for all volumes all over again. The driver seems smart enough to not
upload part files that are already there.
-Chris-
On Fri, 21 Feb 2025, 02:21
On Sat, 22 Feb 2025 at 18:03, Rob Gerber wrote:
> I don't usually use bacularis to edit director or storage resources because
> it strips out all the comments (baculum also does this, IIRC). I understand
> why it does that, since it has to parse the configuration and by definition
> the data af
On Sat, 22 Feb 2025 at 18:01, Rob Gerber wrote:
>> What error message did you experience with Amazon driver?
>
> I saw errors like this:
>
> 22-Feb 10:28 td-bacula-sd JobId 97: Error: B2-TGU-Inc-0048/part.1
> state=error retry=10/10 size=263 B duration=56s
> msg=/opt/bacula/plugins/aws_clo
Replies inline below.
Regards,
Robert Gerber
402-237-8692
r...@craeon.net
On Thu, Feb 20, 2025 at 8:40 PM Marcin Haba wrote:
> On Fri, 21 Feb 2025 at 03:21, Rob Gerber wrote:
> > I'm using the s3 driver instead of the amazon driver. I read that the
> new amazon driver is much better than the s
Hello,
Starting a new thread for this subject.
I don't usually use bacularis to edit director or storage resources because
it strips out all the comments (baculum also does this, IIRC). I understand
why it does that, since it has to parse the configuration and by definition
the data after a # sig
> I've still two question.
More question rised.
Seems that, even using a temporary file media, copy is more performative
then a full backup.
For example, on a test system with an LTO5 tape, full backup took 14 hour,
while copy tape to file media took 4 hour, and file back to tape 3 hour; so,
m
