Exchange 2007 mailbox full backup has finished but not truncate the log files ?

Hi,

I've got an urgent issue here with my current Exchange Server 2007 SP1 CCR mailbox backup, the software that I use is HP Data protector backing up the Active node (because it such an old application it still uses ESE engine to do the full backup).

and I noticed that the current transaction log drives fills up almost 99% full !
when I browse to the Transaction logs folder, the file last modified timestamp was stopped about one week ago.

what should I do to make sure that the transaction log is truncated successfully ?

Thanks.
LVL 9
Senior IT System EngineerIT ProfessionalAsked:
Who is Participating?
 
Kernel_Recovery_ToolsConnect With a Mentor Commented:
Matching drive letters/paths on the other CCR node is mandatory. Without them the CCR cluster will not function correctly.

That would certainly explain your CCR replication being in a failed state.

Backups will complete and will signal Exchange to begin its log truncation, but Exchange will not truncate the logs in a replicated environment (such as LCR, CCR, SCR) until each log has been successfully shipped and replayed on the passive copy of the database.

So yes, fix your storage paths, fix your CCR replication, and you will likely find that will solve your problem.
0
 
aadi369Commented:
Take full backup of the transaction log using your backup solution
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
yes already done, it seems that the issue was due to the CCR replication is suspended for that storage groups, can I turn that off for some Storage Groups only ?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
BusbarSolutions ArchitectCommented:
by default the logs will not be purged until they are replicated...
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
yes, now I understand that I cannot add / map the old LUN in the new DR server.
so is there any way to stop CCR replication for several Storage Group only ?
0
 
BusbarSolutions ArchitectCommented:
nope.
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
so it is not possible to disable the CCR for a particular SG only ?

Suspending it won't truncate the logs even after successful backup.
0
 
vSolutionsITCommented:
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
@vSolutionsIT: that is for the LCR and SCR but not CCR ?
0
 
Sushil SonawaneCommented:
Take full backup of Active node using windows backup then your log file automaticaly purge on the server.

OR

Enable the circular logging purge the logs then disable the circular logging.

Please refer below article for circular logging.

(http://technet.microsoft.com/en-us/library/bb331951(v=exchg.80).aspx)
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
Enable the circular logging purge the logs then disable the circular logging.
 --> how to do that ?
0
 
Sushil SonawaneConnect With a Mentor Commented:
Please refer below link.

Find the topic "Continuous Replication and Circular Logging" here you get the information.

(http://technet.microsoft.com/en-us/library/bb331951(v=exchg.80).aspx)

1) Suspend-StorageGroupCopy cmdlet.
 
2) Enable or disable circular logging. For detailed steps about how to enable or disable circular logging, see How to Enable or Disable Circular Logging for a Storage Group.

 (http://technet.microsoft.com/en-us/library/bb331968(v=exchg.80).aspx)

3) Dismount and then mount the database in the storage group that is being enabled or disabled for circular logging.
 

4. Resume continuous replication by using the Resume-StorageGroupCopy cmdlet.
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
Sushil,

3) Dismount and then mount the database in the storage group that is being enabled or disabled for circular logging.

is not possible because in the DR mailbox server there is no drive which is the target of the CCR, hence the replication is suspended.

I cannot dismount the database ebcause CCR is at the suspended state.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.