Skip to end of metadata
Go to start of metadata

Lift and Shift™ is but a part of the SoftNAS Cloud® Platinum stack, and as such, is part of an integrated whole. Creating an instance of SoftNAS Cloud® provides the basis for not only Lift and Shift™ functionality, but also for UltraFast™ and the remaining components. The same processes outlined in the below documentation apply to the instances or VMs designated for a Lift and Shift use case. 

To create your VMware (on-premise) instance:

If creating an AWS instance:

If creating an Azure Virtual Machine or Virtual Machines:


Note:

Depending on the intended source and target for your data, your Lift and Shift™ implementation could be any combination of the above instances. If shifting your data from on-premise to the cloud, (the most common scenario) a VMware SoftNAS Cloud® instance would be connected to a SoftNAS Cloud instance on the platform of your choice (AWS or Azure). If shifting large amounts of data to another AWS region, you might create a SoftNAS Cloud® instance in each region. If migrating from AWS to Azure, your target SoftNAS Cloud Virtual Machine would be in Azure. Below are some of the supported configurations: 


Source Node Type

Target Node Type

Supported Target Node Storage

VMware

AWS

EBS, S3

VMware

Azure

Premium & Standard Disks

AWS

AWS

EBS, S3

AWS

Azure

Premium & Standard Disks

Azure

AWS

EBS, S3

Azure

Azure

Premium & Standard Disks



The following best performance minimum requirements should be kept in mind when configuring your instances for Lift and Shift™:




MemoryCPUNetworkInstance Size Recommendations
AWS32 GB8 vCPUHighm42.xlarge, c3.4xlarge, etc
Azure28 GB8 coresHighDS4v2, DS14v2, etc
VMware32 GB8 vCPU1GBe minimum recommendedNA