Azure Workload Backup Troubleshooting Scripts

This repo maintains troubleshooting scripts for various issues faced during workload backup ( SQL in Azure VM, SAP Hana in Azure VM ) via Azure Recovery Services Vaults.

These scripts can be utilised to root cause the problems faced by customers during times of critical database backups and database restores. Additionally, some of these scripts are can be used for automating operations and simplifying user experience for workload backup.

Key scenarios covered

• Troubleshooting outbound network connectivity requirements for streaming backup services for SQL and HANA
• Appropriate permission setting to VM managed identity (system-assigned or user-assigned) for integrating with database consistent snapshots with streaming backup services for SQL and HANA

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

Please report issues if any script fails to complete its intended purpose. We actively try to fix the bugs and rectify them.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.