Skip to main content
NetApp Stage KB

Unable to set up backup to AWS S3 from On-prem from non-default IPspace with port or server error

Views:
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
CORE
Last Updated:

Applies to

  • Cloud Manager
  • Backup enable on On-Prem
  • AWS S3
  • AWS S3 Private Link
  • HTTPS
  • Path Style URL
  • Cloud Backup Services (CBS)
  • non-default IPspace

Issue

Unable to setup Cloud backup to S3 over AWS S3 private link from On-prem to AWS S3 from non-default IPspace on On-prem.

OnPremCluster::*> snapmirror object-store config create -object-store-name CloudBackupOnpremAWS -usage data,metadata -provider-type AWS_S3 -server bucket.vpce-081a8b49b8b373173-3cxyvswb.s3.us-east-1.vpce.amazonaws.com -container-name netapp-backup-c1229674-2c6d-11ec-8c33-11ac37ee245a -ipspace NonDeafultIPspace_IClif -vserver OnPremCluster -access-key AXXXXXXXXXX-secret-password XYX -url-style virtual-hosted-style  -is-ssl-enabled false  -port 80 -is-certificate-validation-enabled false
“Failed to backup working environment. Failed to configure object storage. Cannot verify availability of the object store from node NODE-01. Reason: Wrong port or server is not reachable."

Intercluster LIFs  on On-premises are on a separate IPSpaces with connectivity to AWS S3 via VPN.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.
d6c6727c-b591-41ae-99f1-1f00af9500d1