Skip to main content
NetApp Knowledge Base

Creating a PVC from a Trident PVC Snapshot cannot be created in an alternate backend

  1. Last updated
  2. Save as PDF
Views:
250
Visibility:
Public
Votes:
4
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

  • Astra Trident
  • CSI-Snapshot supporting backend driver

Issue

Using a PVC, creating a CSI-Snapshot, and a StorageClass to create a PV from that snapshot, it doesn't matter which storagePools definition exists in the StorageClass, the clone PVC will always be created in the same Trident backend (e.g. SVM, driver) used by the original PVC, which also holds the Snapshot information.
 
For example, for ONTAP that means that the volume (and containing LUN) will appears in the same aggregate and SVM.
 
It cannot be created for a different backend with the same (and definetely not a different) driver, within the set of trident supported storage, e.g. by manipulating the StorageClass' storagePools setting. However, even when trying to retarget the backend, it will not fail the process, instead it will just not apply the requested storagePools or backend change.

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.