Azure DevOps Migration

Question

Azure DevOps Migration

Adnan Khan 20

Hi Community,

We are in the process of migrating from Azure DevOps (ADO) Server 2022 with SQL Server 2019 Standard (running on Windows Server 2019) to Azure DevOps Services using the ADO Migration Tool for high-fidelity migration.

Our largest table size is 45 GB, which exceeds the 30 GB limit for the DACPAC import method. As a result, we are following the Azure SQL Method as outlined in the documentation: Migrate Large Collections.

I have two questions:

Azure SQL Image Selection: When provisioning an Azure SQL Virtual Machine (VM), should we select SQL Server 2019 Standard, or would it be fine to choose SQL Server 2022? Does the version of SQL Server on the Azure VM have any impact on the migration process?

Post-Migration Decommissioning: After the migration is successfully completed, can we safely decommission the Azure SQL VM used for the migration?

Looking forward to your insights and recommendations!

Thanks in advance.

Accepted answer

0 additional answers

Your answer

Answer 1

NIKHILA NETHIKUNTA 4,600 Microsoft External Staff

@Adnan Khan
Thank you for the question and for using Microsoft Q&A platform.
I'm glad to help you with your questions regarding the migration process from Azure DevOps Server 2022 to Azure DevOps Services using the ADO Migration Tool.

Regarding your first question, it is recommended to use the same version of SQL Server on the Azure VM as the one you are currently using on your on-premises server. The version of SQL Server on the Azure VM doesn't have a direct impact on the migration process itself, as long as it supports the required features used by Azure DevOps. However, it's generally recommended to match the version of SQL Server on your source environment to avoid any potential compatibility issues during the migration.
In your case, since you are currently using SQL Server 2019 Standard, it would be best to select SQL Server 2019 Standard when provisioning the Azure SQL VM. This will ensure that there are no compatibility issues during the migration process.

As for your second question, once the migration is successfully completed and you have verified that all data has been migrated to Azure DevOps Services, you can safely decommission the Azure SQL VM used for the migration. However, it is recommended to keep a backup of the VM for a certain period of time in case any issues arise.

You can refer to the below links for more help:
https://learn.microsoft.com/en-us/azure/devops/migrate/migration-overview?view=azure-devops
https://learn.microsoft.com/en-us/azure/devops/migrate/migration-prerequisites?view=azure-devops

Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Adnan Khan 20 Reputation points

2024-12-06T16:23:12.5066667+00:00

Thanks @Nikhila. Truly appreciate your quick reponse.
Adnan Khan 20 Reputation points

2024-12-06T16:24:32.6633333+00:00

One more question: Do you know the primary difference between test run and Prod run? From what I tell from the documentation, only difference is that test run in deleted automatically after 45 days.
NIKHILA NETHIKUNTA 4,600 Reputation points Microsoft External Staff

2024-12-06T16:41:19.7733333+00:00

@Adnan Khan
Glad that I could resolve your query.
You’re correct that one of the key differences between a test run and a production run in Azure DevOps migration is the automatic deletion of the test run after 45 days.
Based on the documentation, the primary difference between a test run and a production run is that the test run is intended for testing purposes only and will be automatically deleted after 45 days. The production run, on the other hand, is intended for use in a production environment and will not be automatically deleted.

It's important to note that the test run is not intended to be used as a long-term solution, but rather as a way to test the migration process and ensure that everything is working as expected before performing the actual migration in a production environment.
https://learn.microsoft.com/en-us/azure/devops/migrate/migration-test-run?view=azure-devops

I hope that helps! Let me know if you have any other questions.

Adnan Khan 20

Hi Nikhila, Any idea on why we would get this error when running the import in the above-mentioned scenario? I setup Azure SQL VM according to the instructions and adding appropriate inbound IP rules as well for all the IPs returned by the command Migrator iplist.

Error:

The HTTP request timed out after 00:01:40.

Details From Import Log:

[Info @14:51:30.388] [Info] Data migration tool for Azure DevOps version 19.235.34928.5

                   [Info] Copyright (C) Microsoft Corporation. All rights reserved.

                   [Info] Executing at 2024-12-11T20:51:30.3725968Z:

                   [Info] Migrator  import /importFile:C:\DataMigrationToolFiles\import.json

[Info @14:51:30.388] -------------------------------------

                     Validating Import File

                   -------------------------------------

                   Validating import specification file...

[Info @14:51:30.669] Validation completed successfully.

[Info @14:51:30.669] Validating import source and target regions...

[Info @14:53:14.394]

                      at Microsoft.TeamFoundation.Common.RetryManager.InvokeFunc[TResult](Func`1 func)

                      at Microsoft.VisualStudio.Services.DataImport.Extensions.AzureRegionIpAddressService.GetServiceTags(ITFLogger logger)

                      at Microsoft.VisualStudio.Services.DataImport.Extensions.AzureRegionIpAddressService.GetRegions()

                      at Microsoft.VisualStudio.Services.DataImport.Extensions.AzureRegionIpAddressService.TryGetRegion(IPAddress ipAddress, String& region)

                      at Microsoft.VisualStudio.Services.DataImport.Extensions.AzureRegionIpAddressService.TryGetRegion(String nameOrAddress, String& region)

                      at Microsoft.VisualStudio.Services.DataImport.Extensions.DataImportPackageExtensions.CheckPackageRegions(DataImportPackage package, ITFLogger logger)

                      at TfsMigrator.TfsMigratorCommandImport.RunImpl()

[Info @14:53:14.410] -------------------------------------

                     Importing Collection

                   -------------------------------------

[Info @14:53:14.410] Please confirm that you wish to continue with moving your data to Azure DevOps Services.

[Info @14:54:12.523] Starting the Import ...

[Info @14:54:12.538] Connecting to https://dataimport.dev.azure.com/?account=False, Check for the authentication dialog.

[Info @14:56:16.497] Import couldn't be started due to an error!

[Error @14:56:16.497] + [Error] The HTTP request timed out after 00:01:40.

[Info @14:56:16.497] See our documentation for assistance: https://aka.ms/AzureDevOpsImportTroubleshooting

[Error @14:56:16.497] System.TimeoutException: The HTTP request timed out after 00:01:40. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.

                      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

                      at Microsoft.VisualStudio.Services.Common.VssHttpMessageHandler.<SendAsync>d__17.MoveNext()

                      --- End of inner exception stack trace ---

                      at Microsoft.VisualStudio.Services.Common.VssHttpMessageHandler.<SendAsync>d__17.MoveNext()

                   --- End of stack trace from previous location where exception was thrown ---

                      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

                      at Microsoft.VisualStudio.Services.Common.VssHttpRetryMessageHandler.<SendAsync>d__9.MoveNext()

                   --- End of stack trace from previous location where exception was thrown ---

                      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

                      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

                      at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__51.MoveNext()

                   --- End of stack trace from previous location where exception was thrown ---

                      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

                      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

                      at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__47`1.MoveNext()

                   --- End of stack trace from previous location where exception was thrown ---

                      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

                      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

                      at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__28`1.MoveNext()

                   --- End of stack trace from previous location where exception was thrown ---

                      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

                      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

                      at TfsMigrator.DataImportPackageHelper.Import()

                      at TfsMigrator.TfsMigratorCommandImport.QueueImport(DataImportPackageHelper helper, Boolean confirmed)

Share via

Azure DevOps Migration

0 additional answers

Your answer