Cross subscription Azure SQL VM database restore using Azure CLI

Nikhil Verma 40

Hi , Anyone tried restoring sql database running on Azure SQL VM and backed up via Azure Backup . Via recovery vault , we are able to perform the cross subscription restore but not using the Azure CLI .

User's image

All desired permissions in place as documented by MS..

Getting below error :

User's image

Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-10-14T11:03:51.98+00:00
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://learn.microsoft.com/en-us/azure/backup/backup-azure-sql-restore-cli#cross-subscription-restore.

https://learn.microsoft.com/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.
Nikhil Verma (NIVER) 0 Reputation points

2024-10-14T11:16:34.7733333+00:00

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." ..
Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-10-14T12:31:24.61+00:00
Hi @Nikhil Verma,

Thank you for pointing that out. You’re correct that in a cross-subscription restore scenario, the source and target Recovery Services vaults will be in different subscriptions. My apologies for the confusion.

please follow the troubleshoot steps to resolve the 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

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

If you have any further questions, please let me know.
Nikhil Verma (NIVER) 0 Reputation points

2024-10-15T09:58:16.5733333+00:00

Thanks Mahesh for answering. Do you see any issue with the command screenshot I pasted above . Assuming all conditions and pre- requisites are met , still i dont get to run the above command .

Any precise Az CLI command example can be shared which I can try in our environment ?

Thanks
Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-10-16T18:06:39.2933333+00:00

Hi @Nikhil Verma,

Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

1 answer

Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-10-15T11:32:28.2666667+00:00
Hi @Nikhil Verma,

Any precise Az CLI command example can be shared which I can try in our environment?

Here’s an example of a precise Azure CLI command for cross-subscription restore:

az backup recoveryconfig show --resource-group <source-resource-group> --vault-name <vault-name> --container-name <container-name> --item-name <item-name> --restore-mode AlternateWorkloadRestore --rp-name <restore-point-name> --target-container-name <target-container-name> --target-item-name <target-item-name> --target-resource-group <target-resource-group> --target-server-name <target-server-name> --target-server-type SQLInstance --target-subscription-id <target-subscription-id> --target-vault-name <target-vault-name> --workload-type SQLDataBase

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

For more information, please refer the document: Cross Subscription Restore.

Hope this helps. Do let us know if you any further queries.If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Please sign in to rate this answer.
Nikhil Verma (NIVER) 0 Reputation points

2024-10-15T13:33:30.12+00:00

Hi , Able to generate the JSON file successfully which when I ran resulted in below error

Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-10-15T18:27:01.4+00:00

Hi @Nikhil Verma,

It seems like you’re encountering the BMSUserErrorDataSourceObjectNotFound error, which typically indicates that the item you’re trying to access might have been deleted or is not registered to the vault.

Here are a few steps you can take to troubleshoot this issue:

Ensure that the item you are trying to access is correctly registered to the vault.

Confirm that the item has not been deleted. If it was deleted, you might need to recreate or re-register it.

Double-check your configuration files and scripts to ensure all parameters and resource names are correctly specified.

Occasionally, transient issues can cause this error. Wait a few minutes and try the operation again.

For more information, please refer this link: https://github.com/Azure/azure-cli/issues/23364

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

Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-10-17T18:07:19.21+00:00

Hi @Nikhil Verma,

Just checking in to see if the above answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Cross subscription Azure SQL VM database restore using Azure CLI

1 answer

Your answer