How do I use Bacula Enterprise Edition with Wasabi?
To use Bacula Enterprise Edition with Wasabi, follow the configuration steps below.
Create a Wasabi API key set (if you do not already have one) and S3 bucket for Bacula in the Wasabi web portal.
On the Bacula Storage Daemon (SD), the S3 Cloud Plugin for Bacula Enterprise Edition must to be installed. This will enable the SD to sync your data to S3-compatible cloud storage providers.
With the S3 Cloud Plugin installed, configure a Cloud{} and Device{} resource in your Bacula SD configuration file (bacula-sd.conf) as follows:
Cloud {
Name = "WasabiS3-cloud"
Driver = "S3"
HostName = "s3.wasabisys.com"
BucketName = "bvolumes"
AccessKey = "GL9ZJQE9BDQ9KPI1GNRF"
SecretKey = "zlqlqeVYpWVBBojvddhvN034oldJev9XRwAZMg45"
Protocol = "HTTPS"
UriStyle = "VirtualHost"
Truncate Cache = "AfterUpload"
Upload = "EachPart"
Region = "us-east-1"
MaximumUploadBandwidth = 1MB/s
}
Device {
Name = "c7beesd1-wasabiS3-dev"
Device Type = "Cloud"
Cloud = "WasabiS3-cloud"
MaximumPartSize = 2M
MaximumFileSize = 2M
MediaType = "cloudS3-media"
ArchiveDevice = "/backup/cloud"
LabelMedia = "Yes"
RandomAccess = "Yes "
AutomaticMount = "Yes"
RemovableMedia = "No"
AlwaysOpen = "No"
MaximumConcurrentJobs = 5
}
The Bacula directive (key = value pair) called BucketName must match the name of the bucket that you created in the Wasabi web interface. The access key and secret key can also be exported from the Wasabi interface. The Bacula cloud driver must be “S3”, in this case. Instead of a single Device{} resource, you can also dene a virtual Autochanger{} with more than one device. For the Region, only us-east-1 can be selected with Wasabi at this point in time.
Once the Storage Daemon configuration has been applied, create a backup job on the Bacula Director (DIR) as usual and point the Storage directive on the DIR to the newly created cloud target. Backup and restore work without any issue in combination with Wasabi cloud storage.
This example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in Service URLs for Wasabi's Storage Regions.