The software used in this tutorial, Zinstall WinServ, is also available from IBM Services, as part of their full service package for large scale deployments. The goal of this tutorial is to allow to complete a server migration in less than 4 hours of “attended” time (total time will of course be longer, mostly spent on transferring data and automated deployment on target). if you are migrating from 2003 to 2016), they will still be incompatible after you migrate them. The downside is that if some of your apps are incompatible with the new OS (i.e.
The advantage of this is that you don’t have to deal with each application separately, the application stack is migrated as-is even if no one remembers how it was configured in the first place, and you do not have the app virtualization overhead. This means that the end result will be a “normal” Cloud server with the application stack, DBs, profiles and data from the original physical server. Note that we will be performing a native migration, not OS or app virtualization. The migration process also allows migration to a different Windwos version, such as 2003 to 2016 and 32bit to 64bit. The overall approach is generic, and can be used to migrate to any Cloud provider, such as Microsoft Azure, Amazon AWS, IBM Cloud (Bluemix / Softlayer), Rackspace and others. In this article, we’ll focus on migration from a physical application server to its Cloud-hosted replacement – migrating the installed applications, databases, user profiles, shares and data.
How to: Server migration to Cloud (Azure / AWS / IBM / Rackspace), including applications and data
0 kommentar(er)
