Hi,

My Active database is dismounted as the drive containing the transaction logs went out of space. how do i quickly recover from this issue ?

Shall i delete the transaction logs that are replicated to passive DB or is there any other way ?

Thanks

This is an old article but still applies:

https://support.microsoft.com/en-us/kb/240145?wa=wsignin1.0

http://blogs.technet.com/b/exchange/archive/2004/05/12/130556.aspx

You want to determine which logs are required and from there which are safe to remove.

By the way, is this SAN storage? Can you increase the trans log space ?

it is SAN storage but we needed a quick solution for now.  But the database is a replicated database (DAG). If i remove logs , wont it affect the passive DB.

or shall i check the last inspected/replicated log in passive DB and then remove the all the previous logs from Active DB. will this work ? 

I would check on the active copy to determine which logs are safe to remove, then remove the same logs on the passive side. Once mounted if replication is having issues, re-seed the passive copy.

If you are using Exch 2013, consider loose truncation going forward...

http://windowsitpro.com/exchange-server-2013/loose-truncation-exchange-server-2013-sp1

Shall i check the active copy  ? or shall i check the lastlogreplayed of passive copy and delete all the logs previous to that from Active copy ?

How to do it ?

Shall i check the active copy  ? or shall i check the lastlogreplayed of passive copy and delete all the logs previous to that from Active copy ?

How to do it ?

As I mentioned above, I would look at the active copy. That is the copy generating the logs.

use the method described in the articles:

Example

"C:\Program Files\exchsrvr\bin\eseutil.exe" /MH "D:\mdbdata\Mb1.edb"

Look for the  Log Required field. That tells you which logs you need ( if any) for the database to successfully mount.  Move the other logs ( Don't delete them) to another drive that has space on both the active and passive copies.   Mount the database. If replication fails, reseed the passive copy.

what if the logs that i am moving are not yet replicated to passive copy.. that may create replication issues.

whereas if i check the passive copy for the already repicated logs and then remove those from active and passive copies....i will be safe. I am not sure ..just curious whether this could also be an option ?

Please correct me if i am wrong.

Regards,

I would only look at the active copy.  Reseed from that once its mounted if necessary.

Thanks for your Patience Andy :)

but please do tell me why not the second option...just for my knowledge !!

Appreciate your help !!

Thanks for your Patience Andy :)

but please do tell me why not the second option...just for my knowledge !!

Appreciate your help !!

The active copy generates the logs. It knows what logs it needs. You don't know that the passive copy has been updated correctly. The DB is very likely in a dirty shutdown, so its important to check the active database for what logs are required so it can mount again.