Link to home
Start Free TrialLog in
Avatar of Albert Widjaja
Albert WidjajaFlag for Australia

asked on

Transaction logs keeps growing during the SG suspended replication in CCR Exchange Server ?

Hi All,

What is the best way to keep the transaction log growth controllable ?

at the moment I have already done the following:

1. enabled circular logging by checking the tick box in every storage groups
2. performing full backup until it completes successfully

but somehow the log volumes keeps growing, so does circular logging cannot help at all when I'm migrating my mailboxes across new storage groups with suspended replication ?

I understand that this is due to the suspended CCR replication as I did not recreate the equivalent disk drive in the newly migrated exchange server mailbox server in DR site, because my plan is to create new drive with larger size to contains the new storage groups that I'd like to migrate across from the old SGs.
ASKER CERTIFIED SOLUTION
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

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
Avatar of Albert Widjaja

ASKER

no I didn't restart the IS service at all.

does it works in that way with CCR ?

my current suspect is that the suspended CCR replay causing it to not trucnate the transaction logs
SOLUTION
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
Hi Kona,

I have CCR between sites, I wonder how can I disable the old storage groups that is now being copied over ?

is that possible ? I know that with SCR and LCR you can disable per SG but what about with CCR ?
What you should be able to do is evict or remove the DR node but you will be down to a single node.    The backup should be able to truncate the logs.  

But I would run eseutil and find out when the last log file was commited to the database and you can safely delete everything older.    Then just run a update for your DR to make sure everything is set and healthy
vict or remove the DR node --> sounds like a plan, but how to do that ?
my current suspect is that the suspended CCR replay causing it to not trucnate the transaction logs - Circular logging has nothing to do with CCR is works as the ESE engine is designed.

vict or remove the DR node --> sounds like a plan, but how to do that ? - This will happen for all DB's and your down to one server with no HA :(

- Rancy
doh ... (-_-)" I guess when the worst case happens due to no more log disk space available and the database dismounted, I guess I have to manually copy the log directory into another location then perform Move-StorageGroupPath -ConfigurationOnly........ command in the larger drive :-|
I agree and if something please involve .... its been a time i worked on E2k7 so want to get my Hand in :)

- Rancy