Skip to main content
NetApp Knowledge Base

CSNAPC-9769: SCO backup verification leaves stale export policies on ONTAP

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

Issue

SCO backup with verification is successful but leaves behind stale export policies on ONTAP once the clone is deleted after verification completes.
This is observed for a specific configuration in NFS filesystem where user mounts  directly BOTH the volume AND its sub directories on a linux host.
We were able to reproduce the issue in-house by changing the mount configs
Example repro config: 

  • Data vol  svm21/datavol is mounted on /mnt/data on the linux host
  • Create a new directory under datavol(eg- TB1) and mount TB1 directory directly on host under /mnt/TB1
    • svm21/datavol ------- /mnt/data
    • svm21/datavol/TB1 ------- /mnt/TB1
  • create a new tablespace on /mnt/TB1 and register the same to the database
  • Take a new backup with verification of the database from SC
  • Backup with verification completes successfully leaving behind one SC generated Export Policy in ONTAP(1 export policy per extra mount)

 

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.