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. Veritas NetBackup™ for Microsoft Exchange Server Administrator's Guide
  3. Configuring Exchange backup policies (non-VMware)
  4. About configuring Instant Recovery backups of Exchange Server
  5. Configuring an Exchange snapshot policy with Instant Recovery
  6. About Exchange Instant Recovery volume rotation
Veritas NetBackup™ for Microsoft Exchange Server Administrator's Guide

About Exchange Instant Recovery volume rotation

At the start of a backup, the Snapshot Client is queried to determine how many Instant Recovery snapshots currently exist for each volume. This information is required for the Exchange databases that are selected for backup. If the number of snapshots is currently at the configured maximum level of snapshots, a snapshot is resynced (or snapped backup or deleted). Then a snapshot is available for the upcoming backup attempt.

The algorithm to determine which snapshot volume is resynced considers whether the snapshot was taken as part of a full backup or an incremental backup. The algorithm tries to maintain as many full backups as possible, even if newer incremental backups have to be resynced.

Feedback

Was this page helpful?
Previous

Schedules settings in Exchange Instant Recovery policies

Next

Adding backup selections to an Exchange policy with Instant Recovery

Feedback

Was this page helpful?