BDRSuite Reviews

Our primary use case is for VM backups.

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

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

Another good thing is that it has cloud backup.

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

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

Six months.

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

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

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

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

The technical support is good.

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

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

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

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

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

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

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

Veeam is good for very high-end servers.

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

Vembu allows you to implement a variety of different requirements.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

We are a business school.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

One month ago, we subscribed for one year.

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

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

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

Mainly, we use it for our backup recovery. If you have relevant data, we need to make backups similar to the data to ensure that we can export it in the case of any emergency or disaster. The main use case is disaster recovery for relevant data to be able to survive after any disaster.

I have two deployments. One of them is Hyper-V deployment with backup for Hyper-V virtual machines. The other one with backup for the Vembu virtual infrastructure version. Both of them are on-premises. There is nothing on the cloud.

All our clients have been happy with the backup and restore features.

It is easy. You can save a lot with their features, without a lot of hassle. You can design your backups closely and flexibly without a lot of details or variables. It is very straightforward. You can put what you want in the right place in a very short amount of time.

The speed of the solution’s restores is good. It is dependent on the infrastructure and the nature of the connection between the storage and servers. Overall, it is good. There are no problems when using it.

You can restore all your data or partial parts of it. You can restore a specific version of the data. It has a lot of options for restore, so you can have the correct data that you want to restore. This is very important. You must know what you are going to restore. Otherwise, you may be overwriting correct data with other data. You must know what specific files you are restoring as well as which version. Partial restore is very important because there might be some files which are newer than the backup and some files that are corrupted. You need to restore some files from the backup, but not all the files.

We have the VM replication. We can copy a VM to another host with VM replication.

Maybe they can add some features regarding working with the vCenter cluster to be able to have more power over the cluster overall, not just over a single or specific host. Also, I would like some enhancements in technology for the web interface, e.g., some interactive technologies to advance the interface of Vembu. Although the current interface is very good, maybe they can use more advanced technologies for its web development.

I have been using it for about a year.

For the entire time that I have used Vembu, I didn't encounter any issues. It is very consistent and nothing failed nor was corrupted. 

I have three people trained on the solution, and the main person is leading the support. They are IT specialists. The role of backup administrator is assigned to them. They keep track of the backup operations done daily or weekly. If something needs to be restored, they are responsible for restoring it.

Scalability is good.

I am backing up two environments: Hyper-V and VMware. One of them is about 40 VMs, and the other about 60 to 65 VMs, supported by three machines that are dual sockets each.

The main component in the backup solutions is compatibility. The backup is located on the hard disk, and I didn't face any corruption of data, which is very valuable. When something happens as an error, there is technical support who gives us the reason why this error is emerging. In most of the cases, the errors are emerging from the operating systems in which you are trying to back up. Sometimes, the client refuses to connect, etc. All this is under control and can easily be solved.

I refer a lot to the knowledge base on the website, which is very good. I haven't needed to contact support persons interactively. 

I tried to install it twice on Linux just for testing, and I succeeded, but it was picky sometimes, because there are a lot of options with command line interface. So, it was a challenge to get it to work on many operating systems. However, on Windows, the setup was very straightforward and no problem at all.

Using Windows to deploy takes not more than five minutes. It is very fast. For Linux, it takes about half an hour to an hour, according to the problems that we would face.

We tried to restore it mainly on the physical machines, not virtual. The hardware that it is deployed on is very reliable. We faced problems on the backup machine itself. The machine, which functions to store the data, must be very reliable. You also need to keep it away from any disaster or security exposure.

I did contact their technical guys for some technical discussions before we deployed one of the instances that we used. They were very good and helpful.

Manually restores or restores from manual backups are very hard. They take some time. Restoring from a platform software, like Vembu, makes things very easier, particularly the speed to restore which version, which state, and to where. So, you speed up the overall operation by 20% to 25%.

The ROI is very good because you have the safety of being protected by backing up your data a lot. If an incident happens, then we can restore valuable data, save a lot of money, and preserve the continuity of the business. This is a big benefit which provides a lot of value. 

The pricing of Vembu is one of its strong points. The license is not as much as other competitors, and it has a variety of licensing options: subscription-based, perpetual licenses, and a virtual machine license. You can design whatever license that you adopted to your environment, and that can support your environment without extra cost, providing more than you need. So, you can design a license that fits your environment and budget. The pricing is very good and can be used when the budget is tight.

I used Veeam software for a while, but as a trial. I didn't support it because their prices are very high. I think Vembu provides the most resolution for our backups.

I use the Microsoft Windows Backup tool sometimes. However, it feels like a very heavy tool, not a sophisticated tool.

I know that there are features that are more advanced with other competitors, but those are not needed often.

I used Vembu's Data Integrity Check once when doing an integrity check for the backup. If I have doubts that the backup is good or bad, it might be good for that, but I haven't used it a lot.

I encouraged you very much to engage with Vembu. Vembu is a really good software. I was convinced to use the company and software the first time that I saw it. I recommend it to everyone I know. It is a very powerful backup solution with a good price.

I would rate it as nine out of 10.

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

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

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

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

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

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

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

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

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

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

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

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

I started two months ago. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

I don't know how to check the deduplication.

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.

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.