Velostrata enables you to rapidly perform migration operations on single or multiple VMs directly from vCenter. These operations can include run-in-cloud, migrate, test clone, etc. Using the vCenter UI to accomplish these tasks is fast and only requires a few clicks. Plus, these operations complete quickly, often in a matter of minutes, empowering fast, simple migrations.
Alternatively, for more complex applications, you can also use our runbook automation feature which lets you take an inventory of available VMs, then define a very specific order for those migrations to take place. This is valuable when you are looking to automate the migration of a more complex app with dependencies.
Here is the general overview of the phases you are likely to encounter while using Velostrata:
Phase 1: Model (For more complex applications)
- Capture VM inventory using Velostrata's Runbook Automation.
Phase 2: Test before you migrate (Optional)
- Create a copy of a running on-premises Workload and run it in cloud. This enables you to test an application in cloud without disrupting the live production system. The clone can be fully operational within minutes. See Running a Test Clone.
Phase 3: Fast cutover to cloud
Once you have completed testing on the clone, get the application and data live in the cloud in minutes. Data syncs back to on-prem as a safety net. The remaining data is migrated in the background.
- While your VM is on-premises or at source cloud, make any necessary adjustments, for example, lower the TTL on the DNS, consider any IP address issues, and so on.
- Move the VM to destination cloud. See Running a VM in the Cloud. Once this is completed, perform any validation/sanity tests and deploy any fixes.
- Migrate the storage to the destination cloud. See Migrating VM Storage to the Cloud.
- Prepare to detach the VM. This takes the data from the cloud storage and writes it to cloud drives. See Preparing to Detach.
Phase 4: Detach
- Once the preparing to detach task completes successfully, you can detach the VM. You must assign a scheduled downtime slot for detaching. See Detaching the VM.
- After detaching the VM, perform any required validation, and then either cleanup or rollback (if you do not want to detach the VM from Velostrata). See Starting the Detach Cleanup