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™ Web UI Cloud Administrator's Guide
  3. Protecting PaaS assets
  4. Protecting Azure Managed Instance databases
  5. Prerequisites for protecting Azure Managed Instance databases
NetBackup™ Web UI Cloud Administrator's Guide

Prerequisites for protecting Azure Managed Instance databases

These prerequisites are required to protect Azure Managed Instance databases without creating a temporary database.

Note:

Managed Instances use Azure SAS tokens to securely put the data in the form of a .bak file in the Azure Blob.

  • Create a storage account name, using the following example:

    • Calculate the hash of the string formed by combining the Subscription ID and Region. Follow this example command:

      echo -n "aaaaaaa-bbb-ccc-dd11-aabbccdd11223344eastus" | sha256sum 2e5fb564552100a6060794937fedc33aefe4d01eb7e27971c1a0ed52c3f78b6c

    • Take only the first 16 chars of the hash, and prefix the characters nbu.

    • Your string becomes: nbu + 2e5fb564552100a6.

    • So, the Azure storage account name is: nbu2e5fb564552100a6

  • For containers, use the following name format:

    • azure-netbackup-<region>

    • If the container does not exist, the NetBackup agent creates it depending on the availability of permissions.

  • Management of encryption keys can be according to your organization.

Feedback

Was this page helpful?
Previous

Protecting Azure Managed Instance databases

Next

Permissions required for protecting Azure Managed Instance databases

Feedback

Was this page helpful?