I have frequently searched for information about the running time of the reACLing process and have found little.
Because of this I want to share some information about reACLing NetApp Filers with you.
Performance of reACLing NetApp Filers
As Tim described in his article, NetApp Filers have to be edited remote via LAN.
This leads to the following questions:
- How long does the process of reAcling NetApp filers take?
- How high is the workload of the network?
During a domain migration I have just moved two NetApp Filer.
A filer consisted of three volumes which were edited simultaneously.
The result shows that the number of items is decisive and not so much the real data volume.
In this constellation approximately 550,000 items were processed per hour.
The simultaneous processing was not of any effect on the speed. The second NetApp Filer only had a Share containing 4,000,000 items. The processing-time was eight hours with again 500,000 items per hour.
It is also very interesting that the second reACLing process was about 50% faster than the first.
This helps with the planning because you can start the first reACling process a couple of days prior to and the faster “Delta”-process just before the conversion.
The workload of the network on the server doing the remote-reACLing was app. 1% of a 1Gbit link.