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

[AVM Question/Feedback]: Recovery Services Vault #3889

Open
1 task done
vivsri opened this issue Dec 5, 2024 · 8 comments
Open
1 task done

[AVM Question/Feedback]: Recovery Services Vault #3889

vivsri opened this issue Dec 5, 2024 · 8 comments
Assignees
Labels
Needs: Triage 🔍 Maintainers need to triage still Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Question/Feedback 🙋 Further information is requested or just some feedback

Comments

@vivsri
Copy link

vivsri commented Dec 5, 2024

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Description

Hi,
Thanks for the RSV module. I just wanted to highlight that we are missing the enhanced policy for backups, which is a requirement for TPM & Secure Boot Enabled VMs.
I got it work so wanted to share the param file with the updated settings for that policy, pls feel free to update your module.
It took me some time to make it work, so worth sharing :)

param parBackUpPolicy = [
  {
    name: 'EnhancedVMpolicy'
    properties: {
      policyType: 'V2'
      backupManagementType: 'AzureIaasVM'
      instantRpRetentionRangeInDays: 2
      protectedItemsCount:0
      timeZone: 'UTC'
      retentionPolicy:{
        retentionPolicyType:'LongTermRetentionPolicy'
        dailySchedule:{
          retentionDuration:{
            count: 180
            durationType: 'Days'
          }
          retentionTimes:[
            '2024-12-04T08:00:00Z'
          ]
        }
        weeklySchedule:{
          daysOfTheWeek:[
            'Sunday'
          ]
          retentionDuration:{
            count: 12
            durationType: 'Weeks'
          }
          retentionTimes: [
            '2024-12-04T08:00:00Z'
          ]
        }
        monthlySchedule:{
          retentionScheduleFormatType: 'Weekly'
          retentionScheduleWeekly:{
            daysOfTheWeek: [
              'Sunday'
            ]
            weeksOfTheMonth:[
              'First'
            ]
          }
          retentionTimes: [
            '2024-12-04T08:00:00Z'
          ]
          retentionDuration:{
            count: 60
            durationType: 'Months'
          }
        }
        yearlySchedule:{
          retentionScheduleFormatType: 'Weekly'
          retentionScheduleWeekly: {
            daysOfTheWeek: [
              'Sunday'
            ]
            weeksOfTheMonth:[
              'First'
            ]
          }
          monthsOfYear: [
            'January'
          ]
          retentionDuration:{
            count: 10
            durationType: 'Years'
          }
          retentionTimes:[
            '2024-12-04T08:00:00Z'
          ]
        }
      }
      schedulePolicy:{
        schedulePolicyType: 'SimpleSchedulePolicyV2'
        hourlySchedule: {
          interval: 4
          scheduleWindowDuration: 12
          scheduleWindowStartTime: '2024-12-04T08:00:00Z' 
          }
        scheduleRunFrequency:'Hourly'
      }
    }
  }
]
@vivsri vivsri added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Question/Feedback 🙋 Further information is requested or just some feedback labels Dec 5, 2024

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days label Dec 11, 2024
@AlexanderSehr
Copy link
Contributor

Hey @vivsri,
Please excuse the late reply, but as the issue was not created as a module issue the automatic owner assignment did not kick in. Highly recommend for next time 😉

@alexanderojala, please triage the issue when you get the chance 🙂💪

@alexanderojala
Copy link
Contributor

The module deploys default backup policies and also it includes a enhanced policy for Azure VMs. I dont think that the module should contain any custom/additional policies. Due to not everyone using the module, having the need for additional custom policies.
Image

@AlexanderSehr Any inputs from your end?

@AlexanderSehr
Copy link
Contributor

AlexanderSehr commented Dec 18, 2024

Now I am a bit confused 😄

If I can see it correctly, only the max test deploys a number of backupPolicies:

  • VMpolicy
  • sqlpolicy
  • filesharepolicy

And the EnhancedVMpolicy would 'just' be another policy that could be added to that list. Maybe I'm overlooking it, but I don't see where it is currently implemented. If that's the case and it is somewhat hard to figure out as @vivsri pointed out, then I guess the only ask here is

  • Should we also add it to the max test so that others can use it as a reference
  • Not add it

If I'm not mistaken and it's just a reference for a somewhat tricky policy, then I'd lean towards the former. An easy addition. Thoughts @alexanderojala? Your screenshot tells me the policy is already deployed but I just can't see where 😄

@alexanderojala
Copy link
Contributor

The module itself does not deploy any custom policies, just the build-in once's (as expected) , HourlyLogBackup(sqlpolicy), DefaultPolicy and EnhancedPolicy for AzureVMs.

My opinion is that we should not add any custom policies to be created when using the module, because the use case for the policy would not apply to every user.

We could argue for it to be added to the max testing, but again there is a built-in EnhancedPolicy deployed so i dont really see the need to test it with a custom policy.

@AlexanderSehr

@AlexanderSehr
Copy link
Contributor

Fair point, thanks @alexanderojala. I agree that it should not be part of the module, but at most the test.

@vivsri I'm currently working on an update that will add UDTs for the backup policies (next to other things). Would that have helped to create the custom policy you listed above? Or would you argue that we should add the example you posted above regardless? As @alexanderojala mentioned, there is a default EnhancedPolicy afterall.

Just want to make sure we get to the best outcome :)

@vivsri
Copy link
Author

vivsri commented Dec 20, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage 🔍 Maintainers need to triage still Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Question/Feedback 🙋 Further information is requested or just some feedback
Projects
None yet
Development

No branches or pull requests

3 participants