Our primary use case is for VM backups.
We were using an older version and just upgraded two weeks ago.
Download the Vembu BDR Suite Buyer's Guide including reviews and more. Updated: June 2022
Vembu BDR Suite is one of the most comprehensive, simple and affordable backup & disaster recovery solutions for the small & medium businesses. Vembu can backup VMware vSphere, Microsoft Hyper-V, Physical Servers, Workstations, Exchange Items, SharePoint Items, SQL Items, Office365, G Suite, etc. – and they can back that up on-site, off-site, or even to the cloud – not to mention that most of this are done within a single UI.
Vembu offers a wide variety of products such as a monitoring solution to centralize the monitoring of all of your backups as well as some which are absolutely free such as Desktop/Laptop Image Backup and the Vembu Universal Explorer for discovering application items within Microsoft apps. It is important to note that Vembu BDR Suite is offered as a single edition software for all businesses, unlike other backup vendors who provide editions with limitations based on the type of businesses.
Vembu has come up with its own free edition of Vembu BDR Suite by which users can backup unlimited VMs with minimal feature restrictions.
On-Ramp Indiana, DH International, Merrimac Solutions, Qsource Networks, TMI, help4IT, Tech North Solutions Inc. Learn more here.
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.
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.
The primary intended target for it was VMware backup and utilizing it in a VMware environment. It is a production, Active Directory, file server type of environment.
I am using the current version.
It hasn't improved the way our company functions from an operational standpoint.
The compression, encryption, and deduplication features are fabulous and great stuff.
What would have been most valuable for me, would have been the convenience and ease of doing the VMware backups along with the ability to provide a low-level, file level, restore all capability without having to structure the detailed Windows Backups association. So, an ease of setup with a granularity of a restore all capability without having to use a standard Windows Backup. I would need to upgrade my VM environment for this to work currently.
I investigated Vembu probably for the first time a couple of years back. I evaluated it in just a quick and dirty manner without any real followup on it. Subsequent to that, I have been more actively utilizing it for about a year.
It seems to be stable. No concerns about that.
Two people are required for deployment and maintenance of this solution.
My impression of the scalability is good. My scalability requirement isn't what some others might be, but the solution appears to be fully scalable.
It is being used in probably 80 percent of our environment. It's not a large environment. We probably won't scale out to the remainder. Eventually, the environment will be drawn in to the point where it's probably 100 percent of the environment that will be covered under Vembu, then that environment will be relatively stable. It won't change past that.
There are just a couple of us actually utilizing it. We're relatively small, so there are really just a couple of users for admin in there. It's a support environment.
From both the sales and technical support standpoint, they have been great. They have helped out to the extent that they can, but it hasn't been enough. There are things that they can't do and it's going to have to happen on my side (in my production environment). It was not clear from the evaluation level, when we ran through evaluation on it, that this was going to be an issue when we got to production.
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.
The initial setup was straightforward.
There were issues with the implementation because of incompatibilities between the tool implementation and our current VMware installation. So, it was an implementation issue that doesn't allow me to use it for VMware backup in the manner in which we would want to use it. That wasn't clear from the evaluation stage nor was it clear from the first utilization of it because it worked in the environment that it was being evaluated in. Based on that, we went ahead and made the purchase of the full implementation. At that point, it became clear that there would be limitations in that implementation that could not be overcome without doing upgrades to the production environment.
The evaluation and deployment took a couple of months.
To get through the evaluation did require support from from them. They were supportive and did provide that support.
There was an implementation strategy with some specific needs that were fulfilled by Vembu. It was an implementation strategy that included a consolidation and transition at the same time. It was a bit of a complex strategy and Vembu fulfilled it. Vembu was the tool of choice because of its ability to do that and because of the features in the suite. What was disconcerting was that it was able to do that part of it, but then when we went to put it into full production, then we encountered these other difficulties that hadn't been planned for or counted on.
To continue to do backups, we fell back to Windows Backup mode. We are still using the tool, but not in the manner in which we would have wanted. The tool purchase doesn't cover all options of the tool, e.g., if I go in and buy it, I have to buy it licensed for VMware Backups, not Windows Backups. At this point, what had to happen was they had to allow it to operate in Windows Backup so I could continue to back up the VMs, but in a trial mode. The trial mode has been extended once, and now we're reaching the limit of that extension again. Because I still haven't been able to update the production VMware environment such that the tool will operate in it in the manner in which I want it to operate, I'm stuck having to go back again to say, "Sorry, I need to extend this trial on it again." Even though I've paid, I'm still only able to operate in a trial mode. So, it's been difficult for us.
I've purchased and been licensed for one aspect of it, which is my preferred method, but the pricing and licensing will not work for the short-term and I can't draw back.
Yes, we did survey others. We didn't match up evaluations. We just didn't have a lot of resources for it. There was a desktop environment to a test evaluation.
We primarily went with Vembu for its flexibility and features.
You should never evaluate in your production environment, but make sure your evaluation is done as close as possible to your target.
We are not using it with Hyper-V.
I would rate this product in the high eights or nine (out of 10).
The primary use case is to be able to back up data outside of on-premise with the ability to restore as fast as possible. We also use Vembu NetworkBackup to selectively back up files on the file share along with our virtual machines. It gives us more control over what we can backup and restore, especially in the files.
We use this solution to back up our virtual environments.
All the features are valuable for different reasons.
The restoring of virtual machines and deduplication features are good. We save time by recreating or deduplicating a machine, as it done automatically. With one or two clicks, we can get something done. We are then pretty sure it is the same as it was before; it is a real duplicate. The deduplication features are useful for accelerating the transfers and when we have more than one version of a virtual machine or backup without taking up X time or space.
If we do a backup of a machine at some point and the server crashes, then we can restore this machine to a different server with the same settings and setup. We will just have to tweak one or two things, like the IP. Then, it is ready to go. This is not quite high availability. However, if we use the replication feature to make an exact copy of the machine, then we can tweak them to work together as active-active or active-passive. This can help us to save time because the deduplication is done automatically without errors and we have minimal changes to do.
I like also the feature where you back up a virtual machine, then it will run a startup and you can take a screenshot of the first few seconds of the bootup. This way, at a quick glance, we can determine the backup is bootable and whether the backup of the virtual machine will be functional or not. Sometimes testing the backup is something that we don't always do on a regular basis until we find out that something is broken. Then, we didn't know until it's too late. So, this feature is appreciated.
With the configuration of backups, there are a few things I would change with the UI.
One thing that I reported with the backups: When there are accentuated characters in a path, then we can't restore documents into a folder. There is a bug with the restoration and restoring files with accentuated characters in the path. Hopefully, they have repaired this because otherwise we will restore files and find out that they are not there.
A little over a year.
It is pretty stable.
I have just two physical machines with five or six VMs each. It is not that big of a setup. From a scalability perspective, I don't know if it will be good or not, but I believe it will be.
There are three users of the solution: a VP of operations, someone who is a jack-of-all-trades, and myself. There is no one with a specific skill set for this. It is really easy to figure out.
The technical support has been good. They have been dedicated to resolving issues.
Vembu was the first solution of this type. This solution was recommended to us.
The initial setup was straightforward. It was easy to install. There are not too many options and it was ready to go almost out-of-the-box. We have a really simple setup so the deployment took an hour or two.
We have seen ROI based on confidence and time saved. We save a few hundred dollars a year.
We have the enterprise version with two server licenses.
Take a look at the pricing and licensing closely. When we installed the BDR disaster recovery server, which is the duplication of the backup data on one server onto a second one where the backup data resides, it was not clear that this DR server needed two other licenses. These licenses were to back up the copy of the first backup server that had two licenses for the two physical host that it was backing up in the first place. Moving files around to a second DR server, why would I need an extra two licenses? I don't know if it's to make money, but it was not very obvious and I had to abort the project from there because I didn't plan to pay for extra licenses to copy data of the first two physical servers. I also didn't understand why it was needed. Hopefully, they will improve the explanation in the documentation for this.
I compared different vendors' functionalities, our requirements, and price. We chose this solution because it was cheaper and easier to use than Veeam and other solutions of this type. Though they are not easy to compare as they all have different licensing models.
Make sure you have a clear view of your architecture and how you will be implementing it. Decide upfront which site will receive the backup and which site will do the deduplication of the backup's redundancy. As mentioned, I started to do some backups on the second office site and wanted to move the backups on to third site for disaster recovery, but I figured out that it would be better to install the backup server on the third site and the deduplication on the second site. However, just exchanging their roles was not that easy because I was missing licensing and backups were already running. I would recommend to ask questions, figure out the licensing model, what needs to be installed where, and their best practices. For example, if I have to do things again, I would do things differently.
I would give the product a seven (out of 10).
We use it to back up ESXi clients, so mainly Linux based or Unix based servers on our ESXi host.
We use the solution to back up our virtual environments (VMware). It has been good for our organization so far.
It makes it possible for us to back up our Unix machines without installing a host, client, or any client software. It gives us some peace of mind in regards to those servers getting backed up.
The number one feature is that we can back up our servers without having to install a client. It is the only reason why I have this product.
The user interface isn't that good. I don't think that the product is user-friendly. Comparing it side by side to Acronis, I would say to Vembu, "Hey, you could make your user interface a little easier."
Vembu will tell you the next scheduled backup, but it doesn't show you the last successful backup. I would have them include a column under "List of Backup Jobs" and have two other columns which say, "Last Successful Backup" and "Next Scheduled Backup", because you don't know now if it's backed up successfully. It just says, "The next scheduled time is this." You don't know from looking at that pane of glass when the last time it actually happened without digging further into reports.
Two years or more.
It is stable. I haven't had it crash or break on me.
I don't think we've actually had a reason to restore a machine as it's never failed. We've never had a server fail. The only thing that it has done for us is give us peace of mind that our server is backed up.
Everybody is impacted if one of these servers failed. The only way we could get it back up and running was to restore it from a Vembu Backup. It would impact everybody if the servers went down, so approximately 3,000 users would be impacted if the backup wasn't successfully happening and we needed to use it.
We haven't had reason to scale it up to back up anything else. We aren't really using the product to its fullest capabilities. I think it has a lot more that it can do.
I am the only user using it, as we only use it for backing up our servers.
I do have plans to increase usage.
Every time I have called, I've had good tech support.
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.
It was pretty easy to set up. The initial setup was probably only 15 minutes.
Our implementation strategy was to make it so we could back up our VMware clients. That was the whole purpose of the software. We don't use it for our Windows Servers. For that, we use a different product. However, we couldn't use the other product on the Linux and Unix space machines because the other software requires that a client be installed.
We bought it directly from Vembu and installed it ourselves.
This solution helps us deliver an enterprise level data protection solution and reduces budgets. We are saving $6,000 every three years versus having another product.
Backups are an insurance thing. This is a life insurance policy to make it so if our servers failed, we would have something to get them back. Since we haven't had a server fail, it is just like life insurance. While it has cost us money, it has given us peace of mind that if we needed it, then it would be there.
The pricing is very good.
Our license is about to expire on it.
We did evaluate some other products before choosing this one.
We also use Acronis Backup Advanced. The way that Vembu backs up to a backup drive, it uses a pool of drives to back up. Whereas, Acronis backs up to just a single file. You can see that individual file on its own. You can browse to it and see that the file that has been saved. It also says the last successful backup it did.
Vembu's user interface isn't as easy to use compared to Acronis Backup Advanced, which has a better interface for me to be able to see what's happening.
I haven't found a competitor who does as good a job for the money.
This is a good product to choose if you are in the same situation as we are in.
It does do compression and that works fine.
We don't use Hyper-V.
I would give it a five out of 10, because I think that it could use some polishing on the interface for the client.
We use it for backing up VMs.
We are using it with VMware and the benefit is that we have reliable backups.
It's pretty basic backup stuff. I set it up and it just runs.
The compression, encryption, and deduplication features all work fine.
The system died twice and it was apparently the result of corrupted disk sectors. I tried to work with tech support to fix it, but they essentially gave up. So twice, I had to rebuild our server. I don't know why that happened and tech support didn't seem particularly concerned about figuring it out. That's my only complaint.
We've been using Vembu BDR Suite for about a year.
It did completely die twice and couldn't be revived. If that happens again, we're probably going to look at another product. My only concern is the stability.
We're not likely to be adding too many more VMs anytime soon. So I don't have any way of judging the scalability. We might deploy it on another site. We'll see about that.
Technical support is good but the problem I have is that I often can't understand the technicians because they have extremely heavy accents, and that makes communication kind of difficult.
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.
The initial setup is simple. It didn't take more than a day or so, including testing. I got a trial version and decided it did what we want it to do and then I just set it up.
The solution provides us with enterprise-level data protection.
The pricing is quite reasonable.
If you can't afford Veeam, which is very expensive, I would recommend Vembu.
Vembu is used by me and another system administrator. That's it. We manage it, but it only requires one person for deployment and maintenance.
Our end-users don't know it's there.
We use it to backup VMware virtual machines, so I'm backing up my VMware environment. My product is for Windows Server Backup.
We are a small business. We don't use the enterprise version of the solution.
It has improved our business continuity.
We have used this solution to recover from a few incidences.
The firewall backup is the most valuable feature. We need it sometimes when we recover a single file.
The compression is the most useful feature for me.
The product's stability needs some improvements.
The support is a bit slow in resolving an issue. It takes a long time to recover.
The solution is 90 percent stable. It is running well. The availability is good.
Two or three employees are needed for deployment and maintenance of the solution.
I only have two servers. I don't test other servers.
We don't count our users for this solution as it is a backup service.
I would rate the technical support as eight or nine (out of 10). I would like them to improve their response rate.
This was our first product.
The initial setup was neither simple nor complex; it was intermediate. It took four hours to set up/deploy. We implemented it into a very simple environment (Windows Server Backup).
We deployed it ourselves.
We have seen ROI with Vembu. The solution is worth it based on the few times that we used it for recovery.
We tested three products. One of the other products that we evaluated was Altaro.
We chose Vembu because the compatibility was better.
I would definitely recommend Vembu. We have been mostly satisfied with the solution. We plan to keep using it.
Overall, I would rate the product as a nine (out of 10).
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.
I use it as a backup solution for our VMware system.
I get my backups done. If I don't get my backups done and something goes wrong, I lose my job. The benefit of using it is that I keep my job.
Vembu helps me deliver an enterprise-level data protection solution and reduce budgets.
The cost is one of the most valuable features.
The problem that I had getting this up and running was that when I put in a backup plan, and wanted to run that backup plan, that plan had to go onto the server that it's going to do the backup on, and it had to pass on credentials. It would be nice, when you create the credentials for logging on to the server, if it would immediately verify that those credentials work. What ended up happening is I'd have to wait until nighttime to really figure out whether those credentials were valid or not. That prompted me to call support.
We've been using Vembu, as a company, for about three months.
The stability has been okay.
The scalability is fine.
I'm the only one in our organization who uses the solution and I'm responsible for its maintenance.
The problem that I really had — and it was not the product — is that when I called in, the phone system is a negative five on a scale from one to ten, where one is the worst. They wanted me to leave a message. When there is a problem with the product and you call in, you want to talk to somebody or wait to talk to somebody, not leave a message. If our system is down and someone says to me, "What's going on? Our system is down. Our company's not running. What are you doing?" the conversation would go something like this:
"I'm waiting for a phone call back."
"You're waiting for a what? A phone call back? You get on that phone and get those guys on the line."
And he would use some other choice words before the word "phone."
Their response was quick, but I'd rather wait on hold. I'll listen to music. In that same scenario where someone asks me what is happening and I say, "Oh, I'm on hold. I'm waiting for support to respond to me," they would say, "Oh, okay. That's good. You've got it under control." It's all perception. Have you ever run a program and it just sits there and sits there and you have no idea how long it's going to take for the update to finish? A minute becomes an hour. It was like that. Their phone system is horrible, terrible.
The support itself was good. The technician was good. However, they all seem to be from India and language could be a problem, although I have not found that to be an issue so far. I would like to see more support from the U.S. I'd rather speak to someone from the U.S. than someone from another country. That's just a preference: "Made in the USA."
The initial setup was pretty easy. I'm going to reconfigure it to be loaded onto the actual VMware machine, but I just don't want to do that at this time. Right now it's running as a software product. I want to run it closer to the VM machine itself, as a fixture associated with it.
The deployment took about an hour. Our implementation strategy was simply to get it to work. We needed the backup.
I did it myself.
It does what it's supposed to do.
The pricing is fair.
I did some research and I looked at some reviews.
I bought it for doing a backup using VMware vSphere and just started with VMware. But I use another product with our legacy system, a product called Acronis. If I were to compare Vembu with Acronis Backup I would say it's comparable, but it's more cost-effective.
If you need phone support, don't buy the product.
I would rate Vembu, overall, as a five out of ten. It would be a ten if they fixed the phone system. I have to hammer that in.
We use it for our file server and database backups.
It hasn't improved the way our company functions that much because we were using a backup which is about the same as Vembu.
The restore feature is the most valuable. It's easy to restore.
We've been using Vembu for less than a year.
It's not that stable yet. Every two weeks, my backup will stop and I have to check it. Sometimes it can be fixed by a restart and sometimes I need support to make it work.
It's scalable. It is being used extensively in our environment, but there are no plans to increase usage. During the season, we're around 200 employees and we back up about 4 TBs.
Support is very important. But sometimes they respond to me four hours after I contact them, maybe more. I would like them to improve their response time. Also, their time zone is different from US/Canada.
Overall, support is very good, but their reaction takes a while.
We were using Zenith ARCA. We switched to Vembu because of the licensing cost. Vembu is cheaper.
The initial setup was straightforward. It's just "click" and "okay."
The deployment took an hour or two. The installation plan was to store things locally. We have an online license for the offsite service, but we don't have the proper device installed yet. It requires a more sophisticated machine.
Initially, I worked on it myself. But, due to some errors, I asked support to reinstall it, to fix it. They were good.
We have seen a return on investment from going with Vembu.
The pricing is pretty normal. It's not too hard to license a server. It's pretty straightforward. If you need four servers, you just acquire four.
We evaluated Ipirius. We went with Vembu because of its features. It's similar to what we were using previously.
If you're looking for a not-too-expensive solution, use the Vembu BDR Suite.
There are three people on our team who can access the server, who can actually operate it: an IT associate, supervisor, and system admin. In terms of maintenance, I ask their support to do it.
Overall, I would rate Vembu at seven out of 10. It's not perfect yet. It doesn't give me confidence that it will run 24/7.
I've actively been using the Vembu product for backups. It is being used to back up the Hyper-V environment that I have. If the hypervisor has hardware problems, e.g., all the storage dies, you can run up a new Hyper-V server, then restore the VMs onto it. It doesn't take that long. So, you are up and running within several hours of restoring it. Also, you can restore individual files. Therefore, it's a full VM-based image backup as well as a file level backup, if you want to restore the files that way. There is also an option to restore AD users, computers, and contacts, in addition to Exchange databases at the brick level.
I'm mainly working with home-based customers. I don't have any business clients yet.
It's on-premise, not cloud-based at the moment. I'm planning to possibly have replication to an external site since my Internet link is much better now. That will be done in the future. I'll probably replicate to a private cloud somewhere.
The main thing is recovery. I have had a lot of hardware failures quite recently due to power fluctuations and overheating. Therefore, I am using it on a lab environment where I test things for customers. It has helped to reduce time. For example, one of the hypervisors died, so I loaded up another non-clustered machine and just restored the previous night's backup, then the VMs worked fine.
I am able to run Vembu on Windows NAS, which is beneficial. It does install on a Windows-based NAS. You can have the server running from the location where you are storing backups. You don't need a separate server for it in this case. This is only available with the licensed version.
The image backup on VM is the most valuable feature.
You can restore to another location or another physical/virtual machine. You can do P2V as well as V2V. That is what I have found most useful.
The encryption feature seems okay. When you change versions, then I have found it to have problems. An example: I was on version 3.9, and I had an encrypted VM. It was restored from version 4 onto a newer Hyper-V server. So, I went from maybe a 2008 to 2012, and it was restored and then it didn't restore, and because of those changes, it didn't like the encryption. But, generally if the version and the hypervisor version are the same, then you shouldn't have any problems with it.
There was one issue though with the hardware IDs. When I went to a different version of Hyper-V, the hardware IDs weren't restored and the machine got two new IDs. The preliminary unique IDs weren't restored, so I had to reactivate programs. That was the only downside.
I have been using it close to two years.
The stability has been okay. If you put too much load on it, then it does become a bit unstable. The server that you are using does matter. Whenever I've tried to contact the tech support, they say upgrade to the latest version. The problem with that is the old backups need to be all done again because it appears that on each version upgrade the old backups no longer continue. They need to be done as a full backup again.
I haven't had too many issues with failed backups. There were some backups failing, but I found that was just before the drive failures. So, there were multiple drive failures which caused the problems, but the product itself has been okay.
At times, when I have done a restore or mount multiple images at the same time, it has become a bit unstable. However, I just needed to restart the Vembu service, then it started working again.
It's fairly straightforward to restore and do backups. It keeps on running. There is not much in terms of maintenance required. It has recovery points that you can retain, so it's pretty much a send and forget solution. You can have it running indefinitely.
It appears to be scalable. If you have a cluster, it will back that up. Also, if you run out of storage space, then you can add more storage to it. So, you can add an additional storage pool from a USB, then allocate that to be used. For example, if you run out of space on one NAS, but that NAS has access to another volume, you can add that as another storage pool so you can have multiple storage pools.
The technical support's response time was okay. I had to wait several hours for a response, but that was probably because of the time difference. All in all, it was quite acceptable and sort of normal.
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.
It was fairly straightforward to install and get running. However, installing the agent on the hypervisor was a bit tricky, because the version that I was using is just a core version. So, it's has no GUI. In that version, there were some special instructions, which we did have thankfully, and there were a few extra steps that I needed to take to install the agent. What normally happens is the agent can be pushed out from the BDR Server, but that wasn't working on the core version. The initial setup was not relatively easy, but not relatively hard, it was just in-between.
The deployment took an hour and a half.
The implementation strategy was to try and get the BDR Server running to sort of simplify things. Then, we could have another server just as a backup server.
I deployed it myself. I did use some documentation that they had. So, it was more or less trial and error. I was running a Windows OS on the NAS, and they didn't exactly say that they supported it. They just said, "If it works, it works. If it doesn't work, then you'll have to get the full OS because mobile NASs come with a Windows Storage Server." They didn't really certify to run on that. However, in the end, it did work quite well.
When one of the VMs dropped off, I was able to recover fairly quickly. Therefore, I have noticed a return on investment. It has helped to reduce at least a day's worth of downtime. Which, if I didn't have the image backup, I would be loading all those VMs again. Some of them did take time to build. So, a case per a day if not more, because the other option was just to rebuild the whole environment from scratch if I didn't have those image backups. So, about every six months, I am saving several hundred dollars of downtime.
I was using their free version, which had limitations, so then I went to the licensed version.
It has actually benefited my operation a fair bit. VMware requires a special hardware while Hyper-V runs on pretty much anything. It doesn't require any special hardware, so it saves a bit of money. Because Vembu does Hyper-V backup, there is no limit on how many VMs you can have. The newer version has a 100 VM limit on the single license, which has been greatly beneficial, because on one host a 100 VMs is a fair bit.
The licensing model is quite complicated; it's not simple. An example: If you have a physical server, you have to pay more for that license than you do for a host. It could be running several VMs and that could be a server VM as well. Then, for web station machines, there is no license for those machines and they have no desktop OS - the free version has all this functionality. Their license model needs to be looked at and simplified.
At the moment, I am doing Vembu for one host. My costs are about $25 USD a month for a single host up to 100 VMs. It's just the license per host with one CPU, but if I did choose offsite cloud replication, they do charge for the data. They charge per gigabyte, or something like that. They have plans.
When they changed to the newest version (4.1), they have more VMs allowed on the free version. Before, there were only three VMs allowed on the free version, and if you needed to back up more than three VMs, you had to get the paid version. Now, you can have up to 10 VMs on the free version. This was when I was just crossing over to 10 VMs or was very close to it. If I had known, then I would've not paid for the monthly licensing cost. I've since crossed 10 VMs, so this doesn't matter to me, but it will matter to someone who only wants to back up a few VMs. E.g., if they had five VMs and were forced onto the licensed version, then in the update, the free version could back up 10 VMs.
I know that the normal Windows Backup won't backup the VMs if you're using it in a HA Failover Clustering environment. If you're using it in a clustered high availability environment, it will back up the VMs. That is the main difference I found. But, in terms of backing it up, Vembu does support the HA Failover Clustering, so it can back up when you have VMs on a Cluster Shared Volume. It can back up those VMs unlike the built-in Windows Backup, which doesn't support that.
I evaluated Altaro but there were some requirements that you needed for install on the Windows-based NAS. That was my main issue at the time. Because of the way I planned to have the backup solution running on the Windows-based NAS, a few of the solutions wouldn't install or had problems.
A lot of the other people that I know use Veeam, StorageCraft ShadowProtect, and Kronos. Not too many people that I know use Vembu, but I found it to be the equivalent of Veeam in some ways. It does work very similarly in its functions.
The pros for Vembu vs Veeam are Vembu's license cost for a host seems to be much cheaper and Veeam might not run on certain hardware. The Veeam Backup & Replication Server has some hardware requirements that I could not get to install on the net, but Vembu installed quite happily.
The cons for Vembu vs Veeam are Vembu's licensed model is a bit complicated, and if things go wrong in Vembu, there is less support out there. You do have to contact Vembu's support to have a look at a problem, whereas with Veeam, there is quite a bit of knowledge out there in terms of online forums.
I have learned just how important backups are.
My advice would be try and implement it on virtual environments. Don't implement it on a physical environment because the licensing costs would be much higher. You will have less options for recovering VMs. It would be wise to have a cluster. Also, the BDR server should be well spec'd. You can run on the minimum spec, but it is recommended that it has some definite amounts of RAM on it.
I am planning to use Vembu to work in VMware, but I have not done that yet. After I pick up some customers, I might try to push it out to them in their VMware environment. At the moment, it's just Microsoft Hyper-V.
I don't really use the deduplication feature.
I would probably rate the solution around seven and a half out of 10. It missed out on a few scores because each time when you upgrade the version, you have to do all the backups again. That's why I didn't give it a 10. If it didn't need to do all the backups again when changing the version, then I would have given it a 10 easily.
In the near future, if Vembu stays the way it is now with its licensing costs and everything else, then I will continue to use it and expand on it. I will try and push it out to some of my customers as well. A lot of customers just use Veeam or Kronos at the moment and may switch for the cost savings.
We back up servers and workstations.
One of the things that Vembu does for us is, of course, create high-availability for backups, which, if we came to a worst-case scenario, is one of the reasons we selected it, with the high incidence of ransomware. Should we be hit with ransomware, optimally it would allow us to be back up and running pretty quickly.
The solution helps us deliver an enterprise-level data protection solution and reduce budgets. It's difficult to estimate how much we have saved, although I know we have saved. We did do a cost analysis up-front and we saved money compared to our prior solution.
The most valuable feature is the ability, from a console, to manage the different computers to be backed up.
In addition, I use the encryption regularly, and the deduplication as well, but not extensively. The deduplication is very handy. It reduces the size of the backups, which we can then upload to an online storage platform. That's one of the reasons I selected it.
We've been using Vembu for about nine months.
I have had issues where it was working and then it stopped and I had to diagnose what had changed or gone wrong to get it back up. While it is generally stable, I've had issues with stability. The last time we had this issue was about six weeks ago.
It's very scalable. As we add workstations, as we grow, we'll generally use the solution on those new workstations.
Customer service could be improved. There seems to be a delay when trying to get to someone for customer service issues. Usually they'll tell me to send an email. That is one area that I would like to see improved.
I had pretty good technical support while we were evaluating the product. Since then, it has not been so good.
We had a solution before Vembu. We switched because of the cost factor and the deduplication.
It was not particularly straightforward. I had to contact customer service in order to complete the initial set up. The deployment took us the better part of a day to complete everything, because we had to reach out to customer service.
We started out by testing it on a workstation and, once we were satisfied that it met our needs, we deployed it to the servers and to the other workstations.
We did it in-house.
The pricing is pretty reasonable.
We looked at Macrium Reflect. That was another solution that we used.
It's a robust solution. Evaluate it first in the environment and ensure that it actually satisfies your needs. It's a fairly cost-effective solution. For us, it has assisted in developing a robust backup strategy of keeping a backup in-house. We back up to a NAS in-house, and then we try to do an online backup off the in-house backup, so that we always have a remote copy of our backup. So it's been a pretty robust solution.
We have about 25 workstations that we're backing up. There are two of us, my IT person and me, who handle the deployment and management of the backup solution.
I would rate the solution at nine out of ten because customer service could be improved. I don't have a specific problem with the product. In our experience, the initial implementation could be easier. The product itself, once implemented, gets the job done. If it was divided up, I would give the working product a ten. But the initial implementation, from our experience, because we needed to have customer service log in to our system and walk us through, I would give a seven. And I would give customer service a seven.
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 back up all our customers' files. We back up only files, and maybe some databases. However, primarily, we are backing up files on our own server.
We are currently using the updated version of this product.
We can create a backup contract with our customers and software using this solution. We can backup the software here in Austria, because we have new rules here in Europe, since last year, which are very strict for data protection.
The network solution is the most important feature, because we have our own backup server and are doing file backups for our customers.
The compression, encryption and deduplication features are important. If we can save space, it's okay. The encryption is also very important, because it is in our contracts. It is a must. We have to use it for our customers.
We have not been able to move our backups from one drive to another one. We can only create a storage pool. However, if we want to change a drive, it is not possible to delete one drive as long there is data on it. For this, we have to call the support. While they can solve this, it is not out-of-the-box.
If there is a failure, the logging for the backups could be better.
Sometimes, I miss some features from the old solution.
The stability is very good, but it is not perfect. Sometimes, we have to restart the server, because of updates. I have to sometimes manually restart the services. When it is running, it's perfect and nice.
When we have to restart the server, then we have some troubles with the services from Vembu. We have to manually restart the services, and afterwards, it's okay.
The software solution is okay. While it has some bugs, it has been okay in most cases.
It takes me two to five hours to do maintenance per week.
We have small customers. For them, high availability is not a priority, only file backup is important. They are very small. They have around five employees. Also, because our customers are not asking for this, we do not offer high availability. We do not have the resources for it, and our servers are probably not big enough for this type of solution. We only offer the simple file backup.
Our biggest customer has about 20 employees. However, they have a huge amount of data.
We have three users in our company, but we represent about 30 companies. All three employees in our company are systems engineers. We do the backups, deployments, and maintenance.
At the moment, we do not accept new customers because we do not want to grow. We are happy with what we have. We have a lot to do. We have had good customers for a lot of years, and that's perfect.
They have very good support. I always get an answer quite fast when we have trouble. When we write an email, on next day, we will have an answer. This is really good and unusual. I like the support.
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.
The initial setup is easy and very nice.
The deployment was not a big project. The backup service was running in a few hours. Then, we have only to implement clients at our customers.
The process is quite fast. We set up a back up server, then alert the clients. We use a Windows Server with a lot of storage capacity. There is no need for an implementation strategy.
We had an old solution with the old clients. We moved them step-by-step as individual customers to the new solution over half a year.
Only from within the organization was it a little tricky, because we had to implement new contracts for our customers. It was technically a little different with the old solution. We did need a new server. Also, we had to move all our customers to the new solution step-by-step.
The return of investment was very fast, within half a year.
The best thing about the product is the license management. It is a true managed service provider solution. It has a good price. The licensing is quite flexible, which is one of the most important things for us.
The high availability is too expensive for our customers.
I did a lot of evaluations before choosing a product. We tested about 20 different products. Vembu was the best. Some of the other solutions were also very good, but were extraordinarily priced (too expensive). Others, I didn't like the licensing, software, or were only cloud solutions.
Vembu has the flexibility with its licenses and is a real managed service provider solution. My feeling is that Vembu understands what a service provider needs, not only local administrators. It is one of the reasons that why we chose Vembu.
We haven't found another solution for its price with all this features.
I would recommend the product. I already recommend it to our partners. It is a really good solution. I like the product. It has good support. For small companies, it's the perfect solution.
We do not use virtual environments. We have done this in the past, but we do not implement virtual clients anymore since we have only small customers and virtual appliances are now on cloud spaces. So, we do not have virtual servers at our customers.
We have used Hyper-V, but it was not beneficial.
We use it purely for Hyper-V backup. It's used to protect our entire server estate.
Our previous backup solution was cloud-based rather than being on-premise, and quite often our backups could lag three or four days behind. We are now looking at having a restore point as low as 30 minutes, where the backup has never been more than an hour behind the live solution.
We use it to back up Hyper-V, and the key benefit of that is purely one of data security and dependability.
The most important features are the backup and the availability of the Universal Explorer.
The in-transit compression is great.
The deduplication could be better. It doesn't give the level of deduplication that I would get with a product that's stored in a more standard file format. I would prefer to be able to use a non-deduplicated store on a third-party deduplicated medium. But as far as the compression and the general structure go, I have no problems with them at all.
Having some flexibility for the backup to be stored in a non-deduplicated fashion so that we could store it on more high-efficiency storage would be helpful; either that or improvement to the data deduplication. The amount of storage it requires for the backup store is excessive, compared to other solutions.
It is absolutely stable. We've had no issues. It's never missed a backup and we've had no issues with data stores, even when we had an issue with the hardware which one of the data stores was on. That was very quickly recoverable and we didn't miss a backup. We've not missed a backup since installing it a year-and-a-half ago.
We're a very small business. We've only got two Hyper-V hosts that it's covering. I imagine the scalability is probably quite good, but I have no other comment on it.
Technical support is fantastic. Responses are normally received within about an hour to an hour-and-a-half. Where something has required escalation, it's been completed within a few hours. We've had very little contact with support, but where we've needed it the response has pretty much been a fix the first time.
We used Microsoft System Center Data Protection Manager, backing up to Azure cloud and we switched for two reasons:
The initial setup was absolutely straightforward. We had an issue, but that was caused by a problem in our Hyper-V environment, rather than Vembu itself. That was dealt with within a couple of days by Vembu support.
The deployment took about three days. It was really fast.
In terms of our implementation strategy, we were moving from Microsoft System Center Data Protection Manager to Vembu. We are quite a small business so we only have two Hyper-V hosts to configure. The strategy was to install, test, and then remove the Microsoft product. It was a very straightforward plan, a very straightforward strategy. And the aim in doing so was to enable a more rapid recovery time.
We did most of the work ourselves. We didn't use a reseller at all, it was so easy to deploy.
It's only saving us about £2,000 to £3,000 a year. But in our IT, that is a help. Our IT budget is only about £250,000 a year so it's saving us one to two percent of our IT budget.
Regarding return on investment, the value of a backup system comes up when you actually need to restore it, so up until the point of restoration a backup system is purely a cost on your P&L, rather than being of any asset value. We've not had the requirement to restore, so the only cost-benefit we've had is in the cost savings over our previous solution.
The pricing and licensing structure are spot on. I don't think there's anything out there in the market that does either the licensing structure or the pricing structure better.
We evaluated Veeam but we selected Vembu because the feature set was what we needed. We didn't need to use Veeam's full recovery, full replication suite. Because of that, our costs are about a quarter of what they would have been with Veeam.
Go ahead and give it a try. It's worth the evaluation and certainly, with the restore options and the Universal Explorer option, it's competitive with things like Trilead and Veeam in terms of backup. Personally, I don't think it's as good as Veeam if you are looking at replication and high-availability but, other than that, for straight backup, I don't think there's anything in the market that's better.
There are only six of us in our IT department who use it. Nobody else has any real comments on it. It's something that sits there and does its job, and does it well. In terms of deployment and maintenance, two of us are responsible for ensuring the backup is operational and maintained.
It's used to protect our entire server estate. It's not a very big server estate, but it is the entire estate. There are no plans to extend its usage. There's nothing to extend it to.
I would give Vembu a ten out of ten. I've evaluated other products. I don't think anybody else has any advantage, certainly in terms of backup, over what Vembu provides. If I were to mark it down to a nine, it would just be for the lack of flexibility on the backup storage option.
We're doing onsite local backups as well as offsite DR of our VM infrastructure.
Realistically, it is no different than the previous backup solution we were using, other than it costs less. As far as workflow is concerned, it hasn't really changed.
We use it to back up our VM infrastructure, but as far as benefiting the organization, it's just a guarantee that, if we go down, I can spool it back up at either location. That's the biggest benefit to this sort of backup solution, instead of files on another drive.
This is a part of our enterprise backup solution. It has saved us a considerable amount of money.
The agentless backups are the big selling point on this, as well as being able to send out across sites so that I can do a restore at either of our two locations.
The compression is good. As far as the encryption is concerned, I'm glad that it's there for site to site. We don't necessarily need it just because of the way that we're connected, so it's not really a selling feature, one way or the other.
The only place where I would really want to see improvement, out the gate, is more granular scheduling. With the previous solution that we were using, you could pick different times based on different days. Right now, with Vembu, I just have every X number of hours on these days, but if I want to do an offset or to only do two backups on Friday and Saturday - versus whole hourly incrementals during the week - I don't have that granularity. That would be something that I would be looking for.
With the exception of when we required that initial hotfix, it has been extremely stable.
Scalability is part of the reason why we got it. The opportunity to push the offsite data recovery to multiple sites, instead of just, one was a big selling feature for us. Currently, we are a two-location organization, but we want the opportunity to be able to scale up and pop another one of these units down to another location and have them replicate freely between.
The tech support is phenomenal. We were not expecting a fix to happen as quickly as it did. The response time, through everything I've experienced so far with them, has been within an hour.
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.
We had a few issues with the initial setup that were solved by support. The actual installation of the software was simple enough. However, there was a bug. We required a hotfix to get two of our larger backups going. But that was remedied within a few days by their engineering team and it has been working flawlessly since. With the exception of just waiting for that to go, it was fairly painless.
The deployment took roughly a week. But we were also figuring out a bunch of different backend stuff as well, so it wasn't a week on the software package in particular. It's a part of a larger backup solution. To get the entire thing up and going was about a week.
In terms of implementation strategy, we did build-outs on separate servers so that we would have dedicated servers that would be doing the backups, instead of having the BDR suite reside on our VM infrastructure. The reasons for that strategy were
It was completely segregated, just to keep the business continuity intact as much as possible.
We were in trial for about a month, and the actual deployment has been in place for about a month.
We did it all in-house.
Our return in investment for this solution, including all the additional hardware that we chose to purchase for it, including hard drives and the server host that it runs on, as well the subscription, means it will be about a six- to seven-month return on investment for us.
The subscription model that we're signed up for is very good. The only thing that is something of a sticking point is the fact that you can't do PO-based licensing. It's all just credit card. That required a little bit of a sell for management because typically everything we do is PO-based and our previous solution was PO-based. That would be the only thing about the subscription service that we didn't really enjoy.
We were really only looking at Vembu. It was brought to our attention by a reseller we had used for another product, as the backup solution that they typically push for clients. We thought we would take a look at it and, after we ran our trials, we found that it would work for us.
Have a separate backup appliance, if you can, a separate, physical backup appliance so that if your host goes, your backup doesn't go down with it at the same time.
As far as the encryption is concerned, I'm glad that it's there for site to site. We don't necessarily need it just because of the way that we're connected, so it's not really a selling feature, one way or the other.
We don't use Hyper-V. Our Vembu is working with EXSi. I have not had to do a full server restore, yet. But I have had to do restores of incremental points in time, for certain files. We have tested the restore feature of the entire guest VM. If I have a server go down, I have a lot of people who can't do work. So a fast restore is critical.
It's just our core IT team that is actually using the solution. There are three people who have direct access to it, but we serve a larger number of users in our organization. However, they don't see anything as far as backend or backups are concerned. As far as they know, nothing's changed, nothing's different, it has no effect or impact on their day-to-day operations.
For deployment and maintenance, now that it's set up, there's not much to do on it, aside from doing checks every so often to ensure that the backups are still happening.
There is a potential use case to increase usage, such as doing some critical workstation backups with it. However, we are not doing that at this time.
I give the solution an eight out of ten. Everything has some room for improvement. The more granular backup scheduling is one of them. There was a slight hiccup that we weren't really expecting, when we were first looking into this, where you can't do a restore while a backup is in process. That was a bit of an annoyance at first, but once we got an explanation from their technical team as to why it's designed and built out like that, it made more sense. It's just one thing that I realize they can't fix but it would be a nice to have.
The primary use case is for backup.
I am using the latest version.
What we like best about the system is the use of its operation and the backups versus what we had to do earlier. We use it to back up our virtual environments, mainly VMware.
Everything is happening in the background without running any commands. It runs seamlessly in the back, so this is a great achievement. This is also a great convenience for this organization. Previously, somebody had to do it manually all the time.
We are now using it 24/7 because it is serving as an online backup, and very soon, the DR will activated on the product.
We invest in the backup so the continuity of the data is not affected.
It takes the sever directly from your VM environment.
The compression, encryption, and deduplicatuion are quite useful.
We are still exploring its features, but we want to see more features that we desire over time.
It is fairly stable.
At the moment, we have an administrator whose responsible for the device.
I am the only person handling the device. It is very straightforward, We have just one person in the organization, a consultant, and I don't go to the site on a daily basis.
I am happy with the technical support. Whenever I have contacted them, I have received the results that I was looking for.
This is the first time that we used this type of solution. We were quite happy with what we received.
The initial setup was quite good. There were no major hiccups.
Even the support teams supported us, which was quite helpful. The deployment took a few minutes.
I am the consultant. I recommended this solution to my client.
I think this solution will help us deliver an enterprise level data protection solution and reduce budgets. We will be moving more into that very soon.
The pricing could have been cheaper.
With another client, we had looked at Veritas. wihich is also quite stable. Between this solution and Veritas, I found this solution to be more user-friendly in terms of its interface.
Go for it. This solution suits organizations where there is no dedicated IT manpower. It can be managed by somebody, like a consultant, who can handle the entire thing.
We are quite happy with the latest version and how it works. We are convinced that this is the right product.
I haven't used it with Microsoft Hyper-V.
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 do cloud hosting for our customers, and we do reselling when they want to do VMware on their premises.
The backup of VMware ESX is the most important to us. That's what we use. We use it to back up all of our private cloud, and it's backed up hourly.
We sent a letter complaining about how the lack of customer service has caused us problems. We're actually dumping Vembu and we're going with Veeam, and we're asking for our money back. The thing that needs to be improved most is their customer support. The product itself is fine, but the customer support is basically nonexistent.
Instead of helping us meet new challenges it has actually caused us problems. We wanted a backup solution so that we could quickly back up and recover all of our customer virtual machines. In case something happened to the hardware, we could quickly recover it on different hardware. We looked at different solutions such as Veeam and Vembu. Vembu was recommended to us and we found it to be cheaper than Veeam but, unfortunately, because they're based in India, not in North America, the customer service doesn't even provide phone support.
We had a lot of problems getting it configured in the first place. They also wanted us to allow them remote access to our machines without us watching what they're doing, which is a huge security risk for us. We said we couldn't do that, and they said they don't offer any phone support whatsoever.
The product itself actually works mostly well. One of the features of the product is Application-Aware and that does not work properly. When we tested it with the Veeam product, it did work properly. We tried to get it to work, to get support to help get it working. It went back and forth for about two weeks through email, trying to get help to get this feature working, and it just did not work.
With the Application-Aware setting, the stability was near zero on a scale of one to ten.
As far as scalability goes, everything seemed okay. I would rate it around a seven out of ten.
I would rate technical support at one out of ten. I don't even know why they have a tech support phone number because I was told in an email from a manager that they don't provide tech support over the phone. Every time I call the tech support phone number, I'm told I have to send an email to firstname.lastname@example.org. I said that I would pay extra for premium support but they said they don't even offer it.
The initial setup was complicated because of the Application-Aware feature not working.
For someone who doesn't want the Application-Aware feature to work, everything else is up to par. The licensing is straightforward. They license it per CPU.
One thing to note is that when you configure which virtual machine you're going to back up, if it's on one physical machine, they license it there. If it automatically fails over to a second machine, the license doesn't automatically move over with it. If they could make that a little more streamlined, that would be an improvement.
We did test Veeam. Vembu vs Veeam came in as a lot less expensive, but I guess you get what you pay for. That’s why we have already sent an email to Vembu saying we want our money back.
We looked at a few other products, but we didn't try them all out.
We've already gone ahead and purchased Veeam, and already tested the Veeam phone support while just on a trial. Someone picks up the phone right away and helps you resolve it. They do remote access, but they let you be on the call when they're doing remote access. They never access your machines without your permission, etc., whereas Vembu was the opposite.
My advice would be not to go with Vembu if you're in North America because it's too hard to get ahold of anybody in India.
We were a reseller, but we've canceled that. We've told all our customers that we're not reselling Vembu because of the problems with the tech support and the problems with the Application-Aware feature not working.
I would rate Vembu at three out of ten because for simple configurations it works fine, but overall, their tech support is very poor. Conversations with tech support and the way they handle tech support are very poor. One example is that I was told that they want to access our servers, but that I wouldn't be allowed to be on the phone and watch what they're doing. I can't be sure that they're only accessing what they're supposed to be doing. The other thing is, they don't offer any extended or premium support. Vembu is for a low-end, small company which doesn't want to do much.
We use it for backup and replication.
We use it to maintain critical data and save it. It suits our needs, is versatile, and the functionality is there.
Vembu is presented more like a multi-platform tool, where you have paper features, VMware, and Hyper-V. I would like to have a different set of products instead of having a single software which does everything. This could be beneficial.
Nowadays, I don't know of a lot of people who are using tapes anymore. If you are using tapes, you don't do backup to the cloud, for instance. Therefore, maybe have a legacy version, then a cloud plus application version.
It is not a well-known software. People do not know about Vembu.
This is not a high-end product.
There were only two issues, which were minor, and the support was very fast. This is probably the top reason why we chose Vembu. They have a very good support team who are responsive. I like the way they handle their clients compared to big vendors on the market, like Veritas, formerly Symantec.
The two issues were fixed in a relatively short time. One was fixed within the same day, and the other one was fixed within a couple days. These are the only two issues that we had for the whole year.
We haven't had a chance to experience scalability.
I would give tech support a score of nine out of ten, which is almost perfect for me.
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.
The initial setup was pretty simple. The backup solution was running within two to three hours. We were maybe missing some technical help during the installation, but there were a couple of technicians who helped me during the setup and finalizing it.
Overall, the setup is straightforward. When you choose the VM options, it is even faster.
We consolidated our infrastructure. We went from about 40 to 15 servers.
The licencing and pricing are good; it's a no-brainer. It is affordable. It has value with respect to the features included in the software.
There is a drawback in the whole approach about how the licenses are managed. There are two consoles: cloud and on-premise. It seems that on a daily basis we have to manage both consoles, which isn't user-friendly. Ideally, it should be either a single on-premise console or only a cloud console. A single platform approach is the better solution. For now, with full licensing, you have to manage your instances on the Vembu Portal, then reassign licenses, and go back to your on-premise management console to do the real management. It is a bit awkward.
I do remember that the pricing was based on a VMware or Hyper-V license, whereas on our end, it should be regarded as a VM-based license. I don't know why they make a difference at the Vembu level. We are currently on VMware migrating to Hyper-V, and we didn't want to buy licenses for VMware, but still have to buy them for Hyper-V. This the only thing which does not seem fully adequate.
We previously used Microsoft Backup, which is not reliable.
I have a lot of experience with Symantec Backup solutions, now Veritas. Compared to Veritas, Vembu is more corporate-oriented and the support is better on Vembu's side rather than Veritas.
We also tested Naviko, Veeam, and Unitrends.
Go ahead and use it.
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 it for backing up virtual machines.
The ability to back up virtual machines is the main reason I use it.
Vembu software runs on a Windows Server. The Windows Server has to be connected to the internet so it can connect with Vembu’s servers. It has to connect with Vembu. For some reason, if it doesn't connect, it stops working, and I don't know why on earth they do that. They require it to connect to the internet and connect with Vembu for it to continue to function. If the internet is down or if the server can't reach the internet, it stops working after a few days. That's not great because there are some people who want to do backups but they don't want to have their server accessible on the internet.
I think that's a horrible design, but it's purposely built in that way. It's something that they put in the product, and I don't know why they did that. To me, that’s a terrible design.
If you bought a new car in the year 2525, a Ford, and your car had to have a connection to the Ford dealership or the Ford company and the connection stopped, and then your Ford car was going to stop working in three days, what would you think about that? But that's the way this software works. They did it, and it’s a horrible design. That's what I don't like about it.
I have never had stability issues with the product.
I haven't had to scale it. It was a small environment so there was no need for me to scale or grow, so I can't really comment as to the scaling capacity.
Technical support gets an A-plus.
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.
It was pretty easy to set it up.
When I upgraded my VMware to version 6, Vembu provided me with an update. That was just a continuation of what it did, but at least they provided the update.
I didn’t do an ROI spreadsheet because this is a time-saver. You can't sell it on ROI. You can sell it on the fact that it is a time-saving tool.
Vembu is too expensive because they don't really have small-business pricing. This is a matter of personal opinion. They're going to tell you that they have competitive pricing because there are more expensive solutions in the marketplace, but there are better solutions in the marketplace that are more expensive. Their product is a better fit for small businesses, but they don't price it that way.
I think they're losing a lot of money by pricing it too high. If the alternative is to manually do backups and they start charging ridiculous pricing for their products, they're not going to sell that many copies. That's probably why they don't. They've got a good product, but they price themselves out of business. That's my opinion.
If I were running Vembu, I would have a small-business suite that's priced for small business. I would allow customers to buy it without a partner, just go direct and price it for small businesses. They would make a lot more money, but they don't want to do that. They want to try to price it ridiculously. It's their call, it’s their product. They made it.
I know many companies won't bother at that price. They’ll just do it manually. I know because I know the market very well here, in the US. I don't think Vembu is a US company. I don't know where they're from.
Their product does a good job. It's just not meant for large environments, so they’re pricing themselves too high. That's just my opinion. Someone will come in and force them to lower their price. As soon as another company comes in, does an online version of it or it does a cost-effective version, they’re going to be forced to deal with this if they want to sell more licenses.
There were other options, but I liked this product. I thought it was easy to use so I took it on. I worked for a partner at the time, and I was going to try to resell it, but I found it to be just too expensive.
The other solution that seems to do better for enterprise customers, the big companies, like Trader Joe's, big retail outlets like that or large grocery stores or hospitals, is Veeam. Veeam costs a little bit more. As expensive as Vembu is, Veeam is actually a little bit more. But because Veaam is meant for larger companies, they sell more instances of it. And by the time you buy the 25-license or 30-license version, it's actually cheaper.
Veeam seems to have much more presence in the marketplace because it's more competitive and scales much larger. I've used Veeam and it's harder to install it, it's harder to get it working. Veeam offers a free version and a small-business solution, but that version doesn't scale well. It's too big. It's like selling a truck to a person who needs a small car. That’s Veeam. Whereas Vembu, they sell a small car, but they want to price it like the huge truck.
Try to negotiate the price. Try to get it to the right price. As a partner, I would try to position it for small and medium-size businesses. I would work with Veeam and say, “Listen. I can't sell it at that price. You're going to have to be more competitive.” As a partner, I would recommend working more with Veeam. It's easy to sell because it's a good product, but I'd be working on the price. It's easy to implement, easy to set up. You can be low a low-tech company and get someone to figure out how to do it easily enough.
The challenge I would have would be getting Vembu to price it competitively. If they aren't willing to, just go with Veeam or tell them to do a manual backup or go with some other solution.
Vembu is a great product. It's priced too high, but it's a good product.
Backup and replication.
If we have any issues with servers having been corrupted or damaged, we are able to restore our backups. We are also able to store our backups offsite, in case of fire. Right now I'm using it with VMware. The benefit is being able to replicate the information to a different offsite building where I can store it. We're an FQHC and we have to have an offsite backup in case of a fire.
If we were to lose all of our data we wouldn't be able to operate. We run a 24-hour clinic, we have an ER department, and the data needs to be safe. If we didn't have that information stored safely, our patient information, we would not be able to run the business. So it's very valuable for us.
It also saves us time being able to do backups automatically instead of manually.
Finally, for reporting purposes, it's safer for us to have multiple places where backups are stored. We feel safe that the information is backed up more than once.
The most important feature is the Restore, to be able to restore in a disaster recovery situation.
If the English accent of the support agents was a little better, so that we, as the users, could understand it better, that would be nice. It's very hard to understand the support people when we talk to them because of the accent.
We haven't encountered any issues with the stability so far. It's been working fine.
It can handle a lot because it's doing a whole data center, so it's handling everything.
Tech support is good.
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.
The initial setup was not complex at all. It was easy.
It's very hard to estimate ROI. If I have a disaster issue here, my whole company is down, so I cannot put a value on it. It's really the value of the whole company. If we don't have that data we aren't able to run. It's a very valuable tool for us.
The pricing is good.
Veeam was one of the options we looked at.
Test it first. Make sure it works in your environment. But I will also say that it's an immediate investment that needs to be done.
We aren't using the compression or encryption features. We don't need them.
I would rate it a nine out of ten. It's not a ten because the accent of the customer support agents is very difficult to understand. You have to ask a few times when speaking to them. That's the only issue, the rest of it is good. It's a good product. It's working.
We use it to back up a test lab type of environment. It's a virtual environment where we use Hyper-V.
The way it improves our organization is that we haven't worried about looking at backups in about a year or so, it's just been running on its own. It also delivers an enterprise-level of data protection and helps with our budget. I estimate we have saved $3,000 - $4,000.
The most valuable feature is the Hyper-V backup - it's just one click. I don't have to worry about it.
There's a feature that does syncing with AWS Cloud backup online. It's not that straightforward to get it set up.
We haven't encountered any issues with the stability of the product.
I haven't tested the scalability yet.
Tech support has been pretty good. I've reached out to them a couple of times and they answered my questions. The support has been pretty decent.
We previously used Veeam. Vembu is much cheaper than the competitor, than the Veeam suite. That's why we went with it.
It was very easy to set up. It took us about 30 minutes to deploy it.
I prefer the way Vembu is licensed. When you look at Veeam or any other product, they price per node. Vembu is licensed per host. You just buy a host license and it backs up unlimited VMs within that host. The others charge per VM.
We evaluated Veeam, Comet, and Windows' built-in backup.
Look at the options out there. If you're looking for a cheaper solution go with this. If you're looking for more features and integrations with other solutions, then you would have to go Veeam.
Although we use it with Hyper-V, I don't know if it enables high-availability. We currently just have the one user, the test environment backup.
I rate Vembu a nine out of ten. The one point off is because the cloud sync options are not that straightforward to set up.
The primary use for this solution is to replace the old-fashioned backup solution that we had that was based at the application level. I was doing backups of an SQL database or mailboxes from Exchange, but we needed a more modern solution where we could back up the entire virtual machine.
The solution is used for taking a backup of the virtual environment, and the benefit of this is that the speed is a lot higher. The product is taking a full backup during the weekend and takes considerably less time than our old solution. During workdays, it's doing an incremental back up every three hours, and that is also a lot faster. It also gives me a lot of options on which restore point I should use, in case I need to restore something. So these are huge benefits for the organization, speed and multiple restore points, that we didn't have in the past.
Another benefit is that the whole process is running at the ESXi level so the users do not really experience any delays or any lack of performance. We just keep them going, using the infrastructure, the VMware infrastructure. In the past, that was not the case because, during the backup process, it was slowing down the server because the server itself was executing the backup. Now, another server and another hypervisor are executing the job and the end-user does not experience anything as a result of the process. It is going on in the background. No delays at all.
In terms of data protection, we are not using disaster recovery because we are not licensed for it. But given the fact that we can afford the few hours the restore is going to take us, it is reducing costs, and the maintenance we used to have of switching tapes and external drives. All that kind of stuff that we had in the past has now been eliminated.
The most valuable features for me are that I can back up the entire virtual machine, but when restoring I can restore at the file level.
One issue that we are facing is that, during the evaluation period, we had some jobs that were replicating three virtual machines from one ESXi to another. Then, during the license purchase and activation, that Replication functionality was disabled because we are not licensed for it. As a result, we have one job left, the replication job that we were running, but since we don't have access to that area of the product we now, we are unable to delete that job. I need assistance on how to unlist that job.
Otherwise, we have no issues. It's functioning as expected and we're getting the results that we were expecting from the product.
A couple of times, the Vembu server was stuck and we couldn't access the web interface of the server and we had to restart the server. But that was during the migration progress where a lot of the equipment was updated and changing, so we cannot blame the product itself. Since the environment stabilized, we haven't faced any issues at all with the product.
We haven't encountered any issues with scalability. We gave it fewer resources than the server needs. Initially, we configured it with 16 gigs and then we cut it in half, giving it just 8 gigs, and the system is still performing and acting stably and within our needs and expectations.
Our building hosts around six companies. Currently, the product is used only for one hypervisor and one of the companies but the plan is to expand: First, the licensing for more hypervisors, and second, to expand the enterprise solution because we might need to use the Replication function that we are not using at the moment.
Their technical support is excellent. The speed at which those guys are replying is like chatting through email. They reply immediately and, in most of the cases, they have the answer available right away. It is very acceptable and we appreciate that.
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.
The initial setup was straightforward because it was an appliance. We downloaded an already-installed and already-working virtual machine which is acting as a backup server. There were minor issues to connect it to our local network and set up some iSCSI drives and volumes, etc., but it was next to nothing when compared with having to install it from scratch.
We downloaded the virtual appliance, activated it, and then configured the network interfaces. After that, we connected the server to our hypervisors and the system was up and running. The deployment took four hours.
We didn't use a third-party service provider at all. We directly contacted Vembu, and the back-office and support personnel were very helpful. Every issue was solved within hours.
In terms of money saved, it's hard to say because we need to calculate the man-hours that we spent on monitoring the old system, and the employees that had to visit the computer room and replace or change tapes, etc. So it's not that clear. But the fact that we were using an old solution for about 12 or 13 years, I expect the amount of money we will save is going to be huge.
We have only been using the product for two months in production now, so the return on investment is not easy to see in that short period. But I believe that it's not going to take more than the next six months to see a return on investment, considering the man-hours that we are saving, that we aren't spending any more monitoring an old backup system.
Pricing is fair enough.
What was not clear enough in the documentation on the website was that that you're licensing per CPU socket and you are only licensing on the restore sockets, not the backup sockets. It's a bit technical, but it was very well explained during the demonstration that we had during the evaluation period. The technician explained exactly how the licensing is working. That was information that I couldn't find on their site and it needed to be explained by their representative.
We had in mind to use another solution that was not based on Snapshots. It was based on replicating on the sub-second level of the VM virtual disks. Although it was compelling, and we considered that solution, it didn't have that direct access to information that the Vembu side was giving us.
To get a quotation on that product you needed to find a representative near you and have them do a quotation for you. It was not that direct and immediate. On the other hand, Vembu had all the pricing and documentation listed on their site, so we had all the information we needed. It was within the budget and we decided to test it. That's why we chose Vembu as our solution.
Although Vembu doesn't seem to be very fast for some environments, for example, banking, because it's based on Snapshots, which is a rather slower procedure, it has been just fine. But I would evaluate another solution that is not based on Snapshots. I can for sure recommend Vembu if high-availability is not a requirement.
We are using the compression that is embedded in the system. We downloaded the Linux virtual appliance, Linux Ubuntu, and this appliance is now part of our live organization, it's a live system. The embedded compression system is very satisfactory and we didn't have to alter anything within it.
We didn't need to activate encryption because our infrastructure is only available within our local network, it's not available outside the firewall, and the destination drive is actually an iSCSI volume that is only accessible through the Vembu backup server. That's why we didn't need to encrypt our backups and possibly add delays to the whole procedure.
We don't use Microsoft Hyper-V, we only use VMware ESXi. The virtual environment that we're backing up through the Vembu solution is one ESXi that hosts three virtual machines. It's an end-to-end VMware solution. During the evaluation period, we also had the option to use the Replication function. We tested it and it's an option for the company to purchase, to upgrade the license to activate it, but this is going to be decided in the future.
The number of end-users using the functionality of the backup solution is around 70, but the end-users don't know it is being used. There are just two system administrators who use the Vembu console as administrators. One is full-time and the other one is part-time, so we need one-and-a-half people to run it. The maintenance is so minor. We just follow up on the emails the server sends saying that we successfully finished a job or that there was an issue. We then visit the web interface look at the reason for that failure - because the server was busy or the like. The maintenance is very easy.
I rate it at eight out of ten because, during the evaluation period, we had a server that was sizing at about 1.8 TB and the product took about 26 to 27 hours to restore it. So the slow restore is an issue. Eventually, we minimized the amount of data. Now, we are less than a terabyte, around 800 gig, so we expect the restore to take less time. But it's the slow restore that makes me give it an eight.
Backup virtual machines on VMware.
I am able to verify we have availability of our VMs in case a failure occurs.
I am still testing restores and it seems some problems may be related to our hardware. Because we have not implemented the correct hardware yet I cannot be sure where the problem is.
No issues with stability.
No issues with scalability.
I run into the problem of their chat service not being available frequently. I like chat as it is quick.
When it is not available I have to get a support ticket going. I was asked to provide a TeamViewer number and that was fine. However, I was waiting for a while and needed to go to lunch. If the TeamViewer session could be accessed either within 15 minutes or scheduled, so I know when they will connect, it would be helpful. It is really necessary that I be available during the session as there are questions. I do not want to be chained to my computer while I wait for the session to start.
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.
Very straightforward. It seemed to be mostly intuitive, although in some areas I had to think about the functionality. I then referred to the instructions and had no issues.
The pricing structure is in line with other solutions. However, the option to replicate offsite to a unit at another office or at home is a big cost benefit. Instead of paying monthly for cloud storage, you replicate offsite for free. If preferred, you can also replicate to Vembu offsite.
We currently use StorageCraft ShadowProtect which is a really good product. As we move forward with Vembu we will want to standardize on Vembu. It seems it is more flexible as a total solution for physical, virtual, file/image backups and offsite provision.
Download the product and give it a run through. With some products, this is a tough process as you spend a lot of time testing and they don't work correctly or have enough benefit to justify a purchase. Then, you have wasted all that time. But Vembu was quick and simple enough, it did not waste a lot of time.
We use it for backup copies of key virtual servers in our company.
Fortunately, we have not had to recover lost data. However, it is reassuring to know that we can recover lost data, if needed.
The most valuable features are ease of setup and configuration.
I have not been impressed by the data compression of the backup images. They seem to take up nearly as much space on the backup drive as they do on the server.
We have not encountered any stability issues.
We have not faced any challenges with its ability to scale.
Their technical support is very good to work with, as they are able to propose alternate solutions to problems that work well for us.
We did not previously use a different solution. Vembu was selected after reviewing, then trying several different products.
The initial setup was straightforward and well-documented.
We were able to take advantage of a promotional pricing campaign.
I do not know how often Vembu offers the promotional pricing campaign, but it can be cost advantageous.
In addition to Vembu, we evaluated Veeam, Unitrends, and Virten as alternative solutions.
Verify that you can restore a virtual machine (VM) from its backup and ensure the notification of backup results (success or fail) is readily available.
It is a backup and disaster recovery solution for small businesses. I use it primarily for Vista machines.
The backup is constant so it makes things simpler for me. To put it simply, it just works.
It's also easy to use because of the graphical user interface. It's simple enough for a child to use. With Vembu Cloud I can view the status of all my clients' backups. I can configure backups from the interface. I am able to do 99 percent of what I need to do from the GUI.
I suggest that the dump of the database have the option to either be backed up to Vembu Cloud or be backed up to all backup sites and not only to default storage.
If the backup server crashes I create another backup server and use the backups and the database dumps. I have to use the default path of the backups. It would be a great option if I could just import the backup files.
In the past, I had some stability issues but I no longer have them. It was corrected in the last version. It is working without problems now.
Scalability is not a problem.
The support from Vembu is very, very good. These guys have saved my life two or three times.
I have used many solutions up until now. I switched to Vembu because of the price.
The initial setup is simple. It is not complicated. The only thing that makes it more complicated is when there are a lot of databases.
I would rate it at 9 out of 10. It's a great option for a small business looking for a cheap solution requiring two or three different backup sites. Vembu provides strong support. I am not giving it a higher score because it is complicated to recover a crashed backup server.
Our whole environment is virtualized except for a couple of servers which are still physical. So I primarily use this for backing up my physical servers. I do an image backup as well as a file-level backup.
The main improvement is the compression, the space. I back up one particular server with close to 1.2 TB, and the way the software compresses it is close to 600 or 700 TB. Vembu compresses it to close to 450 gigabytes, that's gigabytes. So that’s really amazing, the way in which the backup compression happens. It creates a lot of space in my storage. I’m saving almost 50 percent of my file storage space, SAN. that’s one of the key features of this.
One thing I’m very much impressed by is the compression ratio. The rate at which it compresses the data during backup is really very good. In fact, I’d say it’s better than Symantec Backup Exec. I have Backup Exec, in my environment, and I have Veeam. Symantec is now Veritas, so I have played with all the backups, but the way in which this handles the compression is really one of the key features.
It’s also very, very stable. I haven’t made any changes to it. I just installed and it’s working. I restored a couple of times, and everything seems to be fine.
I do have one suggestion for them. The process is a bit cumbersome when you remove an agent, delete that job, and add the agent to the same server. Even though the agent is already installed in that server, the system does not recognize it. We have to uninstall the current agent, restart the server, install the push agent - a new agent - and then restart the server. I think they should try to avoid that. Symantec doesn’t work that way. You push the agent once, the agent stays in the server for good.
It’s very stable. I don't have any issues because it’s automated. The moment a backup is completed we all get an email. First thing in the morning, we check those emails and it’s on top of it.
I’m not going to scale with this because I’m primarily using it for physical servers.
Maybe my next project will be, when my Veeam support runs out, to try using Vembu - because Veeam is very expensive - for backing up my virtual servers and let's see how things are going to work.
Support is very good. When you call them or send out a support email, immediately someone responds. It’s really good. They come back with an answer immediately. There has never been a time where they said they wanted to do some research on it. The moment I send them an issue, the guys fix it immediately.
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.
The setup is straightforward. The only problem is, if I delete the server from my backup list and I want to add the server back, that is complex.
It is very cost efficient, effective. I’d say it's one-third the cost of Veritas when compared to the server backups. I even tried image backups on Acronis, but Acronis is very expensive. So these are some of the key reasons why I opted for it.
Licensing is straightforward, it’s simple, they should keep it the way they have right now.
There is no need for any advice. A person who has infrastructure and backup experience should be able to do it. It doesn’t require any special knowledge for the configuration part or reinstalling.
I rate it at eight out of 10 because of the complexity involved in reinstalling that agent.
Buy, install it, use it, back it up, that’s it. It works fine.
Primary use is for vSphere or VMware.
Live support would be helpful. I've communicated with them via email and through incidents. It might be better if you could have a chat or phone call because backups are important. You don't want to wait for an email. I know of other vendors that have a number you can call; they have people around the clock. It would be good to have a number you can call and your call is answered and taken care of, because backups normally occur at night, not during the day.
I would also like to see more documentation or videos. They have some videos out there on how to do steps, or for training, or to help you know more about their product.
Another leftover issue is that when you get notifications via email on an iPhone, there is only a certain amount of space to view it without having to open the email itself. I have four backup jobs. Their subject line shows "Vembu backup software..." and at the very end they put the server name and whether it succeeded or failed. I asked them if they could put the server name, and whether it succeeded or failed, first. That way, when I look through my emails it tells me whether it's succeeded or failed, and which server. Currently what I have to do is open up each email, and then scroll through to the very end, because it's a very long subject line. They say it's not customizable, and that they are going to look at improving on that in the future.
No issues with stability.
No issues with scalability.
I have enjoyed the support. They're very quick in turning around solutions for the issues and problems that I have had. You get a good turnaround. It takes a little while, but they document it. You can log in to their website and create a ticket, and see in real-time if it has been updated. It's really nice.
We went from a physical server to a virtual server. Vembu is cost-effective versus using VMware Essentials.
The setup wasn't altogether straightforward. There were a lot of items. It took me about two weeks before I could finally get things the way I needed them to be.
The product's pricing is a good value. Regarding licensing, make sure you find the right workstation or server that you're going to install it on, and know the number of sockets it has, since the price depends on that.
VMware Essentials, it has backup and restores capabilities. We also used BackupAssist.
Try it with the trial version. You get free rein of everything there. Test it out and make sure everything works right. You'll find it's easy to use and there is good support, as far as emails back and forth. That gives you plenty of time to try it, and then you can implement it once you've figured out all the items and how to get to things, as well as its limitations. That's pretty much what I did. I got a server and installed the full license and went to town. I put some backups on there and got familiar with it. It was pretty much straightforward.
Also, look at some of the training videos. They make it much clearer.
I like Vembu because of the price point, the ease of use, the support, and it being full-featured backup software for the needs that I have. I would rate it 10, but the one thing is the email notifications, that I mentioned above, that aren't customizable. Maybe adding more customization for the end-user, in the settings, some additional options, would help.
Backing up virtual machines, we use it for Windows Hyper-V platform in one data center, but we've also got future plans for a VMware Hypervisor platform in another data center. So thinking ahead, we chose Vembu.
It hasn't improved things, per se. It's an essential service, done automatically. I would say it is an essential backup system that matches the alternative solutions at the moment in a relatively cost-effective way.
The automated backup of multiple virtual machines. We can back up two hypervisors, one is Microsoft Hyper-V and the other one is VMware Hypervisor.
It is very easy, unless you know exactly what you're doing, to corrupt the virtual machines and they get locked up. Just brief detail: When you are creating a system, if you don't have absolutely every other little background processes in place, it creates Snapshots of the virtual machines. Once it does that, it then won't be able to have a backup. From that point on you have to destroy the virtual machine, which is completely counterproductive on a large system. There is a fundamental flaw in the setup that can be very dangerous, potentially. So that needs to be avoided; whoever writes the software for doing that needs to make sure that that cannot happen.
I have fed that back to the developers. I don't know whether they're going to make that change, but they can't put that responsibility onto customers. It's their software that needs to be able to not allow that to happen. I've not had any response to say, "Yes, we'll do it." So that's a little bit of a fault as well. When we do give feedback we don't get any commitment. Like this survey, we're being asked the questions, but when we give feedback, we don't actually get any response at all.
When it's backing up, it's okay. We've used it to restore the system and that restore system worked. We get an email report on various operations, so we know if something has failed or not. It's operating fine.
We've not encountered any trouble with scalability.
Their tech support is okay, but they don't respond in time to sort out the problem. We sorted it out ourselves. We fed back the answer. There wasn't any thank you. There wasn't any acknowledgment. There wasn't even any appreciation of what we'd actually done, something like, "Yeah, yeah, you shouldn't have done that." That kind of thing. Very basic support. There is a willingness to help and respond, but in actually solving the problem, they're not very good at all.
Then, once we did solve it, there was no understanding of what had been done, so it's at that level that it is lacking. This issue was over New Year's time. I was actually on holiday in India. I had to waste a whole day rebuilding a system from a corrupt backup. And again, no support from the Vembu guys, at all. Once we showed them what had been done, again, no acknowledgment that they'd safeguard this in the future.
It has been several months now and I'm not in a position to be chasing them to improve the product in that way. So it's still there, in potential, for future Vembu customers to hit the problem that we had and they might not be as tolerant or be able to fix it. We're an IT company ourselves, so we do understand the nature of the software that they're running and the problems, but there are major flaws in the design at set up time.
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.
We had problems, initially in setting it up. There was a major bug and the backup process, it corrupted one of our virtual machines which was a live customer system. That wasn't very good. Now that has been sorted and we know how to avoid it, but at the beginning, it wasn't a good system. It has been fixed and it has been working fine since.
It was supposed to be straightforward but it caused major technical issues that were difficult to fix. They were actually unfixable, the problems. We had to basically destroy live production systems.
Pricing is a good value.
Licensing seems okay. I suppose the more volume you put through the system, it would be good to have a volume licensing discount. We're a managed IT service provider, so we're backing up not just our own systems but all our clients'. In that regard, as we grow, we're putting business through Vembu. There is not any specific partner incentive at all. So that would be nice to see.
Microsoft Azure. I can't remember the others but there were a few; the data center ones, but I haven't got specific names. The in-built ones in VMware.
When you do a search on Google about half a dozen pop up and we looked at some of them. With some of them were put off by their business models. So even before we evaluated them, their business models weren't acceptable. The nice thing about Vembu is the subscription, on a monthly basis. It fits into our business models.
I would tell others looking into implementing this solution exactly what steps need to be done in the setup. I've actually documented it, and I've passed that on to the Vembu guys. Take that, and make sure that things are set up very clearly, not, "There you go, it's very straightforward, it'll take you five minutes." It's not like that at all. The marketing of the setup is so misleading. It can cause a lot of problems. They need to be more honest in the way things need to be set up. That would be okay, that doesn't put people off when you have to go through a process. But just saying it's straightforward and it's simple is a bit of a lie, especially if it causes a lot of problems. So there needs to be more documentation on exactly what to set up in what order, and how to do it and what not to do.
Regarding technical support, sometimes, if you pick the wrong time of day to get through you get this constant "We value your business, we're busy at the moment..." and you can be on the phone for ages because it gets redirected to America. You get the feeling that they're not actually busy, they just have some automated lady giving you a message. Again, that engenders mistrust in the technology. It needs to be not advertised as 24/7. It needs to be advertised with the specific hours that support can be provided. That would help a lot, not just saying 24/7 and then not actually providing it.
It goes to America, but it is actually answered in India. It's all confusing. If it's 3 o'clock in India, we understand that they'll be asleep, so why not say we operate at these times, and people will understand that, rather than pretending redirect to an American number, where you're expecting somebody to pick up the phone. But they're picking it up from India at 3 o'clock in the morning. It's forced us to be hanging on to the phone for a long time, while nobody has got any intention of picking up the phone.
In terms of my rating of the solution, I have to do so on two levels. The first is the implementation and that would be a two out of 10. It was bad. But in terms of once it's operating, I would give it a nine.
It has provided us with a value-added service for our customers, aiding us in becoming a one stop shop for all IT and Communication requirements.
The intuitive GUI, ease of use for doing any type of backup.
The Support for Exchange 2016 mailboxes, a daily report for all customers on their last backup (Current report misses some information)
The Backup solution has been very stable and any issues have been promptly addressed by the Vembu support team.
Customer service is always excellent.
Technical support is always excellent.
We switched to another solution only because vembu were discontinuing the product, glad to hear they continued it and we came back on board.
It was extremely simple to setup and we were working in no time at all.
We advise them to check out other solutions but we are very competitive. We license by server/application and storage allocation.
It is between 15–30%
We advise them to check out other solutions, but we are very competitive. We license by server/application and storage allocation.
It gave us an easy to use and stable backup service to offer our customers for a low price.
Central management and easy control of allowed space per client makes end user and client management easy.
The service is built on MCALs, so implement a policy in which someone keeps refilling these. But overall, MCAL is a nice way to be dealing with licenses.
We ran into some problems in which the server hosting the backup service needed to be restarted once a week. We contacted support and they resolved the issue within a week!
We didn’t have any scalability issues.
Technical support is excellent.
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.
The setup was straightforward and support was always available if needed.
The cost is low and has always been. We haven’t found any cheaper solution for our demands. By using the MCAL, we feel safe and secure. It is kind of “straightforward” to add new licenses for the backups.
We did evaluate other solutions.
Use the support. They are knowledgeable and will resolve any issues you may have. They will contact you directly so that you have a person to talk to. You can tell that Vembu focuses on customer support.
Another plus is the ease of use for the users. In our environment, we sell it as a service and our customers install the backup-client themselves.
When migrating systems or doing a reinstall, Vembu has a really easy-to-use system to re-implement the backup jobs and rules. Short spoken: The end user experience is great and easy to use!
Our backups are done on a nightly basis. We don’t run out of space on the backup drives; no tapes/hard drives have to be stored or swapped out.
The online backup feature allows me to store my backups off-site without having to physically drive them somewhere.
There have been times when the backup hangs and does not complete possibly due to a connection issue. Stopping and starting the service usually works to restart it. It would be good if there was a way for it to automatically restart.
There have been times when stopping and starting the service did not work and I had to call support. This has not happened recently, though.
There were no stability issues.
There were no scalability issues.
The technical support is good. They are always willing to help and will see the problem through, right up to its resolution.
Initially, we did onsite backups to tapes and then to hard drives. We switched because we wanted an off-site solution.
The initial setup wasn’t too bad. Once we got everything working, it has been running okay.
It is easy to add products. The pricing is reasonable.
You should definitely consider using this tool, as an off-site backup option.
The biggest improvement has been the ability to allow us as an MSSP to continuously gather extra revenue from this software, so we can use it to back up our clients' data offsite. This is one of the reasons why we enjoy the product and we've enjoyed using it for this long.
When it comes to backup software, one of the biggest things that I use to enjoy about StoreGrid, this changed recently, was the support.
I enjoy the ease of the UI and how simple it is to use compared to other products.
They had a good product and tried to change things by going to a different product. They should have tried to stay with a product that is a proven solution and successful.
One of the biggest things that they lack at the moment, which their competitors currently have, is a hardware device that we can deploy at a client's location. We can have local backup stored on the device and replicate over to our cloud. That's basically one of the biggest concerns that we see for their company that we currently think they are lacking compared to other competitors.
Two or three years ago, they had an amazing support team, especially for the StoreGrid product, which is something that we're currently using. But around a year and a half ago, they brought out a new product called BDR, which from my understanding is horrible. We tried it and didn't like that the support just started going down a bit. They started transitioning more to the BDR side and left the StoreGrid part out.
The system is very stable. It's ideal for our day-to-day basis. I've been using StoreGrid ever since I started working here over five years. It's a good product. We haven't upgraded to the latest patch they've released, and the product still works fine. Overall, we think the actual system software works great.
I have encountered some stability issues, but certain things are awkward to do when it comes to restoring and pulling data, e.g., cracking Exchange databases, pulling emails, and restoring mailboxes.
I would give technical support a five out of 10, because we've had issues in the past where calls haven't been answered. I do call them a lot and the majority of the times, I'm going to the United States, although I know this company is based out of India, and they have offices here. However, when I call during the weekends I've had the following issues:
Originally, it seemed like they were staffed for the actual support need, but now it doesn't appear like it. Only in the past few months have I seen minor improvements. I do understand that in the past year or so, there have been some changes.
However, when it comes to knowledge, they're always willing to help; I would say they're always on top of things. As for being knowledgeable, I would rate them as an eight out of 10.
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.
The initial setup was straightforward.
It's fairly simple and easy, and they make our lives a lot easier when dealing with the licensing and actually purchasing licensing, keeping them in the vault, keeping them in our bank. It gives us an additional way to resell and earn a little extra here and there from other clients. When we do build out servers, backup servers, for them and we have them out on site, we can obviously use the licensing to license their system to obviously mark up and make some money.
Somebody already took on that decision prior to my being here.
Give it a chance. It's a decent product, although not the best of its kind. It is lacking in certain aspects. A piece of hardware being deployed out at a client's office would be ideal. There are a lot of products out there, and it's in the middle of the pack.
On the client side of it, the ease of installing the software and getting it up and running: Each version they bring up, it gets better and better.
While it's hard to say, the support side of it is sometimes a bit hit or miss; the tech support. Generally, I would say about 70% of the time, they're pretty good. They're pretty accurate on what we want, and the odd times, I think it’s lost in translation.
We've had a few bugs with the software and, for some reason, we've always had to get their support to dial in to fix it. It's not something that we can fix ourselves, really.
Generally, we have not encountered any stability issues.
So far, scalability seems OK. We've only grown, not masses, with this software, so it's hard to say, really.
Technical support is 7/10, on average. They could make it better by improving the speed of responses. Sometimes, they'll dial us back in a few minutes; sometimes, it takes them half a day before they have a look at it.
We previously used a different solution. The ease of user feel is really the reason we switched over to it.
The initial setup is going back quite a while back. I think it was in the middle: it wasn't too straightforward; it wasn't that tricky. It was average.
It's pretty straightforward to use once the software gets going.
We were looking for a product with Automatic backup replication and a product that would support MSP rebranding.
I wouldn't use the term 'improved' as the product implementation in the end was a complete failure. The implementation however did serve the purpose of allowing us to grow our BDR service offering from a technical perspective by seeing how things shouldn't be done and then looking at ways of overcoming these issues.
The vendor support service. Operating out of India and not really taking into account the time difference for support tickets meant we were getting responses to our support requests at midnight, when no one was at work to be able to address them. High priority issues which should have at most a 2 hour SLA were not responded to because the support service was not 24x7. The vendor support SLA for this product was terrible.
We used it for 12 months.
The Linux based deployments were fairly easy to manage, however the constant updates were annoying. The MYSQL databases would corrupt themselves which then required a support technician to resolve. Backup jobs would report as have run successfully and then when we checked the data the job had only run for 1 minute
There were issues with the software's ability to handle low bandwidth connections such as ADSL. There were stability issues with running the software on both windows and linux, the advancements of the updates to resolve issues would fix some issues and then create more which points back to issues with Quality Assurance.
The service was able to handle our requirements from a scalability perspective. There were no issues with being able to scale the product upward, however the demands of the software on the hardware CPU would require that the supporting backup server hardware would need to be improved as demand increased.
Extremely Poor. There were no real SLA's available and when we tried to contact our Account Manager for the product they would not respond sometimes for 5 hours after we contacted them.Technical Support:
When they eventually responded they were actually very knowledgable on the product.
Slightly complex, as the installation requires MySQL which is not native to windows so running on windows or Linux requires knowledge of command line for MySQL.
In-house, we were required to know the product to be able to support it as much as possible prior to engaging vendor support.
About $50,000 of lost revenue due to Research and Development Capital expenditure and Labour to setup, we never got the product into a position where it was profitable.
The original setup cost was supposed to be around $25,000 of R&D investment. We are not using this product anymore, it was never profitable for us. I don't recommend investing the time into pursuing this product.
No this one was chosen based on price and rebranding potential.
Look at Dell App Assure.