From a systems administrator perspective, change management can be challenging. You are ready to resolve an issue, patch a system, or otherwise improve the state of a server, but you must first submit a change record for approval. In many cases the change record must meet particular requirements or it’s rejected. Multiple parties may need to approve the change, delaying the implementation. In the meantime you are watching your server languish, and likely receiving grief from the application and service owners. You know that with a few quick keystrokes, the server could be performing better; it could be configured more robustly, that its redundancy could be improved. You are at the mercy of others, others that may not fully understand the change (or at least not as well as you).
Why doesn’t my server boot as fast as my iPad? I like my iPad-mini not just because I can take it anywhere, but because I don’t have to wait very long for it to boot. A simple test revealed that my iPad-mini boots in about 30 seconds. If the iPad is in a sleep state, which is essentially a power-save mode, then in one press of the button it’s awake and ready for use. Most servers also have a sleep mode, aka power save mode, but it’s usually disabled, as it’s been known to cause problems in production environments. In general, a server needs to be readily available 100% of the time.