|
|
Cloud Migration
What We Do:
-
Transfer of data and applications from a local, on-premises data center to the public/Private/Gov cloud environments
-
Moving data and applications from one cloud platform or provider to another -- a model known as cloud-to-cloud migration.
-
Reverse cloud migration, cloud repatriation or cloud exit, where data or applications are moved off of the cloud and back to a local data center.
How We Do:
-
Identify the application. Every company has a different reason to move a workload to the cloud, and goals for each organization will vary.
-
Figure out how much data needs to be moved, how quickly the work needs to be done and how to migrate that data.
-
Take inventory of data and applications, look for dependencies and consider one of the many migration options.
-
Public cloud: lets many users access computer resources through the internet or dedicated connections.
-
Private cloud: keeps data within the data center and uses a proprietary architecture.
-
Hybrid cloud model: mixes public and private cloud models and transfers data between the two.
-
Multi-cloud scenario: A business uses IaaS options from more than one public cloud provider.
-
Public cloud: lets many users access computer resources through the internet or dedicated connections.
-
Private cloud: keeps data within the data center and uses a proprietary architecture.
-
Hybrid cloud model: mixes public and private cloud models and transfers data between the two.
-
Multi-cloud scenario: A business uses IaaS options from more than one public cloud provider.
-
Microsoft Azure
-
Google Cloud
-
AWS Outposts
-
VMware Cloud on AWS; and
-
a container-based PaaS, such as Cloud Foundry or Red Hat OpenShift.
-
Interoperability;
-
Data and application portability;
-
Data integrity and security; and
-
Business continuity.
-
Microsoft Azure Advisor and
-
AWS Trusted Advisor
|