Home > Technical Blog > Bacula with Geyser Data S3 Storage

Bacula with Geyser Data S3 Storage

Updated 1st November 2024, Aleksandar

Geyser Data (www.geyserdata.com) is a Tape Archive Platform-as-a-Service which is globally accessible over an S3 proxy. Bacula Storage Daemon (SD) is able to utilize this service via Bacula S3 Cloud storage plugin.

Geyser Data Tiering

Geyser Data implements implicit (cannot be configured or reconfigured) migration of the data in between the initial CACHE (disk) and TAPE tiers. It will migrate every file bigger than 500 bytes, at a preset time, once it becomes older than 24 hours, and once the CACHE layer becomes full.

Consequently, since it is smaller than 500 bytes, the .part1 file, of the Bacula cloud volume, will never be migrated from CACHE to TAPE tier.

Geyser Data tiering is fully autonomous and Bacula S3 Cloud storage plugin integrates with it seamlessly, there is no additional actions, configuration or products needed to execute backups and restores .

Configuration

Prerequisites

  • Bacula Storage Daemon with Bacula Cloud S3 storage plugin installed.
  • Registered Geyser Data account.

It is important to notice how parameters from Geyser Data Console correspond to specific Cloud resource directives’ values.

Geyser Data account parameters

From Geyser Data Console (console.geyserdata.com):

Name: Bacula

s3Url: s3://boulderlab.geyserdata.com/baculatest-xxxxxxxx-yyyy-zzzz-wwww-qqqqqqqqqqqq/

Key: ABCDEF1234567

Secret: ABCDEFGHIJKL1234567890XYZWQHKJLSUPTRVGFR

Bacula Cloud resource definition

From the bacula-sd.conf file:

Cloud {

Name = “GeyserData”

AccessKey = “ABCDEF1234567”

BlobEndpoint = “https://boulderlab.geyserdata.com”

BucketName = “baculatest-xxxxxxxx-yyyy-zzzz-wwww-qqqqqqqqqqqq”

Driver = “Amazon”

HostName = “boulderlab.geyserdata.com”

Protocol = HTTPS

SecretKey = “ABCDEFGHIJKL1234567890XYZWQHKJLSUPTRVGFR”

UriStyle = Path

}

Leave a comment

Your email address will not be published. Required fields are marked *