We are using BDRSuite entirely on-premises. I don't think we will ever use it on the cloud, but I know they have a BDRSuite cloud offering. I'm gonna look at that for a few cloud-hosted machines. Mostly, we're using it locally. We have a team for deployment, but I did most of it by myself. It was so easy that we didn't need to involve my team. I only needed to add a server inside of BDRSuite. That's all it took. The whole process took about two hours. The only maintenance required is maintaining the physical hardware that it's running on. 

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

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. 

It was very easy to integrate the solution with our existing infrastructure. Everything was backed up at the end of the first week. And at the end of the second week, some refinements were added to make it more informative regarding what it accomplished and a little more efficient in how it did the backups. Two weeks was plenty.

We have three users of the solution in two locations.

It's very easy to integrate Vembu with existing infrastructure. You can put a server by itself, so it doesn't interfere with the existing installation in any way. I haven't had any problems with that so far.

I am able to do the integrations myself.

It does not require much maintenance. You have to check the hardware and then see that everything goes well. I've set up some reporting, so I receive messages in case anything goes wrong or in case the backup fails. But it's very stable, it works well.

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.

The initial setup took eight to ten hours and after one week we had to call to set up some backups on our drive space.

One person was required for the deployment and it was straightforward to integrate with our existing infrastructure.

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

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

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

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. 

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

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

The initial setup is simple. We used our RMM to push the agent to the server. Once the agent was configured on the server, it started working.

Once the service is configured, we add a user account and push the agent. This is all part of the onboarding process. It takes between five and fifteen minutes to add the account and add the users to the account, either on the server or on the console. Once the users are added, the agent is pushed automatically to the endpoints. I deploy the solution for our clients.

BDRSuite is easy to deploy and integrate with existing infrastructure. You can complete the deployment in less than a day. After the deployment, you need to install regular updates. Vembu puts out updates frequently. 

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

Its setup probably took 10 to 20 minutes.

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

The solution requires minimal maintenance. 

The initial setup should be more user-friendly. 

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.

It is straightforward when it works. I have had issues a couple times with new client registrations.

Deployment takes less than an hour.

My implementation strategy is to register the cloud account, install the client agent, configure the jobs, and then run.

It was already installed when I joined this organization.

The initial setup is very simple.

The initial setup was very straightforward.

Vembu has two options for deployment, Windows or Linux, and so we had looked at both options. Both options for setup and configuration were pretty straightforward. There were some bugs that needed to be worked out, so we had to engage the Vembu support team. That team engaged very quickly and worked diligently to get the issues resolved. There were two or three things that needed to be addressed. Ultimately, we chose to go down the path of Windows deployment for Vembu, not necessarily because there were problems with the Linux platform, but because the Windows platform seemed to work better for us for some of the automation that we're doing. Overall, it was very good. 

The initial proof of concept to deployment was about a two-month venture for us. It was not very long.

Three people were required for the deployment. We're all engineers and I have the decision-making ability.

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).

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.

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.

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.

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.

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 initial setup is straightforward and doesn't take much time.

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.

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

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

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.

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.

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.

Compared to other backup solutions, the initial setup was the most straightforward.

The initial setup was not complex at all. It was easy.

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.

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

1. to limit overhead on our current infrastructure and 
2. if any of our hosts went down, our backup would not be part and parcel of our host network. 

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.

The initial setup is straightforward. And what was nice was that I had somebody on the line to talk me through it, just to make sure. You're allowed to play around with it to get more familiar with it. Coming from a Veeam background I tried not to compare it with that. I had to work with it to make 100 percent sure that I appreciated Vembu.

I figured out most of the things by myself because it's straightforward. It's very easy if you have some form of IT or backup background. It should not be a challenge or an issue. Maybe if you're brand new to computers it could be a challenge but if you have some experience with running backups it's easy to work with.

The deployment was done within two days because we don't have a big setup. It was just me involved in the setup, from our side, and for maintenance I have an IT assistant. If I'm not there, he can handle it as well.

The initial setup is very straightforward. The solution is very easy. It's not a complex one where we need to follow detailed diagrams. I installed and tested everything and it's running fine now.

Initially, I had some issues but I fixed them myself. When I deployed this tool it was having issues with some virtual machines, specifically with Windows 2019. Fortunately, I was able to fix that issue by updating the Windows version to the latest software.

The whole setup took one or two days, including the installation and configuration of servers. 

Fixing the issue I mentioned took some days because I need to update the servers. Otherwise, the overall deployment did not take a long time.

In terms of a deployment plan, before deployment I considered my whole environment and then I started the deployment. Our IT team is just three or four people and I did it myself.

The initial setup was complicated because of the Application-Aware feature not working.

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.

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.

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.

The initial setup was quite good. There were no major hiccups.

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.

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.

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.

The initial setup was straightforward.

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. 

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.

It was very easy to set up. It took us about 30 minutes to deploy it.

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 initial setup was straightforward and well-documented.

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.

The initial setup wasn’t too bad. Once we got everything working, it has been running okay.

To install Vembu, the only thing that takes time is the download. But once you have downloaded it, within 30 minutes you are up and running. You schedule your backups and you go to sleep.

I was the only one involved in the setup.

There are two guys on my team who maintain it. They have administrative rights on Vembu, like me. They also have many other responsibilities besides Vembu. It doesn't take a lot of effort to maintain it. Once you're up and running you just check your backups and the status to make sure that everything is running. And if there is an issue, you check the log to see why you are having that issue.

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.

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 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.

The setup was straightforward and support was always available if needed.

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.

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.