Managing it in small and large corporate enviornments for over a decade led me to believe that when it was working, Exchange was very stable and reliable.. But when things would break, they would break in a way that required extensive knowledge of all the areas to fix. Which was a form of job security so Im not complaining.

I guess past reliability might be irrelevent here if an AI slop patch for AI discovered exploits caused the outage. Just speculation though. Since exchange has so many moving parts and so much legacy code, with even more bolted on to make it a cloud service, I could see how an AI exploit fix would not have all the context needed.

There is no information that it was caused by Exchange either, guess we have to wait on those answers. It is just a reasonable assumption.

▲

InsidiousWombat 6 hours ago | parent [-]

Open source options tend to require a bunch of knowledge to set up but after that you generally are equipped with that knowledge to solve any configration issue. I wrote "configuration issue" because aside from "ran out of disk space" none of them really "broke", so it was never "fixing the thing", just the usual mail server admin stuff of figuring out why this or that server didn't like us.

▲

EvanAnderson 6 hours ago | parent [-]

A lot of the bad situations I helped bail other contractors out of, when it came to Exchange, related to disk full conditions, a lack of understanding how transaction logging in the database worked, and database inconsistencies brought on by hardware RAID controller issues or hard power-offs. Very nearly all of my ugly ESEUTIL and ISINTEG experience came from people not respecting the product's storage needs.

Sysadmins who were used to running file servers and thought Exchange was the same thing were the problem. A DBA was actually more apt to understand the product's storage needs because it wasn't wholly dissimilar from the RDBMS they supported.

▲

gmueckl 3 hours ago | parent [-]

Exchange's internal storage is an RDBMS. It's a massively evolved fork of the database engine that was in MS Access.

	▲	EvanAnderson 2 hours ago \| parent [-]
		It's not a RDBMS, though. It's more like a NoSQL database. It also doesn't share lineage with Access other than its code name having "Jet". https://en.wikipedia.org/wiki/Extensible_Storage_Engine It's open source now, too: https://github.com/microsoft/Extensible-Storage-Engine