We are using Veeam Backup for Office 365 to backup all of our mailboxes. If something happened, we only have to restore the mailbox and look for an email.

After migrating to the Vectrus platform, the main focus was on ensuring complete backups of email, Teams, and SharePoint using Veeam Backup. Additionally, user migration and porting are essential aspects of this process. There was a need for archiving user email boxes for several years, even for those who have left the company, and Veeam is utilized to export these backups.

We use Veeam because — while Microsoft provides a terrific environment called Office 365 — they do not back up files that are stored there. The files most customers are concerned about are OneDrive and SharePoint files, but they often overlook their mailboxes and the Exchange piece of Office 365. It is the customer's responsibility to actually back that data up, which Microsoft does not do a good job in sharing with you. We had moved all of our file server shares to OneDrive and SharePoint, and we were just over a terabyte of data. To make sure they were being backed up properly, I implemented Veeam Office 365 Backup.  

We have many customers that are using Veeam Backup for replication and for disaster recovery sites. All our customers use Veeam Backup.

We use it for Nutanix as well. We have many clients that have Nutanix and use Veeam Backup to replicate workloads to another site, a backup or DR site.

We work with Veeam Backup for Office 365. We have two products that we back up. We back up workloads in Azure and Office to on-premise with Veeam for Office.

The solution is used to keep files for posterity, in case of disaster recovery, in case of restoring something that goes missing.

The solution is primarily deployed on the cloud but in some cases we deploy on-prem.

We primarily use the solution as a backup for our Microsoft items.

We are using Veeam Backup for Office 365 to store backups of files, such as pictures that we use and personal files.

Veeam Backup is primarily used by companies already using Veeam to expand their backup to protect their data or who have moved to Office 365 and want to be able to backup to Office 365 in the cloud.

Most of the time, the solution is primarily used for a VM backup from VMware.

If you have any virtualization solution, you don't have to have a VM solution for Linux. We don't need to go through an agent for a physical server. I've only done one integration one time for Office.

We offer clients backup and replication services. According to our clients, Veeam is the very best. 

It is mostly used for PST from Outlook and OneDrive. It is a good solution, and we don't have any issues with any customers.

We use it for different workloads like the VBR, Veeam Backup and Recovery. We use it to back up our virtual servers, physical servers, and our SQL database backups. We also use Veeam to back up the user mailboxes from 365.

We use the solution for backup.

The Veeam Backup solution is very good for big enterprises and complex infrastructures. The main reason we are using Veeam is for end users.

Our primary use case for this solution is to back up and restore from the cloud to on-premises.

We are using Veeam for our customers. It's used for backups and disaster recovery.

The use case is to back up Office 365 data. The users want their data in Office 365 to be backed up because even Microsoft has some data protection limitations. There are cases where the data could be lost, and Microsoft will not take responsibility. It is the responsibility of the users to set up a proper backup. For example, if you have a malicious user deleting certain data, you can restore it yourself. That's a use case for Veeam Backup for Office 365.

Our primary use case for this solution is performing backups.

We are distributors for Veeam.

The use case for this solution is for backup. 

The challenging part is that people don't understand the importance of having a backup of Office 365. They think that their data is on the cloud and it's safe. They don't feel the need to back it up. Once they learn about the Microsoft shared responsibility model, they find out that Microsoft is not responsible for the data.

If, for example, an employee deletes his emails because he is angry with the management and leaves the company, the company will need a backup to restore at some point.

There are various reasons for backing up Office 356. There could be a cyberattack, and there are compliance requirements. 

Even if Microsoft will protect their data, they will still need a copy of it, and the software will help with that. 

Some people have a hybrid setup and will not only have Office 365, but they will be using a mix of Exchange on-premises and Office 365 that they need a backup of. 

The most important part is to have your data accessible and restorable at any point.

The solution is used to backup customers' Office 365 data. It is not really an MSP product. It's on-premise. In order for you to comply with GDPR, if you are an MSP, the only reason to really do that is if you set it up in your own environment and on virtual machines and you literally have to lock yourself out of that machine and give the customer full access to it.

The other thing is, to comply with GDPR and with Veeam for Office 365, is the backups need to be encrypted. There's no encryption. What we did was we basically encrypted the hard drives that come from Bitlocker and only then did we get compliant with GDPR. That part was quite tricky. 

Veeam provides cloud backups. These days, most people want to back things up on the cloud. All the work saved on various office workstations and file servers is backed up on the cloud.

Our primary use case is the backup of our education-related files and data.

We use the product as a data backup tool for Office 365.

The use case differs from customer to customer.

We use Veeam Backup for Office 365 to back up our data, such as mailboxes, OneDrive, or SharePoint. We are able to back up our data on-premises.

We've been using Veeam Backup for about a year. We get a lot of inquiries, whether it be from our partners or from end-users, who would like to backup their Office 365. They inquire about how to do so and the prerequisites, what exactly is required. Generally speaking, their concern is about how much storage is needed for the backup. Every company has a different backup policy, different RPOs, and different pre-pension policies. We help them determine how much storage they are going to need. That's basically it. That's how we deal with it.

When we work with physical infrastructure, we use a Veeam agent to protect that workload, but we use Veeam for Office 365 to protect workloads in 365. 

We install Veeam Backup for Office 365 in every system. We use the system application for taking the backups.

Our customers primarily use the solution as a backup for on-premises because they have nothing on the cloud. They want to be sure that they have the data backed up at least on their side. Before that, the exchange server was on-site and on-premises. The clients put it all in Office 365 and now they want to have a backup on-premises.

We use the solution primarily to protect data. 

We were not aware of the fact that Microsoft was not engaged, could not be, or we were not aware of the fact that it was not possible to engage the responsibility of Microsoft in case we lose or face corrupt data. We thought Microsoft was in charge of all the security and the workload protection. Since we have learned we are not fully protected, and after hearing of some bad experiences from friends, we started using this solution to protect our data and to be sure that no matter what happens, we can get our data from Office 365, and especially, Teams.

Our primary use for this solution in our company is for backing up emails.

The solution is mainly used for production. If they lose connectivity to the cloud, they will have a backup on hand. 

We are using this solution to back up our users' mailboxes, that is, Office 365 mailboxes.

We have Veeam in place for Office 365 backup and restore. We use it for mail backup and restore, SharePoint, and Teams. We were still struggling with the backup of OneDrive, which is still a discussion. We are using its latest version.

We primarily use the solution to backup our Office 365.

We use this solution to backup our database of Office 365 users' information.

Our primary use case is the backup of 365 objects and emails. At the moment, you are just testing Veeam. We are using it for production, and we are running a few productions on APIs.

Our primary use case for this solution is securing data, and we deploy it on private cloud.

We use this solution to protect our mailboxes, our data, and Office 365.

We use it in our office as well as for our customers who have Office 365.

I use it in a multi-tenant way.

We use Veeam to make backups in our system, including backups for Office 365 and other applications.

We use this solution primarily for backup purposes. We use the on-prem deployment model of this solution. 

We primarily use the solution for backup. We leverage it for security reasons so that we feel safe about the security of our data. Microsoft doesn't guarantee anything. If they lose your data, then they lose your data, and that's it. This gives us a sense that we won't lose anything if something happens. 

We primarily install the solution for our clients. 

The solution is used for backup purposes, specifically for Office 365. By default, depending on how it is configured, it will back up every eight to ten days. Beyond that, if you need specific mail recovery or complete mail recovery, you can do that as well. 

I use the solution for software production and virtual machine backups.

As the solution is cloud-based, we are always using the latest version.

The solution allows a person to keep his data third party when it comes to compliance requirements, thus necessitating that it only be backed up at a certain place. The solution is used wholly for compliance requirements. 

We use this product to back up our Office 365 files, such as those in Exchange, OneDrive, and SharePoint.

The primary use case of this solution is for backup and replication of virtual machines, and the backup of MSL.

The deployment model was on-premises.

We use Veeam with a private cloud, primarily for backup.

The primary use case is to keep emails for longer retention time.

We use the private and hybrid models of this solution.

We use the hybrid deployment model. We use it locally. 

We have a public cloud deployment model.