# 27 Using Wasabi Storage

Wasabi Storage is an independent third-party provider of storage account services. Wasabi storage is compatible with Amazon S3 object storage and is available for use through N2WS. Storing snapshots with Wasabi instead of S3 allows customers to save on their long-term storage costs.

{% hint style="info" %}
Because Wasabi is an external cloud storage provider, customers should be aware that Data Transfer charges to the Internet will be applied by their cloud provider for data sent to Wasabi.
{% endhint %}

A Wasabi repository is based on a bucket in the Wasabi system. Wasabi repositories can be used to store snapshots for both AWS and Azure policies. You can cross-cloud backups by going from N2WS on AWS to Wasabi or from N2WS on Azure to Wasabi.

{% hint style="warning" %}
* Make sure that your license supports Wasabi.
* Enable **Wasabi Cloud** as one of your UI defaults in N2WS **Server Settings > General Settings > User UI Default**.
* Immutable backups are _not_ supported for Wasabi repositories.
* Wasabi Repository buckets may _not_ be versioned.
* _Don't_ rename a Wasabi bucket after selection as a repository as the copy will fail.
{% endhint %}

## 27.1 Adding a Wasabi Account to N2WS

Authentication to Wasabi using user-specified credentials is required first for N2WS to access a Wasabi bucket.&#x20;

{% hint style="info" %}
Authentication of Wasabi accounts is by **Access Key ID** and **Secret Access Key** _only_.
{% endhint %}

* Create a Wasabi account in N2WS with the required credentials.
* Create a Wasabi repository in any bucket accessible to the specified account. See section ‎[27.2](#id-27.2-the-wasabi-repository).

&#x20;**To create a Wasabi account**:

1. Log on to N2WS using the root username and password used during the N2WS configuration.
2. Select the **Accounts** tab.
3. In the ![](https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FqWDrQPyY1nKscRhgQr7i%2Fimage.png?alt=media\&token=8b116af5-1c1b-4bf9-929d-6dc551100837) **New** menu, select **Wasabi Account**.<img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FR0Sce2YdxfXyHsiuGBlf%2Fimage.png?alt=media&#x26;token=f216a23d-5234-480f-a367-801bc605c5de" alt="" data-size="original">.
4. Complete the New Account screen using the App registration view information.
   1. **Name** – Name for this N2WS account.
   2. **User** – The N2WS user that this account belongs to. See section [‎18](18-user-management).
   3. **Access Key ID** - ID provided by N2WS for authentication.
   4. **Secret Access Key** - Key provided by N2WS for authentication.

<figure><img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FUiNIe5sWkUOp1dfgKYoD%2FWasabi%20account.png?alt=media&#x26;token=19e1c65d-6f6a-45c4-8dfa-18ed42ada097" alt=""><figcaption></figcaption></figure>

## 27.2  The Wasabi Repository

Wasabi repositories are where backups of SQL servers are stored. Wasabi repositories can also be used to store disk snapshots via a Lifecycle policy or serve as cross-cloud storage for AWS volume snapshots via a Lifecycle policy. For further details, see section [‎21.](21-managing-snapshots-with-lifecycle-policies)

{% hint style="warning" %}
* A single Wasabi container can have multiple repositories.
* Wasabi buckets may _not_ be versioned.
* A Wasabi bucket _cannot_ be renamed after using it as a repository as the copy will fail.
{% endhint %}

### 27.2.1  Configuring a Wasabi Repository

<figure><img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2F1HpQodMxVu6oogAo4pss%2FStorage%20repositories.png?alt=media&#x26;token=9a3bc008-1af9-4cac-9237-8219a0d008d6" alt=""><figcaption></figcaption></figure>

#### To configure a Wasabi Repository:

1. In N2WS, select the **Storage Repositories** tab.
2. In the ![](https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FsJzDBZO2cPyNYxmljKql%2Fimage.png?alt=media\&token=eba176fd-44b1-4238-8323-5c69e7b792d0) **New** menu, select **Wasabi Storage Repository**.
3. In the **Storage Repository** screen, complete the following fields, and then select **Save**.
   1. **Name** - Type a unique name for the new repository, which will also be used as a folder name in the Wasabi Repository container. Only alphanumeric characters and the underscore are allowed.
   2. **Description** - Optional brief description of the contents of the repository.
   3. **User** – Select the user in the list.
   4. **Account** - Select the account that has access to the repository.
   5. **Wasabi S3 Bucket Name** – Select the name of the S3 bucket from the list.&#x20;

{% hint style="warning" %}
* Do _not_ rename this bucket after selection for the Repository as the copy will fail.
{% endhint %}

<figure><img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FLYIiFVxNn6c6j0t93u1S%2Fnew%20Wasabi%20repository.png?alt=media&#x26;token=63c6c741-c032-4b75-af68-b266838fc02d" alt=""><figcaption></figcaption></figure>

### 27.2.2  Deleting a Wasabi Repository

You can delete all snapshots copied to a specific Wasabi repository.

{% hint style="info" %}
Deleting a repository is _not_ possible when the repository is used by a policy. You must change the policy’s repository to a different one before you can delete the target repository.
{% endhint %}

**To delete a Wasabi repository**:

1. Select the **Storage Repositories** tab.
2. Select the repository to delete.
3. Select ![](https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FzpMsc0puxKB1eK1EivVR%2Fimage.png?alt=media\&token=ff0b874c-e1ec-48d3-82ad-9a3cfdc42d50) **Delete,** and confirm.

<figure><img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FQuHNQVcKMmmJdRcygoe8%2FWasabi%20delete%20repository%20cropped.png?alt=media&#x26;token=1662ca7f-d22c-45db-9505-b57f49553c33" alt=""><figcaption></figcaption></figure>

### 27.3  Recovering from a Wasabi Repository

1. In the **Backup Monitor,** select the **Cloud** button for Wasabi <img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FLEEmje6AgNY86RTS88pJ%2Fimage.png?alt=media&#x26;token=d3e87ff9-b93d-43ec-b67d-dc324a91cce8" alt="" data-size="line">.
2. To minimize the top bars, select the up arrow in the top right corner. To open the filters dialog box, select the filter icon ( <img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FEh5gCM5lNcG2XnrPapvz%2Fimage.png?alt=media&#x26;token=64e9eae6-1118-4f5f-ac51-b07656754da1" alt="" data-size="line">).&#x20;

<figure><img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2F2R8kJUD6MT7yjABPDhAt%2Fimage.png?alt=media&#x26;token=618b43f1-4ce1-4ac1-ab3b-d95aa7d24918" alt=""><figcaption></figcaption></figure>

3. Filter as necessary by type of target, policies, users, accounts, backup status, and freezer status.

<figure><img src="https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FEY2iy1xIc84X57Gpo7sS%2Fimage.png?alt=media&#x26;token=ee732eb3-6d28-44bb-871a-e89aedac3163" alt=""><figcaption></figcaption></figure>

&#x20; 4\.  Select a backup, and then select ![](https://2595576055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkJozMa5ikvBn2dFyUwAB%2Fuploads%2FoX2nZKzeJGNb2OC8qJCv%2Fimage.png?alt=media\&token=1a8a39f0-f820-46f9-8c80-2794b0477622)  **Recover**. The Recover screen opens. For backups with multiple resource types as targets, the Recover screen will have a separate tab for each type.

&#x20; 5\.  Follow the recovery instructions for the resource type as described in section [‎10](10-performing-recovery).
