Whats is Called Loose Truncation ? in Exchange 2013 Sp1
Lets make this simple ,
Normally if one Database copy goes offline in one of the DAG Members, Logs are not Truncated in all the databases copies , Which waits for the other failed copy to come back , so that other copies can help the failed copy to re sync the logs
But this situation doesn’t help admins all the time , Lets say I have a four node DAG , if I have one failed copy – logs stops truncating . Disks get filled up , Which stresses the admins to remove the copy and reseed later
Exchange 2013 Sp1 introduces a new feature called loose truncation – To avoid this situation
Loose Truncation is an optional feature in Exchange 2013 DAG – if loose truncation is enabled , Where database copies will check their own disk space , if disk space gets low , All the databases copies will truncate logs independently
Now when the failed copies comes back – It cannot re sync as logs have been deleted , Two options to overcome or fix the failed copy – Enable Auto reseed or Update the database manually
Exchange MVP , Publisher of CareExchange.in
I have been supporting/Deploying/Designing Microsoft Exchange for some years . If you any Questions ?. Please share you thoughts via Comments.
