Acronis 12 Virtual Host - MS Exchange Hyper-V truncate logs issue
We have Acronis 12 installed on Windows 2016 Hyper-V host. Our Exchange resides on a Windows 2012 R2 Hyper-V host. That host is installed from our 2016 host via the agent. We have a backup job for type "Hyper-V" for our MS Exchange 2013. VSS snapshots are on, automatically select snapshot provider and "Enable VSS Full backup" is checked. The full backup is completing successfully but noticing MS Exchange logs has not truncated. What can be the problem?
Acronis fresh installed on our Windows 2016. In 11.7 Advance for Hyper-V, we did not have this truncate problem. We only have Acronis Virtual, no licensing for Exchange which shouldn't be a requirement.
We are on the following:
Web console service: v.12.0.2624
Backup management server: v.12.0.3689
Backup management console: v.12.0.6098

- Log in to post comments

We too are having an issue with our exchange server logs not being truncated however we ARE backing up with the exchange agent and the device is pointing to the "VM" of our exchange server. We have toggled turning on/off enable vss full backup but the logs are not truncating. Called tech support and they don't know how to fix it as of yet.
Does anyone have any ideas on what we can do?
Thanks in advance!
- Log in to post comments

Hello Monique,
Thank you for your posting! As far as I understand, you have installed Agent for Exchange into the guest operating system of the affected VM, enabled VSS Full backup in the backup settings and selected the server as "VM with Agent" as shown on the screenshot above, but still transaction logs are not truncated.
Have you already checked Windows Event logs (Application and System tabs) for any VSS related error?
Next step would be trying to create native Windows backup to check if transaction logs are successfully removed outside Acronis. In this case VSS Full backup will be also used to clear the logs after backup, so we can test if this functionality is working or not. If truncation works with native Windows backup, the issue should be investigated further by our support team.
Thank you,
- Log in to post comments