Migrate SMB, NFS, and DFS FROM Isilon TO Netapp CVO

DFS? Are you looking to move to a new DFS environment of just update the targets of your existing DFS folder?    If just switching the targets at cutover, utilize powershelll with the DFS plugins and script it out.  

The ACLs are a different story. We have a mixed environment where we are utilizing two authentication providers (Active Directory and Redhat LDAP) each being independent of each other. and a mapping rule on the PowerScale clusters to map a token by user name.  This caused issues with migrating shares to Netapp as during the sync, it might pull over the permission as a AD account or LDAP account.  With our Netapp environment strictly authenticating against AD and not LDAP, it would give the LDAP accounts the pass the local Sid in the mapping token the permission.     

To get around this we wrote a script that spanned the tree of the share once migrated to Netapp, and if a Sid is found, does an api call of the Sid to the Powerscale cluster the source was on, matches it to the AD name and removed the SID and applies the AD account and the permissions.  

if your ok with a paid product, datadobi handles nfs and smb covering multi protocol shares.

re dfs, thats a bit left field. If there are not a huge amount of dfs paths, suggest doing it in tranches so you can migrate a group of shares at a time so limiting any potential 'blast radius' I have not come across a specific DFS migration tool as its normally;

1. small
2. changing DFS records to the new underlying path

@tchstnut Thank you for replying, we are moving the DFS shares from on-prem to cloud. We want to retain all permissions, but at the same time remove some old admin access which is no longer required. I believe our authentication will be AD only, with the view there will eventually be no data on-prem at the end.

@cadencep45 I'm not in a position to buy a paid product, I am working for a huge company where the flexibility to do that is beyond my reach and control unfortunately.

It's important to have a solid plan in place to ensure a smooth transition. Here are some suggestions for migrating SMB, NFS, and DFS to NetApp CVO:

1.  Before you begin migrating your data, you should plan out your migration strategy. This should include identifying which data needs to be migrated, mapping out your file system hierarchy, and determining the order in which you will migrate your data.

2. Use a migration tool: Migration tools are designed to help you transfer your data from one system to another. There are a number of migration tools available, including EMCopy, Robocopy, rsync, Goodsync, Gs Richcopy 360, and Datadobi. These tools can help you preserve file permissions and ACLs during the migration process.

3. Before you begin migrating your production data, it's a good idea to test your migration process on a smaller scale. This will help you identify any issues that may arise during the migration process and allow you to make any necessary adjustments.

4. Monitor your migration: During the migration process, it's important to monitor your migration to ensure that everything is running smoothly. This may involve monitoring the progress of your migration, watching for errors or warnings, and ensuring that your data is being migrated in the correct order.

5. Verify your migration: Once your migration is complete, it's important to verify that your data has been successfully migrated. This may involve performing spot checks of your data, comparing file sizes and timestamps, and ensuring that permissions and ACLs have been preserved.

In terms of migrating DFS, you may want to consider using a tool like Microsoft's DFSR Migration Tool, which is designed specifically for migrating DFS. This tool can help you ensure that your DFS namespaces are migrated correctly and that your DFS replication links are re-established after the migration.