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. Access tier property not restored after overwriting the existing object in the original location
NetBackup™ for Cloud Object Store Administrator's Guide

Access tier property not restored after overwriting the existing object in the original location

Explanation

Object with access tier Cool, overwritten by a restore with Hot access tier, does not change the access tier to Hot, it remains Cool.

Workaround

In the case of Azure cloud storage, when we have an object with accessTier as cool, and we try to upload an object/blob of the same name with Hot(inferred) accessTier with an overwrite option, accessTier remains as cold. A new access tier does not get set. This behavior is observed when a file is uploaded from the portal. It does not change accessTier from cool to Hot (inferred) when the Overwrite option is selected on the Azure portal.

Feedback

Was this page helpful?
Previous

Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"

Next

Reduced accelerator optimization in Azure for OR query with multiple tags

Feedback

Was this page helpful?