Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Cloud Object Store Administrator's Guide
  3. Troubleshooting
  4. Creating a second account on Cloudian fails by selecting an existing region
NetBackup™ for Cloud Object Store Administrator's Guide

Creating a second account on Cloudian fails by selecting an existing region

Explanation:

After adding a Cloud object storage account for Cloudian by adding a region with the us-east-1 location constraint, if you try to reuse the same region and create a second account, account creation fails.

This happens because the region listing API is converting the region's location constraint 'us-east-1' to ''<blank> while showing in the web UI. You can see the added region location constraint was us-east-1 and the one that is listed has a blank location constraint field. Account created by selecting such a region from the list fails.

Workaround:

Use the NetBackup Asset Query APIs to create an account. The region details part can be provided in the payload:

"s3RegionDetails": [
  { "regionId": "us-east-1",
    "regionName": "<region name same as listed from prior account>",
   "serviceHost": "<service host same as listed from prior account>"
  }
]

You can obtain API DOC from the schema API:

https://<primary-server-hostname>/netbackup/asset-service/workloads/saas/schemas/create-or-update-assets-named-query-request

Feedback

Was this page helpful?
Previous

The bucket is list empty during policy selection

Next

Restore failed with 2825 incomplete restore operation

Feedback

Was this page helpful?