Link to home
Start Free TrialLog in
Avatar of Jerry Seinfield
Jerry SeinfieldFlag for United States of America

asked on

website and database migration to Azure

Given the lack of support and feedback by the Azure team from another case posted, I am requesting some feedback from the Azure side of things regarding below:


Hello Experts,

I have a customer who runs a public website hosted in their web servers, and he is looking to migrate/replicate workloads (Web/app/database servers) to the cloud so they can in the near future eliminate every single point of failure or application dependencies on prem and host their data on the cloud.

Current environment:

Web servers/App

Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8g
Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8g
Apache/2.4.41 (Win64) OpenSSL/1.1.1c PHP/7.3.11
IIS 10.0 running in  Windows 2012 R2 Standard edition box with SQL Server 2008 R2

The initial plan is to configure an Azure AD tenant, deploy Azure AD connect to sync resources to Azure AD, then use Azure migrate tool to replicate or migrate resources from on prem to the cloud.

The network connectivity  will be a site to site VPN between Azure and the organization, and client will be running a hybrid model for a while, but in the long term solution is going to migrate everything off from on prem to the cloud, so having said I need to clarify few items:

Which of the following approach suit best and is less complicated/cheaper?
Pros and Cons of both scenarios proposed

Approach 1:
Use Azure migrate tool, collect all inventory and dependencies application info and workload, replicate or migrate the server hosting the app and the database. lift and shift option. This is going to stay in a hybrid environment for at least 6 months or a year.

Approach 2:

Given the fact the application resides on a single server and there is only one database server hosting a single instance for the website, re-architect the entire solution, once the database is migrated to the cloud, proceed to setup HA and best practices and update the SQL version from 2008 R2 to a newer one. Collocate web servers in subnet,  database servers in another subnet, and a load balancer to balance all request to web servers

Can an apache server running version above be migrated or sync to the Azure tenant using Azure migrate tool?

Can a Windows 2012 r2 Web server be migrated to the cloud?
Assuming the web site resides either on the apache or the MS IIS web server(not sure at this point)and that's why i need your input for all scenarios

What type of deployment model(if required) is the best for each approach above? I need to understand if a single database, managed instance or elastic pool is the best and why for each scenario.

Please, remember web site currently resides on prem,  either on the Apache or IIS  webservers , The Web server running IIS has SQL 2008 R2 version deployed on same box, with one single database server with a single instance.

I'm also confused with the Azure SQL virtual machines, Azure SQL managed instances, and SQL databases. which of these should be considered for this customer requirement

Can someone please elaborate?

Avatar of Jerry Seinfield
Jerry Seinfield
Flag of United States of America image

ASKER

Any updates?
ASKER CERTIFIED SOLUTION
Avatar of Jian An Lim
Jian An Lim
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you Lian you are a lifesaver.