Results (1310)

Wasabi Object Replication With Veeam v12 Backup Copy Job

Wasabi Object Replication With Veeam
English
English
How do I use Wasabi Object Replication with Veeam v12 Backup Copy Job? Wasabi is a member of Veeam's cloud partner ecosystem. We have worked with Veeam closely to offer both a seamless implementation and a smooth transition to cloud storage. For more information on how Veeam works with Wasabi, refer to Veeam and Wasabi Solution Brief . This article describes the procedure to use Wasabi Object Replication to replicate objects from one region to another within the same continent.  This can be used to recover from natural disasters or other events in a region.   This article covers only Backup Copy Jobs .  Reference the articles listed in the menu to the left for Scale-Out Backup Repositories (SOBRs) and Direct to Object Storage . The data restoration process is handled by your specific backup software application. As there are many, potential variables that will affect your unique environment, Wasabi strongly recommends

Extractor Profiles API in Wasabi AiR

APIs for Wasabi AiR
English
English
Extractor profiles contain configurations for multiple extractors, which are applied at the container level.  Prior to initiating analysis, the extractor profile should be created and configured through the Extractor Profiles page in the user interface. Listing All Extractor Profiles To list all extractor profiles, make the following request: GET /api/data/h2/extractor-profiles Response { "profiles": [ { "id": "default", "name": "default", "description": "default profile" }, { "id": "5f34150bbcf4bbc4903a5546470bf4b3", "name": "JRG Extractor Profile", "description": "This profile will be for compliance analyzation" }, { "id": "5f3fb8f46d91b2bdbb2249fd8b817ebb", "name": "New Extractor Profile", "description": "Profile for test container" } ] Listing All Enabled Extractors for a Profile To list all currently enabled extractors for a specific profile, make the following request: GET /api/data/h2/extractor-profiles/{id} Response This call returns a list of all currently enabled extractors within the requested extractor profile as well as the individual extractor id (s). Assigning an Extractor Profile to a Container To assign an

Leopard WordPress Plugin With Wasabi

Applications G-M
English
English
How do I use Leopard WordPress plugin with Wasabi? The Leopard WordPress plugin is validated for use with Wasabi. To use this product with Wasabi, please follow the instructions below. Leopard documentation Note that this config example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, please use the appropriate Wasabi service URL as described in this  article . 

Account Types and Glossary for Wasabi Account Control Manager

Product Guides for Wasabi Account Control Manager
English
English
WACM Account Types WACM account types define the account's primary purpose and reflect the tabs presented on the navigation bar in the WACM console. The account types you can access will depend on your tier and user permissions.  The following table begins with the Governance Account, the most inclusive (governing) account level. Account Type Definition Product Access Governance Account A Governance Account is the top-level account in the WACM hierarchy. It contains multiple Control Accounts. A Governance Account is procured through Wasabi Sales and the WACM AG product. With WACM AG capability, you can have a “single pane of glass”—one area—to manage multiple Control Accounts. A Governance Account can manage any tier of account. Wasabi Account Governance (AG) WACM Control Account A Control Account is the second level in the WACM account hierarchy. A Control Account consists of a paying Wasabi account and a related Wasabi

Items API in Wasabi AiR

APIs for Wasabi AiR
English
English
"width": 169, "height": 11 }, "confidence": 0, "language": null, "text": "HIT THAT LIKE BUTTON, NATION!", "text_type": "lines" } ], "thumbnail_path": "video_main_frames/frame-0000000002.jpg", "time": 4.004 } ] }, "next_page": "NP-BAwEBBVRva2VuAf-CAAEDAQVMaW1pdAEEAAEGT2Zmc2V0AQQAAQZQYXJhbXMB_4QAAAAh_4MEAQERbWFwW3N0cmluZ11zdHJpbmcB_4QAAQwBDAAAKP-CAwMDYWxsAAVzdGFydA0tMTExMTEwMC45OTk5BndpbmRvdwIxMAA=" } For an asset that is a document: { "contents": { "img": null, "pages": [ { "images": [ { "image_id": "daea649e947b430acceccc089f653c3f", "image_index": 0, "ocrs": [ { "id": "095a5ca47bda4e0a9db562e23070125c", "item_id": "43b89caeb2fd3c23f25b8431e644cabc", "bounding_box": { "top": 15, "left": 522, "width": 217, "height": 24 }, "confidence": 0, "language": null, "text": "Pilgrim Programming, LLC", "text_type": "lines" } ], "thumbnail_path": "document_pages/thumb-pg-00000-img-00000.png" } ], "page": 0, "ocrs": "optionally, a page can have OCR as well, or it can be embedded in the images within the page", "thumbnail_path": "optionally, a page can have a thumbnail path as well as well as each embedded images thumbnail", "page_id": "a uuid to identify the page, optional, will be available when all query param

Wasabi Stats API Reference

Wasabi Stats API
English
English
The Wasabi Stats API is a way to programmatically access bucket and utilization data for all accounts. By using the Wasabi Stats API, you can access daily summary utilization as well as daily utilizations of all buckets, available at a per-bucket level. Wasabi Stats API requests: https://stats.wasabisys.com . Note that this link is used when requesting data; there is no application or page to access.  These API calls require Wasabi API keys, not WAC API keys. Wasabi API keys used must either be Root keys or have associated billing permissions.  The following endpoints are described: GET /v1/standalone/utilizations GET /v1/standalone/utilizations/bucket GET /v1/standalone/utilizations/bucket/:bucketName GET /v1/standalone/utilizations/bucket/:bucketNumber Stats API Authentication and Security For security reasons, the Stats API caller must use HTTPS, as any non-HTTPS calls will be redirected to HTTPS endpoints. Authentication of Stats API calls

Features of the Wasabi Account Control API

Wasabi Account Control API (WACA) Reference
English
English
charged for all accounts in the production environment. Therefore, only use the test environments for development and testing of the integration with the Wasabi Account Control API. Rate Limiting For security and performance reasons, the Wasabi Account Control API will rate limit the number of requests on a per Wasabi Control Account holder basis against the API methods listed below. These limits are currently: 1000 GET operations/min 100 PUT operations/min 100 POST operations/min 10 DELETE operations/min Any call rates that exceed these limits will be responded with a standard “HTTP 429 Too Many Requests” response. Utilization Metrics Wasabi calculates usage metrics once per day at both a per-bucket and per-account level. These records are stored indefinitely in our systems and can be retrieved on demand. The metrics captured are: "NumBillableObjects": 1, "NumBillableDeletedObjects": 1, "RawStorageSizeBytes": 1000000000, "PaddedStorageSizeBytes": 1000000000, "MetadataStorageSizeBytes": 87, "DeletedStorageSizeBytes": 1000000000, "OrphanedStorageSizeBytes": 0, "MinStorageChargeBytes

Arcserve ShadowXafe With Wasabi

Arcserve Applications With Wasabi
English
English
the Add Replication section, select your Wasabi storage as the "Replicate to" destination, configure the desired replication frequency and click Add.  The Wasabi-replication  storage destination is added to the Replication target. Click Save to save the policy. Designing a local backup protection flow with Cloud Replication services In the example below, we configure a protection flow with a SMB share as a backup destination and enable replication to replicate the backup data to a Wasabi. The local storage that will be used for replication will need to be added as Storage (select the appropriate Storage Type - NFS/SMB/iSCSI) Navigate to the Policies tab on the left hand side and click Add new to create a new policy. In the Add policy window, provide a policy name and select the configured SMB storage as the Storage Destination. Provide the desired frequency to take the snapshots. In the Add Replication

Datadobi Products With Wasabi

Datadobi Applications With Wasabi
English
English
How do I use Datadobi products with Wasabi? Multiple Datadobi products have been validated for use with our object based cloud storage service. For detailed instructions on how to configure these products to work with Wasabi, please click on the appropriate links provided below. For integration with DobiProtect, review DobiProtect With Wasabi . For integration with DobiMigrate, review DobiMigrate With Wasabi .

1—Signing Up for Wasabi

1—Signing Up for Wasabi
English
English
Objectives 1 Sign up for Wasabi and sign in. 2 Work with buckets and objects. 3 Create a user account and access key.  Signing Up You can use your free trial to store up to 1 TB of storage for 30 days, without the requirement of a credit card. You will not be charged to work through the exercises in this quick start tutorial, and you will not be charged for Wasabi until you use it for data storage. For more information about your trial, refer to Trial Data Limit and Trial Expiration . For FAQs and information on Wasabi features and pricing, go to the Wasabi product page . If you choose to delete your Wasabi account after signing up, refer to the instructions in Deleting an Account . Go to www.wasabi.com   to sign up. As a user new to Wasabi, you need to set up an account by completing

Bucket Settings

Bucket Settings
English
English
Accessing Settings Options for a Bucket On the Buckets list, click for the desired bucket. Select Settings . For example: This example shows the Settings panel for the widget-project bucket. Note that when a feature is new, it is highlighted in the tabs (as for Object Replication). Click on the main headings to access different panels of settings: Properties (displayed by default) include these options: Bucket Logging creates a text log file of all access to the bucket. You can specify the target bucket in which to store log files as well as a prefix to include in the log file name. Bucket Versioning is a way to maintain multiple variations of an object in the same bucket. You can then retrieve and restore any version of an object in the bucket. This provides protection against inadvertent removal of an object (such as by overwriting or expiration). You can review

Veritas Backup Exec With Wasabi

Veritas Applications With Wasabi
English
English
Wasabi has been certified for use with Veritas Backup Exec. Veritas Backup Exec is a fast, cost-effective, unified backup and recovery solution for cloud-ready organizations. For more information regarding Backup Exec-Wasabi support, please refer to Backup Exec HCL . To use this product with Wasabi, please follow the instructions below. Please Note: The data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, it is strongly recommended that you seek the guidance of your backup software's technical support team in the event that you encounter difficulty, or have application-specific inquiries. 1. Prerequisites Operational Backup Exec v 22 and above An active Wasabi account A bucket created in the Wasabi account Note: To configure Wasabi for previous Backup Exec versions (v20.4 and above) please click here . 2. Configure Wasabi as Cloud Storage Server

Applications W-Z

Applications W-Z
English
English
...

GET control-accounts

control-accounts
English
English
Get Control Accounts Return a list of all the Control Accounts associated with the Governance Account. URL (GET) /api/v1/control-accounts Parameters Key Name Description Required page List page number No size List page size No id Filter by account id No name Filter by account name No governanceAccountId Filter by account governanceAccountId No status Filter by account status (active, inactive) No wasabiAccountName Filter by account wasabiAccountName No primaryApiKey List primary API key includeApiKey Include API key (true) Request Body None Response { "success": true, "message": "Successfully read!", "data": { "items": [ { "id": 29915, "name": "Cloud co", "category": null, "partnerType": "RESELLER", "accountType": "Company", "status": "Active", "imageUrl": null, "creationDate": "2022-04-07T17:24:14.490Z", "address1": null, "address2": null, "country": null, "city": null, "state": null, "zip": null, "mainPhone": null, "billingPhone": null, "contactEmail": null, "billingEmail": null, "businessNumber": null, "taxId": null, "fiscalNumber": null, "vatNumber": null, "website": null, "governanceAccountId": null, "governanceAccountName": null, "subAccountsCount": 4, "wasabiAccountName": "example

ownCloud With Wasabi

Applications O-R
English
English
How do I use ownCloud with Wasabi? ownCloud is certified for use with Wasabi. To use this product with Wasabi, please following the config guidelines below.    Note that this example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, please use the appropriate Wasabi service URL as described in this  article . 

SXcmd With Wasabi

Applications S
English
English
How do I use SXcmd with Wasabi? Multiple SXcmd products have been validated for use with Wasabi. For detailed instructions on how to configure these products to work with Wasabi, please click on the appropriate links provided below. How do I use s3cmd with Wasabi How do I use s4cmd with Wasabi How do I use s5cmd with Wasabi  

POST members

members
English
English
Post Sub-Account Member Creates a new member for a Sub-Account. URL (POST) /api/v1/members Parameters None Request Body { "subAccountId": ####, "firstName": "", "lastName": "", "username": "", "memberRole": "root", "email": "", "password": "", "passwordResetRequired": true }, Response { "id": ####, "subAccountId": ####, "firstName": "", "lastName": "", "username": "", "memberRole": "root", "email": "", "status": "active", (can have values: Active, Deactivated, Suspended, or Locked) "mfa": false, "imageUrl": null, "creationDate": "2023-12-19T09:35:47.598+00:00", "address1": null, "address2": null, "country": null, "city": null, "state": null, "zip": null, "phone": null },

EditShare With Wasabi

EditShare Applications With Wasabi
English
English
How do I use EditShare with Wasabi? Multiple EditShare products have been validated with Wasabi. For detailed instructions on how to configure these products to work with Wasabi, please click on the appropriate links provided below. How do I use EditShare FLEX Sync with Wasabi? How do I use EditShare FLOW with Wasabi?

Wasabi Console Features

1—Signing Up for Wasabi
English
English
The screen that you see is referenced as the Wasabi Management Console or, simply, the Wasabi Console. It consists of the following components.  Trial Countdown and Menu The red countdown message indicates how much longer your trial account will be active. You can click Upgrade Now  to purchase Wasabi at any time during the trial period. After purchasing Wasabi, this message will no longer appear. Click Menu  to collapse the menu area so that only icons are shown and more screen space is available for your Wasabi Console panel. The menu is divided into three basic areas: Data Access to manage buckets and objects , policies , and access keys Users & Groups to manage groups , roles , and users Your Account to establish account settings and billing information , and access Wasabi Academy (Support) All menu options are described with instructions in the remainder of Getting Started and the Wasabi Cloud Storage: Product Guide

AWS SDK for Go (Golang) With Wasabi

AWS Applications With Wasabi
English
English
}) if err != nil { fmt.Println("Error uploading file:", err) return } fmt.Printf("File uploaded successfully: %s\n", result.Location) } Reading an Object From the Bucket package main import ( "context" "fmt" "io/ioutil" "log" "github.com/aws/aws-sdk-go-v2/aws" "github.com/aws/aws-sdk-go-v2/config" "github.com/aws/aws-sdk-go-v2/service/s3" ) func main() { cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithRegion("us-east-1"), config.WithEndpointResolverWithOptions( aws.EndpointResolverWithOptionsFunc( func(service, region string, options ...interface{}) (aws.Endpoint, error) { if service == s3.ServiceID { return aws.Endpoint{ URL: "https://s3.wasabisys.com", SigningRegion: "us-east-1", }, nil } return aws.Endpoint{}, &aws.EndpointNotFoundError{} }, ), ), ) if err != nil { log.Fatalf("Unable to load SDK config, %v", err) } s3Client := s3.NewFromConfig(cfg) bucketName := "bucket-name" objectKey := "object name with prefix" getObjectOutput, err := s3Client.GetObject(context.TODO(), &s3.GetObjectInput{ Bucket: &bucketName, Key: &objectKey, }) if err != nil { log.Fatalf("Unable to