Forum Discussion
Solved
Azure Backup SQL does not discovers all Databases
Hi, did anyone see an issue for discovering DBs on a SQL Virtual Machine with Azure Backup? Extension did installed without problems, Discovery completes successfully, we checked also the NT Ser...
- Update on my own:
After giving the NT AUTHORITY\SYSTEM account sysadmin permissions, we can now see the dabases.
Discovery is done with the NT AUTHORITY\SYSTEM Account :https://learn.microsoft.com/en-us/azure/backup/backup-azure-sql-database#set-vm-permissions)
But for newer SQL Versions (we are on 2016) the "public" role should be enough for discovery process.
(Works fine on another SQL 2016 within the same tenant)
So a bit strange.
We will test the backups and came back.
Ben
Update on my own:
After giving the NT AUTHORITY\SYSTEM account sysadmin permissions, we can now see the dabases.
Discovery is done with the NT AUTHORITY\SYSTEM Account :https://learn.microsoft.com/en-us/azure/backup/backup-azure-sql-database#set-vm-permissions)
But for newer SQL Versions (we are on 2016) the "public" role should be enough for discovery process.
(Works fine on another SQL 2016 within the same tenant)
So a bit strange.
We will test the backups and came back.
Ben
After giving the NT AUTHORITY\SYSTEM account sysadmin permissions, we can now see the dabases.
Discovery is done with the NT AUTHORITY\SYSTEM Account :https://learn.microsoft.com/en-us/azure/backup/backup-azure-sql-database#set-vm-permissions)
But for newer SQL Versions (we are on 2016) the "public" role should be enough for discovery process.
(Works fine on another SQL 2016 within the same tenant)
So a bit strange.
We will test the backups and came back.
Ben
- Backup and Restore works fine.
So we are not sure - why in our case we have to give SYSTEM the sysadmin role.
Solved for now