“No backupset selected to be restored” SQL Server 2012

前端 未结 21 1717
一向
一向 2020-12-04 08:36

I have a SQL Server 2012 database with filestream enabled. However, when I backup it and try to restore it on another SQL Server 2012 instance (on another machine), I simply

相关标签:
21条回答
  • 2020-12-04 08:42

    My problem ended up being permissions. I'm on a dev machine and copied via Homegroup. Somehow, probably based on where I copied the file to, the permissions got messed up and Management Studio couldn't read the file. Since this is dev I just gave Everyone permissions to the bak file and could then successfully restore via the GUI.

    0 讨论(0)
  • 2020-12-04 08:42

    For me the problem was having the .BAK file located in an encrypted folder on the server. Even with full Admin rights, I could never get SSMS to read the file. Moving the .BAK to an unencrypted folder solved my problem. Note that after moving the file you may have to also change the properties on the actual file to remove encryption (right click, properties, advanced, uncheck "encrypt contents to secure data".

    0 讨论(0)
  • 2020-12-04 08:42

    For me, It was a permission issue. I installed SQL server using a local user account and before joining my companies domain. Later on , I tried to restore a database using my domain account which doesn't have the permissions needed to restore SQL server databases. You need to fix the permission for your domain account and give it system admin permission on the SQL server instance you have.

    0 讨论(0)
  • 2020-12-04 08:43

    In my case, it was permissions and the fact that I used "Restore Files and Filegroups..." rather than simply "Restore Database ...".

    That made the difference.

    0 讨论(0)
  • 2020-12-04 08:43

    I got the same error message even though I backup and restore on the same single machine.

    The issue was from here: when backup, i had 2 item in the destination box.

    So the fix would be: make sure only 1 item in the 'destination' box. Remove all the others if there are.

    0 讨论(0)
  • 2020-12-04 08:44

    For me it's a user privilege issue. I logged-in with sa user and its working fine.

    0 讨论(0)
提交回复
热议问题