Can't drop database in "restoring" state from secondary instance of AG

  • auaiomrn

    Ten Centuries

    Points: 1300

    MSSQL version: 2016 (13.0.5026.0)

    Situation: Removed a database from an availability group so it could be restored. When I'm ready to add it back to the group, I go to drop the copy on the secondary instance. It's in the "restoring" state, but that's ok, that's what's expected. But when I try to drop the database, I get an error message saying "the database is in use". When I see what is blocking me, I see a "VDI_CLIENT_WORKER" process. I can't kill it because it's not a user process.

    Any ideas what I can do, aside from restarting the instance? And how to prevent this in the future?

  • Sue_H

    SSC Guru

    Points: 90673

    VDI_CLIENT_WORKER is usually created when using automatic seeding. You could try disabling along the lines of:

    ALTER AVAILABILITY GROUP YourAGName 
    MODIFY REPLICA ON 'NameOfSecondaryReplica'
    WITH (SEEDING_MODE = MANUAL)

    Sue

     

  • auaiomrn

    Ten Centuries

    Points: 1300

    Thanks, someone else was able to drop it - I'm not yet sure how, though.

  • Sue_H

    SSC Guru

    Points: 90673

    If you could find out and post back, that would be great. It helps when others find the same issue that you posted and then they can see how you got it resolved.

    Sue

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply