Link to home
Start Free TrialLog in
Avatar of strategic_network
strategic_network

asked on

BESR 2010 not clearing Exchange log files

Hi,

I've got a Windows Server 2003 box with Exchange 2003 installed upon it,

when running the backup in BESR including the VSS option it does not clear the exchange log files,

running a windows inbuilt backup the logs are cleared, but not when running anything through BESR,

I've restarted the Information store and all other exchange services, and re-run backups, nothing seems to work,

I need BESR to be able to complete the backup and purge the exchange log files, Its not an SBS box and I've checked and the exchange writer is not disabled in the registry.

thanks in advance
Avatar of 5g6tdcv4
5g6tdcv4
Flag of United States of America image

Are there any unmounted mailbox databases or public databases on the server you are trying to back up?
I have seen committed logs not get flushed when there are unmounted DB's on server
is this consistency check of the databases completing successfully? if this check fails, it will not truncate any logs
Avatar of strategic_network
strategic_network

ASKER

no unmounted DB's on the system, consistency of database is fine,

logs commmited and flushed when using Windows inbuilt backup absolutely fine, just not BESR
but does the consistency check complete with the BESR tool
a vss backup must complete a consistency check before it will run and you must be backing up the volume
I had a similar problem and resolved it. Only in my case I had Exchange 2007 SP3 on Server 2008 (also not SBS). But since I think the problem is within BESR2010, which I am also using, I tried the following.

I installed SP3 for BESR2010, which is not deployed through the live update. And when you have seperated the Exchange logs from the DB (dirrent volumes), you must NOT create 2 different backup jobs. Select them both (bij holding Ctrl down) in 1 job. This cleared my logs...

ASKER CERTIFIED SOLUTION
Avatar of strategic_network
strategic_network

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Had Symantec resolve the issue