I'm looking for advice on how to back up my Azure SQL Database in a way that meets compliance requirements, specifically in a cross-subscription setup. It seems like Azure SQL DB doesn't support Long Term Retention (LTR) backups across subscriptions natively. Has anyone explored other methods to achieve this? Any insights would be appreciated!
3 Answers
It's important to note that Azure subscriptions are mainly for billing and role-based access control, not really for backup operations. You can't create a backup in a different subscription since they're not associated with a specific region. The manual approach with scripts and a storage account might work, but I wouldn't recommend that unless absolutely necessary.
If there's a risk of losing a subscription, make sure your applications can quickly set up new ones and recover from backups. This could save a lot of headaches in the long run.
You should clarify what your compliance requirements actually are. Do they specifically mandate that backups exist across subscriptions, or is there a bit of flexibility? That could change your approach significantly.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Fix Not Being Able To Add New Categories With Intuitive Category Checklist For Wordpress
Get Real User IP Without Installing Cloudflare Apache Module
How to Get Total Line Count In Visual Studio 2013 Without Addons
Install and Configure PhpMyAdmin on Centos 7
How To Setup PostfixAdmin With Dovecot and Postfix Virtual Mailbox