--- title: "Nutanix Multicloud Snapshot Technology With Wasabi" slug: "nutanix-multicloud-snapshot-technology-with-wasabi" updated: 2026-04-15T21:59:33Z published: 2026-04-15T21:59:33Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt > Use this file to discover all available pages before exploring further. # Nutanix Multicloud Snapshot Technology With Wasabi [Nutanix](https://www.nutanix.com/) [Multicloud Snapshot Technology (MST)](https://www.nutanix.com/blog/zero-compute-deployment-in-mst-powered-dr) AHV (Nutanix Acropolis Hypervisor) virtual machine (VM) and volume group (VG) snapshots to object storage. This article describes the procedure for configuring MST to back up snapshots to Wasabi Hot Cloud Storage and recovering a VM from a snapshot in Wasabi. ## Requirements - An active Wasabi account - Access to the [Wasabi Console](https://console.wasabisys.com) - AOS Version: 7.5.1 and above releases - Hypervisor Version: AHV version compatible with the AOS version - Prism Central (PC) version: Latest GA release compatible with the AOS version - Nutanix cluster should be registered to PC ## Configuring Wasabi 1. Log in to the [Wasabi Console](https://console.wasabisys.com). 2. Create a Wasabi bucket that will hold MST snapshots. See [Creating a Bucket](https://docs.wasabi.com/docs/working-with-buckets-and-objects#creating-a-bucket) for details. Do not enable Object Lock or Versioning, as MST does not currently support them. 3. Create the following policy for a user (created in the next step). See [Creating a Policy](https://docs.wasabi.com/docs/creating-a-policy) for detailed instructions. Replace YOUR_WASABI_BUCKET with the name of your Wasabi bucket. ```json {  "Version": "2012-10-17",  "Statement": [    {      "Sid": "VisualEditor0",      "Effect": "Allow",      "Action": [        "s3:PutObject",        "s3:GetObject",        "s3:AbortMultipartUpload",        "s3:ListBucket",        "s3:DeleteObject",        "s3:GetBucketLocation"      ],      "Resource": [        "arn:aws:s3:::YOUR_WASABI_BUCKET/*",        "arn:aws:s3:::YOUR_WASABI_BUCKET"      ]    }  ] } ``` 4. Create a user and access keys to access your Wasabi bucket. Review [Creating a User Account and Access Key](https://docs.wasabi.com/docs/how-do-i-create-a-sub-user-with-console-access-and-access-and-secret-keys) for details. Assign the previously created policy to the user. - Allow programmatic-only access, not console access. - Do not require Multi-Factor Authentication (MFA). - It is not necessary to assign the user to a group. - Save the access and secret keys in a secure location. ## Configuring Nutanix MST on Prism Central 1. Navigate to Prism Central and Admin center. Go to Marketplace. Click the Get icon for Multicloud Snapshot Technology. 2. Select the required instance type. Select the cluster. Select the Internal Network (which should be Basic VLAN with DNS IP defined). Provide three static IPs from that VLAN. Make sure the VLAN has DHCP scope, and the DNS IP should be defined in that subnet. Click **Next**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 11.54.06 AM.png) 3. Select the “S3 Compatible (Nutanix certified)” option as the object store provider. Provide the details below. Click **Deploy**. > Note that this config example discusses the use of Wasabi's us-east-2 storage region. To use other Wasabi storage regions, please use the appropriate Wasabi service URL as described in [Service URLs for Wasabi's Storage Regions](https://docs.wasabi.com/docs/what-are-the-service-urls-for-wasabi-s-different-storage-regions). Use the region your bucket is located in. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-13_at_11_58_50 AM.png) - Object Store Endpoint - Wasabi endpoint URL - Wasabi Bucket Name - Wasabi Access Key - Wasabi Secret Key 4. Monitor the status of the deployment. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.07.01 PM.png) 5. Post successful deployment. You will notice “ltss_config” in your Wasabi bucket. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.08.28 PM.png) You will notice MST VMs deployed under the VM sections (Infrastructure, VMs, List). ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.09.45 PM.png) 6. Create a Protection Policy. Click **Next**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.13.25 PM.png) - Enter the Policy name. - Enter the Availability Zone (self Prism Central from where you are going to secure the VMs/VGs). - Select the Wasabi bucket under Recovery Location. - Enter the Protection Policy timing, as required. 7. Configure the Replication schedule. Click **Save Schedule**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.14.50 PM.png) 8. Attach the entities. In the example below, we added a VM under the category. Click **Save** and **Close**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.17.26 PM.png) 9. Navigate to Infrastructure, Data Protection, and VM Recovery Points. Select the VM that has been protected under the Protection Policy. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.20.05 PM.png) You will notice the Recovery Point folder created in your Wasabi bucket. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.21.18 PM.png) After the replication schedule, you will see only two Recovery Points on both the PC and the bucket, as defined in Replication schedule. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.24.16 PM.png) ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.25.09 PM(1).png) ## Restoring From a Backup Snapshot 1. Restore the VM by selecting the Recovery point in your bucket. Click **Actions**. On the Clone panel, provide a new VM name. Click **Clone**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.27.41 PM.png) 2. Review the VM from Infrastructure, VM, and List. Select the VM that you restored. For Power operations, click **Power On**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-13 at 12.30.15 PM.png)