We utilize various tools from different brands such as NEC, HP, and VMware. However, Veeam stands out as a superior option due to its ability to seamlessly integrate and manage multiple VM environments.

We were using Backup Exec. We then switched to Veeam ONE because it is very practical and has different applications integrated with it.

For monitoring purposes, my company uses a free, open-source solution like Zabbix. Compared to Zabbix, I feel Veeam ONE can be more useful for monitoring purposes.

Compared to Zabbix, I feel Veeam ONE has no downsides apart from its reporting area, which can be improved.

We used NetBackup and a new POC called Nakivo, but they weren't as grand as Veeam ONE. The best solution in the market right now is Veeam ONE, so we continued using it.

We used Commvault and Microsoft solutions. We switched to Veeam because of better licensing and pricing.

We were using Veritas before this, it's their NetBackup product. I find that difficult to use, but the great thing there is it can run on a Linux server.

I do have an experience in Veeam One, Veeam Enterprise, and Veeam Backup and Replication. I did not previously use a different solution that was not Veeam.

We chose Veeam over Commvault because it is simpler to use and more cost-effective. Commvault's complexity and lack of readiness for cloud backups made it less appealing. Veeam offered comprehensive backup solutions for on-premises, Azure, and Office 365, with fewer hardware requirements compared to Commvault.

I switched to Veeam ONE due to its simplicity of use. 

I learned about Veeam ONE before exploring other solutions, and I have found it to be a highly cost-effective option when compared to alternative solutions.

In previous work, I've used EMC Networker. I found the solution to be too complex and I wouldn't say that the solution worked well for me. Veeam is much more straightforward and I find its usability to be better.

Before Veeam One, I tried Veritas. In Veritas, if we want to monitor the virtual infrastructure, that is a separate license. Veeam One is very straightforward because it's called the virtual machine. If you have 100 virtual machines, you have to get 100 licenses. Veritas needs a capped speed license, which means I need to understand the customer's environment around the capped speed they use for the virtual machines. The license structure is complex for Veritas. And it is difficult to forecast the capped speed for the next few years of growth.

We used System Center Operations Manager (SCOM) prior to using Veeam ONE. We switched to Veeam ONE when the decision to use a third party solution was implemented.

There are other products for virtualization, but not for Veeam. I don't know any other product that covers Veeam, VMware, and Hyper V.

I previously used SolarWinds and they had better support that was more knowledgeable and responsive.

I've worked with Tivoli Storage Manager, Commvault, Spectrum, and Symantec NetBackup, which is Veritas NetBackup now. 

No previous solution used.

About virtual host, I utilized (and I am still using), Nagios, Netwrix, OpManager but I am preferring them only for OS, network devices, bandwidth utilization and application server monitoring.

I liked Veeam One about VMware and HyperV server monitoring

We used other solutions previously. We are still using SolarWinds Virtualization Manager, version 6.3, in conjunction with Veeam ONE.

One of our large clients decided to acquire Veeam ONE based on their own research. This decision was seconded by us.

We found the reporting and capacity planning tools were really what they needed. That helped us support them better. The cost savings was the driving force.

We previously used IBM & Microsoft solutions.

I used a product called vRanger by Quest. They are very similar, but I decided to switch to Veeam after going to a VMware event and seeing that Veeam had become a partner of VMware. This gave me more confidence in their product.

I did not previously use a different solution.

I use Office 365, Veeam Cloud Connect, and Veeam ONE in my Data Center.

We used PRTG but we were getting a lot of false positives.

We are using both solutions right now.

I did not previously use a different solution.