...
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 instance 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 minimum requirements should be kept in mind when configuring your instances for Lift and Shift™:
| Memory | CPU | Network | Instance Size Recommendations | |
|---|---|---|---|---|
| AWS | 16 GB | 4 vCPU | High | m4.xlarge, c3.4xlarge, etc |
| Azure | 14 GB | 4 cores | High | DS4v2, DS14v2, etc |
| VMware | 16 GB | 4 vCPU | 1GBe minimum recommended | NA |