- Posts: 9
- Liked: never
- Joined: Jun 24, 2013 4:32 pm
- Veeam Software
- Posts: 18037
- Liked: 1533 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Do you see the 'Truncating transaction logs' message in the job statistics window when selecting the particular VM to the left? Have you already contacted technical support with that?
- Posts: 295
- Liked: 59 times
- Joined: Sep 06, 2011 8:45 am
- Full Name: Haris Cokovic
If so whats the state of this writer?
Keep in mind that in your scenario log truncation will still happen on the active node with the active databases. If you are looking for log truncation errors you should take a look into the event logs of your active node
If you cant see anything in the event logs on your active node you should focus on the Microsoft Exchange Replica Writer on the passive node as this one is responsible for log truncation notification issued to your active node after backup was finished. I had this situation too. In my case the above writer wasn't even present anymore. So Veeam finished its backup task and issued the log truncation command but no writer was present to pass this command through to the active node thus no log truncation happened and i couldn't find the event in the event logs. I had to bring the writer back by rebooting the server or just restarting the MS Exchange Replication service.
Described it earlier in this post here.
Users browsing this forum: Bing [Bot] and 18 guests