Cross subscription Azure SQL VM database restore using Azure CLI

Hi @Nikhil Verma,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

As I understand that you are trying to restore an SQL database running on Azure SQL VM and backed up via Azure Backup using Azure CLI.

Based on the error message you provided, it seems like you're encountering a ResourceNotFoundError when trying to perform a cross-subscription restore using Azure CLI.

Here are some steps to troubleshoot and resolve this issue:

• Ensure that cross-subscription restore is enabled for your Recovery Services vault. You can enable it using the following command:

az backup vault create -g {rg_name} -n {vault_name} -l {location} --cross-subscription-restore-state Enable

• Double-check all the resource identifiers in your command to ensure they are correct and exist. This includes --target-container-name, --target-item-name, --target-resource-group, --target-server-name, --target-subscription-id, and --target-vault-name.
• Ensure that all necessary permissions are in place for both the source and target subscriptions. The service principal or user account running the CLI command should have the required roles and permissions.
• Make sure the target server is registered to the same Recovery Services vault as the backup. You can check this by going to the Recovery Services vault in the Azure portal and checking the list of registered servers.
• Running the command with the --debug flag can provide more detailed error messages, which might help you identify the issue. To do this, simply add the --debug flag to the end of your command:

az backup recoveryconfig show --resource-group <resource_group_name> --vault-name <vault_name> ... --debug

I would request you to refer the below mentioned links for more information.

https://zcusa.951200.xyz/en-us/azure/backup/backup-azure-sql-restore-cli#cross-subscription-restore.

https://zcusa.951200.xyz/en-us/azure/backup/restore-sql-database-azure-vm#cross-subscription-restore.

I hope this information helps. Please do let us know if you have any further queries.

Hi , In our case , both the recovery vaults are in different subscriptions . This is contradictory to the point you mentioned "Make sure the target server is registered to the same Recovery Services vault as the backup. You can check this by going to the Recovery Services vault in the Azure portal and checking the list of registered servers." ..