I know that we should run reallocate after more disks are added, I also know that we should run it in volumes basis not on aggr level.
Here is my question. We have thousands of volumes, if we run the following command, then we wil have to keep track of all volumes and manually run through the list one by one. Yet, in SM situation, we will have to break SM relationship first, and go through the same in DR site.
It sounds very time consuming. will this be the right process that we will have to follow?
We have just added 2 new shelves, in addtion to 4 already configured ones which made up one large aggr. So, my question is, should I add these two shelves/disks into the existing aggr, or should I use these new two shelves to create a separate aggr.
I heard that one large aggr should come out better performance, in this sense, I should add two new ones into the existing aggr, thsu, we will only have one large aggr. The issue with this is that we will have to run "reallocate" on all existing volumes.
The other way is to create seprate aggr which includes 2 new shelves only. Thsu, we will not run "reallocate".
Thanks to snthlkumr , this is very helpful in saving efforts by scheduling Reallocation jobs.
However, since this is production environment, and sensitive to I/O activities. Plus, we have quite a few SVM's and each has quite a lot volumes, even with scheduling Reallocations, still it will be a long process.
I am thinking if it is worth it to add two new shelves into the existing aggr, or just to create a separate aggr then to avoid run reallocations. How much difference between these two method?