BDRSuite Backup & Replication Reviews

I use it to back up the virtual machines running on VMware ESXi. I also use it for backing up Windows Server. I don't use it for Microsoft 365. I have a daily backup, and I also have a monthly backup to capture all the data and changes.

I started with version 3.0, and now, it's version 5.3.

The backup window is very reasonable. Recovery is also easier. We have scheduled incremental and full backups, and it helps a lot with our infrastructure. I feel comfortable running this in the virtual environment.

We can instantly recover data. This instant recovery is very important because there are some files we need to recover immediately. We can easily recover a single file or folder. That's a very helpful feature.

It provides multiple restore options for recovering data in a granular manner. We have daily and monthly backups, and sometimes, we need to go back, not just to yesterday. We have multiple restore points, and we can just select one from the menu. It's a very easy and very important feature.

We are running the daily incremental backups. They've reduced the backup window. These incremental backups are very important because we cannot do the full backup during the weekdays.

When it comes to backup scheduling, similar to all backup solutions, it provides scheduling options. We just can't do backups manually. We have pre-configured it with the daily incremental and monthly backups.

It isn't hard to add and remove backup jobs using BDRSuite. You select a machine or a hard disk, and then you can go to the next step and schedule the backup. That's it. I don't need to open the interface every day. I schedule the backup, and I just receive the notification message in my mailbox. That's it. As long as I see a successful message, I'm fine. I just let it run.

Provisioning disks for restoration is easy. You can just select a disk, and you just recover. They'll provision the disk for you.

The most useful feature is that you can back up the virtual machines in different ways. You can back up from a vhost, and you can also back up from a Windows server. It doesn't matter what type of infrastructure or hypervisor is there. It's very flexible, which is its most useful feature for us.

The response time of the support could be improved a little bit. Sometimes, I need to wait for two or three hours to get support. With VMware, we can get urgent support in an hour.  Other than that, I'm pretty good with BDRSuite.

It has been more than three years.

It's very stable. I'd rate it a nine out of ten in terms of stability.

I don't have too much experience with scalability because our infrastructure didn't change too much. 

I'd like to get quicker technical support for urgent issues. Sometimes, it took longer than I expected. For example, I expect support in one hour, but they may get in touch with me within two or three hours. That has happened twice last year, but it doesn't always happen. I'd rate them a nine out of ten.

Positive

We were previously using Veeam Backup. Their features are a little bit different, but they both are doing the same thing. 

We switched because my manager wanted to try this option. The Veeam Backup costs more than Vembu. They also don't support some editions of ESXi, whereas Vembu BDRSuite supports all the versions and all the editions.

It was straightforward. It was set up a long time ago. There was no big change after that. We just upgraded to the latest version.

I implemented it along with the support person. I searched on the web to select the vendor.

It doesn't require much maintenance from our side. There are just patch updates, and they don't happen during the backup window. They do not affect production. It's good.

I'm not sure. It might have been in less than a year. It's cost-effective. It didn't cost too much. We are completely satisfied with the cost.

It's very affordable. We are very satisfied with the cost. It's very affordable for us.

We didn't evaluate any other solution.

I'd advise running the trial of on-premise and online versions to see what's the difference. In the initial setup, you may need to adjust some services or the local backup storage called the repository. Test it first and make sure it's working. There are so many backup tools in the market. You can't just read the white paper to do the selection.

Overall, I'd rate BDRSuite a nine out of ten.

It sits on a hypervisor and backs up two virtual machines. 

The main benefit is that it's inexpensive. We get a lot for a little bit of money. I'm very happy with the savings and with the features. It allows me to do everything I need.

I don't spend much time on it. I interact with it occasionally and check that everything's still going fine. It's very good in that aspect.

It provides multiple restore options for recovering data in a granular manner, which is pretty important because different issues require you to use different approaches. It's good to have as many options as possible.

Our backup strategy is pretty simple. We have just two virtual machines, but it's very good to know that all the other options are there to back up physical and cloud workloads, as well as endpoints, applications, and databases. I'm not planning to use any of them, but I'm very happy that it's there. If there is something that I need to do that doesn't fall under what I'm currently doing, I can always expand quite easily.

It provides incremental backup processing, which saves a lot of space.

The fact that it has a web portal is valuable. One feature that I haven't yet fully implemented, but we're looking forward to, is the heartbeat monitoring which checks the health status of virtual machines to back up.

The interface could be better because I have to fumble around to find things. I can't just sit down at the terminal and know exactly what to do. It could be just me, but I have used a number of different backup products, and I found them simpler. However, its features are very good, so I don't mind sacrificing a bit of extra time to do what I need.

The reason why I haven't implemented heartbeat monitoring is that I can't change the encryption. In order to do heartbeat monitoring, it needs its own default password for encryption, whereas I've got them encrypted with a custom password. I just wish that there was a way to add password history into a job so that it was possible to change it later on without having to delete or re-add. I might manually get around that.

It has been over a year.

Its stability has been alright. I haven't had any issues. The only thing that I ran into was that before we paid for the license, there were things that weren't available in the free version.

We have a small office. I'm the sole IT team in the office. We have two servers that are replicas of each other. Vembu sits on the main server which has got a little bit more power. It takes backups of two server virtual machines that we've got. It backs up to a local NAS as well as a disk. I was really impressed with it because there's a specific backup destination for this type of thing, which I hadn't seen in any other software. Basically, we're backing up to a disk that we swap out after the backup is done and take it off-site. I was just impressed that it exists in the software. We're doing this because of the bandwidth. It allows us to not have to spend an entire week uploading another copy.

In terms of the number of users, I'm the only one who actively interacts with it, but our company has about 25 people. It benefits 25 people.

It's absolutely scalable. If we ever open a new office, it would be easy. For our needs, it's as scalable as we could hope for.

I've interacted with them on one or two occasions. They were fast, and they got quite a few people involved right off the bat. I was impressed. I'd rate them a ten out of ten.

Positive

We never had multiple backup solutions. We have only used one software at a time. 

We previously used tools from other companies. We used to use Symantec. We also used Altaro. We also used a Chinese one. That one by far was the simplest one. Its interface was super simple. However, anytime it has to apply logic to things, you could almost expect it to break. It wasn't good for just setting up and forgetting about it.

We didn't go with Altaro because it was a lot more expensive. There is a free version for up to two VMs which cuts out about half the features. That's fine for a start, but when you want to upgrade, there is a big jump. If the first paid level gives you, for example, 100 virtual machines, which costs a thousand pounds a year, it's a big jump from paying zero to paying a thousand pounds. I don't have the exact number, but the reason we didn't go with it was the big jump between the free version and the first tier of the paid version, so I started looking for other products and came across Vembu. It did pretty much everything that I wanted on the free one, but it had good features in the premium version that would just make your job easier, and because the premium version was not expensive, it just made sense.

It's deployed on-premises. It's deployed on a hypervisor. When I first set it up, it was on a free account, and I didn't know the first thing about it. It didn't follow the tutorial or anything. I managed to get through it without too much difficulty. It wasn't the easiest thing. I didn't find the interfaces as intuitive as the other ones I've tried before. However, there are lots and lots of features there and lots of things you can do on the scheduler. I'm very happy with that.

I installed it myself. In terms of just installing it, it was pretty simple. There wasn't any way to incorporate the backup history that we've already got, but our backup strategy is to have a month of backup. So, there was a month when we had two different solutions in play. After that month, it was just a clean cut to them. It was easy to integrate.

In terms of duration, it's not a fair representation, but it took me about a week. That's purely because I was going through the manual trying to figure out what it can do, and I had the luxury of already having a solution running, so I could have some time with it. I'm sure I could have deployed it in a day or two.

It was just me who installed it. 

In terms of maintenance, I was wondering about that. I tried to go in and see if it needed to be updated because I realized that I have never done it, but I couldn't figure out how to update it. So far, it hasn't needed any maintenance.

It isn't tangible because we haven't had any outages yet, but I have noticed that I spend a lot less time worrying about the backup.

We're ISO 270001 and ISO 22231 certified, so backups are a big part of our overall management system. I used to spend a lot of time on backups and making sure that we could recover in case of a crash. My time investment in that has dropped by 50% percent.

The price point of this software is good, and I can do everything I need.

In terms of the affordability of the solution for businesses with a tight budget, we're on a small business enterprise package, which is half the price of the regular enterprise package. It's super affordable. The features you get for it are enterprise-level. I'm very happy with the pricing.

It's very cost-effective. If I had to manually do what the software does automatically, it would cost a little more. It's like a net positive cost.

In terms of cost-benefit, you get a lot for very little, and it's much cheaper than other products. I've used other products, and it's just as good as others or better than others in some aspects, so it's the one to go for if you aren't scared by it. It takes some time to learn the interface and get familiar with it, but you get a lot for what you pay.

Coming from a small business mindset, it's very cheap to get and try it. You can experience all of the automation features and figure out how much time you're saving by having it in place. It will be worth it. You can buy the pro version and try it because it isn't all that expensive, and it can't go wrong. Just deploy it for a couple of machines, and if it doesn't work, you haven't really lost anything.

I haven't tried to instantly recover data, but I believe that it enables you to instantly recover data.

We haven't created backup repositories in cloud-based object storage because of the size of the backups and our outgoing bandwidth. We might try that at some point next year once the bandwidth situation changes, but for now, we haven't stored the data anywhere other than within our office.

Overall, I'd rate it a nine out of ten.

We are a managed service provider (MSP). We have also started to sell it recently. We have been using this solution at our company, and after testing the product for close to six months, we realized this is a good option moving forward.

We are a managed service provider. For us, this solution is even more beneficial because we can control the licenses, renewals, and other things for customers from a managed service provider's panel, and we get an option to upsell and cross-sell to clients.

Its ease of use and price are most valuable. It is simple and straightforward. Someone who has never used any backup software will easily understand it from the first installation. It is that simple. Price-wise, it is much cheaper than its counterparts. 

It also has very less overhead on IT in terms of the product, service, and outcomes. Another good feature is that you don't really have to install any agent on the server side, especially when you are taking Hyper-V backup. We are using Microsoft Hyper-V, and we are taking backup. No agent and other things need to be installed on your machines.

I have done a couple of restores on a trial basis to check the integrity, and I did not find any issue in terms of the reliability of the restores. It was smooth.

It would be a great improvement if they can give a console to control the systems. All other vendors let you simply log in to the cloud console and control everything from there, but for Vembu, whether you choose Vembu Cloud Backup or Vembu Disaster Recovery, you still need to install the Vembu software on your on-premise system and configure it from there. It would be great if I can get a cloud console to manage the systems. 

They can also give an option where if you don't want to install an agent, you can use your own server and manage it, but if you want to manage it from the cloud console, you install the agent. It should be my choice. I should have control when I am sitting at home. I should also have control over the cloud so that I can monitor everything and do whatever I like. If my organization policy does not allow me to do that, then obviously I don't do it, but Vembu should provide such an option.

I have been using this solution for close to six months.

It looks good to me. So far, I haven't found any glitches. It is always there, so it is stable. You run it through the browser, which makes it simple.

It is scalable. We started with a 30-days trial, and after that, we started using its free version. Today, we upgraded from the free version to the enterprise version. We are also working on putting 10 TB backup on Vembu cloud as well as going ahead with almost eight servers for the disaster recovery offsite. 

To upgrade from the free version to the enterprise version, I simply had to synchronize the license, and everything was set. You can scale it very easily. You just need to activate the license under your account, and then you can log in to the Vembu console and just synchronize the license, and you're done. If you want to go from an on-premise backup to the cloud, you should have a cloud license. You can then synchronize and configure it. That's it. 

In terms of the size of the environment, one of the implementations is done for a government organization, and there are around 20 or 25 users with close to 5 terabytes of data and two virtual machines. We don't have plans to increase its usage in the same organization because this is a small subsidiary of a big government office. With the same client, there is nothing more we can do. They have a limited number of users, but we are working on implementing it for other clients.

I have used their support, and I had a very good experience. We were basically installing a demo for another client, and they were using 2008. We were getting a particular error while doing the installation, and for that, they needed to reboot the server, but you just cannot reboot the server in a live environment. You need to fix up a time for that. For example, if we have to reboot your servers, we need to schedule it with you, and you will schedule a time for it with your management.

Vembu's support is available 24/7. They said that whenever we are ready, we should just send them an email, and they will do a remote session with us, which is what precisely happened. When we were ready, I sent them the intimation that we will be ready in about 15 or 20 minutes, and their support guy connected with it and helped us.

Its ease of use and less price set it apart from other solutions. I have used many solutions, such as Acronis, Veeam, Symantec, Veritas, etc, and all of them are a bit complicated. I found Vembu to be the simplest one. In terms of features, it is similar to others. It has encryption and retention features and multiple backup options that every backup software provides.

Currently, we are also using Acronis, and slowly, we will be migrating from Acronis to Vembu. It is cheaper in price than Acronis. Of course, Acronis gives other benefits such as patch updates, cybersecurity, ransomware protection, and so on, but people have their firewall, endpoint protection, and antivirus. They don't really need to invest again in something that they don't need. The only thing that they particularly need is a backup solution that is encrypted, so there is no point in protecting them from all these things because they are already protected. If you go for Acronis Cyber Cloud, a client is not going to stop using the firewalls or endpoint protection. There is no point in loading double onto that. It is a good addition for those people who are very specific and know what they want. If you just don't know what to do, then you can go on a shopping spree.

With Acronis, all you have to do is to install the agent, and then you can control everything from the cloud. Wherever you are, you simply log in to the console, and you have your servers over there, and you can do whatever you feel like. With Vembu, you have to install the Vembu BDR software onto the server, and from there, you can basically dump the DR or a backup onto the cloud.

It was very straightforward. You simply install the software, plug in the storage or wherever you want to dump that, and create a profile. That's it. These were the three steps, and of course, the fourth one was to activate the free software. You can start with the full-fledged version after 30 days. You can convert the trial version into the free version, which is available online. It is easy. 

Its initial installation took less than an hour. This includes downloading and setting it up.

Price-wise, it is much cheaper than its counterparts. I like its pricing, and its price is okay. The lesser they take, the more profit we can make, but we are happy with its price.

It is very affordable. We were working with a client, and they were looking for backup software and had a very tight budget. When I told them that Vembu is only going to cost around $400 to $500, they were shocked. They didn't believe me, so I showed them the website so that they can check the price themselves. Of course, if they agree to that price, we get a 15% rebate as a managed service provider.

You choose the type of license you want. There are two types of licenses. One is a subscription license, and the other one is a perpetual license. If you go for a perpetual license, next year, if you want, you can renew the support. It is up to our clients whether they want to renew the support or not. They have an option. They also have an option to go for a subscription.

Every IT scenario differs from others. It is a good product, and just give it a shot. If it fits your organization, you will save a lot.

I have been in IT for over 25 years, and I had never heard about this software. I came across this through a consultant who was also working for a government organization. They asked us to install the free Vembu backup software, and I wondered which is this solution. I checked their website, downloaded the software, and installed it for the first time. I was amazed why there is no marketing for this. I get so many marketing emails and other things, but I never got any email related to Vembu. I also didn't come across it while doing research on the internet.

We have been using this solution for only six months. There are many features that we haven't used, but whatever has been phased out and tested was okay. We haven't yet used Vembu to back up Microsoft 365, Google Workspace, or AWS, and we also haven't used Vembu's Download VM to help in migrating physical machines to a VM environment. Similarly, we haven't used its Instant Boot VM feature for instant access to VMs or physical machines after a crash. 

It provides multiple options to recover data during hardware failures or accidental deletion of files, but I haven't tested this option. Having such a feature is a good addition because if some resources are not there, you can restore your data to different ones. We will definitely be using Vembu's data integrity check feature after the enterprise installation.

I would rate Vembu BDR Suite an eight out of 10.

We use it for providing backups and recovery. We have a file server with a little over seven terabytes of data. The content changes quite a bit and we needed an easy tool to work with that would give us the ability to restore in a variety of ways: at the individual file level, folder level, and whole volume level, if necessary. This tool does that for us.

We're in telecom and wireless. We do installations and maintenance of towers and equipment for microwave and cellular. We do that mostly in the United States, occasionally in other places in the world. We'll have 400 people out in the field providing data to us that we have to put in a repository, that's the file server, that shows work prior to us initiating our work assignment from our customer, during the process, and at completion. That way, the customer doesn't have to go to remote places to verify. Sometimes, we can address an intermittent problem and say it's fixed and, of course, it comes back the next day because it really wasn't fixed. So, it's hard for our customer to know when something is done.

So we take a lot of images of our work, associated with projects, and those are uploaded by the field people every day. We provide the backup necessary to our customer. We'll receive ten or 20 gigabytes of images daily, which go into the repository. They have to be tracked and recorded, put into the reports associated with the projects and the status of those projects, and then provided to our customers.

That's what we do on a daily basis. We're a 24/7 shop, so what we do has to minimize downtime, so that the tools are available to the people, especially if they're in the field. They'll VPN in and provide reports and images necessary to show the work has been performed.

The nice thing about Vembu is that when it's running - as it does incrementals daily - we don't see a negative hit on the performance of the server it runs on. I can also pause it, should that happen, but I've never had to do that. 

It generates daily reports. I look at them seven days a week, even though I only work five days a week, because I want to make sure that everything's working fine. From a productivity standpoint, it has not hindered anyone and it keeps me very well informed that our backups are being completed. It gives me the data that I need to know, that makes me feel comfortable: Yes, that makes sense for that day, that much data being added to our repository, etc.

It has made my job, making sure we have a backup and being able to count on using it, a lot easier. As far as impacting the user community that uses the file server that's being addressed for backup purposes, it has not impacted them in any negative way whatsoever.

Finally, it helps us deliver an enterprise-level data protection solution and reduce budgets at a price that - and we don't want to encourage them to change their pricing - is a great value.

The dashboard is very easy to use, setting up the backup is very intuitive. Since that's our primary purpose in using it, it made it easy, when I was doing evaluations a year ago, to choose the product.

If I want to back up to this past Friday, and reinstall the file server to that state, I can choose a point in time and issue the command to back up and I don't need to go in and restore the last full backup and then apply iteratively, sequentially, all the incrementals, as I've had to do in some other software in the past. It's nice that I can pick a point in time and tell it I want to go to that state and it's transparent to me. It happens in the background for me.

It's very easy to use, very quick and efficient. From a backup standpoint, it has provided us the tools we need on a daily basis to know that it's working properly and with almost no manual maintenance work from us to verify it. It just comes to us. It's been very positive, helping us address that need efficiently.

In the beginning, when we had some hiccups, I would chalk that up more to a learning curve for the product. Once we understood how it operated - where we thought it was doing something a certain way and it was not - it was easy to understand, once it was pointed out.

The times when we've had problems, they've not been repeated problems, they've been addressed, and it was more learning curve issues. With any software there is a learning curve. Not all backup software operates exactly the same way, so some things were a little bit different. But once we understood why and how they worked, it made sense. It was sometimes a different approach, but not a problem for us.

There is no problem with the product's stability. We get our nightly reports on schedule. We've never had the application fail, and better, the application doesn't interfere with anyone else's application. It's been everything and more than what we had hoped for.

I can only speak for our environment where we've used it - and I know it has so much more capabilities, because when we go in through the dashboard and the wizard to create backups, we see where we could use it and how we could use it. But in our environment, whether we had seven-and-a-half terabytes or 15, I wouldn't have to change anything.

The other thing that I like is that it has software to provide a distributed copy to another site. It's a very economical add-on to the suite. But because it's terabytes, and with it going across the Internet to do the initial cloning of that, it has a feature where you bring in your other servers, set it up, establish your initial clone there, and you put the server out and then you only have to keep track of the changes, which is much easier to do. We have a 100-megabit connection to the internet, but even there, if you're going to have to keep terabytes worth of data synced, it would be really hard. In this case, we only have to keep track of the delta once the initial distributed backup has been made.

It has a lot of capabilities. We just started getting into the distributed backup and, from a scalability perspective, I've not seen any issues in our use of it. And especially in the beginning, we monitored the resource usage to make sure that we didn't see a degradation on the server to the user. That was not a problem.

I could easily see us doubling what we're backing up without any issues and problems and with no additional tuning necessary.

The other thing that stands out, while it isn't a feature per se, is support. Any time we have a question, whether we call or email them, we get an amazing response. We're not a Fortune 500 company, we're smaller, we don't have a large number of licenses yet. But we get quick response and follow-up to make sure that the issue has been properly addressed, as though we were a Fortune 500 company. I'm amazed by the level of support they provide.

Last time I contacted them was because the volume that we put our backups on became full, and I wasn't sure what the best way was to address the problem. They gave me directions on how to address the problem, but more importantly, on how to avoid the problem in the future.

Around October of 2018, I did escalate an issue regarding backups but that was the only time that I can remember having to do so. Like everything else, it went extremely well. The follow-up and the level of detail, hands-on, were great. I've been in IT for 40 years and it's not something I'm used to seeing. It has been a nice surprise.

The oldest previous solution we had was Windows Server Backup.

Once we put Vembu on the production server, we ran a full backup that evening. That's probably one of the nicest things about the backup. Not that companies don't have seven-plus terabytes of data to backup - that's large, but there are certainly many that have much more than that - but backing up that much data in Windows Backup is an impossible task. So the ability to address the data in the way that Vembu does, versus the way Windows Backup does, we had to use a Vembu-type product. There was no choice. Seven-and-a-half terabytes in Windows Backup, on a server level, would've taken weeks, which is not acceptable.

We needed a solution that was doable. Some of the solutions that we were using took an unreasonable amount of time to back up the data. Even when they were running on the same server and the pool was on the same server that they were backing up to, it was not acceptable. We needed something that was more efficient in the way it addressed reading the file structure. Vembu provided that. Then we had the additional functionalities that we wanted to be able to restore the way I mentioned, plus the support. I can't say enough about the support Vembu. I just don't have any other positive experiences that are as nice as what they provide.

Nothing was complex regarding the initial setup. We could do backups on day one with the software. It wasn't a question of just doing the backups but of trying to do them so it provided us the greatest amount of flexibility and that we were using our pool space as efficiently as we could. That took a little bit of investigating and communication with support. But once we understood it, it was not a problem.

On the initial install, there were some things that I thought were going to happen a little differently. We thought we wouldn't eat up the size of our pool, our repository, for backups as quickly because of compression. But when you think about it, that's not a Vembu issue. That's just a practical result of the fact that jpegs already come compressed, so you're not going to get much compression. We underestimated the amount of space we needed.

Installing it takes just a couple of hours. It's easy to do. There was no negative impact on anything else running on it. It was simple. We did a backup the same day we installed it, in a test environment, so we could do whatever we wanted. We could do restores, do incrementals, combine incrementals to weeklies, etc. And we didn't have any problem doing any of those things. We'd have a question, periodically, but we would get a response the same day, which was always nice.

In terms of staff for deployment, I'll divide that into two pieces. One was a more thorough test of our environment, versus not the high-level tests that we did during the evaluations. We did that over a two-week period of time with a quarter to a half of a person.

Regarding the implementation strategy we developed, there was an assessment of what our needs were, tailored to our specific situation. Once we did that, we evaluated what products we might be able to use. We then considered support and maintenance issues and would the products be able to function within our requirements, timeframes, and give us the backup capabilities at the levels that we wanted: file, folder, and volume. This process allowed us to come up with a shortlist of three products and do a little bit deeper testing with them and decide on which one we thought was the best. 

We haven't done an analysis of how much money we have saved by switching to Vembu. We did a post-implementation assessment that made sure all of our requirements were met. Part of that is financial, but I can divulge the savings that it provided.

I've worked for extremely large companies as well as startup companies. In our environment - out of this office we have 400 field people - we're a relatively small business. If I was backing up multiple file servers, much more data than we are, it wouldn't take much more time with Vembu. There's an inherent amount of time to install and get to know a product, and then to use it. If it's pretty intuitive with good support, it can be really easy. Vembu has turned out to be really easy. The amount of budget associated with supporting is way under what we expected. That's a good thing and that's because of the support that they provide, instead of us having to do things like we have to do with some of our other applications.

For example, we've used our accounting system for a long time here, and people are used to it; creatures of habit, like most. But the amount of support that it takes, despite it being here for decades, means that any time we make a change it's way more involved. There's an element of risk that we don't care for. It's not what we like. There's an unpredictability about it. We have not seen that with the Vembu product.

It's an amazing value. Their licensing structure is easy to understand and it's very fair. We don't have any problem with it.

We looked at different tools and tested them ourselves. We had our own requirements list of what we needed to do, and it was all tailored to our environment. The evaluation occurred over a month of elapsed time and probably involved a person to person-and-a-half in that period of time.

Quite honestly, we could have gone with other products, but the support level from Vembu was unparalleled. Today, a lot of companies want to refer you to a forum, a community, and they don't want to talk. They don't want to provide people who know the product and know your situation. It's hard to find an example in a forum that is exactly like what you're trying to address. Vembu, consistently over the month, as well as the second-level evaluation, was always there to provide support and answer questions. It was a deciding factor, absolutely. They had the functionality, but they provided the real people for support, which just made a world of difference for us.

Some of the companies that we were using and evaluating, when we told them what we ended up choosing, just out of courtesy, in some cases they either didn't know who they were or acted like they didn't know who they were. 

It was an easy decision, when it came to the end, to choose Vembu.

It has to meet your needs. But for most people, for backups of large amounts of data, I would strongly encourage you to use it, and not be hesitant to contact the support desk if you have a question. Don't just install it with the intent that your first use is going to be your final setup because there are ways to tune it to make it more efficient on space usage for the pool where you put your backups. The help is there. That's the good thing. With most other products, you're not going to get the same response. Use the help and you're probably going to be quite happy with it.

I would encourage you to count on support, run your tests, play with it, and you'll be pleasantly surprised and happy with the results.

Of the software that I license, I feel I get more value from this than any others. I just can't think of anything that I'm looking for that Vembu BDR isn't already addressing. I've got no wish list for them.

Everything I need is being addressed by the product and then some. I wish them great success and I want them to be around a long time. I don't want to have to go and replace this. This is a good product. It does what we need and I'm not seeing anything that I wish it had.

I like the compression, encryption, and deduplication features, although in our case, we don't get much compression because a lot of our material is already compressed. There just isn't an opportunity to see a big reduction. But the tools allow us to have every feature we want, including being able to restore from the backups. Of course, we don't have to do full backups very often, because of the way it has been set up.

Encryption today is, obviously, given privacy issues and confidentiality, very important. In our particular case, it's an added plus but it wasn't a real high criterion because the data that we have is not considered highly confidential. In fact, if it was put out in the public domain, it would not cause our customer or ourselves a problem. It's nice to have, but it wasn't something that was as critical to us as it might be to a lot of others.

We don't use it to back up our virtual environments. We keep things very discreet here. We don't run a VM type of environment. Servers are by function. Hardware has become so incredibly cheap. I understand the savings, the value with VM and having a virtual environment for different things. But to us, hardware is just incredibly inexpensive. If we have something in our accounting system that needs to be addressed, an upgrade or the like, we like having it on its own server and discreet from everything else. It also inherently provides easier access control for those systems that are more critical, in terms of the type of information on them.

Regarding staff for maintenance of the solution, we're talking fractions. We just look at our reports daily just to make sure that they are giving us the information we need, indicating that backups were successful and that the expected amount of data that was backed up. We know how much data comes in every day approximately. We can confirm that it's been done properly. It's just minutes a day. I don't think it needs a full day per month of attention. The maintenance is extremely low.

We have other environments that we need to address in a different way than we are today. The company is old enough that, like most entities, it is a creature of habit. So changing the way we do things is a little slow sometimes. But I can see us using this in several other environments, other than what we initially targeted. I can't tell you when that will happen but I believe that it will happen because of the experience we've had.

The end-users don't use it, per se, because they have no touch with it. It's IT that uses it. Nobody has a problem with it. We have a small group of six IT people in this main building. We try to get different people exposed to it. They vary from application support, mostly in the accounting area, and then, because we do a lot of VPN, we have network people who handle network security. We have failover network with multiple ISPs so networking becomes a big issue, plus the security side. Percentage-wise, there are more people involved in network and security than in many companies. Yet those people are still required to be able to support the applications we have, including Vembu. Nobody's had a problem doing that.

I'd love to try it in a virtual environment. We just don't do that here. We're a Windows Server shop, so I've not tried it in other operating systems, like Unix and Linux.

For my needs, I'd give Vembu a nine out of ten, and that's only because I'm hesitant to say anything is perfect.

Everything could be improved. For example, if you were to have a custom backup solution created, it might be a ten if they achieved everything you listed regarding what you need. But it's not practical to do that for an individual or a small company. I've been responsible for a lot of development people and developing applications. It's somewhat subjective on where you place buttons and how efficient they are.

Once you get used to a product, if it wasn't made for you, and it's working and meeting all your needs, without having negative side effects, you got to give it a high score. It's the only fair thing to do. The only way for me to get to a ten is to say that it's perfect, that it laid out all its buttons and features just as I would. If I had written it, maybe that would be the case, but by the time I had written it and gotten it done, I'd be retired. 

It's a great product. Amazing support. It's a very good value for our environment, no question. We will not change. This is a good product that does everything we want and more.

We use BDRSuite for backups of our primary and secondary servers, our virtual machines hosted on Hyper-V, as well as tape backups. 

BDRSuite takes the hassle out of backups by automating the start time, eliminating the need for late-night office visits to manually initiate the process.

BDRSuite enables near-instantaneous data recovery, with even our largest multi-terabyte restoration only taking five to ten minutes. That is quick for a backup. The quick recovery is extremely important to us. We want to have as little downtime as possible.

Granular restore options in BDRSuite are crucial. They allow us to recover individual files without restoring the entire system. This means we can retrieve a lost file without wiping out any progress made since it was lost, saving significant time and effort.

The incremental backups are great! By only backing up changed data, they reduce stress on our servers and drives, which in turn extends the lifespan of our machines.

The backup and scheduling options are great in BDRSuite. I can choose individual times a day down to a minute essentially. Usually, what we do is we set all of our backups to start at midnight so there's nobody in the office, and there's no work that can be interrupted by the backup in the worst-case scenario.

It is extremely easy to add and remove backup jobs using BDRSuite. We select the backup that we're trying to remove, and we just delete it from there. We have to make sure whatever storage it was using is cleared off our machine.

Backing up our virtual machines is crucial, especially since some store medical records. To ensure continued operation and data protection, BDRSuite provides us with a backup solution for our business needs.

Thanks to the breadth of backup coverage provided by Vembu, we have been able to stop relying on multiple backup solutions for different data sources. We were using Windows Backup in a couple of the WD external drives and now we only use Vembu across all of our data sources.

It was extremely easy to integrate BDRSuite with our existing infrastructure.

The smooth implementation is the most valuable aspect of BDRSuite.

Vembu's website doesn't clearly state that their software is designed for tape libraries, not standalone drives. This led to significant difficulty connecting our standalone drive, even requiring a rollback from Vembu to function properly. I'd like to see easier connectivity to tape drives and better stand-alone tape drive management.

I have been using BDRSuite for one year.

I would rate the stability of BDRSuite nine out of ten. Short of the machine shutting off, the software will not go down.

BDRSuite seems like it could handle growth well scalability-wise aside from the occasional reboot issue. However, since we haven't tested it with multiple servers, it's difficult to say for sure. Because of this uncertainty, I'd rate its scalability a five out of ten.

Working with technical support was challenging due to the time zone difference as they are located overseas, but outside of that, they are great to work with.

Neutral

While the initial deployment of BDRSuite itself was simple, it ultimately took three attempts due to connection issues with our tape drive during the first two tries. This extended the deployment process to three or four days.

I was guided through the implementation fairly well by a BDRSuite agent who helped me get it installed.

While BDRSuite's overall return on investment hasn't been substantial, its granular backup feature has proven very beneficial. This functionality saves us significant time by allowing us to directly restore individual files instead of having to restore entire image backups and then manually search for the specific file needed.

BDRSuite, although cost-efficient, is more expensive than most other providers.

While I would recommend BDRSuite for businesses with tight budgets, it's ultimately a case-by-case decision based on specific data storage needs. Not all businesses require comprehensive backups for virtual machines and other complex systems; some may only need a simple image backup solution.

I would rate BDRSuite seven out of ten.

Our company currently uses BDRSuite on a single server for my supervisor and me. It doesn't handle individual machine backups since we have a well-established group policy suite that automates machine setup, making it standardized and efficient. This streamlined process allows us to quickly restore backups whenever a new computer is added or an existing one fails.

BDRSuite may occasionally require attention after a server reboot, which can happen due to hardware upgrades or other unforeseen circumstances. I've observed instances where the task manager details section shows abandoned PostgreSQL connections, requiring us to manually close them and restart BDRSuite for it to function properly again.

BDRSuite is a good option for medium and large businesses. While full VM backups might not be necessary for all businesses, especially smaller ones, having a disaster recovery plan is crucial. However, skip standalone tape drives and opt for a complete tape system to ensure better compatibility with BDRSuite.

I'm using the backup from Vembu for my home lab where I have ESXi. I'm backing up VMware servers. That's all I use it for.  I have Oracle Databases running in these VM machines and I do testing, patches, upgrades, etc. I want to be able to back them up and, if need be, restore them so that I don't have to rebuild them.

I'm running it in a Windows Server in a VM machine. I have ESXi 6.7 running on a Dell PowerEdge R720 and I have a Windows 10 VM running in that. And in that I have the Vembu BDR running as my backup server.

It helps me with restores. I can repeat a test multiple times: Do the test, the restore, and then test again. It saves me time because I don't have to rebuild the VMs every time; rather, I just do a restore. I would estimate it's saving me four to eight hours every time I have to do a restore.

I also had a disk crash and the restore was important because I didn't have to rebuild it. So it helps with data recovery as well.

It gives me peace of mind because I don't have to do the rebuilds. In a home lab, documentation is not usually at the forefront of your thoughts. You are just trying to get it built and tested. Having the ability to back it up and restore without having to remember all the options were that you had installed and what was the data like before, it gives me peace of mind that I have the restore.

The two features that I use are the backup and the restore.

The only thing with room for improvement, as everybody says, since I'm in a home lab, would be the price for the CPU; the cost. If I were to add another CPU, I would start to get into an expense where I would question, "Do I really want to continue backing this stuff up?" But from what I could tell, this was definitely the least expensive option to go with.

I have been using it for about eight months. I bought my first license in April and then I had to buy another one because I added another ESXi server. I have two licenses and they're both for five years. My intention is to be using it for five years and I won't be switching out.

I'm on the most recent version because I just upgraded when it came out.

It has been very stable. There haven't been any issues.

I have it licensed on two CPUs, one CPU in each machine, and it has not had a problem with the 40 VMs that I have.

The only way I would be increasing usage would be if the cost would allow me to add it to another machine. The other machine I'd like to add it to has two CPUs in it, so I would be doubling my license cost. Right now, that's not an option.

For the issues that I've had, the tech support has been very good. I've had no complaints and they've been very responsive. I've only had three or four issues, and they have all been resolved. That has been a very good experience.

The last reason I had to contact support was for a restore that I needed to do. I also moved ESXi servers, so I had to have some assistance because the backup was done on one ESXi server and then I moved it to another ESXi server. I needed to do the restore and tech support assisted with that.

There has never been a situation where I had tiered tech support, where the first person I got didn't know and handed me off to the next person who handed me off to the next person.

Veeam was what I was using before I went to Vembu. 

The wording, when you start Googling this stuff, gets kind of questionable because it says "unlimited free VMs." That really isn't true. You can only do a couple before you can't do anything with it. Veeam was the one I was using first. But when I hit my third VM, it wasn't working anymore. You could only actually do three and you would have to roll out one before you could roll in one. 

The initial set up was very easy. It was just like installing anything on Windows 10. It took about 15 minutes.

The first time around I did it myself. I did move it from one VM machine to another VM machine and I had assistance with that from Vembu, and that assistance was very helpful. That was part of standard tech support.

As far as competitors' prices go, Vembu was definitely better than all the competitors I found.

I would guess it has saved me 30 to 50 percent. The problem is that I'm a single-person home lab, so I have no idea what kind of licensing things happen for a corporation which is looking to buy 500 CPUs. If you were to do that and you were to look at the cost per CPU versus my cost per CPU, theirs might be 50 percent less than what I'm paying.

Veeam was one of the solutions within a list of solutions I evaluated. Cost was definitely one of the big differences, but I didn't use Veeam long enough to go down that path. When I hit the third VM, which was within the day that I started using it, I stopped using it.

Make sure you plan out your backup server for the long-term. When I did this I moved my backup server. When I moved it from one machine to another machine and the IP address changed, there were some headaches. I had to get the knowledge documents and I had to get tech support involved to help me outside of the knowledge document. So try to plan out, for as long as you can plan out, that this is the server, it isn't changing, etc.

It has worked as expected. It's straightforward for backing up and it's straightforward for doing the restores. Other than the navigation and what buttons to push, there's really no learning curve here.

I'm not using the encryption. If the deduplication is in use, it must be so by default because I have not done anything with it.

For what I need it to do, and compared to the other products that are out there, this is the most cost-efficient and best solution for my needs.

We use Vembu to back up and replicate virtual machines. We run virtual machines using VMware ESXi, and we back up and replicate our virtual machines.

The best thing about it is that it has been adaptable to our business model. We are in industrial networking, and they were adaptable to give us offline installers and offline licenses. That has been the biggest thing. They also allow us to order the licenses on a perpetual basis.

Backup and replications are most valuable. It seems that these servers are better because we can do application-aware backups on them. 

Windows 10 does not have application-aware backups. From my point of view, that's what's existing needs improvement. 

Something that I would like to see them do is an on-premise immutable solution.

It's probably getting close to about a year mark.

There are some bugs but not major ones.

From my point of view, it can handle as many VMs as I'm going to see. We have pretty small sites. We range from 3 virtual machines to probably 20, and I feel confident that it could handle as many as we needed.

There are five or six users who are currently using this solution. They are members of the network team here at my company. They are network engineers or network admins.

We have plans to increase its usage. Currently, we have a lot of existing sites that are using a different solution, and their licenses are still good. In the future I see us expanding more. As long as Vembu keeps the same business model, I do see us using the product more.

For the most part, they're responsive. There has never been a time when we opened a ticket and didn't hear from them for days. They're usually pretty quick to respond. We provide them with what they need, and they normally give us an answer whether we like the answer or not. Overall, they're responsive, and they at least give us an answer. I would rate them a nine out of ten.

Positive

We previously used Veeam, and we made the switch due to the change in their licensing. They don't do perpetual licensing anymore. They're going to a subscription-based model, which doesn't fit with our business model.

It was straightforward. The setup is pretty intuitive. We don't need to follow a whole bunch of technical documentation in order to set it up at a site and set up the jobs. The user interface is friendly, and even for offline licenses, they provided a simple document on how to do that. That's straightforward as well. 

Its setup probably took 10 to 20 minutes.

We did it on our own.

So far, we haven't had any actual disaster situations where we've had to use the restore, but overall, we have got a return on investment. It's doing so far what we want it to do.

Its price is fair, and they still allow perpetual licensing, which is extremely important for us. They also have offline licensing.

I am not aware of any costs in addition to the standard licensing fees. In terms of the affordability of the solution for businesses with a tight budget, you aren't going to beat it.

I didn't have any initial expectations of the solution based on its pricing. I found Vembu by just searching for solutions, and I didn't really have an expectation, but it can be said that Vembu has been better than my initial expectation. Its price is definitely fair.

I tested at least five or six different ones. We're in industrial networking, which is very different from a corporate IT network. First and foremost, the thing that I liked about Vembu was the licensing model, and the second thing was its simplicity. All we do is backup and replications, and they have a product that focuses on that without having this big ugly interface with multiple options that we don't even use.

I haven't fully tested all the other bells and whistles on it, but for backup and replications, it's simple, and it does the job. It does exactly what we want it to.

I haven't had to test restores a whole lot, but initially, I tested it, and the restores were fine. They were what I would expect. They were not crazy fast but also not slow. It has not increased or decreased the speed of restores from our previous software. It's about the same.

I'm glad Vembu exists because, for bigger companies like Veeam, it's good that there is competition. That way they can't fully control this market. Vembu is a solution that is more friendly to actual businesses and small businesses.

I would rate it an eight out of ten.

We offer the solution to our customers, primarily SMBs, for backup and disaster recovery. Deployment models include both cloud and on-prem. 

The solution enables us to recover data instantly; depending on the data type and volume, we can recover within seconds or minutes.

It's pretty easy to add and remove backup jobs using BDRSuite, which, in addition to the solution's features, reduces the time we spend on backup management.

The product is very reliable and works well out of the box; many of our customers are buying it.

BDRSuite features a good dashboard, and Vembu is working on making its product more user-friendly, improving the UI, and providing better integrations.

We tested the product's Instant Boot VM feature for instant access to our VMs or physical machines after a crash, and it provided immediate access.  

The solution's UI and integrations could be better. 

We've been using the solution for five years.

The stability is excellent. 

BDRSuite is scalable. 

Integrating BDRSuite with existing infrastructure is quite easy; it doesn't take much time, and we always offer support to our customers. Deployment usually takes less than 15 minutes, and the first backup can be scheduled.  

The solution requires minimal maintenance. 

The product is affordable, and we focus on SMBs for our customer base.

Our company believes everyone should have a backup solution, so we provide affordable pricing to small and medium businesses, bringing them easy access to a backup tool compared to more expensive competitor products.  

I rate the solution nine out of ten. 

Regarding backup and replication scheduling options, we offer weekly, monthly, yearly, and multi-year options so we can customize the scheduling policy according to customer requirements.

We still use other backup solutions besides BDRSuite; we use different products for different use cases.

We use the solution to create backup repositories in cloud-based object storage, including Amazon S3, Microsoft Azure Blob Storage, and Google Cloud.