Dear all,

I have an exchange server 2010 sp2 with 2 databases, about 200GB each database. For both databases circular lodging is enabled. Recently I have configured DAG with another server at DR site. The problem is that the one database is fine but the other database logs are growing extremely fast and the disk get full. I have enable circular loging for both databases. does anyone have any idea why this may happen?

Regards

Pantos

Hi ,

1.First i would suggest you to upgrade to exchange 2013 sp3 with latest RU .

2.Did you meant to say for the database with circular logging enabled is not purging the transactions logs after the passive copy is added on the server residing on the DR site ?

Hi Pantos,

Hope you have not setup lagged passive DB copy. Because Lagged copy will force the server to keep the transaction logs intact and will not replay them immediatly.

Other reasons can be mailbox movements betwee

Hi nithyan,

The first option is not possible right now.  your second question the answer is yes. But as i already mention this happens only to one databse the other one is ok.

Regards

Pantos

Hi satajit,

I just right click and select "add database copy"

regards

pantos

Hi,

Option 1 : Have you disabled the circular logging and enabled it again for the problematic database ?In case if it doesn't help then we need to go for the second option .

Option 2 : Please disable the circular logging for the problematic database .Then take the down time from the customer to dismount the database .Then check the database is in clean shutdown state by using the eseutil tool .

Command to check the database :

eseutil /mh "path of the database file along with edb file name"

If it in the clean shutdown state , please move all the log files to a new folder on the same drive itself .Then start to mount the database .After that DB mount we will be having new log files for that database then re enable the circular logging for the database.

Then we need to remove the passive copy on the DR site server and do a fresh reseeding to have a healthy copy.

Note : Please have a valid backup before doing this activity.

Are your databases still seeding?  I'm pretty sure the logs are going to hang during the seeding process regardless of whether or not you have circular logging enabled.  They need to make it to the other server.  Also, Run-MailboxDatabaseCopyStatus *  and see if logs are not getting replayed on the destination.

Hi,

According to your post, I understand that one mailbox database transaction log grow fast after deploy DAG, however the other one dont.
If I misunderstand your concern, please do not hesitate to let me know.

It may be caused by seeding. Updating, also known as seeding, is the process in which a copy of a mailbox database is added to another Mailbox server in a database availability group (DAG). The newly added copy becomes the baseline database for the passive copy into which log files copied from the active copy are replayed. More details about Seeding process, please refer to: https://technet.microsoft.com/en-gb/library/dd335158(v=exchg.141).aspx

Please ensure that you have sufficient disk space available on Exchange servers, run below command to re-seeding:
Suspend-MailboxDatabasecopy -identity "DB1\MBX1"
Update-MailboxDatabaseCopy -Identity "DB1\MBX1" -DeleteExistingFiles
Also, run below command to show the Copy queue, Replay queue and Contentindexstate:
Get-MailboxServer | Get-MailboxDatabaseCopyStatus | Sort-Object Copyqueuelength

Thanks

I am going to add database copy for the problematic database during this weekend.

I will check and let you know.

Ragards

Pantos

• Edited by pantoskom 1 hour 37 minutes ago

I am going to add database copy for the problematic database during this weekend.

I will check and let you know.

Ragards

Pantos

• Edited by pantoskom Friday, May 08, 2015 5:49 AM

I am going to add database copy for the problematic database during this weekend.

I will check and let you know.

Ragards

Pantos

• Edited by pantoskom Friday, May 08, 2015 5:49 AM

Hi,

Any updates about this problem?