Case Study 1 ~ Migrate Application Workloads to the Cloud
A customer and their partner are tasked with migrating all their on premise virtual and physical server applications to the Cloud. Operating Systems are staying the same just the application workload needs to be migrated to the same platform in the cloud environment. For example on-premise Windows Server 2008 R2 hosted applications to Cloud Windows Server 2008 R2 VM.
Traditional migration approaches had issues. Finding application source and exact configuration for a manual rebuild was very time consuming, risky and in some cases impossible. Physical to Virtual / Virtual to Cloud was also a difficult process due to required connectivity between the environments, expertise needed and sometimes impossible due to differing hypervisor architecture. For additional complexity existing Servers have an Enterprise Application layer or other applications which was NOT to be migrated to the Cloud. In this case a conversion or creation of a "Server clone" to a cloud format was not viable.
Zaptz EzySnap Server automatically separated the application layer from the underlying operating system. This enabled the applications to be automatically extracted from the source server. The extraction process was completely configurable where the client configured EzySnap to NOT extract unwanted applications. For example the base database was easily updated to exclude AntiVirus, Backup, Software Inventory, Hardware utility applications (Enterprise Application Layer). Other applications was also easily removed on an ad-hoc basis when required. Granular authoring was conducted when needed to change any environmental requirements, for example ServerNames, UNC paths to database servers etc.
The client was able to migrate their on premise application workloads without their unwanted applications to the cloud using a single Zaptz EzySnap Server command line. This was all achieved in a very fast, simple and flexible way.
Traditional migration approaches had issues. Finding application source and exact configuration for a manual rebuild was very time consuming, risky and in some cases impossible. Physical to Virtual / Virtual to Cloud was also a difficult process due to required connectivity between the environments, expertise needed and sometimes impossible due to differing hypervisor architecture. For additional complexity existing Servers have an Enterprise Application layer or other applications which was NOT to be migrated to the Cloud. In this case a conversion or creation of a "Server clone" to a cloud format was not viable.
Zaptz EzySnap Server automatically separated the application layer from the underlying operating system. This enabled the applications to be automatically extracted from the source server. The extraction process was completely configurable where the client configured EzySnap to NOT extract unwanted applications. For example the base database was easily updated to exclude AntiVirus, Backup, Software Inventory, Hardware utility applications (Enterprise Application Layer). Other applications was also easily removed on an ad-hoc basis when required. Granular authoring was conducted when needed to change any environmental requirements, for example ServerNames, UNC paths to database servers etc.
The client was able to migrate their on premise application workloads without their unwanted applications to the cloud using a single Zaptz EzySnap Server command line. This was all achieved in a very fast, simple and flexible way.