You might want to move an aggregate composed of array LUNs to a less-loaded system to balance the load processing over the systems.
Before you begin
- You should plan the number and size of your aggregates ahead of time so that you have flexibility in the amount of the workload that you can shift from one system to another.
- You should ensure that the target system meets the following requirements:
- The target system must be running a version of Data ONTAP that is the same as or later than the version running on the source system.
- The target system must support the size of the aggregate being moved.
- Enter the following commands on the target system:
- Enter the following to access the nodeshell: system run -node node_name
node_name is the name of the target system.
- Obtain the system ID of the target system by entering either of the following commands: disk show or sysconfig
You need to provide the target system's ID on the source system when you assign each of the array LUNs to the target system.
- Enter the following commands on the source system:
- Enter the following command to access the nodeshell: system run -node node_name
node_name is the name of the source system.
- Enter the following command to display the array LUNs that the aggregate contains: aggr status aggr_name -r
The array LUNs that are displayed are the LUNs that you need to reassign to the target system to be able to move the aggregate.
- Write down the names of the array LUNs in the aggregate that you want to move.
- Enter the following command to shut down the source system: halt
- At the boot environment prompt, enter the following command to boot the source system: bye
- Interrupt the boot process by pressing Ctrl-C when you see the following message on the console: Press Ctrl-C for Boot menu
- Enter Maintenance mode.
- When prompted whether you want to continue with booting, enter the following: y
- Enter the following command to take the aggregate offline: aggr offline aggr_name
aggr_name is the name of the traditional volume or aggregate.
- Enter the following and confirm that the aggregate is offline: aggr status
- In Maintenance mode, enter the following command separately for each array LUN in the aggregate that you are moving to the target system: disk assign -s system_id_target disk_id -f
system_id_target is the system ID of the target system (the system to which you want to move the array LUN.)
disk_id is the ID of the array LUN you want to move.
Note: Entering this command automatically removes ownership of the array LUN from the source system and assigns it to the target system.
- Enter the following commands on the target system.
- Enter the following command to start a scan so that the target system can recognize the LUNs you moved to it as its own: disk show
The target system should still be in the nodeshell
- Enter the following command: aggr status
The display shows the foreign
aggregate as offline.
Note: The aggregate you are moving is a foreign aggregate to the target system.
If the foreign aggregate has the same name as an existing aggregate on the system, Data ONTAP renames it aggr_name(1)
, where aggr_name
is the original name of the aggregate.
Attention: If the foreign aggregate is incomplete, that is, if you have not moved all the array LUNs in the aggregate, go back to the source system to add the missing array LUNs to the aggregate you moved to the target system. Enter the following on the source system: disk assign -s system_id_target disk_id -f
- If Data ONTAP renamed the foreign aggregate because of a name conflict and you want to change the name, enter the following command to rename the aggregate: aggr rename aggr_name new_name
aggr_name is the name of the aggregate you want to rename.
new_name is the new name of the aggregate.
The following command renames the users(1) aggregate as newusers:
aggr rename users(1) newusers
- Enter the following command to confirm that the aggregate you moved is online: aggr status aggr_name
aggr_name is the name of the aggregate.
- On the source system, reboot the system out of Maintenance mode.