Microsoft supports the ability to create snapshots of Exchange data using VSS. Microsoft provides Exchange-specific VSS writers that coordinate with the Exchange Services, operating on behalf of the Plug‑in for Exchange, to prepare the Mailbox Database files for backups and freeze the input/output (I/O) activity due to Exchange transactions before backing it up, and then to unfreeze and truncate logs after the backup is complete.
NOTE: The Backup Files to Storage option is supported with any disk-based storage. To use the Perform Backup Off-Host using Client, Retain Array-Based Persistent Snapshot, and Discard After options, the data that you back up must reside on a NetVault Backup-supported disk array. Also, for persistent snapshots, only the metadata is copied to the target. |
If you use a Backup Type that supports transaction log file truncation, such as the Full and Incremental Backup types, the truncation of transaction log files is performed by the Exchange Server after the plug-in informs it that the backup completed successfully. Also, when the truncation occurs depends on Exchange Server and whether it still needs the logs for more purposes, such as replication; therefore, truncation might not occur immediately after a successful backup is completed.
For Exchange Server to truncate a transaction log file, the following criteria must be met:
To reduce the effects of transaction log file buildup due to suspended or offline database copies, Exchange Server 2013 Service Pack 1 introduced loose truncation. With loose truncation, each database copy tracks its own available disk space and applies loose truncation when disk space gets significantly low. With loose truncation applied, each passive database copy independently truncates its own transaction log files. For the active database copy, truncation ignores the passive database copy that is farthest behind replaying logs.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center