Skip to main content
NetApp Knowledge Base

Is it possible to remove, hide or set restrictive permissions for the .copy_offload folder?

Views:
882
Visibility:
Public
Votes:
0
Category:
clustered-data-ontap-8
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9

Answer

Is it possible to remove, hide or set restrictive permissions for the .copy_offload folder?

This folder is used by Microsoft Offloaded Data Transfer (ODX) in both SAN and SMB environments.

As long as ODX is in use, it is not possible for the folder to be hidden or removed, per the special system file requirements, as outlined in the Use cases for ODX.

When using the ODX feature, there are ODX system files, which exist in every volume of the system.
You must not remove or modify these files unless technical support tells you to do so.
These files enable point-in-time representation of data used during the ODX transfer. The following system files are in the root level of each volume that contains LUNs or files to which data is offloaded:

  • .copy-offload (directory)
  • .tokens (file under .copy_offload directory)

If the decision is made to disable ODX, remove the folder effectively by running the following command in diag mode:

::> set diag

Warning: These diagnostic commands are for use by NetApp personnel only.
Do you want to continue? {y|n}: y

::*> copy-offload delete-tokens -path dir_path -node node_name

Additional Information

 

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.