Your Data Deserves Better Than Veeam - Part 2: Comparing Microsoft 365 Setup

William Urban, Technical Marketing Manager and Ruso Bhattacherjee, Technical Content Marketing Specialist

The painless pivot to simplifying data protection

People often get scared when they have to switch to new data protection software. Typically, switching means reconfiguring everything in the new solution from scratch. For legacy data protection solutions, you also need to include the effort of ensuring that your hardware and infrastructure meet both business (such as speed and security) and software requirements. 

Despite familiarity with using other SaaS solutions, some Druva customers have also echoed this sentiment, believing that there would be some hidden or unintended consequences of switching. When organizations are used to legacy data protection solutions like Veeam, moving to a new solution, no matter how cost-effective, simple, and secure, can seem like an insurmountable task.

However, a SaaS data protection product like Druva includes everything you need for data protection at no extra cost — storage, compute, software, and security. Because of its SaaS simplicity, switching to Druva is easy and fast.    

To explain how simple it is, we will do a side-by-side comparison of the exact steps that you need to complete to get both Druva (SaaS data protection) and Veeam (legacy data protection) up and running. For this demonstration, we will be setting up and backing up Microsoft 365

We want to help you visualize and understand exactly how much effort and complexity you can save with Druva.

Configuring your data protection solution

Prerequisites before you begin configuration 



Doesn't require any pre-configuration

Yes, you don’t need to do anything to start backing up your Microsoft 365 data with Druva.

Learn and understand at least 3 different aspects.

  • Become familiar with the Veeam Backup for Microsoft 365 architecture and deployment scenarios.

  • Ensure your machines meet the hardware recommendations and system requirements for Veeam Backup for Microsoft 365 components.

  • Become familiar with the authentication options.

Configuring backup infrastructure




With Druva, you back up data to the cloud. So, the entire infrastructure is already ready before you even think of what kind of data you want to protect. You don’t need to bother about physical hardware such as servers, storage, proxies, etc. 

Configure 3 different infrastructure components.  

  • First is backup proxy servers. They conduct all read and write activities during data backup, restore, and several other stuff. 

  • Next is backup repositories. They act as storage systems for backups and backup copies. 

  • Lastly, configure object storage that extends the backup repository storage system.

Connecting your backup solution with Microsoft 365



Authorize with a 2-step process.

Provide Druva authorization access to your Microsoft 365 tenant using your Global admin rights.
This is similar to allowing permissions when you download an app on your mobile phone.

Complete a minimum of 4 different steps.

  1. Download the installation package from the Veeam website.

  2. Install Veeam backup for Microsoft 365 on a physical or virtual Windows-based machine by following a 9-step process.

  3. Install Rest API using a 9-step wizard. 

  4. Install the license.

If you want to deploy on AWS or Azure, you will need to follow a different set of steps.

Adding users that you want to back up




Druva automatically connects with Azure AD and discovers all users and groups that your organization has (see image below).

Requires 3 different components, 2 separate configurations, and an understanding of performance issues before you complete adding users. 

Veeam uses 3 different components to back up Microsoft 365 organizations. 

But, that’s not it. You also need to add backup accounts and configure backup applications. 

However, it’s not that easy. Before configuring, you need to understand the impact of multiple backup applications on performance

Configuring your backup settings



Select 5 options in a single pop-up window (see image below).

Configure 10 different general settings. Then, build a backup infrastructure using 3 components.   

After you configure the settings, you’ll need to understand SSL certificate scenarios and install the certificates. 

But wait, there’s more! You must set up backup infrastructure by configuring backup proxy servers, backup repositories, and object storage. 

Completing your first data backup




Backups are triggered automatically at your defined intervals.

Configure at least 3 sets of multi-layer settings before you can even think of backing up data.

You can back up data using backup jobs. However, to create a backup job, you must understand 5 different object types

Then, you have to create a backup job using the Backup Job wizard. 

Restoring your data 



3 simple steps

End users or admins can restore data. An admin has to:

  1. Select a user.

  2. From a snapshot, select the data that they want to restore. 

  3. Select the location where they want to restore.

For end-users, the process is even simpler. They just need to complete steps 2 and 3 of the above procedure. 

See the image below for a look at restoring data from within the Druva console.

Involves 5 components of the Restore Portal and learning about its limitations and considerations.

Alternatively, you can use any one of the 4 separate Veeam Explorers for Microsoft 365. 

Data restore uses a separate portal altogether named Restore Portal. You must familiarize yourself with the five components of the restore portal before you begin restoring data. 

Additionally, you must also understand the considerations and the limitations of the Restore Portal before restoring data.

If you want to take the Veeam Explorers route for data restoration, remember that each explorer requires Planning and Preparation before you restore data.

Note: All information has been collected from Veeam documentation and our Druva docs portal.

Price doesn’t equal cost

Veeam is not only complex to operate and maintain, but also costly. Veeam’s costs include on-premises hardware, software, management, and data center elements that, when recognized, represent a much larger financial commitment compared to Druva’s cloud-native, SaaS-based approach. With Druva, customers can eliminate up to 40% of their backup costs and gain back precious people hours on an ongoing basis. 

We let our customers speak for us

Companies that switched to Druva from Veeam achieved results like these thanks to the SaaS advantage Druva offers — simplicity, cost savings, time savings, and scalability. 

“From the beginning, Druva’s setup has been very intuitive and easy to use. It just works. We don’t have to hassle with things that aren’t functioning as they should. We’ve never had a problem with backup recovery. Druva is a solid product.”

- Michael Brandley, Global IT Manager at Pyrotek

“I’m the CIO and do not work on day-to-day technical tasks. I was personally able to deploy Druva within a few clicks which says a great amount about its intuitiveness and user-friendliness.”

- Tom Ferrucci, Chief Information Officer for Natco

“Veeam required so much underlying infrastructure to facilitate backups. And since we were looking to drive huge changes internally within a short timeframe, we needed a solution that we could get up and running quickly.” 

- Max Yip, Head of Infrastructure, Security & Ops for Kerry Properties

Try Druva and say goodbye to complexity headaches

To learn more about how simple Druva is to deploy, use, and back up your data than Veeam, visit our Druva vs. Veeam competitive page.

Read part 1 of this blog series for an overview of how Druva beats Veeam on simplicity, security, and savings, and part 3 for a look at how the two solutions differ in their approach to security patching.

Ready to try Druva? Your data deserves better than Veeam — switch to Druva and get up to 6 months of 100% SaaS data protection FREE.