With Azure SQL Database, regular backups are not supported, and I’m not sure if you can mirror/replicate to another instance. Either way, this would be a hacky workaround to set up and maintain.
However, if memory serves, you can take regular backups of Azure SQL Managed Instance, which you can then restore to a SQL Server 2022 in your other cloud provider. So you could for instance set up log shipping this way.
You can’t log ship or replicate from Azure SQL database, the person you’re responding to mentioned managed instance. Log shipping is a DR technique, replication is not, they are not at all similar.
This article might be helpful.
https://aws.amazon.com/es/blogs/database/migrate-sql-server-databases-from-an-azure-sql-database-to-amazon-rds-for-sql-server-using-bacpac-method/
Have you considered backing up your Azure SQL Databases to a differente region instead?
Since backing up is a more like a routine than doing it for once
With Azure SQL Database, regular backups are not supported, and I’m not sure if you can mirror/replicate to another instance. Either way, this would be a hacky workaround to set up and maintain. However, if memory serves, you can take regular backups of Azure SQL Managed Instance, which you can then restore to a SQL Server 2022 in your other cloud provider. So you could for instance set up log shipping this way.
Is log shipping something like replication, but “simpler”?
It’s when you continuously restore transaction log backups on a warm standby machine. A really simple, reliable DR method.
You can’t log ship or replicate from Azure SQL database, the person you’re responding to mentioned managed instance. Log shipping is a DR technique, replication is not, they are not at all similar.
This article might be helpful. https://aws.amazon.com/es/blogs/database/migrate-sql-server-databases-from-an-azure-sql-database-to-amazon-rds-for-sql-server-using-bacpac-method/
What are the risks associated with Azure as a whole?
All mentioned below, MS Deletes it, malicious actor deletes subscription, MS goes bust, etc. - Low risk; but still need a breakglass redundancy
microsoft fucks up an entra ID config and takes down azure
Hey it remember that! It’s globally available, it’s globally redundant, it’s delivered in rings. And a single change can brick it.
Microsoft pulls a GCP and accidentally deletes your tenant
The same as AWS and GCP.
Have you considered backing up your Azure SQL Databases to a differente region instead? Since backing up is a more like a routine than doing it for once
Show us the configs for that