Adding Generic S3-Compatible Object Storage

 

Note

Only specific S3-compatible vendors are supported. Please see Feature Requirements for more information.

To add S3-compatible object storage to Inventory in NAKIVO Backup & Replication, follow the steps below:

  1. Verify that the S3-compatible object storage meets Feature Requirements.

  2. Click Settings in the main menu of NAKIVO Backup & Replication.

  3. Go to the Inventory page and click "+".

  4. On the Platform page of the wizard, select Cloud Storage and click Next to proceed.

  5. On the Type page of the wizard, select Generic S3-compatible Storage and click Next to proceed.

    1. On the Options page of the wizard, provide the following information:

      • Display name: Specify a name for the S3-compatible object storage device. This name will be displayed in the Inventory.

      • Service endpoint: Enter a full HTTP/HTTPS URL that is used to access the storage.

      • Region code: Optionally, enter the technical region code where the data is stored. To enter several region codes, separate them using the semicolon “;” symbol. It is highly recommended to leave this field blank.

      • Access key ID or Username: Enter the storage access key ID or username that was created during account setup or on the App Keys page in your storage account.

      • Secret access key or Password: Enter the storage secret access key or password that was created during account setup or on the App Keys page in your storage account.

      • Click Connect to bring up the Certificate Details popup.

      Note

      The Connect button may be disabled if no HTTP/HTTPS certificates are detected or required for the storage to be added to the Inventory.

  6. Optionally, you can select Auto accept new certificate if this certificate is expired or changed.

  7. Click Accept to confirm the certificate.

  8. Finally, click Finish when you are done.

    Note

    When configuring NGINX Proxy for MinIO Server used as the vendor for generic S3-compatible object storage, make sure you either turn caching off (proxy_cache off;) or set proxy_cache_convert_head off;.

    Find more information on the topic here.