The nice thing about SmartPools and its file pool policies is that one doesn't need to change paths or directory names for data, just create (or modify) the policy rules. In particular, do not actually use path names like "/ifs/xnodes" -- this would be cumbersome to track and update when data gets migrated to another pool.  A bit more practical example (simplified, omitting the recommended "clustername" in the path): /ifs/projectA /ifs/projectB /ifs/projectC /ifs/projectD Let's say projects A-C are the "old" ones on X nodes so far, to be migrated to NL nodes, and project D has been freshly created for the "new purpose".  By a clear scheme, there would be three rules for projects A-C -> NL nodes and one rule  for projectD -> X nodes.  One might take a short cut and define the SmartPools "default policy" to be -> NL nodes and then have only one explicit policy for project D -> X nodes (less typing or clicking in the UI).  Makes sense?
I have a customer that has some data on X node of a Isilon cluster that has mix of X nodes and NL nodes, customer now wants to move all the data (~15TB) from x node to NL node and dedicate the x node for a different application, I haven't done this before so wanted to check what is the best way to go about it and if there is any tool available to move the data between different node type in same Isilon Cluster?
Moving Data between different storage nodes