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.
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).
Currently, we use Vembu for weekly backups of our virtual infrastructure and monthly backups for separate, confidential data.
We use it only with VMware.
If our country is hit by a meteor, I have secured data in another country on the other side of the world. Then, I can start the restore process immediately with this solution.
There is an option to back up a specific folder from a specific source, not the whole virtual machine.
The encryption is a must in these days. You can't do anything without encryption of your traffic or data.
The compression is unusable in every scenario because the data that we backup is too different, according to each type. Therefore, the compression is not applicable everywhere. So, we don't use the compression at all.
They can work on their cloud solution. In these days, the data becomes too much and you have to back up a lot of data to the site. They could offer cheaper storage to their clients with the cloud, making this a single source of truth solution. In our project, we are using two service providers: One who offers our storage and another who offers the software. If they work on their cloud solution and can offer their clients lower prices for this type of storage, this would be a really good improvement.
It's pretty stable. We haven't had any issues with the software, like crashing or freezing.
I don't have any of the reservations about the scalability because we currently use it on a single machine.
We have about three users who are part of the IT department, including two senior administrators and me, as IT manager.
Our account manager has provided us with great information and support. He is always on time. I haven't needed to wait more than two hours to read the answers to my questions.
Three years ago, we started the project to duplicate our infrastructure in every single aspect and needed to create daily backups of our virtual machines.
We picked Vembu two years ago, but switched to another solution which comes with integrated backup for virtual machines. This year, we start another project, which is to create offsite backups somewhere in the world. There were some requirements: the backup storage to be encrypted, the transfer to be encrypted, and not be so expensive. So, I looked at Vembu and Vinchin again. We were only satisfied with this tool (Vembu) when we started talking about money, because it was cheaper and could easily encrypt our non-dedicated storage.
The initial setup was as easy as one, two, three. I downloaded the software, then ran the application. They have a perfect documentation section on their website where you can find what you need: this tutorial.
Our deployment was about an hour.
We always start any project with a deployment strategy. This includes some type of testing. We go in with the result that we want and compare the software with our requirements. If it fits, then we start to reach the end result.
Currently, our whole offsite backup project, including Vembu, is about $500 per year to back up everything that we have. It is a lot of data, about 50 terabytes.
I find the licensing model to be valuable. The payment model is done with a set price or per virtual machine, and it is also done annually or on a permanent basis. You can choose whichever licensing model you prefer.
For our company, the current price of Vembu against Veeam is a few times cheaper. In our infrastructure, if we picked Veeam, we would have to pay about $20,000 per year. Now, we are currently paying about $2,000 per year for Vembu. You can do the math. The price is great.
Money always matters, so it could be cheaper, but this is not realistic for the market.
When we started to look for this type of software, we had to choose between Veeam, Vembu, or Vinchin. Vinchin is a new player on the market.
We integrated a service provide into our own solution. This is why I picked Vembu at first, because it can be integrated with a third-party service provider and was the only software able to be integrated into our solution. Vembu offers a cloud offsite service, which is a type of Vembu storage where you can store your backups if you don't have other options.
Vinchin is easier to use with simpler interfaces. However, when you read the features, because it is new software in the market, there were not some functions built-in, like encryption. Vembu encrypts the traffic when it transfers it to its destination. According to our Vinchin and Vembu comparison, Vembu is pretty complicated against Vinchin, but Vembu is easier to install and update.
Reasons why we went with Vembu:
The software is currently satisfying our needs for us. We aren't using all of Vembu features at the moment.
We use data reservation in our offsite data backup.
It is compatible with almost everything that exists on the market. It's compatible with VMware and Hyper-V. With VMware, it works very well. We haven't had any issues so far.
I would advise to try it and not to look at the prices of the top players on the market, though do look at alternative software. Sometimes, you need to try more than one or two solutions, then switch to whichever one is better. Pretty often, we speak to some not-so famous product or company to complete our approach.
I would rate the solution as a 10 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:
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.
We were looking for a backup for Red Hat Virtualization. We don't need any advanced features from a backup solution yet. We don't have VMware or Hyper-V, we only have Red Hat Virtualization.
We are a service provider and we have many customers but we are only using this solution for one of our customers. They have a small environment with four servers.
It was very difficult to find a product that supports Red Hat Virtualization natively and to take a snapshot of the VM or a full backup or a dump from the machine. The option that Vembu proposed, to take the machine as an image, take it from the system, is also good. It has enhanced our backup system. Before, it was very difficult and we did it manually. Now, it's easy to take an image from Red Hat.
BDR Suite helps us deliver an enterprise-level data protection solution and reduce our budgets. It is about half of the cost of other products we looked at.
They said they can support Red Hat Virtualization and we assumed that they support any compatible system but we found we need to do a network backup or a network image, which is not what it said on their website. I have had many discussions with them about where this component is. Initially, I was searching for a component which would back up Red Hat Virtualization. They said they support this in the same way they support Hyper-V and VMware. I haven't found the feature in their portal or in any of their software. They haven't made a special agent for it, in the way they did for Hyper-V.
When we were in negotiations and discussing this with their pre-sales, we said we haven't found any documents from them talking about how they support Red Hat Virtualization. At the end of the day they said, "No, we deal with Red Hat Virtualization in the same way that we take an image of a file through the network." It's not native in the solution itself. For VMware they have a special agent. But for Red Hat, it's just a network backup, the same as files. When I asked about a license to support Red Hat, they said you just take the network backup and it will do the same job.
For the moment, that is fine for us. We will take the image. But it is not what we expected from the product.
We started with it just before the [COVID-19] lockdown in April, but we haven't worked much with it yet.
We have yet to test the stability of the solution.
We have also not yet tested the scalability.
In the future we may increase usage if we find it's good for backup. We plan to take the DR solution from them.
We haven't had to contact technical support yet.
We have used many solutions in the past. We switched to Vembu because of the Red Hat Virtualization. Our old solutions don't support it.
The initial setup was straightforward. There were no difficulties and no advanced settings that you need to learn before you do the setup. We had it deployed within minutes.
We have an enterprise license. We found it very simple and straightforward. For our needs, the price of the backup system is not too much.
However, the prices are not clear in the portal. Not all the items are listed.
We checked out Veeam and Acronis but both were very expensive compared to Vembu.
I can recommend Vembu for those who need just file backup.
It's a straightforward solution. It was easy to install and deploy for many machines, taking backups from files and servers in the same way. They offer 10 GB for cloud that you can use for free.
We haven't tested its compression, encryption, or deduplication features yet. So far, just our system admin is using and maintaining the solution.
We are using it for the backup of our VMs and restoration activity. We are deploying some new technologies for which we would be able to use the features of Vembu.
It has been very helpful for data backup and restoration and license management. License management and everything else works smoothly, which is very useful for us.
Its restores are nice and reliable. They are fast and smooth. As compared to other tools, they are 80% faster. The speed of the restores also depends on my network. We have less than 10 gigs of speed.
It provides multiple options to recover data during hardware failures or accidental deletion of files. They have many options to restore the data. We tested them during the DR last December. Having multiple ways to restore the service and data is very useful.
Its download VM feature is useful in migrating physical machines to our VMware environment. There were no challenges in doing that through the GUI. It was user-friendly.
The ability to map a drive and restore a separate file is most valuable. The restoration activity is good.
The data integrity check features are useful during the restoration activity. At the time of restoration, we are also checking the DR plan.
We haven't yet checked its compatibility with the new technologies in the market, such as Nutanix. It would be good if any new technology can also accommodate Vembu.
They need to improve their marketing because not many people are aware of it. People ask me what is Vembu, and I have to explain to them it is a good tool for backup and other things.
I have been using this solution for more than three years.
Its stability is good. Its reliability is good when we have VMware and Linux VMs. It works smoothly.
Its scalability is dependent on the number of licenses that you purchase. Currently, we have 10 to 15 engineers and project managers who use this solution.
It is being used extensively. We are using only Vembu for the backup part. So, our core data depends on this solution. We have around 20 VMs, and we are taking backups of almost 100 GB of file server data. We might increase its usage in the future. Some of the people approached us to go for a new tool, but I explained to them the features that it offers. We don't have any plans to move to another solution.
Vembu team is giving excellent support to us. They provide 24/7 support. We can reach out to them at any point in time. They are able to address and give proper support for our queries. I would rate them a 10 out of 10.
My organization was using another solution previously. I have used Symantec backup and other tools in my previous organization. All these tools are more or less the same.
It was already installed when I joined this organization.
We have seen an ROI in terms of reliability. When we invest in a backup solution for infrastructure backup, it should work at critical times. With Vembu, I am able to restore data quickly without any issues.
Its price is reasonable as compared to other solutions. There are no additional costs.
While increasing the count on the server-side, we have to take care of managing or optimizing the license.
We have not used Vembu's instant boot VM feature for instant access to our VMs or physical machines after a crash. We have also not used Vembu for the backup for Microsoft 365, Google Workspace, or AWS.
I would rate Vembu BDR Suite a 10 out of 10. It is a good tool for backup, replication, and restoration. Everything is good in this solution.