A technician created a job on a backup server to back up the new email server. After a few days, the technician notices the email server logs are not cleaning up after the backups are completed…

Deleting logs before the backup removes the transaction log chain that the email server needs for point-in-time recovery and could corrupt the mail database.

Email servers like Microsoft Exchange use VSS (Volume Shadow Copy Service) writers and application-level APIs to coordinate with backup software. When the backup application lacks the correct API integration or agent plugin, it performs a file-level backup that the email server does not recognize as a valid application backup, so transaction log truncation is never triggered. Acquiring and configuring the proper API or backup agent enables the backup software to communicate a successful application-aware backup to the email server, which then automatically purges committed transaction logs.

Changing the backup destination to a network location does not affect whether the backup software uses the email server's application API, so log truncation behavior would remain unchanged.

Stopping email services to perform a cold backup may allow a file-copy backup to complete, but it causes unnecessary downtime and does not establish the application-aware backup process needed for automatic log cleanup.