Skip to main content
NetApp Knowledge Base

Trident Protect SnapMirror Relationship Remains Uninitialized Due to Incorrect SVM Peering Configuration

  1. Last updated
  2. Save as PDF
Views:
11
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • NetApp ONTAP (9.x and newer, Cluster-Mode)
  • Trident/Trident Protect
  • Kubernetes/OpenShift clusters using Trident Protect for DR
  • SnapMirror XDP relationships managed by Trident Protect

Issue

  • After configuring TridentProtect for disaster recovery in a Kubernetes/OpenShift environment, SnapMirror relationships are created on the destination Storage Virtual Machine (SVM), but they remain in an “Uninitialized/Idle” state and do not progress to “Established”.
  • As a result, data replication for DR does not function.
Observed log output:
time="2026-07-22T14:53:29Z" level=error msg="GRPC error: rpc error: code=Unknown desc=encountered error(s) in creating the volume: [Failed to create volume pvc-bf79cc49-0f3b-416a-bbdc-74ff945b1411 on storage pool ... from backend ...: backend cannot satisfy create request for volume ... (backend SVM <DR_SVM> is not peered with required SVM <SOURCE_SVM>)]"
logLayer=csi_frontend requestID=f2f12bd7-42c1-4c7d-b374-3cc949b36ece requestSource=CSI
ONTAP SnapMirror show output:
<DR_SVM>:volume1 XDP <DR_SVM>:volume2 Uninitialized Idle - true -
ONTAP peer show output:
Peer Vserver      State    Applications   Remote Vserver
---------------------------------------------------------
<DR_SVM>          peered   snapmirror     <SOURCE_SVM>
<SOURCE_SVM>      peered   snapmirror     <DR_SVM>

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.