Lift and Shift™ is but a part of the SoftNAS®
...
stack, and as such, is part of an integrated whole. Creating an instance of SoftNAS® provides the basis for not only Lift and Shift™ functionality,
...
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:
...
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 SoftNAS®, (the most common scenario) a VMware SoftNAS® instance would be connected to a SoftNAS 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® instance in each region. If migrating from AWS to Azure, your target SoftNAS 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
