An IT professional would have a disaster recovery plan. Some even have tiered plans depending on the type of emergency.
I will agree a server system is more complex. Sometimes it's the only way you can meet certain security measures is through the use of a server.
I've said this before and I'll say it again. What really matters in terms of reliability is the hardware. Spontaneous software failure is extremely uncommon when you have a dedicated computer/server. Most software issues arise from users executing programs on a dedicated machine that they shouldn't be. Keeping a dedicated computer minimizes this error significantly. But everyone still keeps backups just in case. Full image backup can have you up and going to an exact image of your computer from the previous day.
I don't what you mean by server crashed, but there are a few possibilities.
-If we have a hard drive failure, RAID covers us. The system would still run with no down time. Can be used on P2P or Server.
-If we have a PSU failure, redundant power supplies cover us. The system would still run with no downtime and you can replace the and unit at your convenience. Can be used on P2P or Server.
-If we have a memory error, ECC RAM corrects and stops a blue screen/crash/reboot, uptime is maintained, and data loss is prevented. Can be used on P2P or Server.
Prior to virtualization, the main way to defend against motherboard failures was quite expensive. Often involving a second high priced, identical server. With virtualization, we can jump from computer to computer with little to no downtime. There are other enterprise techniques like failover clustering but that gets complicated.
.png "ACUF Donor I")
