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
NetBackup™ Web UI Cloud Administrator's Guide

Protecting Azure Managed Instance databases

NetBackup version 11.0 onwards supports Azure Managed Instance backups using the native backup mechanism T-SQL. This backup method does not require creating a temporary database during backup. A .bak file is generated in the staging area on the Azure Blob storage and later moved to Universal share. The Managed Instance uses Azure SAS tokens to securely put the data in the form of .bak onto the Azure Blob. This method is supported only for full backups. If you use an AMI, the same AMI must be attached to the storage account. The backup and recovery workflows of these databases are the same as the other databases.

Feedback

Was this page helpful?
Previous

Consideration for protecting RDS Custom for Oracle assets

Next

Prerequisites for protecting Azure Managed Instance databases

Feedback

Was this page helpful?