ONTAP Discussions
ONTAP Discussions
Hello Experts,
I know this should be possible, but could you please provide additional steps or latest trappings in order for me to execute this properly?
Thanks in advance.
Solved! See The Solution
Well your data aggregates are several "layers" away from your clients. Client access comes from either accessing a volume or a LUN, which in itself, is housed within an aggregate, which is made up of multiple disks.
Increasing the aggregate size by adding disks has no inherent effect on the volumes in the aggregate at all, let alone reaching down to within the volume or LUN level that a client could see. I can't immediately find a document saying it's not impactful but just by design, no it's not impactful.
As far as the client is concerned, it cares about access to the volume or LUN. It has no concept of what's even happening at the aggregate level, let alone disks.
Another document, might be helpful.
You can use the
>>storage aggregate add-disks
command with the -simulate field to get an output example before you actually commit the changes. You'll need the -mirror-disklist field as well to list the disks going into the mirrored aggregate. See below links for details.
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Protection_and_Security/MetroCluster/disk_count_in_first_plex_show_unexpected_number_when__addin...
Thanks Dareen for this information.
But in terms of rationalization on the client side, I need an information that this expanding or provisioning will not affect the production environment. Although technically speaking, we knew that all tasks to expand the Aggregates and also the assigning of disks is a so called “non-disruptive” operation. I'm actually looking for some kind of justification.
thanks!
Well your data aggregates are several "layers" away from your clients. Client access comes from either accessing a volume or a LUN, which in itself, is housed within an aggregate, which is made up of multiple disks.
Increasing the aggregate size by adding disks has no inherent effect on the volumes in the aggregate at all, let alone reaching down to within the volume or LUN level that a client could see. I can't immediately find a document saying it's not impactful but just by design, no it's not impactful.
As far as the client is concerned, it cares about access to the volume or LUN. It has no concept of what's even happening at the aggregate level, let alone disks.
Another document, might be helpful.
Thanks Darren for your inputs. Big help