Sarbanes-Oxley can also impact performance of an ESX Server, because the gathering up of log files at incorrect times will inadvertently cause a load on the system. With the advent of ESX version 3, it is now possible to store VM log files with the VMDK, and access to the file system holding these logs has been throttled so that copies to and from do not adversely impact performance. What logs are necessary? Those logs that tell who did what and when are ultimately required, but many system administrators are streaming all logs to tape for later retrieval. For ESX, this will be all the logs from each VM running on the host and all the VM log files and service console log files in /var/log. Once more, a single host is best to use to gather all this information so that no one LUN or server is overloaded. Because the ESX service console is Linux, the network features of syslog can be used to create a logging server so that all data is logged to one host from where it can be conveniently archived. The key is to make use of syslog to send the logs to the remote host and the local host. To do that, modify the /etc/syslog file as follows: Duplicate each uncommented line and add to the end instead of the local filename the @ipaddress option to force log files to not only be stored locally but remotely to the IP address of the syslog server.