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 Exchange Server Administrator's Guide
  3. Protecting Exchange Server data with VMware backups
  4. About protecting an application database with VMware backups
  5. Limitations of VMware application backups
NetBackup™ for Microsoft Exchange Server Administrator's Guide

Limitations of VMware application backups

Databases are cataloged and protected only for the configurations that are supported for VMware backups. Make sure to store databases and transaction logs on supported storage.

VMware application backups do not support the following policy options and configurations:

  • Incremental backups. Instead, you can create a policy for Exchange Server incremental backups.

  • Consistency checks of the Exchange Server.

  • Dismounted databases.

  • Exchange Server databases are not cataloged and backed up if they exist on the following:

    • Any virtual machines that use raw device mapping (RDM).

    • Virtual Machine Disk (vmdk) volumes that are marked as independent.

    • Virtual hard disks (VHDs).

    • RAID volumes.

    • ReFS file systems.

    • An excluded Windows boot disk.

Feedback

Was this page helpful?
Previous

About protecting an application database with VMware backups

Next

About configuring a VMware backup that protects Exchange Server

Feedback

Was this page helpful?