Skip to main content
NetApp Knowledge Base

What is the difference between -object-store-server and -object-store-name

  1. Last updated
  2. Save as PDF
Views:
106
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

FabricPool

Answer

  • What does the first and second command implement? What is the meaning of -object-store-name, and how is it different from -object-store-server?
::*> vserver object-store-server create -vserver Cluster -object-store-server S3server.local -is-  http-enabled true -is-  https-enabled false -listener-port 80 -status-admin up
 
::*> storage aggregate object-store config create -object-store-name LocalFPwithS3 -provider-type ONTAP_S3 -server S3server.local -is-ssl-enabled false -port 80 -container-name ontaps3bucket -ipspace Cluster -use-  http-proxy false -access-key OntapS3UserAccessKey -secret-password OntapS3UserSecretkey
  • The first command creates the object store server on the cluster, whereas the second command creates the FabricPool configuration, which enables the tiering of cold data to the object-store-server.
  • The object-store-name (e.g., LocalFPwithS3) is the name of the FabricPool configuration itself, where as the object-store-server (e.g., S3server.local) refers to the actual object store server.

Note: In the second command, the -server parameter refers to the same -object-store-server created in the first command.

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.