Since our new UForge Migration service launched a couple of years ago, we've developed a certain amount of expertise in the nuts and bolts of moving your workloads to the cloud, or between clouds. We make no claim to address all your workload migration challenges, of course. When you're looking at a full analysis of all your datacenter applications, for example, then companies like our parent company, Fujitsu, provide great services to help you through. Once that's done, however, Fujitsu teams will be using UForge Migration and other tools to actually migrate the applications.
However, we do understand what our customers are looking for when they migrate to cloud, and the sorts of approaches they can take. CTO James Weir, recently authored a blog post outlining three potential approaches you can take to cloud workload migration within a hybrid IT environment, and the pros and cons of each.
Read the full post here.
Following Elaine's recent post on supported operating systems in the latest UForge AppCenter 3.6 release, here's a quick recap of the supported output formats (cloud, virtual and physical).
The goal of white box migration is to change the contents found during the scan of the live system prior to migration.
White box migration is not supported for Windows.
The goal of black box migration is to reproduce a near identical copy of the currently running workload. However, there will always be small differences between the two workloads after migration is complete.
To migrate a live workload to a new target environment, you first copy the uforge-scan binary to the target environment and launch the binary. This binary analyzes the live system and sends back a report, known as a scan back to UForge.