UNIX-environment full rebooot

Yes, virtual machines, as well as physical, require periodic maintenance, upgrades, reboots and more. However, if you resort to the simple arithmetic and multiply the number of reboots the machine at the time it takes to reboot, implementing virtual infrastructure only to “reboot” can be a year to save a few months time. Of course, it is necessary to make allowance for the fact that this arithmetic is applied mostly to the Windows-based servers, while in Linux / UNIX-environment full reboot is required infrequently. In any case, regardless of the operating system, time waiting until the unit will return to work after restarting a fully functional state is large enough. What is there plus a virtual machine? First of all, the VM, in principle, rarely require more than three to five minutes for a full reboot, since all the physical components of the emulated “hardware” in themselves are not reloaded, and all services to manage, operate below the hypervisor, remain intact. Therefore, the typical delay switch-off of equipment and management software for running virtual machines have no effect. Secondly, more importantly, restart the virtual machine, which operates under a certain set of services inside the network, does not entail a reboot of other virtual machines running on the same physical, but also responsible for other tasks, which is impossible when all services are running at the same time on the same server without virtualization. That is, if you need a physical server, for example, to restart the Exchange virtual server and database, a virtual server for the company’s Web site will remain intact. If they worked in parallel on a single machine rather than two virtual, they are both on the restart would be available.
2/