A+ for Druva!

Originally, we were looking only at endpoint backups for our users' machines. After talking with Druva, we found it was quite easy to implement SaaS backups for our Google Workspace, which included Google Drive and Gmail. With the system we were previously using, the end-user data restore process is a bit of a nightmare and not end user friendly at all. Druva, on the other hand, is very easy to use and I no longer need to assist end-users with file restoration. Moving between machines - if the user's laptop is replaced, for example - is also very easy. When the user logs into their Druva account, the system notices a different machine and asks to either add the device to their account or replace the one already found. If replaced, it will ask if it should begin a file restore process. Backups are also a breeze as you can define different backup profiles to different sets of machines. These profiles are then pushed out to the assigned clients without having to mess with the end user's client install. Profiles can be either as granular or as simple as you'd like to use and can be applied across a number of platforms.

We've been using Druva for our Google Apps for Work data backups. Largely, it runs on its own, without issue - this assumes the setup was done correctly and Druva has been granted sufficient access rights. It gets your Gmail, Google Drive, and Team Drives data in incremental backups. Set a schedule, have the user register, and Druva does the rest without any action required from the user.