storage aggregate object-store attach
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Attach an object store to an aggregate
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The storage aggregate object-store attach
command attaches an object store to an aggregate to create a FabricPool. This command requires two parameters to create a FabricPool - an aggregate and a configuration to attach an object-store to the aggregate. This command verifies whether the object store is accessible through the intercluster LIF both from the node on which the aggregate is present as well as its High Availability (HA) partner node. The command fails if the object store is not accessible. Once an object store is attached to an aggregate, it cannot be detached.
Parameters
-aggregate <text>
- Name of the Aggregate-
This parameter specifies the aggregate to which the object store must be attached to create a FabricPool.
-object-store-name <text>
- Object Store Configuration Name-
This parameter specifies the object store configuration that describes the object store to be attached. The object store configuration has information about object store server name, port, access credentials, and provider type.
[-allow-flexgroup {true|false}]
- Allow Existing FlexGroup Constituents in the Aggregate on Attach-
This optional parameter allows attaching object store to an aggregate already containing FlexGroup constituents. The default value is false. Mixing FabricPools and non-FabricPools within a FlexGroup is not recommended. All aggregates hosting constituents of a FlexGroup should be attached to the object store.
Examples
The following example attaches an object store to aggregate aggr1:
cluster1::>storage aggregate object-store attach -aggregate aggr1 -object-store-name my-store