Setting up object stores for FabricPool in a MetroCluster configuration

If you are running ONTAP 9.7 or later, you can set up a mirrored FabricPool on a MetroCluster configuration to tier cold data to object stores in two different fault zones.

Before you begin

About this task

Procedure

Specify the object store configuration information on each MetroCluster site by using the storage object-store config create command.
In this example, FabricPool is required on only one cluster in the MetroCluster configuration. Two object store configurations are created for that cluster, one for each object store bucket.
storage aggregate
    object-store config create -object-store-name mcc1-ostore-config-s1 -provider-type SGWS -server
    <SGWS-server-1> -container-name <SGWS-bucket-1> -access-key <key> -secret-password <password> -encrypt
    <true|false> -provider <provider-type> -is-ssl-enabled <true|false> ipspace
    <IPSpace>
storage aggregate object-store config create -object-store-name mcc1-ostore-config-s2
    -provider-type SGWS -server <SGWS-server-2> -container-name <SGWS-bucket-2> -access-key <key> -secret-password <password> -encrypt <true|false> -provider <provider-type>
    -is-ssl-enabled <true|false> ipspace <IPSpace>

This example sets up FabricPool on the second cluster in the MetroCluster configuration.

storage aggregate
    object-store config create -object-store-name mcc2-ostore-config-s1 -provider-type SGWS -server
    <SGWS-server-1> -container-name <SGWS-bucket-3> -access-key <key> -secret-password <password> -encrypt
    <true|false> -provider <provider-type> -is-ssl-enabled <true|false> ipspace
    <IPSpace>
storage aggregate
    object-store config create -object-store-name mcc2-ostore-config-s2 -provider-type SGWS -server
    <SGWS-server-2> -container-name <SGWS-bucket-4> -access-key <key> -secret-password <password> -encrypt
    <true|false> -provider <provider-type> -is-ssl-enabled <true|false> ipspace
    <IPSpace>