Skip to main content
Question

unable to do a backup with nutanix AHV

  • August 27, 2026
  • 1 reply
  • 9 views

Forum|alt.badge.img+1

Hi everyone,

We are currently facing a Commvault backup issue on Nutanix AHV.

The initial problem was related to HotAdd / SCSI device detection on the Commvault Access Node. To fix that first issue, we had to add the following additional setting on the Access Node:

VirtualServer\bEnableSCSIWLunDeviceCleaner = True

After enabling EnableSCSIWLunDeviceCleaner, the initial HotAdd issue was resolved.

The logs now confirm that the disk is correctly attached and opened:

Disk [SCSI.0] is attached at [/dev/sdb]

Opened [/dev/sdb] successfully

However, we are now facing a different issue when Commvault calls the Nutanix Data Protection APIs.

The compute-changed-regions call returns:

HTTP 401
Invalid cookies present in the request

Commvault then reports:

JWT Token has likely expired. Trying Discover cluster again

During the new cluster discovery attempt, Nutanix returns:

HTTP 429

Failed to perform the operation as rate limit set by the API has been exceeded

PLAT-10003 - RATE_LIMIT_EXCEEDED

Then compute-changed-regions fails again with:

401 - Invalid cookies present in the request

and eventually:

ComputeAllocatedRegionsForDisk failed

Failed to get disk file extents

Since the disk is now correctly attached and opened, the issue seems to be related to JWT/session handling and API rate limiting on the Nutanix Data Protection APIs.

We also noticed that different API versions are being used:

discover-cluster        -> v4.1
compute-changed-regions -> v4.0

Has anyone seen this behavior with Commvault and Nutanix AHV, especially the following errors?

401 - Invalid cookies present in the request
PLAT-10003 - RATE_LIMIT_EXCEEDED
JWT Token has likely expired

Any information about a known issue, Nutanix KB, workaround, or fix would be appreciated.

1 reply

Sureshkumar S
Vaulter
Forum|alt.badge.img+12

Hi ​@mahmoud Hatira ,

Good day!

I hope this is nutanix prism central client 

I could see that there is a fix for API issues on customer maintenance release MR44.18

Try updating your accessnodes to MR44.18 and retry backup

Regards,

Sureshkumar S