Also, if you are doing NAS data (and unstructured, like home dirs, NOT databases or VMDKs) you should upgrade to 9.7P5 and use FlexGroups which would utilize your entire system: aggregates on both nodes, Networking on both nodes, CPU/RAM on both nodes. Actually can improve performance!

--tmac

Tim McCarthy, Principal Consultant

Proud Member of the #NetAppATeam

I Blog at TMACsRack




On Tue, Jul 7, 2020 at 3:12 PM Oliver Brakmann <oliver.brakmann+toasters@posteo.de> wrote:
On 2020-07-07 20:51, Rue, Randy wrote:
> We're currently running two SVMs, each with its own aggregate, one one
> each node of a FAS8020 cluster running 9.1P6 (I know, I know).

Conceptually, SVMs do not own aggregates. SVMs can generally use
resources from all over the cluster.  For aggregates, you can restrict
that with the "aggr-list" property of the vserver object.

> When I try to add a new volume to one SVM I can only see one aggregate
> but I'd like to put that volume on the other aggr.

That's probably the aggr-list property then.  You can modify that list
with the vserver modify command:

vserver modify -vserver Vserver_name -aggr-list aggr_name[, aggr_name]

> How can I tell if I'm running HW or SW based ownership?

That won't be the issue. HW-based disk ownership has been deprecated in
the 7.3 days, IIRC, and ONTAP 9 doesn't support it at all anymore.

> To confirm, if I was running SW based should I be able to use either
> aggr on either SVM?
>
> And last, is there any way to change from HW to SW without tearing it
> all up?

As mentioned above, irrelevant.

Hope that helps,
Oliver
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
https://www.teaparty.net/mailman/listinfo/toasters