Infrastructure and Database Migration To Microsoft Azure Specialization2024
Infrastructure and Database Migration To Microsoft Azure Specialization2024
Audit Role
•Definitions:
− The kick-off call/meeting date is the date we enter for the engagement start date.
− The date of the close-out meeting is the date we enter for the engagement completion date. We also
get close-out documentation signed by the customer, showing we completed all committed
deliverables.
© 2023 Lunavi | Confidential |
CUSTOMER MIGRATION SCENARIOS
• The below 3 unique customers represent 4 migration scenarios stated in the controls.
Migration of MySQL,
PostgreSQL, MariaDB, or
MongoDB database to
Azure*
• Lunavi CAF is a methodology focused on capturing customer business requirements. It is based on the
Microsoft Cloud Adoption Framework.
• Our process, built on a robust foundation and leveraging Azure best practices, not only accelerates
platform usage but also provides valuable recommendations for customer business problems. This
methodology benefits our customers significantly.
• The business decisions are based on the Cloud Adoption Strategy Evaluator's output. These
assessment results/recommendations are stated in the Strategy Planning documents below.
Statement of Work Cogent Bank Executed SoW Vulcan Eyewear Executed SoW
Page #9 Page #7
• Lunavi uses Azure DevOps to plan and track all Cloud Adoption projects.
• This demo will provide evidence for Sprint Planning, tracking approach, and completion.
During the assessment, the Lunavi cloud enablement team identifies skilling requirements and gaps and
documents the requirements in the build documentation. We document customer technical roles
expected to require new skills.
• We use Bicep modules to implement a repeatable Azure Landing Zone. Bicep enables repeatable,
consistent code deployment.
• The deployments are configured using Microsoft Entra ID, adherence to the guidance in Network
topology & Connectivity, and resource organization (implementation of tagging)
• We follow the “Start Small & Expand” method when deploying Azure Landing Zones.
1. Cogent Bank
2. Vulcan Eyewear
1. ASSESS
2. DESIGN
3. DEPLOYMENT
4. REVIEW AND RELEASE FOR OPERATIONS
Conducting a thorough workload assessment is crucial before initiating the migration process. This step
ensures that all necessary pre-migration or pre-deployment planning and sizing have been meticulously
performed, setting the stage for a successful migration. Lunavi assessments cover the following focused
areas:
Migration Service Cogent Bank Vulcan Eyewear Mercy Mercantile
Upstream Mapping • AzureMigrateProject_Mapping_CogentBank.pdf • MyMigrateProject_Mapping_Vulcan.pdf • AzureMigrateProject_Mapping_MercyMercantile.
pdf
• CogentBank-Dependency-Analysis-Lunavi.pdf • Vulcan Eyewear - Dependency Analysis -Lunavi . • Mercy Mercantile-Dependency-Analysis-Lunavi.
pdf pdf
The infrastructure, data volumes and database sizes • Cogent_Initial_Azure_Migrate_Assessment.xlsx • Vulcan Eyewear_Initial_Azure • Mercy_Initial_Azure_Migrate_Assessment.xlsx
are to be migrated Migrate Assessment.xlsx
The timeline and approach • Azure DevOps Board Demo • Azure DevOps board Demo • Azure DevOps Board Demo
The migration risk assessment. • CogentBank-Azure-Strategy-Planning-Lunavi.pd • Vulcan Eyewear - Azure-Strategy-Planning-Luna • Mercy Mercantile - Azure-Strategy-Planning-Lun
f vi.pdf avi.pdf
• Strategic Migration and Assessment Readiness
• Strategic Migration and Assessment Readiness • Strategic Migration and Assessment Readiness Tool (p. 18-19)
Tool (p.18-19) Tool (p. 18-19)
Backup and DR for Existing Workloads • CogentBank-Azure-Strategy-Planning-Lunavi.pd • Vulcan Eyewear - Azure-Strategy-Planning-Luna • Mercy Mercantile - Azure-Strategy-Planning-Lun
f vi.pdf avi.pdf
• Strategic Migration and Assessment Readiness
Tool (p.14) • Strategic Migration and Assessment Readiness
Tool (p. 11)
Licensing and cost management requirements. • CogentBank-Azure-Strategy-Planning-Lunavi.pd • Vulcan Eyewear - Azure-Strategy-Planning-Luna • Mercy Mercantile - Azure-Strategy-Planning-Lun
f vi.pdf avi.pdf
(p. 5-6)
Documentation of the customer’s existing identity • CogentBank-Azure-Strategy-Planning-Lunavi.pd • Vulcan Eyewear - Azure-Strategy-Planning-Luna • Mercy Mercantile - Azure-Strategy-Planning-Lun
implementation on Azure, gaps identification, and best f vi.pdf avi.pdf
practices recommendations
• The Solution design requirements stated in Control 2.1 are included in the Strategy & Planning Document, Azure Setup
Guide, and ITOM Handoff Documentation. The details are presented in Slides #18 and #19.
• We present 2 evidence examples for Scenario 1 and Scenario 2. A total of> 4 evidence examples are presented using 3
unique customers.
Migration Scenarios Cogent Bank Vulcan Eyewear Mercy Mercantile
• Azure Well-Architected Review is part of the Lunavi Cloud Enablement process. We evaluate customer workloads
based on the WAR and discuss actionable guidance with the customer.
• The projects demonstrated in this section (3.1) are the same as the control 2.1. Design – Infrastructure
Migration section.
• The projects demonstrated in this section (3.2) are the same as the control 2.1.
• The Lunavi Cloud Enablement team has experience using native Azure migration tools.
• We will demonstrate Option A of the control for the customer projects below. The 3 unique customers
selected cover 4 of the following tools.
• Lunavi uses the ALZ Bicep framework to deploy Azure Landing zones for all customers.
Automated Deployment: Deployment of Azure Example 1: ALZ Bicep deployed via Azure Example 4: ALZ Bicep deployed via Azure
Landing Zones DevOps pipelines DevOps pipelines
Cloud service provisioning and de- Example 2: ALZ Bicep deployed via Azure ALZ Bicep deployed via Azure DevOps
provisioning: Viewing service templates, DevOps pipelines: Storage Accounts, VMs pipelines: Storage Accounts, VMs
packages, or runbooks used in deploying
customers’ Azure environments.
Automation of routine operations: We Example 3: Azure Update Manager for Azure DevOps pipelines, Azure Monitor
deploy Patching framework for managing Packaging resources
software updates for the virtual machines
• We have documented and maintained the Service Validation Testing process in Azure DevOps.
• We document Azure DevOps backlog tasks aligned with customers’ expectations and Azure best
practices.
• Evidence 4:
Vulcan Eyewear Initial Azure Migrate Ass
essment
• Evidence 1 & 2: Cogent Bank and Vulcan Eyewear Azure DevOps backlog Tasks List Demo.
• This is the evidence for the Service Validation testing (Migration Check List) included in the Azure
DevOps backlog task. The exact process followed in all the Cloud Enablement projects.
• Validate sign-in with local credentials or keys for RDP or SSH.
• Verify that DNS servers are configured in TCP/IP settings for the OS and that name resolution works correctly.
• Verify that the TCP/IP settings for the OS enable the server to receive an IP address via DHCP.
• Verify that access to OS licensing is activated and that there's access to cloud-based licensing endpoints (such as Azure endpoints for key
management services).
• Validate sign-in with domain credentials.
• Verify that the application has access to dependencies (such as target URLs or connection strings).
• Verify installation or update required Azure agents:
• Azure VM agents for Windows or Linux.
• Log Analytics agent for Windows or Linux.
• Service Map agent for Windows or Linux.
• SQL Server IaaS Agent extension.
• Validate VM monitoring via a new or existing service.
• Validate VM patching via a new or existing service.
• Validate VM backup via a new or existing service.
• Validate VM antivirus and endpoint protection via a new or existing service.
• Tag Azure resources.
• Update any existing configuration management database (CMDB).
• Conduct a post-mortem and document lessons learned.
• We have documented architectural best practices to remediate issues with migrated platforms or
workloads that do not meet performance or cost expectations.