Log files are vital to how Exchange Server functions. Brush up on how log files have changed in Exchange 2013 to protect your setup against disaster.
Exchange Server 2013 improvements show Microsoft is focused on using physical servers and Exchange data protection features to protect against disaster. A new Exchange install shouldn’t look to older, unsupported methods for recovery, such as disks filling up unexpectedly and logs that must be manually removed. Ensuring that Exchange is properly designed before a disaster strikes relies on built-in functionality to protect against outages.
We’ll look at some of the new and updated Exchange Server transaction log features to help you prepare for and recover from disaster.
Exchange is similar to traditional database servers in that it uses databases and log files. As with Microsoft SQL or Oracle databases, changes are written to the transaction log files before being committed to database files. From Exchange 2010 onward, there is a 1:1 relationship between each database and its corresponding log files; if there is a database, you can be sure to find corresponding log files.
