In MetroCluster the limit looks to be 96 disks, is this the same for a normal AFF? Checking HWU this says 48 partitions can be deployed at initialisation, but can be increased later, Id like to include as many as possible from the outset.
#AFF - ADP Disk Limit
arctic nexus
pearl zodiac
Correct. MCC (whether MCC-FC or MCCIP) has a strict requirement of symmetric drive layouts. In that, you will need twice as many drives at each site. Once group of 48x drives will be for the local HA pair; the other 48x drives will be for the remote HA pair.
It will look something like this in the end.
Please follow the MCC deployment instructions carefully to ensure that the local nodes have drives allocated to Pool0 and the remote nodes will be contained within Pool1.
arctic nexus
Sorry it was more around the non-mc setups and what the upper limit of partitioned disks was allowed? At initialisation its 48, but wasn't sure how many after you could add.
pearl zodiac
You can exceed 48x, but it is done manually by various means.
arctic nexus
If you had 4x fully populated NS224 shelves connected to an A900 at initialisation will ONTAP only partition the disks in the first 2 shelves, or will it use another way to choose 48 disks across all 4 shelves?
pearl zodiac
I will only target 48x drives during initialization
Your best best is to initialize with only 48x drives. Then, disable auto-assignment manually via CLI.
From there, attach the other 48x drives but assign them to Pool1 instead.
If you initialize the system with all drives attached, they will be in Pool0 and ineligible for MCC usage
arctic nexus
This is a non mcc setup, but I'm guessing same rules about number of disks connection at initialisation applies?