Skip to main content
NetApp Knowledge Base

ACC replication fails if a different peer name than the remote SVM name

Views:
7
Visibility:
Public
Votes:
0
Category:
astra
Specialty:
snapx
Last Updated:

Applies to

  • Astra Control Center 23.10.0-68, 24.02 (ACC)
  • Trident 24.02

Issue

Whenever BlueXP is used for creating a mirror relationship for the first time between two vservers, a vserver peer must be created.
At that point, BlueXP creates the vserver peer by choosing a 'Peer Vserver Name' DIFFERENT than 'Remote Vserver Name'.
Since the peer vserver name is different, so volume provisioning fails on the destination cluster and stuck in pending state when replication is initiated using ACC.

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.