Veeam Data Platform Reviews

In terms of use cases, I'm very familiar with the environment and the platform. I've been using it for the past six years. I mainly rely on it to manage the users on the platform and resolve any issues they may encounter. If there's a problem beyond my expertise, I open a support case.

In terms of backup installation and business continuity, VM has been invaluable. There was a time when we had an issue with one of our systems, and Veeam became unavailable. This particular Azure machine is utilized in about six or seven countries. All I had to do was log into my Veeam account in that location, activate the Continuity and Recovery (CR) feature, and everyone could resume working. It involved changing the IP address or the capabilities of the application server since the assessment is based on the application server's availability in another location. The IP addresses would vary.

So, I informed the application department to make the necessary modifications, and they immediately restarted the system for use.

Security is one of the most valuable aspects. In VM Backup, encryption is enabled as well. Depending on your backup job, you can increase security by setting up encryption and assigning a password. 

The encryption password is used to protect the backup files. Even if someone gains access to the backup job or files, they won't be able to utilize them without the password.

In terms of improvement for VM, I believe we should focus on reducing data leakage and addressing a specific issue. There's a situation where VMs run on different locks. It's running on the VM while having a relationship with nearby solutions running on the same server and storage. This creates a bottleneck that needs to be eliminated. The efficiency of the solution should be improved.

I have been using it for six years. We are currently using version 11 in our environment. It's located in a different place.

It's very stable. I would rate it as a nine.

In terms of scalability, it is fantastic. I would give it an eight for scalability. Currently, we have around 500 users utilizing it for the HQ. We plan to expand the usage in the future.

I've recently tried using version 12. Although I haven't used it for long, I find it nice. I'm currently using it for one of our main offices at the HQ. It hasn't been fully deployed yet, but we're considering deploying it before the end of the year. The plan is to scale it within our HQ infrastructure because that's where we have the highest workload and need more information about different features available in version 12.

The technical support is fantastic. When I encounter an issue, I simply need to contact the engineer who guides me through the process of uploading the logs. They analyze the logs and most of the time, they are able to provide a solution. The log analysis is crucial in identifying any problems specific to our environment. Sometimes, there may be delays if the issue requires further investigation, but the engineers are proactive in communicating and resolving the problem in a timely manner. 

However, there might be instances where the problem lies with our internet connection, and in those cases, the support team may not be able to identify the issue solely through log analysis. In such situations, a remote session is highly beneficial as it allows them to have a deeper understanding of our environment, and combined with my own knowledge, it speeds up the analysis process and enables a prompt resolution. I appreciate the importance of a remote session in such cases as it facilitates faster analysis and helps in finding a timely resolution.

Positive

The initial setup is very simple. I would rate my experience with the setup ten out of ten. I've been setting it up myself since 2015 for each of our countries. I handle remote activities and upgrades without needing to involve the team of engineers. It's a straightforward process, and I haven't encountered any difficulties.

I work with my company's IT team to handle the deployment. It's done in-house. The deployment process takes around an hour. 

Typically, I discuss the deployment process with my manager or attend a meeting to discuss the solution and get approval. It's not a cumbersome process and is quite straightforward.

I would give it an eight. The only problem we face is when our support expires, and we need to renew. If we're purchasing a new license, that's when difficulties arise.

There are no additional costs or hidden fees. It's a straightforward pricing structure.

We tried using Micro Focus. Veeam Backup & Replication provides us with more than what we actually need, especially because of the application solutions it offers. Micro Focus, on the other hand, only focused on backup without additional application features.

In terms of stability and efficiency, I highly recommend it. I've already introduced it to two or three different companies where my colleagues work, although I'm not sure if they have already adopted and purchased it.

We use Veeam ONE for backup and replication, and disaster recovery purposes.

I like the backup and backup copy features.

Agent backups could be better. I have many problems with agent backups, particularly on Linux and MySQL databases. MySQL works well with Microsoft products but not with other products. The database backups are not working correctly, and we are losing business. I am not getting any support; administration is also a significant problem.

I have been using Veeam ONE for over four years.

Veeam ONE is stable for small uncomplicated projects.

On a scale from one to ten, I would give stability an eight.

Veeam ONE is scalable.

On a scale from one to ten, I would give scalability an eight.

Support could be better. 

The initial setup is straightforward. Based on the project size, implementing this solution can take 24 hours, 72 hours, or even a week. A team of four can quickly deploy and manage this solution. They can handle configurations and backup failures daily. I can maintain 12 projects by myself.

On a scale from one to ten, I would give the initial setup a nine.

We implemented this solution.

We pay every month for Enterprise Plus. There are no additional costs.

On a scale from one to ten, I would give Veeam ONE a three.

We use the product to manage the data workloads for small and medium businesses.

Veeam Data Platform’s most valuable feature is replication.

They could offer a hardware appliance as a comprehensive, full-stack solution. At present, we have independent software and hardware for data backup purposes. Instead, they could provide all the necessary components in one single box. Additionally, they should add new features for containers to align with the landscape of new technologies and cloud-native applications.

We have been using Veeam Data Platform for seven years.

I rate the platform’s stability a nine out of ten.

Veeam Data Platform provides better scalability than Backup Exec in terms of time. It works smoothly without any complexities for workflow or database management.

I rate the scalability a nine out of ten.

We use Veritas, Commvault, and NetBackup to manage workloads for enterprises.

The initial setup is simple. The installation process is swift. However, post-installation, the crucial aspect lies in the expertise of the implementing engineer to configure the tool effectively for scalability. We can deploy it on the cloud and on-premises as well.

The product is inexpensive. They offer customizable licensing models including perpetual and subscription-based licenses. However, I recommend using Backup Exec for customers using Microsoft products such as Windows Server as it offers more flexible pricing models.

The platform has a useful disaster recovery feature. Additionally, it has a good feature for instant recovery. However, a notable consideration arises when dealing with a scenario involving seventeen workloads, where customization may require the provision of two packs, each accommodating ten instances of Instant VM recovery. This setup could potentially result in having three VMs left unused. 

I rate it a nine out of ten.

At the moment, I face difficulties when trying to deploy Veeam ONE because my active directory restricts some particular rights.

In general, the solution needs to have lesser limitations.

The technical support of the product needs to be faster.

I have been using Veeam ONE for five years. I am using the solution's latest version. My company is a customer of the solution.

Stability-wise, I rate the solution a six out of ten.

It is difficult to deploy Veeam ONE. I think Veeam ONE is a good product to supervise and monitor infrastructure and for backup purposes.

Scalability-wise, I rate the solution a two out of ten.

In my company, we have ten people who use the solution.

When I create a ticket, Veeam's technical support directs me to its L2 support. I rate the technical support a four out of ten.

Neutral

On a scale of one to ten, where one is being difficult, and ten is easy, I rate the setup phase an eight.

The solution is deployed on-premises.

In the upcoming month, we have plans to deploy it on Azure Cloud.

There was no particular process we opted for deployment.

Our company receives the product at a good price from one of Veeam's integrators, so we don't need to pay the price of the solution declared to the general public.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the price a five.

Veeam ONE is a good product for its supervising capacity, management capabilities, and monitoring purposes.

I rate the overall product a seven out of ten.

We primarily back up VMware and Hyper-V, and we have some physical boxes as well, both physical Windows and Linux boxes. We also use the scale-out capability going out to the public cloud. We don't have any NAS devices. So, there's no taking advantage of that. We're not using the instant recovery engine. I believe we use the Veeam ONE software as well. 

We have customers all over the place. They are using the current version and the earlier versions. 

In terms of deployment, it is a combination. In a lot of places, it is deployed in a private cloud environment with more than one site for replication, but we do have other customers that go out to the public cloud for an off-site copy. The cloud providers primarily are AWS and Microsoft Azure.

The normal backup and replication features are valuable. 

It is cost-effective. A lot of times, people pick Veeam because of its price.

Its native capability for talking to the public cloud needs improvement. Connecting to a public cloud is a little bit more of a challenge when it comes to Veeam than it is with Rubrik or Commvault. There are still some hoops that you got to jump through in order to send Veeam backups out to public cloud repositories. It is not as simple as it is with other products.

I have been using this product for three to four years.

It is very stable.

It scales out easily. The only challenge is that as compared to some of the other products, it is a little bit more difficult to do things when you're dealing with the public cloud. Other products integrate a little easier. Veeam has not gotten there a hundred percent. You've got to deploy additional infrastructure out in the public cloud. So, on a one to five, it is a three. It is a little bit more difficult, but it is scalable.

We have hundreds of customers who are utilizing Veeam. They are any type or range of engineers, IT directors, and IT managers. There is a whole different range of individuals who are supporting backup environments running Veeam.

There are probably plans for increased usage. A lot of it comes down to the requirements of our customers.

Their support is good. We never had a problem. They are always reachable and able to answer. The engineers we deal with are able to answer all the questions that we have.

We've got customers all over the spectrum. Some customers do switch to Veeam because of its ease of use and its price point.

We sell and support Commvault, Veeam, and Rubrik. If I had my preference, Veeam might not be the first choice, but a lot of people do pick Veeam depending upon their requirements and their price point because it is more affordable than some of the other products.

It is pretty straightforward. On a scale of one to five where one means incredibly difficult and five mean just effortless, I would rate it a four out of five.

I don't do a lot of deployments. It is mostly handled by a different group of people in my company.

We do offer professional services for implementation. Very often, we will take care of that, but it isn't really required.

The number of people required for its deployment and implementation depends upon the size of the environment. A small environment could be basically installed, maintained, and managed by one person. A much larger environment, depending upon how frequently you're doing restores and how complex your retention policies are, could require more people.

It is hard to give that because everything depends upon the size of the environment. Smaller environments are going to have a much faster return on their investment than larger ones. It depends upon what they're doing.

It is more cost-effective than some of the other solutions, but a lot of that comes down to the fact that we're a reseller. So, depending upon the deal, we do negotiate different price points for different customers. The price varies depending upon the size of the customer, the size of the deal, and the discounts we can negotiate.

Price does come into play during the evaluation. We have dealt with customers who evaluated products like Backup Exec, Commvault, Rubrik, Veeam, and Simplivity. There are quite a few that are in the mix. More often than not, depending upon the size of the customer, people pick Veeam a lot of times because of its price.

The biggest thing is to do the research. Do a comparison of each industry-leading product and see which feature set you're looking for. There is the price point as well, but I usually recommend that the feature set is more important than the price. If you're looking for specific features and capabilities and they're not available in a product, picking that product because it is the cheapest could be a mistake. So, make sure that you're comparing feature sets and purchasing the one that has the features that you're looking for.

I would rate this solution a seven out of ten. There are other products that have more advanced features. They would be rated a little higher.

We're using Veeam for our on-prem backup of VMware vSphere environment and a couple of physical Microsoft servers. We're using version 10 of Backup & Replication.

It has an intuitive interface, and it provides us with successful backups without needing to tweak or do any adjusting. We just set it up and like their ad says, "It Just Works."

The one downside to Veeam is that they don't have a cloud product of their own. They partner with people and they support vSphere 7 and our cloud backup doesn't, and neither do many of the cloud backups that they partner with. I've looked at a couple of them. We partner with iland and they don't support version 7. They only support version 6.7.

Iland is our cloud backup and it utilizes Veeam. Veeam supports version 7 of vSphere, so they stay pretty up to date. They lag behind, but everyone lags behind a little bit. Once vSphere VMware does an upgrade, it takes a little while for places to support that upgrade. Of course, we always wait until our backup product supports it. But Veeam does a pretty decent job of keeping a short window, and they're able to support a fairly current version of VMware.

We've been using this solution for two years.

They don't have a dedicated support person for you, like ExaGrid, but their support is decent.

We've used Symantec, Veritas, and Arcserve years ago, and those interfaces were awful. Veeam is hands down the best interface that I've dealt with for a backup solution.

The setup was very straightforward.

I wish Veeam had their own cloud product. We are looking at a company called Infrascale, and I've seen that they have a lot of benefits over the other solutions we've looked at. I also want to look at Unitrends again because it was a pretty good solution when we were using it, but it had some drive failures. Plus, their GUI was all over the place.

With Infrascale, you can boot up your VM in their DR site, just like I can in vSphere, and log into it and look at it. A majority of our VMs are Microsoft Server products, so we could log into it and test that the data is there. That would make it great for testing our backups, which is something we need to do because our New York state auditors require that. It would make it so easy to test the environment, and it's not so easy with Veeam. You need a VMware and a vSphere environment in place to bring those VMs up, but here you don't.

I would rate them a 10 out of 10. They probably have the best product I've ever dealt with.

We use it to backup our VMs.

It assists in enhancing data protection and recovery strategies, including disaster recovery scenarios where backups are replicated to alternative locations for additional redundancy. Additionally, these tools enable the scheduling of backups at specified intervals, ensuring that backup copies are retained for a defined period to facilitate recovery when necessary.

Veeam ONE helps in supporting risk management initiatives.

Backup management features are crucial for ensuring the reliability and automation of backup processes. These features enable automatic scheduling of backups, reducing the likelihood of human error associated with manual backup procedures. Additionally, they offer the capability to protect data consistently and reliably, mitigating the risk of data loss due to oversight or human error.

I have been working with it for several years.

Stability is excellent; there have been no instances of technical issues or downtime experienced.

The majority of our clients are enterprises.

The quality of technical support is satisfactory. I would rate it nine out of ten.

Positive

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.

The initial setup and implementation process is relatively straightforward. However, challenges may arise, particularly concerning data management, especially when dealing with large volumes of data. The complexity tends to increase as the amount of data grows.

Deployment can be completed swiftly, typically within a month. However, the duration of tasks such as replication increases proportionally with the size of the data being handled.

The pricing is reasonable and falls within the average range.

I would recommend it, although we've only utilized the backup feature. Overall, I would rate it eight out of ten.

We use it at our site for our nightly backup and for disaster recovery (DR) replication to another site. So, we use WAN Accelerator. We use scheduled copies to another datastore, and then, of course, we do it for our backups for SQL servers and other servers.

WAN Accelerator helps tremendously with replicating our data because we have a large chunk of data that gets replicated between our two facilities. We're getting ready to purchase Nimble Storage that has Veeam integration, and it is supposed to improve our replication even more.

The SME that helped us with the implementation would probably have more insight because he used it way more than we have. We just use it for making sure that our backups are done daily, and the replications are being performed between sites. We haven't had any issues at all with it other than the fact that there is a slight process to acquire additional licenses if we want to expand our number of hosts. That's because it is based on the number of cores and threads that are used. 

I have been using this solution for three or four years.

So far, it has been pretty steady and stable. I haven't run into any type of issues with it.

It is scalable. What they definitely don't recommend is running it off a virtual machine rather than its own physical machine, but then we have some replication servers that we use for VM. So, the actual Veeam installation is set up on a physical Dell server, and then it is almost like they are sub engines. You would use these other processes to kick off the replication for whatever you want to be replicated to your DR. So, it is not all functioning from a single server. We have like three or four of those forms of replications.

The tech support and the training are pretty good. I sent one of my former employees, who was an intern and also my main Veeam administrator, for the training. He said it was very technical, and there was a lot to digest. He couldn't just do a transfer of knowledge because someone would have to go through that program to get a good understanding of how the solution works. He had gone through a lot of reference documents that came from it, and based on his feedback, it was pretty good.

We used to have Symantec Netbackup, and we replaced it with Veeam. Symantec Netbackup was clunky in terms of the upgrades. The other issue was that you couldn't throttle the replication bandwidth. 

It had the capability of doing a DR replication, but if you fall a couple of versions behind, there was no gradual update. If you fell behind by four versions or something like that, it was a nightmare trying to get it upgraded to the latest version. We had to have a consultant come in who worked with Dell but was intimate with Symantec products. He had to spend a week or two weeks with us to go through that upgrade process. It was more designed for backup to tape, and that was the main function for which we were using it. When we decided to go away from backup to tape and we wanted to do site-to-site replication, we didn't think that it had that inline capability. It was also costly.

From my understanding it was straightforward. A colleague in one of our other facilities was more intimate with the solution. Basically, we bought a physical box. It was a Dell box that had storage on it. It was our main Veeam backup server that handled the replications because it was used to store the backups. So, we didn't back up to tape. We back up to disk, and it replicates to the DR disk. Setting that up wasn't a problem. 

We also had to expand our local backup by using an additional span and then configuring that in order to work with Veeam as well. We didn't have any issues with it. 

In terms of maintenance, we only assign one person who manages it. So, it is a part of his daily tasks. This person looks for success and failure, and, if needed, kicks off a backup that failed. He also does the quarterly review to make sure that it is up to date and addresses any replication issues. 

If you are trying to replace an existing solution, you need to map out how to integrate Veeam while not impacting the current backup. That's what we did. We had to look at how do we continue our Symantec backups while implementing our Veeam. We slowly graduated at it. 

If you are doing any replication with Veeam, you need to determine the tier of the replication to a DR site. We broke out our SAN datastore so that the storage for what we would consider critical backups are done from a different datastore versus the entire SAN. Instead of implementing it first and then trying to change everything around, we did a lot of such pre-work prior to implementing it.

One of the things that Veeam doesn't like is a major change. In such a case, you will lose your data points or restore points. This means that if you've done 14 restore points and you go and make some major change to it, it could break that 12 restore point chain, and now you basically have to start all over again.

I would rate Veeam Backup & Replication a nine out of 10.