Veeam Data Platform Reviews

The solution is based on the IAF solutions that are specific for moving the data centers that we have to the cloud. This is the main tension for us right now. We are investing in some past solutions, however, we're not using them yet. There are some tests, some small tests, however, we are moving IAF solutions in order to move our data centers.

We like Veeam as it is the kind of backup that has basic snapshots. It's very useful for us as we have a lot of virtual servers. This is the most impressive thing that we see. 

There are some special features from Veeam. They have the replication and the kind of backup that we can use. We have a very strong solution in the network. Due to the fact that we have several internal DMS's, we needed to make a special design. Veeam adapted to that. That's why we choose it. With all the solutions, it was not possible to use the actual network structure that we had. Veeam made it possible.

The solution is stable and the performance is good.

The product can scale. 

For us, it's important that the products can be adapted to different network scenarios. This is the biggest problem. The issues that we had when we selected the products were due to the specifics on the network from a security point of view. Security for us is the most important feature that we need to work with. THey need to ensure that it's possible to secure the network.

The initial setup is complex. 

We use several proxies, reverse proxies, due to our needs. It's not so common. There's not too much information and it's not so useful. They could develop it more and they could market it better. Not many users have this scenario. The reverse proxy, for us, was an important piece to implement. If a user has a good view of the reverse proxying during the implementation, it's better.

The solution has been implemented in the company for about one year at this point. 

The solution is very stable. We needed to buy the biggest server to accommodate it. The requirements were very high. That's why we started late when they decided to use it. However, after we followed the recommendations and followed the certification of equipment servers and storage that we needed, it's okay. Now we find it's very stable.

The scalability is very good. Everybody uses it. In general, we have about 125,000 people using it.

We likely will increase usage in the future. 

We needed some technical support at the start. It was good. Here in Brazil, they are from Brazil and they have helped us too in the design phase. That said, the product is very good. We don't need exactly support for any issue that we found. We've only needed some help for the implementation, the start of the design.

In terms of the implementation, it's still being rolled out. It's very big and there is a very sparse structure that we have. It's global. It will take about two years for it to be completely implemented, due to the places and locations we need to implement it. We need to make and design for each place as it is not standard. That's why it takes a long time. We prefer to take it in parts to be careful with the implementation, in order to see if it's really what we want. Therefore, for us, the setup is quite complex.

The results have been good so far. People are liking it very much. That said, we still have some designs to do for other places that we have implemented.

Due to the implementation, we are doing, there are about 50 people working on the deployment. This is just an estimation. It's quite a large project.

We pay the licensing fees on a yearly basis. There may be a few additional costs, however, I cannot speak to those exactly. Our technical team might have a better idea of what is involved in terms of licensing arrangements. 

We tried the base license, however, it's my understanding that it wasn't enough and we needed a bit more. 

We are a Veeam partner.

In terms of types of deployments used, at this time it's been working more on-premises, however, we have intentions to use the cloud. We are moving several loads to the cloud. 

I would advise new users that the design is the most important piece. There are several options in the ways that you can implement it. My recommendation is to look at the strategy. Networking becomes very important. Having a good design at the outset makes things easier. 

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

Our primary use cases for Veeam Backup & Replication are backing up to the cloud, backing up to a couple of deduplication appliances, and backing up to local disk - compressed to disk.

Veeam Backup & Replication is far more dynamic as far as being able to generate backup jobs. We used to use a product called NetWorker, and at the time the version of NetWorker we had would not back up to the cloud. I think it does now, but we're not using it anymore. But at the time, NetWorker was fairly new and it was just a tape backing up the disc. So Veeam is far better dealing with virtual environments and the cloud as targets. The capability with Veeam is just there.

Veeam Backup & Replication works. It integrates very well with VMware, but not so well with Nutanix, but that's common, I understand. I have both VMware and Nutanix virtual environments and I'm backing up through the same Veeam services. I have proxies running on both environments. Like I said, integration with VMware is excellent with very granular recovery while with the Nutanix environment it is not as intuitive, not as readily available.

In terms of what could be improved, when creating a backup job with Veeam, you can create a daily backup, but it doesn't do it within that job. It does not give you the ability to also set the terms for monthly and/or weekly backups. It has to be a separate job. It gets clunky to manage the timeframes where you don't want a daily to run on this day and creating weeklies. And you don't want a daily to run on this day doing monthlies. That is hard to deal with. It would be really nice if you could do it through a single command line or a single interface.

It is called a father son, or grandfather, type backup structure. The retention periods are not consistent or not available for different retention periods within that job. Retention periods being daily, weekly, monthly.

As for what I would like to see in future releases, just the integration to other virtual environments. In our case, the Nutanix environment is incomplete with the enterprise manager recovery tools part of it. That's where it is incomplete on the Nutanix side as well on the ESX. On the VMware side, the ability to set your retention policy within a job over multiple periods would be really nice if that was doable.

I have been using Veeam Backup & Replication for well over a year, probably 18 months, maybe even close to two years.

The product relies fairly greatly on the implementations of the storage vendors. For example, we were using large storage in AWS and it was using Microsoft. It's the format - ReFS, the recovery, the storage, the dis format, the volume formatting. We had a serious failure and lost six 30 terabyte ReFS volumes in AWS and lost nine 15 terabyte ReFS volumes on our local storage. I was able to recover the local storage in a little over two months. To recover the AWS storage of our volumes we calculated would have taken between six months to a year and probably cost us several tens of thousands of dollars.

So our volumes are still sitting in recoverable AWS in the case where if we actually have to recover something it's doable at significant cost. But we don't use ReFS storage anymore.

I'm not big. We have 200 employees and maybe 50 or 60 or 70 VM's, something like that. We have a data domain appliance that we rent space on that is offsite. We have an extra grade appliance and I have a bunch of CADA disks on a net app for just local storage. If that's scalable, I don't know. My understanding is that I can create more, but everything is local. So I don't have to have remote backup servers. But I understand that with my license I can create remote backup servers, as well.

That sounds like it's pretty straightforward. You link it and you can move backups from one site to another and then recover them off that other site. From what I've read, it sounds amazing, but from what I've done, I've never had to go into any great remote control, remote access or remote sites. So I don't know as far as the scalability goes. It sounds like it can scale up the ying yang. The one thing that I'm aware of though, is that when you're doing the backup, when you're scaling, you wind up with tears, because you have one server backing up a set of VM's, or an environment. And you have another server backing up another environment or another set of VM's.

If you lose one backup server it is able to catalog those backups from another server. I know you can catalog those backups to another server to recover. So it's dynamic. I've had to do that. I've had to build a new server and then recover the catalogs and recover data. It is powerful, it is capable. I like it.

In terms of direct users, it is me and three others that have gotten their fingers into it a little bit by the documentation that I've written on how to do something step by step. But there is really only me managing the system.

We are using this product extensively now. 

From the time that we installed it until now, we had to switch from CPU licenses to what they call UL, Universal Licensing. Because CPU licensing was only available on a VMware infrastructure and when we entered do our Nutanix infrastructure, we had to change the licensing model. There was a small cost to doing that because of the way it's licensed. We have not had to increase our license count yet. I will be shortly implementing another version of the Veeam. I think it's a very simple license, it's the five user license. It's in the VLU, but it's not the enterprise version of it, for our computer science department. They will be managing their backups with Veeam and a technician who I will be training.

That ReFS issue was one of the things that I had with technical support. For the most part they have been very responsive. They have been helpful when it's actually a Veeam issue. With the ReFS thing, they couldn't do anything about that and they referred me to Microsoft, which was a fricking waste of time. I'm so ticked with Microsoft.

We used to use NetWorker for 10 or 12 years.

We made the switch because of the virtualization and cloud access as well as disc storage on the version of NetWorker that we were running. NetWorker requires a physical appliance and the upgrades to NetWorker were cumbersome. The next generation of NetWorker, if we had stayed, would have required a rebuild of our hardware, which we've done once and was a pain in the backside. At that point, I don't think we could have run NetWorker because it wants to go to talk directly to devices and manage devices at a hardware level. So you can't virtualize the connections. So our NetWorker product had to reside on a physical machine.

I don't know if that has changed since we haven't used NetWorker for probably three - four years. We haven't done any upgrades in four years. So the move to Veeam or Commvault, which was the two that we were looking at, was primarily because we had local vendor support for both products. The move to Veeam was well priced, Commvault was out to lunch as far as dollars and cents. We are a fairly small shop and the pricing was just outrageous for Commvault 300 virtual machines. 

Veeam natively lives in a virtual environment. NetWorker couldn't. We also used to use a Norton product. I have forgotten the name of it - it starts with an S.

Those were retired when we started using Veeam. It has been four years since any of those were active, but those were for our remote sites. They only backed up the tape. We didn't explore Backup Exec in a virtual situation. Just didn't even look at it. I don't know if that was a mistake. I don't think so. Like I said Veeam, works really well. I am very pleased.

The documentation to set it up was great. I think we were up and running in about 30 minutes. That was to set up the backup server. Then there is building other services - the proxies, the repository manager, the enterprise manager for managing backups and recoveries. But to set up the backup server itself was super easy.

We just did it in house.

My advice to anyone considering Veeam Backup & Replication, is, like anything, to build a test site - do it on a test environment. Don't mess with your live system right off the bat, play with it, get familiar with it. It took me about about four, five or six weeks before I felt reasonably comfortable and built up in our production environment and the various servers. I started backing up and playing with a couple of Veeams that were smaller, and not backed up to the NetWorker, but I was backing them up and looking at how I could do recoveries. Eventually, I could do a full Veeam recovery and I could move it to another site and recover it, and all that sort of thing. I watched over time how retention worked. During that time I was asking questions of the Veeam technical support, too. They were very responsive.

So do it in a test environment if you don't have any training. I read online documents and went through a free Veeam school online, a bunch of documents, and there were a couple of YouTube type tutorials. I did a lot of that sort of thing as well. But it was all done ad hoc from work, I didn't go and do any formal train. So build the test environment and play.

On a scale of one to ten, I would give Veeam Backup & Replication an eight. It's got room for improvement.

It is for backup and disaster recovery as a service. It is deployed in our data center, and then we sell the service to our customers.

The granular restoration that it provides for a business application is most valuable. For example, for Exchange, we can restore a single mailbox or email. We can also do SQL Server restoration and bare-metal recovery for operating systems. 

Replication features are very useful for customers. They can recover the services and move from one data center to another.

Veeam currently lacks features for backing up to network-attached storage. Veeam Backup & Replication agents do not support S3 storage. Only Veeam Backup & Replication server supports S3 storage. 

We have been using this solution for about five years.

Its stability is good. I would rate it an eight out of 10 in terms of stability.

It scales well. I would rate it an eight out of 10 in terms of scalability.

In our infrastructure, we have hundreds of users. Our customers are from many markets, but its users are from their IT department.

I would rate them an eight out of 10.

It is not complex. It is straightforward. We can deploy it to our customers in about 1 to 2 hours or 1 to 2 days. It depends on a customer's infrastructure.

We deploy it ourselves, and we only use support when we have technical issues with the product. We have three engineers for deployment.

It is very difficult to calculate because it is a backup solution. It is not a business service, which makes it very difficult to calculate the ROI.

We are fine with its pricing policy. 

We provide service for our customers, and the licensing is on a monthly basis. They get licenses, computer resources, and our support. Everything is included in a single price.

I would advise others to test this product before buying it. There are many backup products and services, and they have different features and functionalities. We provide our customers a 30-days trial period to test the product for free, and then they can agree or not agree to use this product.

I would rate it an eight out of 10.

I'm the system admin, and I'm taking care of backups and every job in Veeam Backup. We have the AIX machines and we are deploying the AIX machine; we are doing the backup and trying to restrain the AIX on them.

It's very customer-friendly and user-friendly and we use it mostly to backup an issue. 

We have done a multiple-time restore on Veeam Backup and that is an awesome feature. It's a very critical system, we have to restore it and Veeam makes it easy to do so to protect our system.

Initially setting up the product is easy.

The solution has been quite stable. 

Technical support is good.

It supports the technology and it's actually more secure and has enhanced itself. Veeam is always making itself better in terms of functionality and features.

Part of the issue we've had is with the AIX backup. Currently, Veeam has issued version 2.0 for the AIX machine, however, it is not capable of taking the entire machine backup and restoring at the one side. It is only taking the backup of the partitions only. There is a limitation there right now. I'd suggest they improve the functionality in the Veeam Backup agent so that it will take an entire machine backup. That would be more beneficial for the official system for the AIX's.

The stability for AIX machines could be better.

Veeam Backup also needs to be possible in Azure, so that if something goes down Veeam can take care of everything. Our local vendor in India for the Azure environment has found out there is no availability for Azure for Veeam Backup and Replication. If there is an existing Veeam option that supports the Azure environment, they need to relay the message. It's not clear now and it appears there isn't one.

We'd love to see the solution offer more compression in the future to allow us to save more space. 

It's stable for the ESXi and other Linux and workstations they've established. In the case of the AIX machine that we are using, the stability needs to be improved.

The solution is totally scalable. That said, one thing I didn't get from local resources is that Veeam Backup cannot perform in the Azure environment. 

Technical support is good. It's awesome. Still, we can't get the right solution at the right time. If I'm asking about what ports need to be open for the Veeam Backup and Replication and they are just suggesting the link and just showing the port, it's not quite as helpful as we would hope. For example, what can do we to improve from this side? There needs to be more specificity in terms of the level of technical support we get when we have specific concerns. We would be grateful for this.

The setup process was really easy. I've done it so many times, actually and I am quite comfortable with the steps now. However, in the case of AIX, most users don't know about the AIX deployment. They are not seeing exactly what needs to be done. That part needs to be taken care of by Veeam directly.

I can't speak to the exact pricing, however, in our region, in South Asia, pricing is always a concern.

We tried Commvault also, however, it's not user-friendly and it's not as easy compared to Veeam. They have their own benefit, however, they simply are not user-friendly enough for us. Veeam is easier, and it's reassuring. We've saved money with Veeam as we've had to restore a few times now and we've saved so much data using it. That's why it's good. It's proven itself again and again.

We are customers and end-users of Veeam.

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

We primarily use Veeam as a backup system, so for backup operations. Every company needs to have backups and restoration, and cannot live without it. We have ransomware, system failure, and a lot of problems facing us, so we need backups for the emailing systems, database, Hypervisor, and VMs. 

One of the most valuable features of Veeam is that the restoration is easy and reliable. 

The ease of use could be improved, but I don't have a very deep amount of experience in Veeam, so it's difficult to say what could be improved. 

I have been using Veeam for a couple of years.

This solution is stable, and the restoration of Veeam is easy and reliable. 

A partner or mine has contacted technical support many times. He was very satisfied and recommended their support team. 

I have also tried Veritas Backup Exec, which is more difficult to use. 

It takes about two hours to install and implement this solution and to start backing up data. The operation of backups depends on the customer's data, so the timeframe will depend based on that data. 

For deployment and maintenance, we have one person for administration and restoration and the IT manager for managing the system. 

In my organization, users use it centralized, and it works for the servers and operates silently. No one can pause or refuse the backup operation. We implemented it like this for all customers, so that it backs up to the server and works without user involvement.

We implemented this solution through an in-house team. 

We pay for a license to use this solution, and we recommend that our customers pay for a license and a renewal license. 

I rate Veeam Backup a nine out of ten, and I would recommend it to others. 

The primary use case is backup and replication. This solution is a backup, so it is used on-premises.

From my experience, Veeam is very good. Its interface is user-friendly. We can restore it whenever. It's not complicated. It's very easy to manage and administration is very easy.

Veeam should go for a different version of a hypervisor. For example, they are concentrating on Microsoft Hyper-V and on VMware. There are some virtualizations there, like AHV Nutanix. In that case, they need to rebuild application-wise. I checked with an AHV for my personal knowledge, and I couldn't find the same as in the VMware and Hyper-V. It's totally different. It opens with a different port.

They need to do some repository and improve the backup chain and logs. For example, sometimes we still need to call support for small things, and they're looking for the log. 

In this case, they need to give some training to the administrators. It should be easy. In this case, there are some knowledge bases. If you go to the Veeam site, you will see the knowledge bases, but there should be a little awareness. Administrator awareness should come up for that, like with the small issues and how you want to replicate. When you have some small issues, you should be able to go through it by yourself and solve the issue instead of opening the ticket and waiting for the engineers to troubleshoot.

It was scalable.

Technical support is amazing.

Veeam is totally different from Veritas when it comes to virtualization and virtual machines. For Veritas, we are just using the standalone, physical servers.

Veritas is good for a small environment. We are taking more backups in Veeam only, and we're only taking some backups in Veritas, which is like a physical server.

The cost is expensive. It will depend on how you are managing your environment, your requirements, and if you can easily manage a license. It's not that difficult, so you can manage it, but the cost is high, so you need to check directly with Veeam as well as the local partner so you can get the discount prices.

I would rate this solution 10 out of 10.

We have used this solution to back up our on-premise environment. Currently, we are backing up our VMs VMware.

Veeam Cloud Connect has helped us to reduce the cost of cloud storage for an offsite solution using their archive storage feature. 

The most valuable feature this solution offers us is new and allows us to store data in the cloud and works with Azure and AWS Cloud. This is useful for managing the retention of large volumes of data. 

The continuous backup functionality is useful for us to keep all our data up to date. 

It would be useful if we could integrate our on-premise VM solution with the Azure workload backup from the existing console. This would assist our customers in reducing the cost of hardware. 

It would be good to have the option to store the data directly to Azure, AWS Cloud or any other cloud solutions. 

We would like to have cloud storage set up as a storage solution instead of local storage and have an integrated console for AWS, GCP and Amazon Azure workloads.

I have been using this solution for the last five to six years. 

This is a stable solution for a medium-sized environment. We haven't tried it for a large-scale environment but the solution may not perform as well at a larger scale.

The support offered is very good, however, hey recently introduced a ticketing system that requires us to raise a ticket from their portal site and wait for a response. Calling them directly is not possible. 

We used to use Commvault as our backup solution. We switched because we wanted to avoid having an offsite team and hardware. 

The initial setup is straightforward and very simple. It took three to four hours to set up the environment. 

We have like pooled license and act as a seller. We pay approximately $800 per month. There are no additional costs from Veeam directly but the solution does require cloud storage that needs to be paid for. 

It's an excellent product that is simple and easy to setup. If you have a medium-sized environment and infrastructure, this is a good solution. There is an option of a 30-day trial to test all the features the solution offers.

We are a technology company running our own data center and we have been using Veeam Backup and Replication for the past six or seven years out of the 18 years that we've been in business. Our staff comprises six other employees other than myself and we manage the data center by ourselves with our development team.

We use Veeam Backup and Replication for performing VM replications and backups for our 20-30 servers in the data center. Specifically, we use it for our VMware and HyperV server hypervisors, and (partly) with our Oracle OEM server. We also use Veeam for AD backups, which has been a very successful experience.

In all, we have around 700 end users with Veeam, of which about 500 are branch users and 200 are customers.

Some time ago, we lost some of the groups within our AD Organizational Units, but through Veeam we were able to successfully recover all the data thanks to Veeam's AD backup functionality.

One of the best things about Veeam is that they have consistently improved on themselves since they started. Personally, I've been using Veeam since around 2013/2014 when it was only supporting certain hypervisors such as HyperV, and since then it has become truly mature enterprise-level software with a lot of versatility. Despite that it's now an enterprise product, it's still user-friendly and easy to approach.

If they could add more support for all of the modern hypervisors, that would make Veeam much better and more flexible to work with. For example, there is no solution for VM to VM replication when it comes to Oracle OEM servers. Instead, we have had to implement Oracle Data Guard and some other syncing procedures for our replication of VMs with Oracle OEM.

On a separate note, I also think that they could add more functionality when it comes to real-time replications. 

I've been using Veeam Backup and Replication for about seven years now.

Its scalability is good. I've been testing Veeam since around 2013 and they have constantly expanded their features, improving day by day. Our management particularly likes this about Veeam, and we are hoping Veeam will keep working to add more hypervisor support, such as for Oracle OEM. That would make it really easy for us to scale up our usage of Veeam even further.

Veeam's technical support is very good. I also like that we have public learning resources such as live session webinars. Their support staff are very well trained and we really appreciate their effort. The way they train and assist, even a layman can understand.

Setup is very simple. It's not a complex interface. A layman can understand it in two to three days if they have a good trainer.

I'm the senior architect and system admin managing all the servers (physical and virtual) in the data center. When it comes to implementations, I have another manager beside me, along with five other junior staff.

I implemented Veeam myself in one day, and added all the infrastructure with HyperV and VMware to our repository. We have almost 200 VMs for different applications and we implemented those in two days. Most implementations take just a few hours.

Although our license includes support, we have only really used the support when we were using Veeam for Active Directory. The rest of the time, we find Veeam easy enough to use without paying extra support fees. We are technology-aware people and experienced with this kind of technology, so we opted for the perpetual license. We mainly go with perpetual licensing with our various vendors (including hardware vendors) such as VMware, NetBackup, and so on.

Veeam Backup and Replication literally saved our business. We have already had two or three disasters over 50+ VM servers, and twice when we crashed the main servers, Veeam enabled a fully successful disaster recovery.

Overall, its ease of use largely depends on who is using it. If the user is a layman or non-technical person, we have to teach them from scratch. But if they are tech-savvy, there's not much to it. 

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

We are using the latest update at the moment. 

We use the solution to do backups and replication between sites, in addition to restores. We employ it solely for its basic functions.

The restore capabilities are the most valuable features.

Veeam Backup & Replication should include a cloud solution. 

The cost should also be adressed. This would bring up my rating from a seven to a ten out of ten. 

We have been using Veeam Backup & Replication for eight to 10 years.

The solution is stable and reliable.

The solution is easy to scale. 

We have yet to make need of technical support, although I feel it to be good. 

I believe the initial setup to have been straightforward, although I cannot say this with certainty, as I was not involved in it. 

While I don't know the exact parameters of the maintenance, I do know that all of our support needs in this respect are covered. 

Maintenance is handled by a third party. We do not have a separate team for handling this. 

While I do not know how much the product cost, as I was not involved in this sphere, I do know that this could be better. 

There are probably just three to five of us using the solution, solely in the IT department. 

I would recommend the solution to others for its ease-of-use. 

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

It's generally used by colleges, universities, and healthcare. I support a very, very small amount of healthcare. I support state and local government - such as towns, counties, and police departments. It's used in the public sector.

It's streamlined the backup and recovery for my customers in the sense that it has an easy management console that's easy to set up any type of instant recovery. 

It also has helped them as it plugs into just about any cloud. They can not only have backup and recovery but have a disaster recovery plan as well. It really just takes the heavy burden of backup and recovery disaster recovery off of customers and streamlines it.

I like that it's agent-less. That's very important to customers. 

The biggest positive aspect is the fact that Veeam is relatively hardware-agnostic in regards to what you target Veeam on. This makes it, in the public sector space, very affordable for customers to get into and to have a really good backup and recovery solution. They can choose what type of target they're going to couple the Veeam software with and they can ensure it will be within their budget.

The initial setup is simple. 

I find the product very scalable.

The stability is good.

Technical support is great.

The licensing models, from a reseller's perspective, could be better. Veeam has changed its licensing models. It'd be nice to have some sort of cheat sheet as we are getting tripped up on the new licensing models. 

Although to Veeam, it probably seems easy for them to understand the licensing models, as a reseller of many different products, we're finding ourselves getting tripped up on just the licensing models. 

Any type of cheat sheet to help partners understand the licensing a little bit better, so we can have a quick reference guide when we're on the phone talking to customers would help us a lot. 

To someone like myself who covers VMware, Veeam, Dell, HP, and a wide set of products, anything to make my life easier to kind of solve the problem for the customer and close the deal and not have any unanswered questions, which are usually around how it's licensed and how it's priced, would help us sell more of their product.

I've been dealing with the solution for at least five years. 

It's very stable. From a post-sales perspective, I have not had any customers complain about Veeam or anything being unstable about it. I do come across customers every once in a while that just don't like Veeam. I do not know why. It's usually someone within the organization that's not on the call. I just had a school district in Colorado. They said his director does not like Veeam. I couldn't get any real answers as to why, however, everyone has opinions, and it's not related to stability. I'm very confident in selling Veeam. 

That said, I do come across customers that have had bad experiences. However, I can't elaborate on that, unfortunately.

It's extremely scalable. It's very flexible. I feel very confident about the scalability. There are no questions about that. You add more licensing, you can add more drives to whatever appliance that you have on-site. It's very, very scalable.

A lot of my customers, more and more customers, have Veeam. What I anticipate seeing is that a lot of people are going to need to expand their Veeam licensing and renew their support on the Veeam licensing. That's where I see growth. Almost definitely, every account that I come across has some level of backup and recovery in place. 

I've found the technical support to be excellent. The folks that I work with that support our partners are great.

I would say the majority of the customers are using Veeam or Barracuda. In some cases, customers use Unitrends. However, a lot of them, my customers, are using Veeam.

Barracuda's pricing is through the roof. They have not stayed competitive. Customers really frown upon their pricing immediately. 

Unitrends does not have the mind share of many customers. Many have not heard of Unitrends. In the public sector, traditionally school systems and so forth, use the Barracuda. A lot of that is in the public sector. Unitrends is a little bit harder to sell as it's a new product. Also, from a partner perspective, they are much harder to navigate as far as getting pricing and the account manager wants to talk to you. It seems like they get caught up in the procedures of selling it. Whereas, Veeam streamlines that whole process for us and really makes it easy to sell.

The implementation is very straightforward. 

Deployment is circumstantial depending upon how large the customer's environment is. My company has a services team that can put together a statement of work to help with any type of setup, installation, or migration to services. In some cases in larger accounts, we'll bring in our services person to go on-site and help them install, implement, and set up Veeam. That's all part of the solution portfolio that we support.

You only need one person for deployment and maintenance, even in the larger accounts. Based on everything that I support, installing Veeam is probably one of the easiest deployments that are out there. We only deal with under 1,000 users. Some of the colleges get a little bit big. However, I'm not in the enterprise space. I'm in the public sector. We do have some large cities from time to time. Most of the deployments that I do are usually under 1,000 and are very small counties and so forth.

We can help our clients set up the solution.

The Veeam engineers have actually helped a customer install it on-site as well. There was a gentleman from the Veeam engineering team that called him on his cell phone and they had it installed within five minutes. It was phenomenal support.

The return on investment is the protection of the client's data center. It's hard to tie a dollar amount to that.

Veeam's pricing typically is extremely competitive. Rarely do we see it higher than the competitors'. With their new licensing model that they have put into place, they have really made it extremely affordable for a lot of my small towns who have to go to the town hall or police departments and request money. You've got the chief basically running the IT and running the police department. They look at things differently as they're not IT people necessarily that we're working with. Therefore, when they see pricing on technologies, it's even harder for them to justify the spend. However, Veeam has done a really good job at really staying competitive. I would say that they're definitely the strongest from a pricing perspective.

In terms of extra costs above licensing, if someone decides to use the cloud, that would be considered an operational cost. Then, of course, whoever the IT staff is, there's got to be some level of maintenance and provisioning and configuring and so forth of users. There's the head count too that goes with supporting Veeam.

I'm a reseller.

We tend to deal with the most recent version of the product.

Clients should understand how to configure it and how to set it up. That's kind of where my expertise would come in is configuring the hardware that the Veeam is going to reside on.

I'd rate the solution at a ten out of ten based on the overall support, the professionalism. From my perspective, Veeam does everything. They're my number one product. I tell my guys over at Veeam that support me, they are the best. They're always there to support me and get back to me. It's a great company.