Alright, thanks – Maybe I can find a way to work around the need for distinct volumes by using qtrees or something like that for this specific application.

Best,

Alexander Griesser

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia-it.com

Web: http://www.anexia-it.com

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Von: Parisi, Justin <Justin.Parisi@netapp.com>
Gesendet: Mittwoch, 25. Juli 2018 21:45
An: Alexander Griesser <AGriesser@anexia-it.com>; Toasters <toasters@teaparty.net>
Betreff: RE: Max volume count per node

There is no way to raise it. It’s set to the limit based on the max load a node can carry in the event of a failover and is hard coded. There are discussions to raise the limit in the future, especially with the use of FlexGroup volumes, but there is no timetable.

As for now, to raise your max vol count, add more nodes. :-P

From: toasters-bounces@teaparty.net <toasters-bounces@teaparty.net> On Behalf Of Alexander Griesser
Sent: Wednesday, July 25, 2018 12:39 PM
To: Toasters <toasters@teaparty.net>
Subject: Max volume count per node

Hey there,

does anyone know what the real implication of the max volume count per node setting on the FAS systems is good for?

Is there any chance that this limit gets raised on newer OnTap releases or is there any secret flag to raise it (knowing that support would not want to see that)?