Skip to main content
NetApp Knowledge Base

Azure Blob containter is not created automatically when activating backup on BlueXP

  1. Last updated
  2. Save as PDF
Views:
86
Visibility:
Public
Votes:
0
Category:
cloud-backup-service
Specialty:
ds_cbs
Last Updated:

Applies to

  • BlueXP Backup and Recovery
  • Azure Blob

Issue

  • After an old connector is deleted and a new connector is created, the Azure Blob container is not created automatically when activating backup on BlueXP
  • The old container name is still displayed when activating backup, even if the container has been deleted from the Azure blob
  • No object store record in the command output of storage aggregate object-store config show

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.