![]() Note: This server only had two volumes however additional volumes can exist in the event additional databases are required.Īs the system volume was corrupt and no longer booting, this needed to either rebuilt or restored from backup. ![]() ![]() ![]() Remember Exchange 2010 has a 90% disk I/O reduction over Exchange 2003. Volume 2 (Logs + Database) which contain the Exchange 2010 database and log filesĭue to the changes in Disk I/O it is no longer a requirement to separate transaction logs from the Exchange database as I/O is no longer an issue.Volume 1 (SYSTEM) consists of Operating System, Page File and Exchange System Files.This server was one I setup a couple of years back and as a result it followed my standard multi-role Exchange server build which consists of two or more NTFS volumes. The Exchange 2010 SP3 server was running on top of a VMware vSphere 5.1 clustered environment hosted on shared storage. We were not able to access Windows in anyway even by booting into safe mode and had no indication as to why the failure occurred as we could not access the server event logs. The server server would not boot and was simply blue screening. Yesterday I responded to an emergency callout to a customer with 800 users running a single Exchange 2010 SP3 UR3 multi role server running on Windows Server 2008 R2 SP1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |