Skip to main content
NetApp Knowledge Base

Kubernetes Trident TMR Configuration Fails: “No available backends for storage class” and Replication Not Detected

  1. Last updated
  2. Save as PDF
Views:
31
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Trident (Astra Trident) 26.x and later
  • Kubernetes / OpenShift clusters using Trident CSI
  • Trident Mirror Relationships (TMR) with SnapMirror
  • SVM peering and replication configurations

Issue

When configuring Trident Mirror Relationships (TMR), Persistent Volume Claim (PVC) provisioning fails for StorageClasses that require replication.

Observed Errors (Trident Logs)

time="2026-06-03T01:39:24Z" level=info msg="nobackendpools support the requisite protocol" logLayer=core requestID=... requestSource=CSI workflow="volume=create"time="2026-06-03T01:39:24Z" level=info msg="nobackendpools support any requisite topologies" logLayer=core requestID=... requestSource=CSI workflow="volume=create"time="2026-06-03T01:39:24Z" level=info msg="nobackendpools found for given NASType" logLayer=core requestID=... requestSource=CSI workflow="volume=create"time="2026-06-03T01:39:24Z" level=error msg="GRPC error: rpc error: code=Unknown desc=no available backends for storage class rep-ontapnas" logLayer=csi_frontend requestID=... requestSource=CSI

Observed Behavior
  • PVC provisioning fails for replication-enabled StorageClass
  • kubectl get tmr does NOT show localVolumeHandle
  • No volume is created on ONTAP backend
  • Backend shows replication capability as false

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.