Veeam Data Platform Reviews

This solution is used to backup, restore, and replicate our data.

It's an easy-to-use tool with multiple functions.

The replication is easy.

It provides good findability of the missing documents.

I'm pleased with the ability to search for documents; it's very useful.

There is a lot of documentation available online. The Veeam forum is a great place to start because it contains a great deal of information.

Scalability, as well as licensing costs, need to be improved.

I like the idea of a web-based version or a web console. That is the top priority for us.

We have been using Veeam Backup & Replication for more than five years.

We are working with the latest version.

Some features are missing, such as web-based versions. 

I only have the software on the machine, and I must log in to use the software. There are some features that are missing in terms of stability.

Scalability needs to be improved.

In our organization, I am the only user from the IT department.

I contacted technical support in the middle of last year. There was an issue with our Veeam account that was resolved in a matter of days.

The initial setup is straightforward. 

It is just a small installer. That was all there was to it, we just needed to fill in some options.

The licensing cost needs improvement.

We have a yearly perpetual license. 

I was comparing Veeam to Dell DPS, and I was looking for information on products other than Veeam or Dell but were somewhere in between.

My advice is to determine whether the version they have is the correct one that they require, as Veeam has three different versions. As a result, you must determine which version is appropriate for your organization. That is a mistake that we have made in the past.

I would rate Veeam Backup & Replication an eight out of ten.

It is for backup and replication.

We use it for failover and disaster recovery. There have been times when our primary systems have failed, and we've been able to run virtually until our primary systems are available again. From a business continuity experience, it has worked fairly well.

Replication is most valuable.

The cloud part of it can be improved. There should be an option for Veeam in your own cloud, as compared to the Veeam cloud offering that's currently there. The rest of it is easy. 

I have been using this solution for eight years.

It is stable.

I am not trying to scale it up.

I didn't have any issues with technical support.

We use Zerto for the main part, and Veeam for a little part. We use them for different things. I prefer Zerto because I get a better RTU and RPO. It may be not as easy to set up, but once it is working, the RPO is in a region of 10 seconds. As compared to Veeam, its replication is currently two or three times.

It is of medium complexity.

It is relatively cheap.

I would advise others to use it. It is a good system.

I would rate it an eight out of 10.

We like it due to the fact that we can get error messages to alert us to issues. We can get a forecast for our storage and so on. It's really good.

The initial setup is easy. 

The solution is stable. 

The product is very scalable.

Technical support is helpful and knowledgeable. They respond very fast.

You have several monitors you have to tune. You have several snapshots on the volume and so on, and this is the standard. However, for example, if you have Rezon from VMware, you have much more snapshots on the volume, and yet it's not a problem as Rezon doesn't have these issues with the huge number of snapshots. They should offer more snapshots on Veeam.

The pricing could be reduced. 

When you have to renew the licenses you sometimes have some trouble getting rid of the old one and reassigning it to the new one. That's an aspect that could run smoother and could be better.

We've used the solution for the last eight years.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

The solution scales very well.

You just put in another license key and you can add some hosts. It's that easy.

We have five people that directly use the solution within our company.

Technical support from Veeam is great. You don't want to have an issue, however, if you do, they can help you really fast, and they know what to do and they ask the right questions to get deep into the problem if you have something complex or difficult. They'll help you install a patch so that everything is fine. It's great.

The price always could be lower, however, compared to others, it's pretty much in line with other options on the market.

I haven't really looked into other solutions. I've compared the open-managed integration for vCenter, and that's a really cheap one - however, it's hard to install and you often have issues. I would say it's a small giveaway from Dell as an add-on to the hardware.

We're a customer and an end-user of the solution. 

We have the Veeam plugin from Dell and Veeam ONE. Veeam ONE is in the availability suite we have ordered and we changed our hardware from Dell and for the last five years, we have the open-managed integration.

We're currently on version 11 and we updated the solution in February.

For those considering the solution, I would advise that they deactivate the alarm at first and then run it in a warning mode so that you can learn within the environment. Veeam has some limits, and these limits are often only baselines. You may have other limits as you have faster hosts or you have other storage, et cetera. If you run in warning mode, you can learn and put in the correct baselines. You can tune it and then you won't get so many alerts. Once you have tuned your environment against the Veeam baseline it's really comfortable to work with. 

I'd rate the solution at an 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. 

The solution is primarily used for backups. 

We're a managed service provider and we use it to back up our own stuff. We use it to backup all of our client's data. Obviously, depending on the client, they're very much siloed. We've got multiple backups and multiple instances of Veeam deployed in their particular partitioned-off networks. Those are daily backups. We do full backups and we do incremental backups. Exactly what that schedule depends on the client itself, however, on a daily or a weekly basis, we have the typical things that end users do where they delete files and we have to go recover them. 

We've had catastrophic failures at sites due to our location in Florida. Over the years, hurricanes come through and things happen, and we've had to deploy backups to get clients back up and running.

The most important features of backups are them being able to make sure they're reliable, and that whatever you need to restore you have access to. Veeam offers us that. You can easily restore everything to get the data back in the event of an emergency.

It's a pretty complete product. 

For the most part, it is competitively priced.

Technical support has always been very helpful and responsive. 

Pricing is always an issue. The less it costs, the better for us and our clients. Therefore, if they can lower the costs, that would be ideal for us.

The ease of usability and a learning curve to get up to speed are usually important. If they can continue to streamline and simplify their product, that would help us a lot. During the initial setup especially, there's a bit of a learning curve. 

I've been in the business for 30 plus years and have health with multiple backup solutions, including Veeam, for many, many years. 

The solution is reliable. It's stable. There are no bugs or glitches. It doesn't crash or freeze.

Technical support has been good. We haven't had any issues really. 

There's a learning curve you need to deal with when you are implementing the product. Once you're implementing it and figuring out everything configuring the features, it's okay, however, it's not exactly straightforward.

We go through some training first from our more senior-level people that have already been using it when we train new people, and obviously, that has helped when it comes to implementation. We're finding it's getting easier to cross-train folks.

We're generally able to support it, in terms of maintenance. We've got thousands of users, and therefore, we've got several people on the team at various stages. We have two or three senior guys and then we have several of the mid-tier folks, and obviously, we've got new folks coming on every month that we're cross-training for the entry-level positions.

In terms of pricing, our marketing department handles that. I don't really deal with that area. However, I can say that I would assume that the solution is competitive or else we would not be using the product.

I'd advise those considering the solution to first make sure they take the vendor training and get at least one or two on the team up to speed from people that know the product. Then, use them to cross-train the rest of your staff.

I'm always researching and downloading information, and recently, I was looking at that Cloud Backup Report.

We've looked at other options. They're all pretty similar. With Veeam, the interface seems to be fairly easy to use and the price points are good. I don't know exactly what it is off the top of my head, however, I know that we've had several conversations about it being price competitive.

I've done lots of backups in the past, both onsite offsite, and for DR.

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.

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.