Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Lift and Shift™ is but a part of the SoftNAS dSphere™ 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. Once formally released, the full dSphere stack is unlocked via license key. However, it will first be made available as a beta in the current release (3.6). As dSphere functionality is included with your standard SoftNAS Cloud image, the installation process will be exactly the same as previously documented according to the relevant platform. 

If creating an AWS instance or instances:

If creating an Azure instance or instances:

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.

  1. AWS – at least 4 CPUs, 15G Memory (i.e. m3.xlarge, m1.xlarge)
  2. Azure – at least 4 cores, 14GB Memory (i.e. DS3, DS3_V2, DS4, DS4_V2, DS12, DS12_V2)
  • No labels