Hello,
Please insure that the PluginDirectory is defined in the
bacula-sd.conf file. Then check and ensure that the plugin is in
that directory.
Finally, the following commands could potentially help us:
stop the storage daemon
start it by hand in a shell window with -d20 as one of the
options.
bconsole
status storage=xxxx
where xxxx is the name of any storage device.
The status of the plugins should be sent to the stdout of the
shell window where you restarted the storage daemon.
The output of the compile and link of the storage daemon would
possibly be helpful.
Best regards,
Kern
On 7/17/19 5:40 PM, Bryan Sockel via
Bacula-users wrote:
Hey Guys,
Trying to setup a new backup server to run backups to
an AWS S3 Bucket. I was able build both required version of the
libs3 driver and bacula community install (9.4.4) and all
appears to be correct. I need a little help setting up my
bacula-dir and bacula-sd files in order to use the backup. I
think i have the Bacula-SD file configs correct, but beyond that
i am unsure of how to proceed.
bacula-sd.conf
Device {
Name = CloudStorage
Device Type = Cloud
Cloud = S3Cloud
Archive Device = /backups/CloudStorage
Maximum Part Size = 10000000
Media Type = CloudType
LabelMedia = yes
Random Access = Yes;
AutomaticMount = yes
RemovableMedia = no
AlwaysOpen = no
}
Cloud {
Name = S3Cloud
Driver = "S3"
HostName = "s3.amazonaws.com"
BucketName = "s3-test"
AccessKey = "AccessKey"
SecretKey = "SecretKey"
Protocol = HTTPS
UriStyle = VirtualHost
Truncate Cache = AfterUpload
Upload = EachPart
Region = "us-east-1"
MaximumUploadBandwidth = 5MB/s
}
_______________________________________________
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