Skip to main content
Question

Nutanix Files deployment and migration from an existing Files environment

  • April 27, 2026
  • 3 replies
  • 22 views
Daniel Martinez
Forum|alt.badge.img+2

Hi,

Im working on a project where we need to deploy a new Nutanix Files instance on a new AHV cluster.

The customer already has an existing Nutanix Files deployment running on an older AHV cluster that will be destroyed as soon as it is migrated. Also as part of the project we will have to migrate the existing shares and data from the old Files environment to the new one (as well as from other FS not related with nutanix files).

I would like to clarify two main points:

1. Deployment method: Prism Central vs Prism Element

For a new Nutanix Files deployment, is it currently recommended to deploy and manage the File Server from Prism Central / Files Manager, or is it still preferable in some cases to deploy it directly from Prism Element?

My understanding is that Prism Central / Files Manager is the more modern and centralized approach, especially when managing multiple clusters or using newer Files features, but this scenario means we have only one prism central and one cluster so I would like to confirm whether there are any limitations, caveats, or best practices that would make Prism Element a better option in some scenarios.

2. Migration from old Nutanix Files to new Nutanix Files

Once the new File Server is deployed, what would be the recommended migration approach from the existing Nutanix Files environment to the new one, with minimum service disruption?

The current idea would be to create the shares on the new File Server, perform an initial data copy, run incremental synchronizations, and then perform a final cutover during a maintenance window. However, I would like to understand what Nutanix recommends as the best option:

  • Native Nutanix Files migration features / Smart Sync / Smart DR, if applicable
  • Nutanix MOVE 
  • Robocopy for SMB shares
  • rsync or another method for NFS exports
  • DFS Namespace or DNS alias cutover for minimizing impact on users
  • Any other recommended procedure

 

I am also interested in understanding what is migrated automatically and what must be recreated manually on the new File Server, for example:

  • SMB shares
  • NFS exports
  • Share-level permissions
  • NTFS permissions / ACLs
  • AD user/group permissions
  • NFS permissions or export rules
  • Quotas
  • Snapshot schedules
  • Any File Analytics, antivirus/ICAP, or other Files-related configuration

One point I would especially like to clarify is the permissions part. For SMB shares, I assume the relevant permissions are the share permissions plus the NTFS ACLs, based on AD users/groups. For NFS, I assume the relevant configuration is more related to export rules, allowed clients, root squash, UID/GID mapping, etc. Is that correct, or is there any Nutanix-specific permission model that needs to be migrated separately?

Any guidance, best practices, official documentation references, or real-world experience with Nutanix Files-to-Files migrations would be appreciated.

Thanks in advance!!!

3 replies

J
Forum|alt.badge.img+3

1. Deployment method: Prism Central vs Prism Element
you will install the nutanix files in PE for PC you will install the file manager and from there you can manage files which are hosted on all PE (your case , you have only one).mostly PC for file will be used for advanced feature, such as smart-DR and etc.
2. Migration from old Nutanix Files to new Nutanix Files
I think move is the best option, if you like to go with nutanix files DR , then you need to see the compatibility and etc, I suggest open a case with Nutanix if you like to understand your options, again please read your move release note (as you need a version which is compatible with both clusters) and see if there is any limitation which is a show stopper for you.


 

    C
    Nutanix Employee
    • CristiNutanix Employee
    • Nutanix Employee
    • April 28, 2026

    ​​​​​Deployment method: Prism Central vs Prism Element

    When your FS will be running any of the newer versions (5.3 etc) your FS will be PE deployed but PC managed. 
    Basically you can do it old style (PE deployed) and benefit from all the new functionalities. 
    Migration from old Nutanix Files to new Nutanix Files

    You can use a PD based failover (you only handle the PD level replication etc) but basically you bring up the old FS with on the new AHV cluster. If you don’t want that and you can afford running both FS in parallel , you can do SmartDR.
    Smartsync is also a good option here especially if you want to switch some of your shares from Standard to distributed.

    I’d recommend to see if you can perform an audit (use some PS hours if you have)  this way you’ll get a tailored recommendation for what is better for you to do.

     

      Daniel Martinez
      Forum|alt.badge.img+2

      Hi Cristi,

      Thanks, this is very useful!

      So, if I understood correctly, even with newer Files versions such as 5.3+, it is still valid to deploy the File Server from Prism Element in the traditional way and then manage it from Prism Central / Files Manager, while still benefiting from the newer functionalities. That is good to know!

      Regarding the migration, the customer currently has an existing Nutanix Files deployment on an older AHV cluster as mentioned in the first post, and the goal is to move the shares/data to a new AHV cluster with minimum service impact.
       

      Based on your reply, I understand the possible options as follows:

      - PD-based failover: useful if we want to bring up the existing File Server on the new AHV cluster almost as-is, but that includes the FSVMs too or just the data (the shares)??
      - SmartDR migration tool: useful if we can run both File Servers in parallel and perform a controlled migration.
      - SmartSync: useful especially if we want to migrate or reorganize some shares, for example changing some Standard shares to Distributed.
      - Robocopy/rsync: possible fallback if native options are not suitable or if we need a more manual approach. For example if we have to migrate a CIF share that is placed on an external storage such as Netapp or NAS or whatever

      I assume that all the previous options will keep the ACL or NFS user permissions over shared folders...

       

      Terms & ConditionsAccessibility statement