BDRSuite Backup & Replication Reviews

Our primary use case is for VM backups.

We were using an older version and just upgraded two weeks ago.

The virtual machine backup is important for stability and scalability since our servers are on virtual machines. 

Another good thing is that it has cloud backup.

There are bugs. For one month, I encountered a big issue where my storage pool could not be identified. My backups were stopped because they were not able to locate the storage pool. So, I removed the settings and started the backups again. The application is not stable. It needs some debugging and testing on the build side of production.

We use Vembu with Microsoft Hyper-V. While the installation is not a problem, there is a problem with the operation side of things. It should be automated. There is something wrong with the structure affecting the product because the backup should not be disturbed. We found without any changes to the network structure then the backups would be affected and I could not fix it by myself. I did not contact support for this, as it was probably due to the new update, but I am unsure. Now, I am monitoring this issue.

Six months.

Its application stability needs improvement. I have seen issues recently with it. Backups must have a very stable application. If your backup system is crashing, that means you cannot trust it.

The scalability is good. It can scale. Adding a new server to a foreign location is easy.

We have nine locations. We do have plans to increase usage of the solution. 

The IT department has five people who are administrators. One person configures the backups and others monitor the backups.

The technical support is good.

This BDR is the first proper solution that we are using. We previously used manual backups.

Initially, we had some problems when we tried to do the setup ourselves, but then the support helped us. They had a direct session with me and helped me with the installation. After that, it was fine.

The deployment is easy and fast. A location can be deployed in a day.

For each version, we have a dedicated BDR server and local storage. I schedule the backups. From there, we upload to the cloud storage. Therefore, each location will have their own BDR that will back up to the cloud.

The initial deployment to the cloud is important because once the backups are into operations making changes is not that flexible.

This solution helped us deliver an enterprise level data protection solution and reduced our budget by 50 percent. We spent $3,000 on Vembu's licenses where other solutions were almost double.

The competitor for Vembu is Veeam, who is very popular and famous. Vembu is good, but still has a long way to go. We found Vembu BDR to be more affordable.

Veeam is good for very high-end servers.

Right now, we are satisfied with Vembu's operational performance and requirements. It is just a simple backup solution where we can backup all of our VMs.

Vembu allows you to implement a variety of different requirements.

I would rate the product as a six (out of 10). It needs some more work to be done in regards to product stability and functionality.

We use it for backing up physical Windows Servers and one hypervisor server. The main draw for us was the ability to back up hypervisors, Hyper-V, specifically.

Overall, it's unattended, so we don't have to manage it. Once it's set up, we get notifications of a failed or successful backup every night, or for whatever schedule we have it set on.

We've had a couple of instances where an employee might have accidentally deleted a file, a network file, and one of the servers that we back up is that file server, and we have been able, with no problem at all, to quickly log into the web-based interface and restore files again in a matter of minutes; just individual files from any specific backup. That's an example of what we've been doing with them.

The most important feature, in terms of the hypervisor, is the ability to restore a virtual machine in a matter of minutes. We can take the backup of a virtual machine and we can restore it to the actual Vembu Backup server as a temporary solution, in a matter of minutes. We can just spin up a VM in no time; different hardware, even different processors. It's pretty dynamic in that sense.

The file restoration comes in a close second, but the biggest deal was to be able to restore virtual machines, very quickly and easily.

Since we got it up and running it has been unattended. I got the schedule set up and I got the integration Service Packs sent out to all the servers, and I have not touched it since July. It's pretty stable.

Once you have all your servers in the Vembu BDR software, and they're being monitored and backed up, it's very stable. As I said, it has been three months and I've not even looked at it. I get those emails about a successful or a failed backup, and I've not even had a failed backup yet.

Scalability depends on your resources internally. It all depends on the hardware you're backing it up to, the amount of RAM and storage space that you have. So scalability is subjective.

As long as you can scale internally, it can scale with you. All you have to do, on their end, is purchase more licenses for whatever server you're going to be backing up. Right now I have eight physical servers and one hypervisor with two processors. That's how the licensing works for me. If I were to add another server, I would just purchase another license. So it's easily scalable.

The tech support is the one thing - that is not a system issue - but which is a little bit difficult to work with. They've been great when I get them on the phone, but they work in different time zones. We're in Mountain Standard Time in America and the tech support works out of India, and something like 9:00 pm here is 9:00 am for them. So every tech support issue that I've had to contact them on has always been late and night. It's not a game-changer, but it's definitely not the best solution.

The customer support has been great when we get together. They have a weird way of doing it where they'll do a TeamViewer session with you and have you leave the TeamViewer session running until they remote in. I'm not comfortable with that, so I've always been on the line with them. As far as interacting with customer support, it's been great, it's just getting together with them at a specific time that is an issue.

We bounced around between file-based backups with CrashPlan and we also used the Veeam physical server backup, the free edition. And we dabbled with the Veeam hypervisor backup as well.

The main reason we switched was the affordability of it as well as the ability to back up and restore hypervisors in a matter of minutes. And the ease of use was also a factor. It seems much less cumbersome than some other applications I've used. It just does the job and it's something that we don't have to worry about. Once it's set up and working, it's just working.

It was very easy to deploy. I had no problem at all. I had no problem in deploying the actual BDR software, and then I had no problem pushing out the integration service to the servers that I was going to back up. It went very smoothly.

We have not used it long enough for me to be able to tell you our ROI.

The product's pricing is of good value. It was much more affordable than the alternative solution to it, which was Veeam. That would be the closest competitor, and between those two, Vembu was much more affordable. It seemed reasonable for what we needed to do.

If all you're backing up is physical servers, there are probably better solutions or solutions out there that are probably less expensive. But to get everything under one umbrella, especially with the hypervisors, if you have any kind of virtual environment, this is the way to go, as far as I'm concerned.

One that we evaluated was the Veeam Backup software solution. That's very popular for virtual machines, specifically, hypervisors, Hyper-V and VMware. In that box, there's a one-footer. We evaluated Veeam and we evaluated CrashPlan for a time, and we also dabbled in something called Five9 software. It's a virtual machine management platform that, as a side job, does backups for your virtual machines. We only dabbled with that for just a little bit. We just checked it out. It was nothing that we were actually considering.

Plan accordingly. Know exactly what you're backing up, not even considering the licenses - the licenses are the easy part. Just know what you're backing up and what you're going to need to restore in the event of an outage, because if you don't have the hardware to support five virtual machines that you need to restore, you're out of luck. Plan for space and for resources to restore your virtual machines too, in the event of an outage.

We've used it in production now for about three months. There was some testing and playing with it prior to that. I know that there are plenty of improvements that they're working on. None of them really reflect the kind of work environment that we have here, so as of right now, it does exactly what we need it to do.

Overall, I would rate Vembu Backup at nine out of ten and that's only because of the tech support. As I said, that's specific to me. Somebody in India wouldn't have that same problem. Or somebody in a different time zone or who has a different work schedule, it wouldn't be a problem. But for me, the only deficiency would be that tech support time-zone issue. But other than that, it's been easy to deploy, easy to manage. I don't have any problems with it so far.

We use the solution for the backup and recovery of our VMware data.

BDRSuite's data protection policy is excellent. A trusted source recommended the solution to me, and I have confidence that my organization is in capable hands by using it.

It is important that BDRSuite provides multiple restore points for recovery data in a more granular manner. For instance, if we identify an injection in our file by examining our log for the relevant time frame, we can restore our system and import our data to a different aspect. Therefore, it is crucial for the engineers to understand how to use the backup system, as restoring the data guarantees that there is no malware present.

The incremental backup process works perfectly because the backup system checks file access, which helps us maintain a smaller disk size.

BDRSuite has improved our organization by ensuring our data is secure during a disaster.

Backup of the VMware server is the most valuable feature.

The instructions are hard to follow and could be simplified.

Scheduling backups is challenging due to the poor quality of the UI. I would rate the UI a three out of ten, as it has significant room for improvement. The graphical interface, including its design, icons, layout, colors, and fonts, is not comparable to Google's. In my opinion, the design is the most significant feature that needs improvement.

The price has room for improvement.

The 15-day trial period for BDRSuite is insufficient to fully experience the solution and make an informed decision about its use.

I have been using the solution for four months.

The solution is stable.

We can scale by adding additional licenses. 

Our server handles up to 10 million users.

The individual with whom I have been in contact is competent, but the support team responsible for reading emails is inadequate. They are unable to comprehend the problem and as a result, there is a lot of unnecessary communication back and forth, which is a waste of time.

Negative

Previously, I employed BASH Programming to export all the data daily, and I synchronized it on a server using a daily cron job to back up the system. However, BDRSuite is a more convenient option since it enables us to restore files at the file level. We can simply open the backup, choose the desired file, and send it to the server.

The initial setup should be more user-friendly. 

The implementation was completed in-house.

The license is per unit and is expensive.

I give the solution a five out of ten because I have not had to deal with a disaster situation yet.

To ensure the security of their data, individuals using BDRSuite should obtain certification. Although I have not personally verified this, a friend of mine used BDRSuite for their data center and found it to be secure. BDRSuite is a competitor of Zoho which is comparable to Google in terms of functionality. However, some users may find issues with the user interface and design, particularly those who prioritize aesthetics and ease of use. While technical users like myself will have no issues, others may find BDRSuite to be somewhat complicated upon examination.

I have approximately 50 clients for whom I provide backup services using Vembu software.

I don't have a virtual environment.

I use the encryption, and I think my clients feel secure knowing that.

I have a couple of examples where I was able to restore a client's data on the spot. This definitely was a success for me, where my client saw how the solution actually works in cases where they would need to retrieve their data when a failure happens. It doesn't happen very often, but it has happened a couple of times.

The only things that I use it for are file backup and SQL backup. I don't do much beyond that. It is pretty much straight file backups and restores. What I like about these features are the ease of installation and automatic scheduling. I do like the email feature where I am able to email the client and myself directly after each backup whether it's been successful, partially backed up, or failed.

I am very pleased with the compression, especially with some of the larger SQL databases that need backup. The amount of compression is impressive.

The reporting can use some improvement. I still use the old StoreGrid Cloud while I'm migrating the rest of my clients over. I am able to export all of my clients' usage for the month, which I then import into my billing program. It helps me speed up the billing process. Also, I can generate a report that gives me statuses of everyone's backup, which I don't get from Vembu Backup Online either. I would like to have something similar where I can export everyone's usage at any time for all their backups, so I can use that to import them to my billing program. 

I would also like to be able to have a report where I can check the status of everyone's backup. Right now, I have it programmed to where I get an email for every backup sent to me. Then, I read those emails and chart them on an Excel spreadsheet separately: success, failure, etc. I keep a weekly log of that. If I had a report, it would make this process a lot easier.

I used to be able to manage the amount of space allocated to each client. Right now, I can't. I have to send in a request if I want to add space to this one or create space for another.

I like the stability. I have been pleased with it.

I have had some things that I've contacted technical support about and they have corrected them. I was surprised because I was running across multiple problems frequently. It's been pretty good lately, but the problem was with the cloud.

It is very simple to add new backups.

I am the only person using it in my company.

I have about 50 clients that have on average about one to two backups. There are almost 100 individual backup schedules which are running.

I support an environment of approximately five to seven terabytes.

I would like to add more clients going forward.

I am very pleased with Vembu's technical support.

I have asked Vembu technical support how to handle the following scenario and haven't gotten a good answer:

I have a couple of clients who are pretty large (a couple of terabytes). If I ever had to restore that, it would take quite a long time. I would like some suggestions on where to maybe physically backup on their location. Then, am I sending that up to the cloud? If I were to restore, could I restore right from their location locally? Since that would be much quicker.

This was my first backup solution.

The initial setup is straightforward: Creating a client and logging into that client on their workstation, then being able to download the software to that machine and setting it up whether it's a regular file backup or SQL. This has become very simple for me after doing it so many times.

The initial setup does not take very long. The only thing is that it is taking me a while to migrate my clients from StoreGrid Cloud over to Online Backup because of access to my clients. Once I get in, the actual setup probably takes me 20 minutes to a half an hour per client.

The implementation is pretty much the same for a lot of my clients because they are from the same type of industry. I have a lot of dentists. I'm pretty familiar with the software that they use. I know when I go in there what to expect and what I should be backing up.

I have a gentleman who gives the IT support to a lot of dentists in my area. As he goes to the different locations where he might either be replacing a server there, or if it's a new client of his, then he'll contact me and I will remote in. I will install the backup software on their server, and we set it up that way for the most part.

I have seen ROI with Vembu.

The pricing is reasonable. I am okay with it.

I did look at other backup solutions as well. I don't remember who they are.

It is an easy solution as far as its installation, scalability, and dependability. I have a regular full-time job as well as doing this. I can count on this solution working properly, and it allows me to be able to have another side income without a whole lot of hands-on everyday maintenance to it.

I have not used Vembu with Microsoft Hyper-V.

We are using it for the backup of our VMs and restoration activity. We are deploying some new technologies for which we would be able to use the features of Vembu.

It has been very helpful for data backup and restoration and license management. License management and everything else works smoothly, which is very useful for us.

Its restores are nice and reliable. They are fast and smooth. As compared to other tools, they are 80% faster. The speed of the restores also depends on my network. We have less than 10 gigs of speed.

It provides multiple options to recover data during hardware failures or accidental deletion of files. They have many options to restore the data. We tested them during the DR last December. Having multiple ways to restore the service and data is very useful.

Its download VM feature is useful in migrating physical machines to our VMware environment. There were no challenges in doing that through the GUI. It was user-friendly.

The ability to map a drive and restore a separate file is most valuable. The restoration activity is good.

The data integrity check features are useful during the restoration activity. At the time of restoration, we are also checking the DR plan.

We haven't yet checked its compatibility with the new technologies in the market, such as Nutanix. It would be good if any new technology can also accommodate Vembu.

They need to improve their marketing because not many people are aware of it. People ask me what is Vembu, and I have to explain to them it is a good tool for backup and other things. 

I have been using this solution for more than three years.

Its stability is good. Its reliability is good when we have VMware and Linux VMs. It works smoothly.

Its scalability is dependent on the number of licenses that you purchase. Currently, we have 10 to 15 engineers and project managers who use this solution.

It is being used extensively. We are using only Vembu for the backup part. So, our core data depends on this solution. We have around 20 VMs, and we are taking backups of almost 100 GB of file server data. We might increase its usage in the future. Some of the people approached us to go for a new tool, but I explained to them the features that it offers. We don't have any plans to move to another solution.

Vembu team is giving excellent support to us. They provide 24/7 support. We can reach out to them at any point in time. They are able to address and give proper support for our queries. I would rate them a 10 out of 10.

My organization was using another solution previously. I have used Symantec backup and other tools in my previous organization. All these tools are more or less the same.

It was already installed when I joined this organization.

We have seen an ROI in terms of reliability. When we invest in a backup solution for infrastructure backup, it should work at critical times. With Vembu, I am able to restore data quickly without any issues.

Its price is reasonable as compared to other solutions. There are no additional costs.

While increasing the count on the server-side, we have to take care of managing or optimizing the license.

We have not used Vembu's instant boot VM feature for instant access to our VMs or physical machines after a crash. We have also not used Vembu for the backup for Microsoft 365, Google Workspace, or AWS.

I would rate Vembu BDR Suite a 10 out of 10. It is a good tool for backup, replication, and restoration. Everything is good in this solution.

Our daily scheduled backups are only with Vembu. We are using the disk based solution only.

We are a business school.

We have restored with the full backup. It was completely fine using Quick VM Recovery. The time frame depends on the size of the server, e.g., if it is 100 GB, then it will take an hour. Restoring would not be possible without Vembu.

Because all our servers are hosted on VMware, the VMware backup is the most valuable feature. The integration and backup with VMware are very good. 

The compression is fine because it is compressing the full backup files. For example, if our full backup is 100 GB, then it can be reduced down between 40 GB to 80 GB.

There are some limitation in Vembu that can be improved. When you take the backup from any server, the full incremental backup is limited. For example, if you run a weekly full backup and monthly backup, they cannot be run at the same time. I should not have to create a new job, but in this scenario, I am creating two jobs. The limitation is created because if I select monthly backup, then I cannot select weekly backup.

We have only been working with Vembu for a few months.

The performance is good. There are no issues with performance.

Backups are run at night, then we check them in the morning. We don't do active maintenance.

If we have multiple jobs running at the same time, then the performance will be reduced, e.g., if you run four or five jobs at once. If only one job is running, then the solution can be very fast.  

It is deployed across our entire network, but we have a very small environment.

Their technical support is good and helpful. Their response time is as we expect it to be. If I raise a case, they will come back to me within half an hour to an hour at maximum.

Previously, we used Veeam Backup, but we replaced it with Vembu. We switched because Vembu is more cost-effective. So, price was a factor.

The initial setup is straightforward and doesn't take much time.

It takes two people to deploy it, e.g., a backup admin and I deployed it.

This solution has help us deliver an enterprise level data protection solution and reduced budgets.

With our manual backups, we can combine two or three jobs into one, taking three hours. We are reducing our time spent on backups by approximately two-thirds.

One month ago, we subscribed for one year.

At another organization, I have worked with Dell EMC NetWorker and Commvault (about two or three years ago). Dell EMC NetWorker can do the weekly and monthly backups that Vembu cannot.

We are not using the deduplication feature. I am not 100 percent sure how the deduplication works on Vembu.

I would rate this solution as a seven out of 10. The product is good, but they need to resolve the multiple policies issue that is currently restricting us on the server.

We're deploying it to support the backup of some on-premise VMware vSphere workloads.

Vembu has been a great benefit to us and it's been very positive. I would definitely say it's been a good thing.

We're using some very specific components of it like the on-prem backup to back up some separate systems for DR.

The restores have been reliable. We went through testing validation and we haven't had any issues.

We just started to use Vembu's Data Integrity Check. We need to validate the backups to see that they're able to be restored. This feature is pretty important. It's a big deal.

The restores have performed very well but our infrastructure is highly connected. Our infrastructure is the way it was before. We have a 10-gigabit infrastructure. So the performance of our backups has occurred the same as it did before, and it's been very good. We haven't noticed any difference between what we were doing before and with Vembu now.

It's important to us that Vembu provides multiple options to recover data during hardware failures or accidental deletion of files. But it's not critical because we back up the entire environment. So if we had a problem, we pull back the entire system. There's only a couple of instances where we pull back individual files. Being able to recover the entire virtual machine is the most important piece.

We used the Instant Boot VM feature for instant access to our VMs when we did the testing, but it's not necessarily something that I think is going to be an absolute requirement for us. It would be important if we lost everything

We do a lot of internal automation, so the Vembu API definitely has some gaps. The Vembu API could definitely use some improvement. We do rely a lot on automation outside of just the regular interface. We've noticed that the Vembu GUI is good, but we do leverage the APIs for a lot of stuff, and there's definitely some room for improvement there.

When it comes to the GUI, it could use some UI modifications to make it a little bit easier to navigate, filter, and sort information.

We just made the purchase. We just went through the evaluation and we purchased it in the last two months.

So far, it has been very stable for us. We haven't had any problems.

We're not a big shop. We don't scale to thousands and thousands of workloads, but it's scaled very well for the things that we've needed to do.

We're 100% into Vembu right now. I don't know that we'll be looking to do anything more. That all depends on what the infrastructure requires of us, but right now it's working very well. I don't think we're going to scale out and do Hyper-V, Office 365, or any of that stuff, at least not right now. If that does become a need, we'll be using Vembu for that because we know it can do that kind of work, but right now that's not in scope for us.

We have a little over 150-some odd workloads, virtual machines, and we have six hosts. Spread across six hosts, we have 150 workloads. It's not a big environment.

Technical support was very good. We engaged them. They did respond very quickly. We were able to get them in and work through the issues that were there. They did have to go back to the team a couple of times to get some answers for us, but it was certainly no more than one business day between them going back, figuring out what's going on, and getting back with us. They were very good.

We did use another solution but it was for the exact same kind of thing that we're using Vembu for.

It worked fine for a while but the updates weren't happening on a regular basis and the product wasn't moving forward the way that we wanted it to. Vembu has a lot more time under its belt in terms of development and whatnot. It turned out to be a much better solution for us.

The initial setup was very straightforward.

Vembu has two options for deployment, Windows or Linux, and so we had looked at both options. Both options for setup and configuration were pretty straightforward. There were some bugs that needed to be worked out, so we had to engage the Vembu support team. That team engaged very quickly and worked diligently to get the issues resolved. There were two or three things that needed to be addressed. Ultimately, we chose to go down the path of Windows deployment for Vembu, not necessarily because there were problems with the Linux platform, but because the Windows platform seemed to work better for us for some of the automation that we're doing. Overall, it was very good. 

The initial proof of concept to deployment was about a two-month venture for us. It was not very long.

Three people were required for the deployment. We're all engineers and I have the decision-making ability.

We have seen ROI. The real return is when something bad happens. All the proof of concept work that we did, all the testing we did, it all panned out for us. We're already seeing a return on that.

They do have a pretty good breakdown online. Their product detail and data sheets and all that kind of stuff listed out pretty well what it does. So we knew right away that it was going to probably align with what we needed to do. It was pretty easy for us to understand how well it was going to be aligned.

I think it's priced well. Obviously, we're happy with the pricing.

There were a number of different technologies we looked at. They were all the same basic feature functionality that we were looking for. In some cases, it was the price. A couple of the products that we were looking at are more than twice the cost of Vembu. We're not a big environment so to pay twice the amount of money for effectively the same solution just didn't make a lot of sense for us. There are some less expensive solutions too but they didn't offer some of the automation that we needed. They didn't offer an API. They didn't offer as easy a path to getting into Vembu as Vembu offered. Vembu wasn't the least expensive and they weren't the most expensive, but it did align with what we needed. And a lot of what we needed was VMware and vSphere backups, automation, those kinds of things, and we felt that Vembu was the way to go.

We do have a tight budget. We're not a big shop or environment. It was very affordable. The cost was a big deal but it was very affordable for us.

Look at it to align it with what you need it to do. See if it is well aligned with the way your infrastructure operates and the needs that you have with what Vembu can offer. Obviously price and budget are concerns, but I think that initially, it has to meet your needs. You're not going to go out and buy something that only gives you half of what you need. It's really all about evaluating the business needs first.

I would rate Vembu an eight out of ten.

We are using the Enterprise version for backup. With the license that we have now, I'm using the NetworkBackup application. This includes having email backup with MS Exchange Server, which is very helpful because we can restore by mailbox or mail. We don't have to restore the entire server.

We also have FAS, Windows Subsystem for Linux, and MySQL databases. It is very easy to use with them.

I have some virtual machines. I use an VMware ESXi server to back them up.

I have a strategy in the company where everyone needs to bring all their important files on the server. People should not be keeping their folders on their computer because of two types of situations:

1. In the last two months, there were situations where the local hard drive failed, people were very happy to have their files on the server. 
2. There have been three times where people modified the file, then asked me if it's possible to get back the file that they had before, so I used the backup. 

I just started backing up to virtual machines. They are very good if something happens. I can restore to another site. There are a lot of options to restore with virtual machines, such as, mounting on another server to open mount locally and extracting some files. I was very surprised because it seems like we have a lot of options. 

I was very happy seeing that the incremental backup was very nice because the modified files are taken from the number of times it was modified. Thus, if I have a file I modified two years ago, I don't back it up each time.

It backs up from the latest version. I can write there that I need the last three modified images of the file. One image could be from a year ago, another one or two days ago, and the third from three years ago. It does not delete by date.

It is easy to use. There is an offsite DR solution where I can keep an offsite copy of the backups. 

The transfer is encrypted. I checked the storage pool's compression and not a lot of space was used. I was expecting more, which is why I think the compression is good.

I saw that it's not possible to have the last full backup duplicated on our site. Therefore, if I have a lot of information on the main site, I would not want to copy any information to those site servers. It would be nice to be able to make a copy of the last full backup. 

I have sent a lot of missed scheduled emails, but maybe I'm doing something wrong. I will try contacting support to see what I can do better. 

I started two months ago. 

Nothing has happened other than expected until now. We have had no errors.

A system administrator and I are doing deployment and maintenance. He checks the tasks every day.

It's 100 percent scalable because we can add as many servers as we want. 

Their support is great. I think they work 24 hours a day. I get a very quick turnaround time from them no matter the day or time that I send them an email.

A long time ago, I used Symantec Backup. I cannot compare the two solutions.

I was trying to find a backup solution two months ago. I googled for the best backup solution vendors in 2020. I saw Vembu. It was listed as very easy to use and cheap for what it's doing, as a platform. I started a trial (pilot). When I checked the license prices, it was free which was in my budget. I was really happy to find that someone from a management location could do backups using the service.

The price for Vembu was very important and key to our decision-making. Also, Vembu support was very important. When I didn't know how to do anything, I wrote to support and the response time was quick. Basically, it was cheap, easy to install, the agentless backup was very nice, and support was very responsive

The initial setup was very easy. It integrated easily with Windows, Linux, and NetApp backup.

The deployment took about one hour (max) per server.

This solution helps us deliver an enterprise level data protection solution and reduces budgets. 

With the free version of Vembu, you receive three virtual machine backups. However, if you buy the NetworkBackup Enterprise version, you don't have access to the features seen in the free version. This is a situation that Vembu should solve. This caused a misunderstanding between sales and us. I was hoping if I buy the licenses, then after the trial I would not have to purchase virtual machine licenses. Maybe they should offer these three virtual machine backups as part of the Enterprise license.

I tried to install two other solutions. However, I found Vembu very nice because in its trial period, it includes all the features. During the trial period, I was able to check exactly what happens if I use another type of solution from Vembu, and it was easy to test.

I chose this backup solution because it fits what I need.

Try it and see what it can deliver. It is very easy to test and check the licenses. 

The only situation that was not what I expected: I need to have a full copy of the backup, plus a live session of the back up which involves a lot of copies. I need a lot of hard drive capacity offshore and offsite.

I don't know how to check the deduplication.