Re: [Bacula-users] Cloud storage and bacula 11

2022-10-20 Thread Chris Wilkinson
I have v11 working with Backblaze B2. Initially I had some failed backups
that left some orphaned volumes on B2. I cleaned those up with a couple of
bconsole scripts and since then it's been OK. I do see some retries=2 or 3
and occasionally some part files fail to upload necessitating a repeat and
clean up of B2 and the cache.

I haven't seen any errors of the type you quote.

The upload speed is ~6MB/s on a 300/50 line so that's what I'd expect.

I marked up some differences with my SD below.

-Chris

On Tue, 18 Oct 2022, 10:58 pm Daniel Rich via Bacula-users, <
bacula-users@lists.sourceforge.net> wrote:

> Has anyone been able to use cloud storage reliably with Bacula 11? I am
> trying to convert from using volumes on local disk to using minio as a
> cloud service without much luck.
>
> The odd thing is, it will work for a time. But if bacula-sd or bacula-dir
> restarts, I end up in a state where the device status shows things like:
>
> Device Cloud (S3 Plugin): "cloudDrive-01" (/tmp/cloudDrive-01) is not open.
>Device is BLOCKED waiting for mount of volume "rpi-0002",
>Pool:rpi
>Media type:  CloudType
>Drive 0 is not loaded.
>
> and I don't see any obvious way to force it to mount the cloud storage
> into that device node -- short of running s3fs to mount the volume as if I
> was doing a restore. I would think that would not be needed since this
> mount request is from a backup.
>
> Restores are another problem, as I have yet to get one to work reliably
> with cloud media. Maybe I just need to tune my settings a bit more, but
> doing a mount of a volume with lots of small files via. s3fs is painful at
> best, and doesn't work at all in the worst case. Having to mount that under
> a specifc directory when I'm running bacula-sd in a docker container is
> even more painful, since it requires reconfiguing and restarting bacula-sd
> any time I want to restore something.
>
> Here's a sample of my config (with passwords/hostnames obsfucated of
> course):
>
> Device {
>   Name = cloudDrive-01
>   Device Type = Cloud
>   Media Type = CloudType
>   Archive Device = /tmp/cloudDrive-01
>   AutomaticMount = yes
>   AlwaysOpen = no -> yes
>   RemovableMedia = yes -> no
>   Label Media = yes
>   Random Access = yes
>   Autochanger = yes -> deleted
>   Maximum Part Size = 50MB
>   Maximum File Size = 50MB
>   Cloud = minio-nas
> }
> Autochanger { -> deleted
>   Name = CloudAutoChangerS3
>   Changer Device = /dev/null
>   Changer Command = ""
>   Device = cloudDrive-01, cloudDrive-02, cloudDrive-03, cloudDrive-04
> }
> Cloud {
>   Name = "minio-nas"
>   Driver = S3
>   HostName = "nas.xxx.com:9000"
>   BucketName = "bacula"
>   AccessKey = "bacula"
>   SecretKey = "xx"
>   Protocol = HTTP
>   UriStyle = "Path"
>   Truncate Cache = "AfterUpload" -> no  I keep the cache for faster
> restores
>   Upload = "EachPart" -> atendofjob
>   Region = us-xxx-1
>   MaximumUploadBandwidth = 100MB/s ->1000
> }
>
>
>
> Dan Rich  
> http://www.employees.org/~drich/
> "Step up to red alert!" "Are you sure, sir?
> It means changing the bulb in the sign..."
> - Red Dwarf (BBC)
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Cloud storage and bacula 11

2022-10-18 Thread Daniel Rich via Bacula-users
Has anyone been able to use cloud storage reliably with Bacula 11? I am trying 
to convert from using volumes on local disk to using minio as a cloud service 
without much luck.

The odd thing is, it will work for a time. But if bacula-sd or bacula-dir 
restarts, I end up in a state where the device status shows things like:
> Device Cloud (S3 Plugin): "cloudDrive-01" (/tmp/cloudDrive-01) is not open.
>    Device is BLOCKED waiting for mount of volume "rpi-0002",
>        Pool:        rpi
>        Media type:  CloudType
>    Drive 0 is not loaded.
and I don't see any obvious way to force it to mount the cloud storage into 
that device node -- short of running s3fs to mount the volume as if I was doing 
a restore. I would think that would not be needed since this mount request is 
from a backup.

Restores are another problem, as I have yet to get one to work reliably with 
cloud media. Maybe I just need to tune my settings a bit more, but doing a 
mount of a volume with lots of small files via. s3fs is painful at best, and 
doesn't work at all in the worst case. Having to mount that under a specifc 
directory when I'm running bacula-sd in a docker container is even more 
painful, since it requires reconfiguing and restarting bacula-sd any time I 
want to restore something.

Here's a sample of my config (with passwords/hostnames obsfucated of course):
> Device {
>   Name = cloudDrive-01
>   Device Type = Cloud
>   Media Type = CloudType
>   Archive Device = /tmp/cloudDrive-01
>   AutomaticMount = yes
>   AlwaysOpen = no
>   RemovableMedia = yes
>   Label Media = yes
>   Random Access = yes
>   Autochanger = yes
>   Maximum Part Size = 50MB
>   Maximum File Size = 50MB
>   Cloud = minio-nas
> }
> Autochanger {
>   Name = CloudAutoChangerS3
>   Changer Device = /dev/null
>   Changer Command = ""
>   Device = cloudDrive-01, cloudDrive-02, cloudDrive-03, cloudDrive-04
> }
> Cloud {
>   Name = "minio-nas"
>   Driver = S3
>   HostName = "nas.xxx.com:9000"
>   BucketName = "bacula"
>   AccessKey = "bacula"
>   SecretKey = "xx"
>   Protocol = HTTP
>   UriStyle = "Path"
>   Truncate Cache = "AfterUpload"
>   Upload = "EachPart"
>   Region = us-xxx-1
>   MaximumUploadBandwidth = 100MB/s
> }
>


Dan Rich 
http://www.employees.org/~drich/
"Step up to red alert!" "Are you sure, sir?
It means changing the bulb in the sign..."
- Red Dwarf (BBC)
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users