Skip to main content
commvault.com commvault.com
Question

unable to do a backup with nutanix AHV

  • August 27, 2026
  • 3 replies
  • 41 views
Novice
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.

3 replies

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

MichaelCapon
Vaulter
Forum|alt.badge.img+19

Hello ​@mahmoud Hatira,

 

Could you clarify the size of the VM disks where we’re hitting the API rate limit on the Nutanix APIs during backup?

Does this issue affect specific backup Jobs? (For Speciifc VM’s? Or only incremental jobs?)
Also, How many VM’s are scheduled to backup at the same time here?

 

Thanks & Kind Regards,

Michael

yousef
Apprentice
  • yousefApprentice
  • Apprentice
  • September 8, 2026

Hello ​@mahmoud Hatira,

To start with, I recommend using the VSA for Nutanix AHV available in the Commvault Software Store:

Commvault Software Store – Nutanix AHV VSA

The package is available in QCOW2 format and can be deployed on the Nutanix AHV environment.

Regarding the backup issue, it appears to involve two main Nutanix API errors:

  • HTTP 401 – “Invalid cookies present in the request”: This is typically related to authentication or an expired/stale API session.
  • HTTP 429 – “RATE_LIMIT_EXCEEDED (PLAT-10003)”: This indicates that the Nutanix API is throttling requests due to a high number of API calls.

Recommended Troubleshooting

1. HTTP 401 – Authentication Issue

  • Verify that the credentials configured in Commvault for Prism Central are valid.
  • Use a local Prism Central account or supported directory service account rather than a SAML/SSO account.
  • Re-enter the Prism Central credentials in Commvault Command Center.
  • Restart the Commvault services on the VSA/access node to clear any cached authentication sessions.
  • Test connectivity from the access node to Prism Central over TCP 9440.

2. HTTP 429 – API Rate Limiting

  • Check the current Nutanix API rate-limit configuration.
  • Avoid running a large number of concurrent backup operations against the same Prism Central.
  • Review the number of concurrent data readers and reduce them if necessary.
  • Stagger backup jobs where possible to reduce simultaneous API requests.
  • If the issue continues, Nutanix Support can review the API throttling and rate-limit configuration.

3. API Compatibility
The logs show that different Nutanix API versions are being used for some operations (for example, v4.1 and v4.0). This can be normal depending on the Nutanix environment, but we should verify that the Prism Central/AHV versions are supported with the installed Commvault release.

I recommend starting with the VSA deployment and authentication verification, then we can monitor the backup job and address the API rate-limiting issue if it occurs again.

 

https://www.linkedin.com/in/yosef-hesham-3a34a9190/

Readiverse Academy Certifications

description of image
Terms & ConditionsAccessibility statement