Isilon File Pool Policy Limitation / Workaround?

Question

All, We've reached the maximum amount of file pool policies defined with 128 (apparently it is not recommended to go over 30 file pool policies). We are a hosting company that manages over 500 NAS file systems across two tiers. The default policy places the data in the top tier, while the file pool policy moves the data down to the lower tier. Can anyone recommend a viable workaround to manage the growing environment? I know wildcard/expression can be used in the path but I wanted to check the community first since our local SE never comes back with an answer. Looking back, we probably should have just added the tier into the directory path and only have a handful of file pool policy. But we were not made aware of this limitation until we hit it. Here is how our structure is laid out on: /ifs/Isilon_cluster/accesszone/filesystem1 /ifs/Isilon_cluster/accesszone/filesystem2 /ifs/Isilon_cluster/accesszone/filesystem3 /ifs/Isilon_cluster/accesszone/filesystem4 ... ... /ifs/Isilon_cluster/accesszone/filesystem100 Can I do the following: Create new directory and create symbolic link on Isilon cluster with the new directory structure /ifs/Isilon_cluster/accesszone/tier2/filesystem100 -> /ifs/Isilon_cluster/accesszone/filesystem100 /ifs/Isilon_cluster/accesszone/tier2/filesystem200 -> /ifs/Isilon_cluster/accesszone/filesystem200 Apply file pool policy on /ifs/Isilon_cluster/accesszone/tier2/* Thanks in advance!

Vinh_ISD · Answer

Ugh, not sure why the formatting of the post got garbled up.

Isilon

Was this post helpful?