Is there a pseudo backup procedure to force Exchange log truncation?
Not to steal JoeQwerty's thunder, as I think his answer to this question is more than valid and definitely applicable in pretty much any scenario, except possibly yours. (Hence why I upvoted it.) However, I did find a way to do what you are after...
Fake VSS backup
Basically what this does is fake a VSS backup on the volume that the Exchange database is on, which ends up causing Exchange to truncate the logs.
Breaks Incremental Backups
This will break any backup softwares incremental backup chain so the next real backup will have to be a full backup.
Use Passive Copies
In a DAG, do this on a passive copy if possible.
You have to add both the drive/mount point for the database and the log.
- Open Command prompt as Admin
add volume x:(where "x" is the drive for the Exchange database)
add volume y:(where "y" is the drive for the Exchange log)
create. This will take a few minutes while VSS does its thing.
end backup. This is where it will set the logs to truncate. You will have to wait for the next log to generate before it starts to happen.
At that point if you look in the Application eventvwr logs you should see an entry similar to:
(Or you can try PowerShell like so:
Get-EventLog -LogName application -Source msexchangeis | select -first 10)
Hope that helps...
Use Windows Server Backup to backup the server. It will purge the Exchange Server transaction logs after a successful backup.
You could try this to forego the backup route. It's a manual process, but it's probably safer than anything else, short of a backup:
EDIT: This tool doesn't seem to exist in Exchange Server 2010
In this scenario I would:
- Dismount the store/DB to apply this change.
- Mount the store/DB this will take some time to sort out the logs.
- Dismount the store/DB to apply this change
- Mount the Store/DB.
Hope this helps,