• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 391
  • Last Modified:

Exchange not truncating transaction logs

Is there a way to tell Exchange server 2007 to truncate transaction logs for a storage group after its been backed up even though the other storage groups are still being backed up?

For example, I have 20 storage groups, each with 1 mailstore in it. Can exchange begin truncating the logs of storage group 1 once its backup has completed, even though storage groups 2 through 20 are still being backed up? And then similiarly, begin truncating the logs of storage group 2 once its backup is completed, event though 3 throughh 20 are still backing up? etc. etc.

My problem is that my exchange server will not beging truncating transaction logs until all 20 storage groups have been successfully backed up. If even 1 out of 20 fails backup, nothing is truncated.

thank you
0
cyberleo2000
Asked:
cyberleo2000
  • 5
  • 2
1 Solution
 
Seth SimmonsSr. Systems AdministratorCommented:
what backup software are you using?
0
 
cyberleo2000Author Commented:
symantec netbackup
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Look all DB's under a Storage group have to be successfully backed if not Logs wont Truncate and also it has to be either Full or Incremental for logs to be purged.

Do hope no SCR or disconnected Storage copy is available

- Rancy
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
cyberleo2000Author Commented:
Its an active-passive CCR cluster. We backup the passive node. Each mailstore is in own storage group, so shouldn't the logs for that mailstore truncate as soon as netbackup tells the vsswriter that mailstore has been successfully backed up? I'm not getting any event id 224.

I'm wondering if the problems isn't with netbackup but rather with vsswriter.
0
 
cyberleo2000Author Commented:
log files are being truncated, its event 224 that is not being generated.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So were you simply trying to check for event 214 to determine if Log truncation is happening or not after successful backups ?

- Rancy
0
 
cyberleo2000Author Commented:
backups are successful, logs are truncated, but events 223 and 224 are not being generated.

I initially thought log truncation was not occurring because I was not seeing the events. But the number of logs in the log folder decreases substantially after a backup, so they are truncating.
0
 
cyberleo2000Author Commented:
i figured it out
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now