Relocate failed or vetoed aggregates

Contributors Download PDF of this page

If any aggregates fail to relocate or are vetoed, you must manually relocate the aggregates, or if necessary, override either the vetoes or destination checks.

About this task

The relocation operation will have paused due to the error.

Steps
  1. Check the event management system (EMS) logs to determine why the aggregate failed to relocate or was vetoed.

  2. Relocate any failed or vetoed aggregates by using the following command:

    storage aggregate relocation start -node <node1> -destination <node2> aggregate-list <aggr_name> -ndo-controller-upgrade true

  3. When prompted, enter y.

  4. You can force relocation by using one of the following methods:

Option Description

Overriding veto checks

Use the following command:
storage aggregate relocation start -node node1 -destination node2 -aggregate-list <aggr_list> -ndo-controller-upgrade true -override-vetoes true

Overriding destination checks

Use the following command:
storage aggregate relocation start -node node1 -destination node2 -aggregate-list <aggr_list> -ndo-controller-upgrade true -override-vetoes true -override-destination-checks true