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 Microsoft Azure Stack Administrator's Guide
  3. Troubleshooting
  4. Known limitations for Microsoft Azure protection using NetBackup
NetBackup™ for Microsoft Azure Stack Administrator's Guide

Known limitations for Microsoft Azure protection using NetBackup

The following table lists the known limitations for Microsoft Azure protection using NetBackup:

Table: Known limitations

Limitation

Workaround

Unable to obtain the authentication token after NetBackup upgrades from 8.1.2 to 9.0.

The encryption and the decryption algorithm is updated in NetBackup 9.0. Remove all the existing Microsoft Azure servers from NetBackup and add them again after NetBackup upgrades to 9.0.

VMs in a provisioning state other than Succeeded are backed up successfully, but their restore can fail because of the inconsistent VM state at the time of the backup.

If the restore fails for any VM, check the log files and check whether the provisioning state of the VM was Succeeded or something else during the time of the backup. If the provisioning status is anything apart from Succeeded, the VM cannot be restored.

Feedback

Was this page helpful?
Previous

About NetBackup for Microsoft Azure debug logging

Next

Backup fails with error 6662

Feedback

Was this page helpful?