Wasabi storage
Wasabi is a high-performance, cost-effective, and Amazon S3-compatible cloud storage service designed to provide fast, reliable, and affordable storage solutions. Positioned as a direct alternative to Amazon S3, Wasabi offers highly durable and scalable object storage with a simple pricing model—free from egress fees or API request charges often associated with other cloud providers.
Wasabi is an excellent storage option for Backup Administration, especially for managing backed-up data. With its combination of scalability, cost-efficiency, and robust security features, Wasabi ensures that your valuable data is safely stored and easily accessible whenever needed. Its Amazon S3 compatibility allows seamless integration with Backup Administration, leveraging existing workflows and configurations to create a reliable and efficient data backup solution.
The storage demands of modern businesses often include the need for cost-efficient yet high-performance options. Wasabi excels in these areas by providing a storage platform designed for large-scale archiving and backup tasks. Backup Administration users can leverage Wasabi to keep backed-up data organized, safe, and accessible over the long term, aligning with best practices for data compliance, governance, and disaster recovery.
For more details about Wasabi’s capabilities, features, and configuration options, visit the official Wasabi website and its documentation section.
How to configure the Wasabi Storage
First, you set the Storage name, the Type (Amazon S3), the Role (Primary), and the Priority. The Primary role means, that the storage acts as the main repository for the selected workflow or task (e.g., email backup or document management). It is prioritized for data storage and retrieval. If multiple storages are defined, the one marked as “Primary” will take precedence over others (e.g., for storing live or frequently accessed data).
Once the storage type (Amazon S3) is selected and the Role and Priority is set, you will be able to choose Wasabi from the service dropdown menu. In Backup Administration, the service endpoints for Wasabi are preconfigured, but you can choose a more fitting option from the menu.
Next, configure the Bucket name you created on the Wasabi store.
The version specifies which communication version to use for the service endpoint (the service version is specified by the endpoint service). If you are using Amazon S3, you can use Service Version 2 or 4. Wasabi supports both Version 2 and Version 4 of the Amazon S3 communication protocol. Choose the version that matches your needs or the one specified in Wasabi’s documentation. In this configuration, Version 2 is selected.
The Access Key and Secret Access Key are required to authenticate with Wasabi storage. They are provided when you create an access key in the Wasabi Console.
This store type also supports compression and single instancing, which can save you a lot of space. Always use the Test configuration button to verify the connection to the Wasabi bucket. Once the test succeeds, click Save to finalize the setup.
After creating the storage, opening it for the first time or selecting the Edit option from the context menu will display an additional feature in the Storage Repository window: the Status option, which can be:
- Enabled: The storage is active and ready for use in the system. It can accept new data, perform retrieval operations, and serve as part of workflows like archiving, backup, or file storage.
- Disabled: The storage is temporarily turned off and will not be used by Backup Administration. It remains in the system but cannot accept new data or participate in workflows until re-enabled. The backup will still function if there is an allowed writable replica storage. In this case, documents will be stored in the replica storage, and when the storage is re-enabled, the Storage Replication Job will duplicate the files to the primary storage.
- Unavailable: You no longer wish to use the storage. In this case, it will not be able to receive anything. No operations can be performed with this storage until the issue is resolved and its status returns to Enabled.
- Removed: The storage has been deleted or disconnected from the system. It is no longer available for any operations or workflows.
