cancel
Showing results for 
Search instead for 
Did you mean: 

LognotTruncate

Golani
Level 3

Hi

We have exchagne 2010 DAG and after backuup logs are not truncate and in application log we getting following warnning

event id 915

"Information store (5832) There were 206 logs files not found in the log range that were attemted to truncage"

Thanks

 

 

4 REPLIES 4

VJware
Level 6
Employee Accredited Certified

Is SP2 applied on the media and exchange servers ?

Ensure, Advanced Open File and Checkpoint Restart options are disabled from the backup job properties.

If running an AV scans on the Exchange server, pls exclude the beremote.exe process

Is this a regular backup job or just a one-time backup as the one-time backup job does not truncate logs.

Lastly, are there any exchange vss or replication errors in the event viewer of the exchange server ?

 

ArulPrasad
Level 6
Employee

Hello Gol,

How the is the preference set on the backup Job, is it set to doa Passive Copy backup or active copy backup?

 

on which node is this error seen? does this match with the backup job settings?

 

You can try this:
 

Change the Backup job to use different settings i.e If it is Passive copy , change to Active copy... and see if that works...

as stated By Vjware ensure to have all the noides patched .....

 

let us know how it goes...

 

Kind regards,

Arul Prasad R

VipulK
Level 4

Hi,

Please check the tech note: http://www.symantec.com/docs/TECH146208

Check for Event ID: 9827 and 9780, these are events for Log being backed up and marked for truncation.

If the Events are generated, then some thing in exchange is not working correctly and truncating the logs. I would suggeste you to reboot the mailbox servers and then run a fullbackup to check if logs get truncated.

In case the logs are still not getting truncated, then unable circular logging on the Databases and then reboot the mailbox servers.

 

 

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...not quite the same error or version of Exchange (OP is using Exchange 2010!)...also, no need to type in bold :)