The primary difference between backing up your endpoint and server is the scope of the backup. Servers use more bandwidth than endpoints— more data is often involved. Certainly, daily backups can curtail the lag which occurs when an entire server array is backing up, but it’s still likely to see the network underperform during this time.
Meanwhile, if you’ve got endpoint devices set to automatically backup to a cloud network at, say, 15-minute intervals, device performance is hardly impacted. Basically, a few megabytes are uploaded four times an hour. Bandwidth is hardly impacted, either. You couldn’t have a 15-minute backup solution automatically in play for most servers. Doing so may not be conducive to streamlined network operations.
Additionally, when you’re backing up a server, there’s more risk involved than when you’re backing up an endpoint like a desktop, laptop, tablet, smartphone, or another IoT device that is regularly used for production purposes in your business.
Something else to consider is the time involved in recovery. It generally takes longer for a file server on a network to reboot and re-upload conserved files than it does for an endpoint device. Accordingly, it makes sense to have endpoint backup protocols which automatically backup to the cloud, as well as strategically appointed times for file servers to back up in a similar way. The truth is, you need a backup that is comprehensive regardless. Having both backups for endpoints and servers makes sense.