Skip to main content
NetApp Knowledge Base

Trident backend definition update on MetroCluster switchover and -back made easy

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

Applies to

  • Trident for Kubernetes/Openshift
  • (Clustered) ONTAP Metrocluster switchover/switchback
  • SVM-DR usage failover/giveback

Description

According to the online documentation, when an MetroCluster, which uses VServer-DR, is in use, and a switchover or switchback happens, several things need to be handled:
  • if the SVM name is in the TBC YAML or the tridentctl managed JSON (Point 6: SnapMirror SVM Disaster Recovery Workflow for Trident), it needs to be updated - see also Issue #228
  • the TBE created from the TBC also maintains a list of storagePools in its definition, albeit base64 encoded - see:
    • kubctl get tbe <BACKEND> -n <TRIDENT_NAMESPACE> -o json
    • base64 -d "<base64_encoded_string>"

 

 

 

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.