I was using Datto and Datto Cloud Continuity, which has a few other features, such as Datto SaaS Protection to back up mailboxes and stuff. Now, we can do all that under one platform.

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.

I've been using Veeam for quite some time with other customers. I don't know of other customers who use Vembu, but it's very similar to Veeam. I'm finding it quite similar to Veeam, which is good. Because if anyone wants to move to Vembu, and they've used Veeam, they will pick it up quickly.

I came across Vembu when I was searching for alternatives for Veeam with any type of image backup for Microsoft Hyper-V. I came across Vembu who had at the time was giving backups for up to three VMs on the free version. I was sort of growing with my VMs. I had three, but I soon crossed that amount. That's how I came across Vembu: I found there were cost limitations and was looking for an alternative to Veeam that did the same sort of thing.

We used a variety of other solutions. The BDRSuite user interface is much improved over a product like Microsoft Robocopy. We're primarily a Windows shop, and the time frame to copy is significantly improved by using the Vembu product over what Microsoft makes available.

We chose it because it has the ability to do a hybrid backup. It means that you can have a server at the customer site to make quick restores and still have the security of having a backup copy of whatever you backed up at the customer site. You're going to have that stored at another place. In case of a complete burndown or whatever at the customer's site, you would still have the data. That was the main reason for choosing Vembu.

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. 

Previously, we performed manual backups using a tool manager and implemented automated backups using Google Drive Sync. However, this solution proved ineffective, prompting us to switch to BDRSuite.

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.

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.

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.

We previously used NinjaOne but switched to BDRSuite due to its lower cost. NinjaOne charged $40 per terabyte, while others charged only $4.

Before BDRSuite, we mainly used a Citrix XenServer Host for around 20 Citrix VMs. We adopted BDRSuite because there was no automated backup mechanism. We needed a third-party solution, and there was a lot of overhead for hardware. Our customer needed backups for two SAP VMs. We got the hardware, VMware, and whatever they need to design a full VMware backup solution. 

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.

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.

Three years ago, we started the project to duplicate our infrastructure in every single aspect and needed to create daily backups of our virtual machines.

We picked Vembu two years ago, but switched to another solution which comes with integrated backup for virtual machines. This year, we start another project, which is to create offsite backups somewhere in the world. There were some requirements: the backup storage to be encrypted, the transfer to be encrypted, and not be so expensive. So, I looked at Vembu and Vinchin again. We were only satisfied with this tool (Vembu) when we started talking about money, because it was cheaper and could easily encrypt our non-dedicated storage.

Mozy used to be the major player in this market space. Mozy’s demise, with its purchase by Carbonite, left a void for a solution that could handle SQL cloud backups and meet small business needs. Vembu Cloud BDR has been filling this void for my small clients for a few years now.

I have clients that have used many solutions. For those who switched to Vembu Cloud BDR, most are coming from Carbonite (originally Mozy) or Backup Exec with local storage.

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.

No, we were not using any backup solution earlier.

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.

This was our first product.

We used Microsoft System Center Data Protection Manager, backing up to Azure cloud and we switched for two reasons: 

1. Vembu is less expensive.
2. It gave us more control as to where we keep that data.

We were relying on Microsoft Backups, which are just basic backups. We were trying to find something simple to use and easy to deploy, and that is why did proof of concept with three different products. The short list came down to Vembu. 

Currently, we are using mass technology, so we store from mass seamlessly. Then, we use the replication feature from VMware to remote that. So, we do double backup. Local backup and remote backup plus replication, which is very accessory resilient.

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

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.

This was my first backup solution.

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

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

I didn't use a previous solution. I selected this solution because it was the only one I could find for the cost that did what I needed it to do.

We were using Symantec Veritas Backup but it was an old-fashioned solution - at least the version that we were using. It was doing backups on the level of application, taking a backup of a database or directory structure or the like. We switched to Vembu because it allows us to back up the entire virtual infrastructure and then we minimize the downtime in case of an emergency or a failure.

We had a few concerns with our previous backup solution that we were looking to remediate.

1. The synthetic full was a forever backup, which over time would take up a ridiculous amount of space. With the Vembu BDR solution, we are able to configure a retention process of however many days we specify. This greatly reduces the amount of backup space used and ultimately saves us in hardware costs.
2. The time needed to maintain the backups was a problem. Our volume of failed backups on Vembu BDR is at least 50% less than our previous backup platform. This not only reduces our engineering costs but also increases the morale of our engineering team, as they are less stressed about failing backups.
3. Backup chains on our old backup platform had to be manually validated and cleaned up. I felt the risk of missing a file during this process was too high and could result in the inability to restore data. With Vembu BDR, the retention process is entirely automated within the software and requires no manual cleanup.

I purchased Veeam but my local reseller sold me only a minimal number of licenses and I was not told that I needed to purchase many licenses. So it was not cost-effective for us to have that solution installed here.

Previously, we had only local backup solutions at our customers on tapes. We had trouble all the time with tapes. This was more than 10 years ago. Then, we switched to drives to create the backups at our customers' sites, but all the time these drives were defect. So, we implemented a big server in our company, where we only have to do maintenance on one big device, not on all the small devices at our customers. We searched for a solution, and Vembu was our first choice.

The current version of Vembu is much better now than the previous version. The newer version is nice. It may not have as many features as the older solution, but it is faster and better to administrate. It is a good solution.

We did use a different solution previous to this. It was an onsite and cloud-based solution. With the cloud-based component, we switched because of the cost savings with Vembu, because we have two sites that we can leverage. The two sites are for disaster recovery, which is far cheaper than doing a cloud-based backup.

It's a very nice, easy, and economical solution. I'm coming from a Veeam background, but Veeam is a bit expensive. That's why we opted for Vembu. I tested out the Vembu trial version and found that it has a lovely interface, it's easy to work with, and it's something I can teach quickly. With Veeam, you must attend courses to understand it; you can't just show somebody. If I'm on leave, or I'm leaving the company, I can give anybody in my position a quick rundown.

The company I'm supporting now is not a corporate company or a listed company. The company I used to work for was a listed company and they were forced by the auditors to use a certain type of backup solution but it was expensive. When I started with this smaller company, they didn't have any backups. If something happened they would lose all their information. I was browsing the web looking for an economical but effective solution to meet the needs of this organization. I was surprised, as I had never heard about Vembu. But I checked them out and that's where the journey started with Vembu.

It's cost-effective for us.

Our basic goal is the backup of our infrastructure. We chose this platform because it's cost-effective.

Before Vembu I was using Symantec (which is now Veritas). The main reason I switched is the price point, the cost. Vembu cost me one-third of what Veritas was charging me for backing up the three servers.

We have used many solutions in the past. We switched to Vembu because of the Red Hat Virtualization. Our old solutions don't support it.

We had a solution before Vembu. We switched because of the cost factor and the deduplication.

This is the first time that we used this type of solution. We were quite happy with what we received.

Previously, it was a bit different because our environment had been a hosted environment. There was a different tool being utilized by the hosted provider. Our implementation of Vembu was a standup as we brought something in-house.

We went from a physical server to a virtual server. Vembu is cost-effective versus using VMware Essentials.

We haven't actually switched. We do use Microsoft Azure backup systems. We've used our own online backup systems. We've used in-built data center backup solutions a well, so there are a number of solutions. All of them have their weak points. The Vembu one is working and it's stable.

I didn't previously use a different solution. I really don't remember because when I took on this position, the solution was already out here. From my understanding though, we did use a similar solution. It really comes down to pricing.

Vembu was the first solution of this type. This solution was recommended to us.

The reason I use Vembu is to back up my virtual machines. You can back up virtual machines manually but Vembu does it automatically. I'd rather have it updated and backed up automatically, without my having to think about it, rather than for me to have to remember to do it every couple of weeks. This is just an automated way to do something that you should do, and that's the reason why I have it.

The previous process I had was to manually back it up, but now it's automatic and I don't have to worry about it.

We previously used Veeam. Vembu is much cheaper than the competitor, than the Veeam suite. That's why we went with it.

The prior solution took hours to restore a computer. When it was done it had an error that the support staff couldn't figure out. While they were trying to figure it out, I installed a trial version of Vembu BDR with no assistance from Vembu support as it was so simple. I was able to perform a backup and restore easily. And the most important item was the restore time which took 15 minutes.

We did not previously use a different solution. Vembu was selected after reviewing, then trying several different products.

We switched to another solution only because vembu were discontinuing the product, glad to hear they continued it and we came back on board.

Initially, we did onsite backups to tapes and then to hard drives. We switched because we wanted an off-site solution.

Prior to using Vembu I tried Acronis. That is what we were using before we dropped it for Vembu. The main difference I see between Vembu and the other solutions we've tried is that with Vembu, you don't need anybody to tell you what to do. Once you have done the installation you just look at the user interface — it's very friendly — and you can do things yourself without resorting to help from anybody.

If I want to back up a VM or all the servers I have in vSphere, I just drop the password of vSphere and it will do everything automatically for you. You just tell it what you want to back up. Acronis doesn't work that way. The guys on my team found Acronis difficult to use. In terms of user-friendliness, Vembu does a better job. With the click of a button, you know what you need to do.

Acronis would time out most of the time. If you have a slight network-connectivity issue, it causes a problem.

I found Vembu by searching online for free backup solutions. I saw a lot of solutions but that is how I started with Vembu, with their free version. I saw that it solved my problems.

We previously used a different solution. The ease of user feel is really the reason we switched over to it.

We were using VDP, which is a free application from ESX. But it's not very good, in fact it's awful, and it's no longer supported. We replaced it with Vembu and we're quite happy.

We were using Zenith ARCA. We switched to Vembu because of the licensing cost. Vembu is cheaper.

We did have a previous solution, but it was almost 10 years ago. We were not happy. The provider and the software didn’t work as we hoped. We called it “one-time-backup” internally.

I have used many solutions up until now. I switched to Vembu because of the price.