Exam AZ-305 topic 3 question 18 discussion

First one should be A: Prepare For the migration by: A. Adding a secondary replica to AG1 Reason: Creating an Always On availability group on VM1 would not be necessary, as you already have an availability group (AG1) in place on your on-premises SQL Server instances. By adding a secondary replica to AG1, you can provide a copy of DB1 that can be used for the migration. This will allow you to minimize downtime on DB1 by performing the migration on the secondary replica, while the primary replica remains available for use. Perform the migration by using: B. Azure migrate

This should be 1. Creating an Always On availability group on VM1 2. Use distributed availablity group Reference: https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-distributed-availability-group-migrate-ag?view=azuresql

Preparation: Creating an Always On availability group on VM1 is necessary to establish the target environment. A distributed availability group (DAG) requires both the source (on-premises AG1) and target (VM1) to have their own availability groups. This setup bridges the two environments, enabling cross-platform (Windows → Linux) and cross-version (SQL 2017 → 2019) replication. Migration Method: Distributed availability group (DAG) is explicitly designed for minimal downtime migrations. It allows asynchronous replication between the on-premises AG1 and the new AG on VM1, followed by a controlled failover. This aligns with Microsoft’s recommended approach for migrating Always On availability groups to Azure VMs, especially in heterogeneous environments.

WHERE IS MALTONIS?????

- Adding a secondary replica to AG1 - Azure Migrate

1. Creating an Always On availability group on VM1 2. Use distributed availability group Choose method from first link and prerequisites from the second! https://learn.microsoft.com/en-us/data-migration/sql-server/virtual-machines/overview https://learn.microsoft.com/en-us/data-migration/sql-server/virtual-machines/distributed-availability-group-prerequisites

WRONG 1. Adding a secondary replica to AG1 2. Azure Migrate

This question is still relavent (10 Nov 2024) , but I was not sure about answers as so many options are discussed. I choose 1. Replica AG1 2. Azure Migrate

•Prepare for the migration by: Adding a secondary replica to AG1 •Perform the migration by using: A distributed availability group

The correct answer should be : Adding a secondary replica to AG1: Ensures continuous data synchronization between the on-premises environment and VM1 during the migration, minimizing downtime. Using a distributed availability group: Provides a seamless and robust mechanism for high availability, real-time data replication, and automatic failover capabilities, ensuring minimal downtime during the migration process.

I see some of the answers and I dont understand some: how can you create Creating an Always On availability group on VM1 if you have only one virtual machine with one SQL server? The idea of creating Always On Availability Group is to involve two servers. You can't do it with one server but even if you could it wouldn't make any sense. To do this migration I believe you need to uprade sql servers on prem and use Azure Database MIgration Service. Adding a secondary replica is technically feasible but if you do it then database will be replicated automatically (synchronously or asynchronously). What is the reason to use Azure migrate then? My option is * upgrade on prem servers * use Azure Mgrate (Azure Database MIgration Service to be more precise)

If you extend the existing on-prem AG to AZURE by adding another replica, why do you need to migrate DB, isn't the SQL synchronization copy the DB to new replica? Considering the given options, I think only possible selection here is Creating an Always On availability group on VM1 and using a distributed AG. Also AZURE migrate is not for DB migrations and it's for recommendation and advise about migration, isn't it?

I would go for 1. Creating an Always On availability group on VM1 2. Use distributed availability group that can be configured to include both Availability groups AG1 and the new one in Azure on Linux VM, thank you can perform the failover from there Read this carefully https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/distributed-availability-groups?view=sql-server-ver15

box1 : Creating an Always On availability group on VM1 box2: Use Distributed availability group

Surely for question 1 you would add a Secondary Replica to an already existing Availability Group?

Got this ques in my exam on 29th Jan 2024 and scored 950. I chose box1 : Creating an Always On availability group on VM1 box2: Use Distributed availability group

I would say Adding a secondary replica to AG1 and Azure Migrate. Upgrading the on-premises SQL Server instances: This could introduce downtime on the on-premises instances and is not directly related to migrating to VM1, not necessary. A distributed availability group: This is typically used for scenarios where you have availability groups spread across different geographical locations, and it is not necessary for a migration to a single VM. Log shipping: Log shipping involves periodically copying and restoring database transaction logs and may introduce downtime during the cutover.