On Tue, May 08, 2018 at 01:33:47AM +0000, Fenn, Michael wrote:
How many total shares do you have? We've had good luck with a 1:1 ratio of volumes to shares since the platform limit is 1000 volumes/node on most recent hardware. With that model, you can shuffle volumes (and thus shares) between aggregates online with vol move, and you get easy access to goodies like QoS.
We have about 1300 shares at the moment. More volumes is not manageable IMHO. For example, an altavault restricts snapmirror to 100 volumes. We already have more volumes that that.
Regards, pdg
"Peter" == Peter D Gray pdg@uow.edu.au writes:
Peter> On Tue, May 08, 2018 at 01:33:47AM +0000, Fenn, Michael wrote:
How many total shares do you have? We've had good luck with a 1:1 ratio of volumes to shares since the platform limit is 1000 volumes/node on most recent hardware. With that model, you can shuffle volumes (and thus shares) between aggregates online with vol move, and you get easy access to goodies like QoS.
Peter> We have about 1300 shares at the moment. More volumes is not Peter> manageable IMHO. For example, an altavault restricts Peter> snapmirror to 100 volumes. We already have more volumes that Peter> that.
Yeah, I can see how that would grow pretty badly. Of course 1300 shares is a huge number too, maybe too many? It would be interesting to see how you logically split things up. It tends to grow over time unfortunately, without planning until you hit the point you need planning. Heh.
I assume you're in cDOT mode? Would maybe setting up juntion paths would be the better solution, where you share out a group of top level CIFS shares, and then the next level down you have volumes mounted... but you said you have too many volumes already, so that probably won't fly.
I personally would be pushing to have *fewer* shares and more volumes/qtrees. Though I'm not sure if qtrees have gotten all the abilities of 7-mode yet in the 9.x series of cDOT.
Can you give a made up example maybe? Then again, I'm really just bikeshedding here, not providing a good solution. :-(
John