Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Azure SQL DB/MI Immutable Storage setup #182

Open
joeharlan opened this issue Jun 17, 2024 · 0 comments
Open

Support for Azure SQL DB/MI Immutable Storage setup #182

joeharlan opened this issue Jun 17, 2024 · 0 comments
Labels
azure Microsoft Azure

Comments

@joeharlan
Copy link

Is your feature request related to a problem? Please describe.

In order for immutable backups of Azure SQL DB and MI to be created, there is a separate setup process that needs to be carried out in each Subscription that is done after the role for this Protection is onboarded. The steps are currently handled by a wizard in Rubrik Security Cloud. It is used to establish a single Archive Location configuration specifically for Azure SQL and allows the user to define database credentials for access to each instance. These credentials are then used to enable Change-Data Capture (CDC) and interact with the SQL Engine to coordinate the creation of BACPAC formatted exports. No automation currently exists for this process.

Describe the solution you'd like

These configuration and setup steps need to be automated in our provider and allow for the configuration of credentials on a per SQL DB / MI service instance basis.

Describe alternatives you've considered

No other options for automation of these steps exist today in any of the published SDKs.

Additional context

Setup reference in RSC Docs: https://docs.rubrik.com/en-us/saas/saas/azr_sql_setting_up_immutable_backups.html

@johan3141592 johan3141592 added the azure Microsoft Azure label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure Microsoft Azure
Projects
None yet
Development

No branches or pull requests

2 participants