I implemented it along with the support person. I searched on the web to select the vendor.

It doesn't require much maintenance from our side. There are just patch updates, and they don't happen during the backup window. They do not affect production. It's good.

I deployed it myself. I did use some documentation that they had. So, it was more or less trial and error. I was running a Windows OS on the NAS, and they didn't exactly say that they supported it. They just said, "If it works, it works. If it doesn't work, then you'll have to get the full OS because mobile NASs come with a Windows Storage Server." They didn't really certify to run on that. However, in the end, it did work quite well.

It was just me who installed it. 

In terms of maintenance, I was wondering about that. I tried to go in and see if it needed to be updated because I realized that I have never done it, but I couldn't figure out how to update it. So far, it hasn't needed any maintenance.

I implement the solution for our clients.

We did it on our own.

The implementation was completed in-house.

I deploy and maintain the solution.

We had help from the vendor team for the installation process.

We deployed it ourselves.

We did most of the work ourselves. We didn't use a reseller at all, it was so easy to deploy.

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.

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

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.

We bought it directly from Vembu and installed it ourselves.

I did it myself.

We deployed in-house.

We did it all in-house.

My experience working with the Vembu person during the setup was good. They are very proud of the product. They want it to work.

I didn't need too much help for Vembu, other than for licensing. They helped me on the licensing purchase.

We did it in-house.

Even the support teams supported us, which was quite helpful. The deployment took a few minutes. 

I am the consultant. I recommended this solution to my client.

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.

In-house.

I did not need a third-party to deploy Vembu. But when I used Acronis, I had to call their support. Acronis has a partner here in Nigeria that I worked with. The fact that I had to work with a partner with Acronis, and I didn't have to with Vembu, is a major difference.

Initially, I worked on it myself. But, due to some errors, I asked support to reinstall it, to fix it. They were good.

In-house, we were required to know the product to be able to support it as much as possible prior to engaging vendor support.