Veeam Data Platform Reviews

The solution provides great insights. Veeam ONE is like a consolidated monitoring and reporting solution for Veeam Backup Replication, and Hyper-V and VMware environments. It basically provides a pane of glass to monitor and report on both your backup infrastructure and your virtual infrastructure if it is Hyper-V or VMware. 

What I really like about it is that usually I would deploy it before I deploy Veeam Backup Replication to get insights on the environment that can help me avoid issues during the VOT or during the implementation of Veeam Backup Replication. For example, I can get insights to see if there is any bottleneck on the production storage on which the servers are residing.  If I need to back up, I can find out if the storage has very low space and if I trigger backups with Veeam or any other situation if I come and conduct a snapshot if it will likely cause a recall production issue.

Another really amazing feature I like about Veeam ONE is not just that it helps me plan the deployment and whatnot, in general. It can help me generate reports about the virtual environment that are totally unrelated to the backup. For example, I have one customer within the POC for Veeam Backup Replication and for Veeam ONE, the Veeam Availability Suite. They are using NetBackup. And they said, "Okay, we are okay with NetBackup. We don't need Veeam Backup Replication. But, We want Veeam ONE" This is due to the fact that once I integrated Veeam ONE, I was able to provide them insights into their environment that they had no clue about. For example, how much space is being utilized in the data center, what kind of data growth they're having in the data center, any issues in the infrastructure, and if there are areas for improvement.

Veeam ONE also recommends solutions for the issues. It can let you classify your data center. It will classify your systems and then report on them accordingly. Basically, it would provide many insights and monitor services. Some decision-makers are not into the technical aspects and whatnot. They're into the numbers and where they are right now, where they want to be, the loss options for capacity planning, et cetera.

It's strictly a reporting and monitoring solution for Veeam, Hyper-V, and Veeam Backup Replication. It's a monitoring solution for virtual data centers and backup in one console. Usually, reporting solutions do not have this functionality. You will have report decisions for VMware, however, they will not monitor the backups.

The solution is carefully designed to be easy to use - even if you're in a panic.

Technical support is great.

The solution can scale. 

They need to support more platforms. Right now, they support their Veeam Backup Replication product, which means they provide monitoring and visibility reporting to the backup infrastructure and the backup portion. However, for some people, they're not using VMware. They are not using Hyper-V, or they have other workloads. For example, they have Nutanix. Veeam can monitor the backups, which is part of Veeam Backup Replication, however, it cannot monitor Nutanix itself.

They also do not monitor physical workloads, for example, physical Windows Servers and physical Linux Servers. They report their backups. They monitor their backups through Veeam Backup Replication. They don't have server monitoring and reporting. That's where there is room for improvement.

The management software for Veeam ONE is installed only on Windows.

Recently, for some reason, a client didn't have the feature "offload backups to object storage", like Azure cloud storage, and for some reason, we were unable to locate any sort of particular report for that particular backup point. Having much more extensive backup reports would be great. They have a lot of backup reports which are great, and they have the option to create backup customer reports, however, it would be great to have additional reports along the way.

I've been using Veeam ONE also since version 9.5.

Veeam One is pretty scalable when it comes to VMware and the Hyper-V. It is scalable and has a modular architecture, just like Veeam Backup Replication. You can have the server run in one place and the client run in another. It works well.

Technical support is a tricky question. In general, if you're asking about Veeam when compared to other vendors, honestly speaking, the technical support response times are quite good. Support will vary by engineers, no matter which vendor you deal with. One day, I'll have a really bad engineer, the next I'll have an excellent one.  However, I evaluate more so based on response times, and as I've said, their response is always excellent. 

The solution is very straightforward to set up. It's a product that's designed to be easy to use, and implementing it is no exception.

Veeam has a suite called the Velamen Availability Suite. This Suite consists of two products; Veeam ONE and Veeam Backup Replication. Usually, we use these two products at the same time for different purposes.

I've been using the solution since version 9.5 and now it's on version 11.

I'd rate the solution at a nine out of ten.

The solution is so good to use. It allows for proof of concept. One can run a test on the database, move backups from one server to another, do file restoration or make use of portal storage features. 

Backup and storage is very fast, reducing what would otherwise take hours to minutes. Veeam was designed for virtual environments. The first year it was involved in supporting VMware virtual environments. 

While I do not recall whether the latest version is 10.0 or 11.0 I do know that it allows one to make a back up repository that is very scalable and simple. This can be added from multiple different levels, in respect of a single disc, through employment of cluster servers, data domain storage, or even tape library. This means the repository is very scalable, as the growth of data in the past years has presented a big problem. Cloud services can be employed as a back up repository. 

While I may not be the user testing each new market product, I am very happy with the solution's scalability. It boasts a support team that is good and fast and can conduct its affairs in a host of languages. When it comes to instances involving support, I can discern the differences over the past two months. Technical support is fast, helpful and provides good advice. 

While we do not consider it to be a big deal, I know there are other users who consider the running of the latest version of VMware vCenter while making use of the virtual environment to be an issue. One must update VMware or Veeam with care because of the compatibility issue involved. Installation and support must be taken into account. 

While strength, complexity and compatibility of the solution may pose issues for others, they do not for me. 

I feel the solution to be user-friendly. 

The monitoring, reporting and dashboard features are also fine. 

I am not aware of implementation issues and I have no concerns about the solution's security or stability. I have even tested the setup and it can be automated. At present, I see no need for an increase as I am not making 100 percent use of the product. 

This said, the limits of Windows integration on servers should be addressed. Many shops use only Linux and do not wish to run the Windows Server policy. As they have people with an understanding of Linux, they do not see the need to employ another person merely for backing up the server. 

Nowadays one can run Microsoft SQL Server on Linux without any problem, perhaps with this same ability being afforded to Windows Server. 

Occasionally, in the course of upgrading one's virtualization platform, the backup can be ruined. I know of people who do downgrade virtualization out of concerns for the success of a data center backup run. For me, personally, this does not present an issue as I am more conservative in how I conduct my administrative functions. 

We have been using Veeam Backup & Replication for three or four years. 

The solution is absolutely stable. 

The solution is absolutely scalable. 

I am absolutely satisfied with technical support. We benefit from it completely. Its multi-lingual character is definitely important. 

We were using IBM Tivoli Storage Manager for 15 years before making use of the solution, although I don't know what the product is called at present, as it replaced a branded IBM Protect product. 

We were using IBM Tivoli Storage Manager at a time when the majority of our data servers were running on physical machines. From IBM's perspective, the licensing has become more involved since virtualization became increasingly prevalent. While it was not in my purview, the prohibitive nature of the product led us to migrate to Veeam software and to procure a different license. 

While IBM Tivoli Storage Manager was considered to be the leading solution of its time, it was also very complicated. 

The installation involves a single package and is pretty simple. This is in comparison to the installation of the DB2 of Tivoli. Now, the installation is done in a single stroke and is so simple and the solution so nice. While we don't really make use of it at the moment, several years ago we constituted one of the main monitors of the virtual environment. 

The installation time is contingent on its scale as it varies based on the size of the environment. Another factor would involve the installation of disparate versions for different machines, such as concerns a proxy repository. A further possibility is to install everything in a single machine in virtual storage. 

I would put the main installation at 20 minutes and add another hour for configurations, such as those involving emails and reports. 

I consider the installation to be fully completed once I can carry out a task. We are talking about one or two hours. This takes into account the different applications for disparate environments in Veeam's environment. 

Overall, we have two people who are responsible for deployment and maintenance as it relates to everything involving the physical backup and virtual environment. 

We purchase a license annually. 

When it comes to the cost, IBM software is significantly more expensive than the solution for our environment, although we are talking about four years ago. 

We have two Veeam servers in two disparate sites.

The solution is not deployed on the cloud. One of the servers is physical and the other virtual, with the support and backup capabilities comprising 50 kilobytes of SSD storage. 

I would recommend the solution to others. 

There are approximately 700 people making use of the solution in our organization. 

I rate Veeam Backup & Replication as a ten out of ten.

I have two to four servers, and I back up one VM to another VM through Veeam Backup. That's the primary use case.

Veeam Backup is very user-friendly.

It's integrated with many deduplication software solutions  - including Dell software.

It's simply very good software for backup purposes. All the IT infrastructure is shifted on Veeam rather than other methods. 

The initial setup is very easy.

The stability is good.

The solution can scale well.

They are fulfilling the requirements of their users and the updates they offer are good. I used one update recently and it was good. Any previous problems were solved in the update release.

Unfortunately, when one of my servers crashed, I instructed a colleague to delete the backup job, and he did. He accidentally deleted backup replication, however. I had nothing then. Both the backup and the original machine were deleted. We learned that there is no chance for recovery once the backup is deleted. They should make it possible to restore a replica in cases where it is accidentally deleted.

The restoration, reiteration, or snapshotting somehow is creating some sort of problem for us right now. I don't know, if it's the hardware's fault or a software issue, however, sometimes it takes a long time to delete a Snapshot. It can take anywhere from 30 minutes to two hours. They have to minimize the time of restoration that Snapshot is creating right now.

The patching can be quite difficult at times.

We try to make the backups run at off-peak times, however, sometimes something goes wrong and it doesn't back up as scheduled. 

I've only been using the solution for about a year at this point.

We've found the solution to be quite stable so far. We haven't had any issues.

It is scalable. It's good for scalability. 

We only have one person that handles the backups. Not every user in the company has access to the solution. We don't intend to add more users.

We use ten Veeams, give or take, currently. However, we might add more in the future.

We use the community edition. The problem I've faced in the community edition is that the community edition always relies on the community to solve a problem. I tend to google answers or ask the community. They seem to have a lot of users and it helps in the sense that there is a lot of information out there. You can typically find an answer to your question.

The solution is very easy to set up and integrate with other solutions. It's not complex at all. The process is extremely straightforward. 

It only takes one person to set up and administer the product. We have one or two people on staff that can handle any Veeam related duties. With jobs and replicas, it is a good practice for both to know the all use cases, to know all the backups and backups replicas. Then they will find it easier to handle and they will better understand the jobs.

I use the community version of the solution. I'm not sure of the licensing costs for the paid version.

We are end-users of the solution and we rely on the community version right now. IN the future, we may use the licensed paid version.

I learned to use the latest update, however, my preference is that I use the second last update. I'm not necessarily on the latest version.

I'd recommend the solution. 

I'd rate it at a seven out of ten.

I have found the backup call feature very good.

I have found that the reporting could improve in its structure.

In an upcoming release, the remote site application, physical workload, and other application integration could improve.

I have been using the solution for approximately four years.

We have experienced some bugs that we reported to the Veeam team and most of the issues have been resolved. For example, we had an issue recovering a file that was 256 characters long which we were testing out. We resolved it by restoring the whole volume.

We are satisfied with the technical support.

We have also worked with Acronis, Commvault, and Veritas.

The initial setup is very simple.

The price of the solution could improve when comparing it to competitors. The market is very competitive and they should have some discounts or special offers.

We have evaluated Commvault and they have a very fantastic rating compared to Veeam Replication. 

I rate Veeam Backup Replication an eight out of ten.

We use this solution to backup and replicate our visualized and physical infrastructure. We use it to take backups on a daily/monthly basis; to take snapshots for disaster recovery; for application-aware processing.

Veeam Backup and Replication is mainly used by our IT team but we have a Veeam Backup Agent deployed on all of our workstations to make backups for end-users. In total, there are roughly 60-65 people using this solution in our company. 

For maintenance, we only require two engineers and a manager.

This solution is very flexible and user-friendly — it's very good. It's very good with our virtual and physical infrastructure.

They need to improve the reporting. There is something called Veeam ONE Reporting — it's a separate module altogether. It's not included in the Veeam Backup and Replication bundle; it has to be purchased separately.

There's a lot of room for improvement surrounding the backup process. Searching through folders is complicated; customization involving backups is lacking. For instance, if I want to backup a particular server and store it in another repository, I have to first define a repository then I have to create a policy. Next, I have to execute the policy. It's not as if I just snap my fingers and it works — no. You need to build it and put that intelligence inside of it in order for it to act intelligently. 

In addition, it should be more flexible when it comes to customizing policies. 

I have been using Veeam Backup & Replication for roughly two years. 

The technical support is very slow — their response time is very slow. 

If I raise a ticket, they should quickly respond. Their first response is very slow; they work on their own sweet time. For instance, four days ago I reached out to technical support with an issue; only last night did they respond — they sent me an email asking me for our logs. The response time is very slow. It took almost four days for them to even respond. After I've uploaded the logs, they'll review them and come back with their findings. In other words, it takes roughly eight to 10 days just to understand the case — that's really bad.

On a scale from one to ten, I would give their support a rating of zero. 

The initial setup was very straightforward; however, the configuration was not straightforward. After it's set up, you then need to build it. Think of it like making a pizza: first, you need to make the dough; then you need the proper ingredients; then you need to preheat the oven to the proper temperature — it's a precise process. 

We pay on an annual basis. We pay roughly $12,000 for our software subscription. 

I would recommend Veeam Backup & Replication to others. Overall, on a scale from one to ten, I would give this solution a rating of eight. The only issue I have is with their technical support; otherwise, it's a great product. 

We chose Veeam because, according to Gartner and multiple reports, it's the number one product for virtualized infrastructure. We got the demo and began a POC on a couple of servers. It was good for performing backups, etc., but it's not about the product. The product is good, it's the service after the sale that you have to look out for. After the sale is complete, the service and support are what matters. This can make or break a product.

Our primary use case of this solution is for application servers, web servers on Linux, Windows, AIX, databases, Db2, Sybase, Oracle and the like. 

I think this solution does VM back ups very well. 

I find this product to be rather weak when it comes to database integration and that really is problematic. It needs to have better integration with the database components as well as the cloud-based services.

I've been using this solution for about a year. 

At the moment, this product is not very stable. 

I think it is horizontally scalable, but not vertically very scalable. It tends to run into issues with regards to performance if you require vertical scalability.

In South Africa, the technical support is average. They should respond more quickly and be more customer friendly. The rep really needs to be more knowledgeable. 

We previously used Veritas. 

The initial setup was quite complex and took us a few months to install. We used a partner and vendor for the installation because we had a lot of problems. As a result, we're not sure if we'll continue with the solution or choose an alternative. 

We chose Veeam because the licensing was cheap and we got a special deal from them. 

I wouldn't really recommend this solution. In terms of the integration of this solution, we're finding it doesn't do everything it promises. There is a difference between what the sales people tell you and the reality. Because of the issues we've had, I rate this solution four out of 10.

We primarily use Veeam Backup and Replication in small installations and projects with Windows as well as standard Linux systems. We also use it as a backup solution for cloud products such as Office 365. In total, we have around 14 Veeam users, which covers about 100-200 devices using it.

Regarding the technical implementation, we have three primary technical personnel that maintain our use of Veeam. Because our company is multinational, with data centers located in Nordic countries such as Finland, we often have conferences outside our country and we share the services used to configure and perform the maintenance of our systems when needed. In this case, I can't point to an exact number of all the technical staff involved with Veeam throughout the greater organization.

Ideally, when it comes to backups, we prefer to use only one solution rather than two. However, we also have customers in the healthcare sector in Portugal who are using legacy UNIX and Oracle systems, and Veeam does not have agents for these operating systems. So when these customers want to create disaster recovery plans, we like to use Commvault to set up replication and create backup copies of the data code.

Veeam is quick, easy to work with, and its support for Microsoft products is good. They also provide adequate solutions for backing up Microsoft applications in the cloud, such as Office 365.

Veeam needs to have more support for non-Windows systems and other databases. For example, I can do SQL with Veeam but not Informix or Oracle. This is unfortunate because we have many partners with Oracle systems and Informix databases, and Veeam does not yet have the agents we need for specific Oracle and UNIX operating systems.

Because we are limited to using Veeam on mainly Microsoft systems, we have to resort to another backup and replication provider, Commvault, to handle these other systems. In general, I think that Veeam needs more improvement in terms of support for other applications and IT systems. It would be much more convenient for us to have all our backups for the different systems covered under one solution only, rather than having to use Veeam alongside other solutions like Commvault.

I have been using Veeam for a couple of years now. 

As far as I've been using it, it has been a stable solution.

With regard to scalability, we don't have any problems in terms of basic Windows systems.

Our local support team for Veeam is composed of four technical members who assist with support across the board. In first line support, there are more support members, but in second line support there are only two to three people who can support our customers. However, the problems are generally so easy that when using Veeam across our data centers, there aren't many support issues that can't be solved quickly.

It took us about five weeks to install Veeam in our environments and to implement it with our various solutions. We did not have much trouble with the initial setup, and it wasn't very difficult to work with.

We have implemented Veeam in-house, as it is very important for us to do it this way when it comes to backups and data replication.

We pay yearly licensing fees for Veeam in our data centers where we're using disaster recovery and replication between our many solutions, especially cloud solutions. From the beginning, we've done our licensing from a separate channel through our data center team in Seattle.

Veeam is a good backup product but it definitely needs more complexity when it comes to supporting different types of systems and applications. That said, it works perfectly for how we use it in our Microsoft solutions and I know we will continue to use it.

I would rate Veeam Backup and Replication a ten out of ten.

We use this solution to back up our two VMware sites, and some physical boxes.

Mainly, it is used for our two VM sites at either campus.

It works with the client. We have it on a clustered SQL which works well.

We have local backups at either site, as well as some backups going to an external storage appliance. It gives us information about what is going on.

We are also using replication.

It has improved the way that our organizations function.

It's fairly easy to manage and set up. 

Once you get it working, it's fairly reliable and fixes itself. It's pretty good at keeping the backups running.

It works well with SharePoint.

The initial setup could be simplified. It takes a bit to find the documentation. 

It takes some time to get through the knowledge base and the changes in the versions over time.

Trying to find everything on how to configure it and set it up can get frustrating in trying to sort it out.

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

I am using version 10.

This solution is stable. Once we have all of the backups working, it never has any issues, except for the server going off, but that is a network issue or during the time that it's self-healing.

It keeps going and keeps running.

It's a scalable solution. I added one. We have a couple of proxies at either campus with one backup server with an enterprise manager on it. It works well.

I am the only person in our organization who is using this solution.

I have used technical support in three or four cases. They were able to help me. They are pretty good. I would rate them a nine out of ten.

We were using Microsoft Data Protection Manager and NetBackup. We decided to go with Veeam after testing it out, as it seemed to work better than the other products we were using.

The initial setup is okay. 

It just took a while to try to sort out what is going on with it.

Review the documentation and their knowledge base on how to set it up and configure it. 

It takes a bit to get it sorted out and to figure it out, but once you get it working it just keeps working.

I would rate Veeam Backup Replication a nine out of ten.