Skip to main content
Prevent azure Backup&Recovery Service Vault's recovery point deletion before it really expires

Hi All!

Here before we might be able to delete the recovery point before it gets expired in Backup Vault (BV) and Recovery Service Vault (RSV) but now we can overcome some accidental deletion by restricting it.

Azure offers a feature called immutability which prevents the deletion of recovery point from azure BV and RSV until it really gets expired.

This feature is reversible by default(i.e. you can enable and disable from properties at any time). This option is not only at the time of creation. you can enable it even in the existing RSV and/or BV from their properties.

You can make the immutable irreversible too by locking immutability.

Please look into the below image(s)

Enable immutability option in new vault


Enable vault immutability option in existing vault

Comments

Post a Comment

Popular posts from this blog

Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
1 comment
Read more
Glimpse - Azure function migration from .net6 in-process to .net8 isolated Microsoft/Azure periodically announces the end of support for some services and ask us to migrate to a new version/release when they come up with a robust solution than the deprecated. In this post we are going to see a glimpse/UI configuration change of azure function 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗳𝗿𝗼𝗺 .𝗻𝗲𝘁𝟲 𝗶𝗻-𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗺𝗼𝗱𝗲𝗹 𝘁𝗼 .𝗻𝗲𝘁𝟴 𝗶𝘀𝗼𝗹𝗮𝘁𝗲𝗱. Here, I'm not going to deep dive about the migration whereas going to see the illustration of changing .net version from UI. For learning, GUI is the best place to start. So, as a dev guy we would prefer azure portal mostly. Consider a scenario that, you're requested to migrate your existing .net6 function app to be migrated .net8 isolated, you would go to settings panel and try to change the version in configuration, but the option would be disabled, it was disabled for me initially. Shocking and Afraid! After some point of ...
Post a Comment
Read more
Azure Devops - How to use classic pipeline variable group in YAML pipeline Hi All! When we need to use a group of variables in a pipeline, we can go for variable group instead of variables. The main usage of variable group is that can be used it across multiple pipelines in the same project. For example, I have a below variable group in my azure Devops. By default variable groups can be used across classic pipelines without any explicit permission granted but that variable group could not be used by YAML pipelines typically. So, How how can I use that variable group in my YAML pipeline? We can achieve it through "Pipeline permissions" option on top of variable group page. In the below image, I grant permission to my dotnet6app YAML pipeline to use variable group We can revoke if we don't need a YAML pipeline should not access variable group as below. Now, I want my all pipelines should use variable group. I don't want manual intervent...
Post a Comment
Read more