Migrate Group Leader Functions to Backup Leader

You must have set up a secondary management IP address that is associated with the backup group leader array.

Use the group command to migrate the group data and management services from the Group Leader (GL) array to the Backup Group Leader (BGL) array. Having the BGL take over the GL management role, you can maintain services even though the original GL is offline. At that point, you can take the former group leader offline or remove it from the group.

IMPORTANT: Manually moving the GL array management role to the BGL array in the group is a support-assisted procedure. Performing group leader migrations with encrypted volumes in any pool in the group requires an outage window, because encryption passphrase reentry is required. For more details about manual Group Leader migrations, refer to KB-277.

Perform this task from the group leader array.

NOTE: It is a good practice to migrate the GL management services to the BGL before performing a scheduled outage.

From the CLI, log on to the group leader array.
Verify that the replicated configuration data on the BGL is current with the GL data.
group --status
This identifies the BGL, informs you whether it is “In-sync” (current) with the GL, and provides the secondary management IP address.
Determine whether you can safely migrate the group management services from the GL array to the BGL array.
group --check_migrate
Start the migration.
group --migrate
NOTE: If the migrate process cannot find a secondary management array, a message is displayed stating that the IP is missing. You have the option to create one and then restart the migration.

The operation normally takes up to about 60 seconds to complete. When it is complete, the backup group leader takes on the role of the group leader and starts handling the management tasks associated with the group. As the new group leader, it acquires the group scope IP addresses, including management and discovery.