![]() This is one reason why it’s generally not a good idea to deploy Exchange Server on a domain controller as explained here. An example of this is Microsoft Exchange Server which uses the Windows write cache function for its own transactional logging function. On the other hand there are also some applications where disk write caching always needs to be enabled. ![]() Brien Posey explores this issue in some detail in his article Solutions for Virtualizing Domain Controllers (Part 5) on. In fact when you promote a Windows Server system to the role of domain controller, Windows automatically disables its write cache function. ![]() One example of such a scenario is Active Directory domain controllers where disk write caching should always be disabled to prevent corruption of the directory database and/or loss of important security information for the domain. Having a backup power source such as a UPS can help mitigate such risks.įor scenarios where data integrity is more important than performance it’s important that disk caching be disabled. In addition, file system corruption and/or data loss may occur. The result can be that Windows thinks certain data was written to disk whereas in actual fact the writes weren’t committed to disk. That’s because a sudden hardware failure, software crash or power outage could cause the cached data to be lost. But while these “delayed writes” can help Windows run faster, they also have a risk associated with them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |