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. The Cloud object store account has encountered an error
NetBackup™ for Cloud Object Store Administrator's Guide

The Cloud object store account has encountered an error

Explanation

In web UI, the Cloud object store account status is shown as:

The Cloud object store account has encountered an error, see user documentation, and re-create the account.

You cannot edit the Cloud object store account in this state. All jobs corresponding to the Cloud object store account keep failing.

Cause

The Cloud object store account goes to an error state when:

  • The alias corresponding to Cloud object store account is accidentally deleted using the csconfig CLI.

  • The alias corresponding to the Cloud object store account is accidentally updated using the csconfig CLI.

Note:

It is recommended not to use the csconfig CLI to update the alias corresponding to the Cloud object store account. The correct way to update the same is through the Edit workflow or create-or-update API. Aliases with the same name as the Cloud object store account are the aliases corresponding to the Cloud object store account.

Workaround

The NetBackup domain name must be unique across the Cloud object store account, Cloud storage server, or MSDP-C LSU. They share a single namespace. Hence, we can have the following usage scenarios:

Case 1: When there is no valid Cloud storage server or MSDP-C LSU with the same name as the Cloud object store account in the environment.

  • Gather the Cloud object store account details as per your environment and cross-check the details obtained.

    • Optionally, if the Alias corresponding to the Cloud object store account exists, use the csconfig CLI and note down the details of the alias.

      • Use the following command to list all instances for the type and locate the Cloud object store account and its instance:

        <install-path>/csconfig cldinstance -i -pt <provider_type>

      • Use the following command to get the details of the instance and the Cloud object store account:

        <install-path>/csconfig cldinstance -i -in <instance name>

      • Validate the details with the gathered information.

      • Delete the Alias using the following command:

        <install-path>/cscpnfig cldinstance -at <api_type> -rs -in <instance_name> -sts <cloud_object_store_account_name>

  • Delete the Cloud object store account that is in an error state.

  • Create the Cloud object store account using the noted details.

Case 2: When you have a valid and in-use Cloud storage server or MSDP-C LSU with the same name as the Cloud object store account in the environment.

  • You cannot reuse the same name.

  • You need to gather the Cloud object store account details as per your environment.

  • Identify the new name for the Cloud object store account.

  • Delete the Cloud object store account which is in an error state. Remove the account from the policy.

  • Create the Cloud object store account using new name and details gathered. Assign this account to the same policy that the old account used.

  • This changes the Client Name used for the bucket, starting from the next backup onwards.

  • NetBackup identifies the old backups using the old account name.

Feedback

Was this page helpful?
Previous

Azure backup jobs fail when space is provided in a tag query for either tag key name or value.

Next

The bucket is list empty during policy selection

Feedback

Was this page helpful?