LogoLogo
  • 1 Introduction to N2WS
  • 2 Installing and Upgrading N2WS
  • 3 Start Using N2WS
  • 4 Defining Backup Policies
  • 5 Consistent Backup with N2WS
  • 6 Windows Instances Backup
  • 7 Linux/Unix Instances Backup
  • 8 Using Elastic File System (EFS)
  • 9 Additional Backup Topics
  • 10 Performing Recovery
  • 11 Disaster Recovery
  • 12 Cross-Account DR, Backup, and Recovery
  • 13 File-Level Recovery
  • 14 Tag-based Backup Management
  • 15 Resource Control
  • 16 Security Concerns and Best Practices
  • 17 Alerts, Announcements, Notifications, and Reporting
  • 18 N2WS User Management
  • 19 N2WS IdP Integration
  • 20 Configuring N2WS with CloudFormation
  • 21 Managing Snapshots with Lifecycle Policies
  • 22 Configuring Workers
  • 23 Capturing and Cloning in Network Environments
  • 24 Orchestrating Recovery Scenarios
  • 25 Monitoring Costs and Savings
  • 26 Using N2WS with Azure
  • 27 Using Wasabi Storage
  • Appendix A -Recommended Configuration for Copy to S3
  • Appendix B - Agents Configuration Format
  • Appendix C - Time Zones
  • Appendix D - Datadog Integration
  • Appendix E - Splunk Integration Support
  • Appendix F - Resetting Root Password or MFA
  • Appendix G - Securing Default Certificates on N2WS Server
Powered by GitBook
On this page
  • 27.1 Adding a Wasabi Account to N2WS
  • 27.2 The Wasabi Repository
  • 27.2.1 Configuring a Wasabi Repository
  • 27.2.2 Deleting a Wasabi Repository

Was this helpful?

Export as PDF

27 Using Wasabi Storage

Previous26 Using N2WS with AzureNextAppendix A -Recommended Configuration for Copy to S3

Last updated 7 days ago

Was this helpful?

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.

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.

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.

  • 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.

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.

Authentication of Wasabi accounts is by Access Key ID and Secret Access Key only.

  • Create a Wasabi account in N2WS with the required credentials.

  • Create a Wasabi repository in any bucket accessible to the specified account. See section ‎.

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 New menu, select Wasabi Account..

  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 .

    3. Access Key ID - ID provided by N2WS for authentication.

    4. Secret Access Key - Key provided by N2WS for authentication.

27.2 The Wasabi Repository

  • 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.

27.2.1 Configuring a Wasabi Repository

To configure a Wasabi Repository:

  1. In N2WS, select the Storage Repositories tab.

  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.

  • Do not rename this bucket after selection for the Repository as the copy will fail.

27.2.2 Deleting a Wasabi Repository

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

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.

To delete a Wasabi repository:

  1. Select the Storage Repositories tab.

  2. Select the repository to delete.

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

In the New menu, select Wasabi Storage Repository.

Select Delete, and confirm.

‎21.
‎18
27.2