Skip to main content
NetApp Knowledge Base

How does character encoding affect file migration from RHEL7 (EUC-JP) to ONTAP (UTF-8)

  1. Last updated
  2. Save as PDF
Views:
135
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • Red Hat Enterprise Linux 7 (RHEL7) with EUC-JP encoding
  • NFS (v3, v4, v4.1)
  • SMB (SMB1, SMB2)
  • FTP

Answer

  • When migrating files from a server with EUC-JP encoding (such as RHEL7) to an ONTAP system using UTF-8 encoding, special considerations must be taken to avoid issues such as file name corruption. 
  • Here's how different protocols handle character encoding during migration:
    • NFSv4.x and SMB (CIFS): 
      • These protocols inherently use Unicode, which minimizes the risk of character encoding issues during migration. 
      • ONTAP systems, when using NFSv4.x or SMB, automatically handle the conversion between different character encodings. 
      • Therefore, when migrating data via these protocols, ONTAP does not require any special configuration for character encoding.
    • NFSv3: 
      • Unlike NFSv4.x, NFSv3 does not enforce the use of Unicode. 
      • When using NFSv3 to migrate data, it's crucial to ensure that the destination ONTAP system is configured to use the same character encoding as the source. However, due to potential risks of file name corruption, it's recommended to avoid using NFSv3 for migration if the source and destination have different character encodings. 
      • Instead, consider using NFSv4.x or SMB, which provide better support for encoding conversion.
    • FTP: 
      • The FTP protocol does not specify character encoding, which means it's up to the client and server to ensure they agree on the encoding used. 
      • When transferring files via FTP, make sure both the FTP client and the ONTAP system are set to use UTF-8 to prevent any character encoding issues.

Additional Information

additionalInformation_text
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.