Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated links in the proper manner.

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

...

...

Virtual Machine or

...

If creating a VMware (on-premise) instance or instances:

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 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. If shifting your data from on-premise to the cloud, a VMware SoftNAS Cloud instance would be connected to a SoftNAS Cloud instance on the platform of your choice (AWS or Azure)

 SoftNAS dSphere™ functionality should not be used in a production environment until its formal release.

...

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