Today was one of those days... let's not go there. It caught me cold today. The monitoring of the Exchange environment was not running properly and the impending disaster was only noticed when it had already occurred.
Within a few hours, the Exchange log partition was full of transaction logs. When users reported that they could no longer receive and send mails, I switched to the Exchange servers. Only a few MB left on the drive. The EventLogs red...
The motto was "restore availability as quickly as possible", so I took a quick look at the EMS to see if the databases were still online:
Get-MailboxDatabaseCopyStatus
The databases were still online, but there were only a few MB free on the log file partition and the queues were already full. First thought: Why didn't the backup run? There shouldn't really be that many logs there... However, the logs were all from the last few hours, so the backup had run cleanly. Second thought: There was something....
Exactly, I recently read the article: http://blogs.technet.com/b/exchange/archive/2013/04/18/troubleshooting-rapid-growth-in-databases-and-transaction-log-files-in-exchange-server-2007-and-2010.aspx
Phew, availability or analysis?! Availability! (see title). So again, no time to read... So quickly get rid of the logs to get everything running again:
https://www.frankysweb.de/?p=1077
Finally space on the log file volume again, everything is back to normal. What was the problem?
http://support.microsoft.com/kb/2814847
Bad unpatched iPhones.
Hallo Franky.
Ging mir heute genauso. Da kann einem schon mal das Herz in die Hose
rutschen. Ich habe es aber glücklicherweise frühzeitig bemerkt, weil ich mir
mittels Leistungsüberwachung den disc-space überwache.
Danke dir.
DANKE! :-)
Danke, Admin from Hell, für die schnelle Problemlösung! ;-) Coole Seite!!!