seanluce / anfhealthcheck Goto Github PK

Can the ANF Backup status be included on a per volume basis, e.g. completed or failed? For auditing purposes, can we report on ANF backup status over a length of time?

On line 280 in ANFHealthCheck.ps1 the wrong variable is used.

The line currently reads:
if($enableVolumeCapacityRemediationDryRun -eq $false) {

it needs to be changed to:
if($enablePoolCapacityRemediationDryRun -eq $false) {

In the current version of ANF HC script, Volume Snapshot Status is missing 'snapshot count' per volume column.

@seanluce first of all, thank you for providing this ANF Health Check, it is very helpful. it captures almost all the required information.
actually this is not an issue, rather a request. is it possible to include Pool Consumed Size (Current sum of all volume logical sizes) of the capacity pool?

Thank you in advanced.

Hi Sean,

I am trying to test the ANFHealthCheck runbook on my local computer first before try it through azure automation but when i run it nothing happened.

I am using the below parameter to run it locally.

.\ANFHealthCheck.ps1 -SubID xxxxxx -OutFile myfile.html

I only see the below msg and nothing happened, its been running for long time without any progress or error.

"Unable to Connect-AzAccount using these parameters" and after this msg it select the subscription and then nothing happened.

In scenario of using health check remediation mode for shrinking - the capacity pools are resized first and then volumes which is a problem as capacity pool will not shrink after volume size is reduced

ANF Backup structure was updated by Azure. They now use Azure Backup VAULT.
Some of the volumes now report a 0 count and no entry in the last backups.

This started after August 21st.

The recommended API call now is

az rest --method GET --uri '/subscriptions/*****/resourceGroups/resourcegroupname/providers/Microsoft.NetApp/netAppAccounts/netappaccountname/backupVaults/testVault/backups?api-version=2022-11-01-preview'

Requirement - Need to enable the vault and add all the volumes before this works.

Can you check if the fix that was applied on 23rd August could have impacted this backup reporting issue? and I see this issue only in South Central US as of today and not in other regions.

This issue can be reproduced as well – see below even the commands are not working –

Same command I run for volumes ctc019 and ctc018, for volume ctc018 I can see backups but for ctc019 only Null value [ ] even though this volume has backups that are visible in GUI.

Right now, ANF Healthcheck remediation doesn't maintain a log of what changes it made. It would increase the adoption of the code if we had logged the changes.