Skip to main content
Version: 7.3

Wasabi storage

Introduction​

The Wasabi storage page in Backup Administration for Microsoft 365 allows administrators to configure Wasabi as an Amazon S3-compatible storage target, including the required storage settings, Wasabi-specific options, connection testing, and the storage status options available after creation.

Wasabi is a high-performance, cost-effective, and Amazon S3-compatible cloud storage service. It provides highly durable and scalable object storage as an alternative to Amazon S3, with a simple pricing model that does not include egress fees or API request charges commonly associated with other cloud providers.

Its scalability, cost efficiency, and security features make it well suited for Backup Administration — particularly for storing backed-up data safely and retrieving it when needed. The Amazon S3 compatibility allows seamless integration with existing workflows and configurations in Backup Administration. For large-scale archiving and backup scenarios, it can keep data organized, secure, and accessible over the long term, supporting compliance, governance, and disaster recovery requirements.

For more information about Wasabi's capabilities and features, see the official Wasabi website and Wasabi documentation.

Configure Wasabi Storage​

When configuring Wasabi Storage, first specify the basic storage settings:

  • Name: Specifies the name of the storage.
  • Type: Select Amazon S3 as the storage type.
  • Role: Set the role to Primary. A Primary storage acts as the main repository for the selected workflow or task, such as email backup or document management. If multiple storages are defined, the storage marked as Primary takes precedence for data storage and retrieval.
  • Priority: Specifies the priority of the storage.

After selecting Amazon S3 as the storage type and setting the Role and Priority, select Wasabi from the service dropdown menu.

Backup Administration provides preconfigured service endpoints for Wasabi. Select the endpoint that best fits your configuration.

Configure the following Wasabi-specific settings:

  • Bucket name: Specifies the name of the bucket created in Wasabi.
  • Version: Specifies the Amazon S3 communication version used with the service endpoint. Wasabi supports both Version 2 and Version 4 of the Amazon S3 communication protocol. Select the version required by your configuration or specified in the Wasabi documentation. In the example shown below, Version 2 is selected.
  • Access Key: Specifies the access key used to authenticate with Wasabi. The access key is provided when you create an access key in the Wasabi Console.
  • Secret Access Key: Specifies the secret access key used to authenticate with Wasabi.

Wasabi storage also supports the following options:

  • Compression: Compresses files to reduce storage space usage.
  • Use single instancing: Keeps only one physical copy of a file in the storage when the same file occurs in multiple locations.

We recommend verifying the connection by clicking Test configuration. After the connection test succeeds, click Save to save the configuration.

Storage status​

After the storage has been created, the Status option becomes available when you open the storage for the first time or select Edit from its context menu.

The storage can have one of the following statuses:

  • Enabled: The storage is active and ready for use. It can accept new data, perform retrieval operations, and participate in workflows such as archiving, backup, or file storage.

  • Disabled: The storage is temporarily turned off and is not used by Backup Administration. It remains in the system but cannot accept new data or participate in workflows until it is enabled again. Backup can continue if an allowed writable replica storage is available. In this case, documents are stored in the replica storage, and when the storage is enabled again, the Storage Replication Job duplicates the files to the primary storage.

  • Unavailable: The storage cannot currently receive data or be used for operations. No operations can be performed with the storage until the issue is resolved and its status returns to Enabled.

  • Removed: The storage has been deleted or disconnected from the system and is no longer available for operations or workflows.