David_001
David_001

Reputation: 5802

Azure Database Migration Service stuck at "log shipping in progress"

I have a super small (no data, just a few single column tables, I'm just testing) on premise SQL server database that I'm trying to do an online migration for, to a SQL Managed Instance.

As far as I know I've configured everything as it should be - backup files are present in the file share, and the DMS is set up and can see both the SQL Server and the Managed Instance. However, it doesn't restore anything. It's stuck saying "log shipping in progress":

log shipping in progress

If I look at the managed instance itself, I can see a database has been created, and is currently in "Restoring" status.

My question is: how can I resolve this?

Maybe there are other logs I can look at, or there's some other permissions thing I don't know about, or something else?

I've tried creating a new project from scratch, but it had the same issue. And I've tried waiting... but I don't think it's working. As I mentioned, this is a DB with only a few tables (maybe 4), a single column in each table, no data at all.

Upvotes: 1

Views: 761

Answers (2)

Alan Borsato
Alan Borsato

Reputation: 256

You need to assign permission to the service principal running the migration service at subscription level:

az role assignment create --assignee [YOUR SERVICE PRINCIPAL] --role contributor

Upvotes: 0

Rizwan
Rizwan

Reputation: 318

Looking at your image, looks like there is no issue with DMS connecting to backup location and uploading backup and log files.

What is interesting is the field for last backup file applied and last applied LSN is empty. Makes me think there is some issue on the SQL MI machine.

I would recommend to open a case with MS Support on this.

One other thing you can try is to do a manual failover and your machine will failover to secondary node and then run the DMS job again.

https://techcommunity.microsoft.com/t5/azure-sql/user-initiated-manual-failover-on-sql-managed-instance/ba-p/1538803

Also try to take a look at what is going on with the SQL MI with any blocking.

You can use sp_whoisactive which is the latest version and it works on Azure SQL MI https://github.com/amachanic/sp_whoisactive/releases/tag/v11.35

Upvotes: 1

Related Questions