Overview

The Runbook Automation Tool simplifies the mass migration of VMs from on-premises VMware or AWS into GCP. It is available for use from the Velostrata Manager page (https://IP_OF_VELOSTRATA_APPLIANCE). Typically, runbook automation is only used when migrating multiple VMs, sometimes tens or hundreds in one sprint. The purpose of runbook automation is to automate a migration of VMs in a pre-defined order. To do this, a runbook file (CSV) is used, where the RunGroup variable is defined as follows:

  • -1 indicates this row (VM) will be skipped/ignored.
  • All other values are migrated in ascending order. 5 VMs with RunGroup 100, for example, will move together in a group. Then another 3 VMs with RunGroup 200, for example, will move together next. And so on. 

After defining the runbook inventory file, you'll also select a job, which is what actions are performed on these VMs. For some operations (run in cloud, full migration, offline migration) the first operation that takes place is a graceful shutdown of the VM at the source (on-prem or cloud). After that, when the runbook automation actions run, they do so in a sequence as defined, and are all re-entrant, that is, if there is any failure in the process, you can fix the problem and either click the re-run button from the runbook interface, or you can create a new job altogether with the same runbook file. The actions available via runbook are defined below: 

Test Clone

Creates clones of the selected VMs for the purpose of in-cloud testing. A test clone will look and feel like the live systems, and will leverage what appears to be the live data. However, no live data (nor the VM) are actually affected through usage of test clones. This is only available for on-prem to cloud migrations.

Delete Test Clone

This will shut down and terminate the test clones that were previously created. This is only available for on-prem to cloud migrations, and where a test clone is already running.

Run in Cloud

Moves the source VMs from on-prem or AWS to GCP.

  1. Shuts down the source VMs in reverse order of the RunGroups.
  2. Executes the Run in Cloud operation for each instance.
  3. Waits for the management task to complete.
  4. Waits for the successful completion of the TCP port probing (Optional).

Note: For cloud-to-cloud migrations, the WriteIsolation value will be ignored because TRUE is the only available option as write-back is not supported.

Move Back

Moves the instances in GCP back to their source, either on-prem or AWS.

  1. Stops the VMs in reverse order of the RunGroups.
  2. Moves back each instance.
Full Migration

Runs a series of automation tool actions to migrate a group of VMs, as follows:

  1. Runbook begins the full migration tasks
  2. Waits for the VMs to be in the 'Cache on Demand' state.
  3. Waits for the successful completion of the TCP port probing (optional)
  4. Waits for the 'Ready to Detach' state.

Note: For cloud-to-cloud migrations, the WriteIsolation value will be ignored because TRUE is the only available option as write-back is not supported.

Offline Migration

Velostrata enables you to migrate workloads with operating systems that are not currently supported by Velostrata's streaming technology. During the offline migration process, the VM storage is migrated to the cloud first, and the VM is started in the cloud only after the migration is completed. Velostrata automatically performs the detach and cleanup of residue data associated with the VM.

Prepare to Detach

This brings the VMs running in the cloud to a state where they are ready to be detached from their on-prem sources.

Detach

Once the VMs are in a Ready to Detach migration state, and the preparing to detach tasks complete successfully, you can detach the VMs. This severs their ties to on-prem, and means you can no longer perform instant rollback via Velostrata. 

Note: This job waits for the successful completion of the TCP port probing (Optional).

Cleanup

Once the VMs are detached and you have completed any required validation, you can start the detach cleanup. For each VM, this marks the VM as unmanaged by Velostrata.