The initial setup was easy. They helped us. All we had to do was install the boxes. Once we installed the boxes, they connected remotely and helped set everything up. We installed the client on the servers that needed to have them and they configured things and made sure everything was running with a little bit of testing. Then they let us go. They checked back a week or two later just to see how things were going. But we've had so few issues that it's pretty infrequent that we have to talk to these guys.

The integration process with our organization's network was easy and seamless. There was very little impact. The only thing we had to do is because we have an internet connection to our sister office, an MPLS network. At one point we had to increase our bandwidth. At certain times of the day — although we tried to do it just at night — if there was a large amount of data to replicate, then it would still be running the next morning. And that impacted things to a slight degree. After upping our bandwidth we had no issues at all.

The deployment of our newest boxes took two-thirds of a day or so. The biggest problem was my getting the other box up to Tallahassee. We could have had it shipped, but we don't have any IT in that other office, so one of us had to go up there. So the delay was really on our end because I had to get the hardware up there and install it. We spent two or three hours in the Orlando office setting all that up and then another two or three hours in our Tallahassee office setting up the other box. Altogether, it was definitely less than a day.

Quorum maps out the implementation plan for you. They do some research in the beginning, before the box is ever shipped. They needed an IP range for five or six IP addresses. We sent that to them and they labeled what was going to be the interface for each office. They've got it down to a pretty streamlined process where there's really not a lot of lag time or any mysterious questions.

It takes one person, from our side, for deployment. We have a staff of two people in our IT department. The other person I work with stayed here while I was in the other office setting it up. Since we're the only people in the IT department, nobody else would be going in and using it.

In terms of maintenance, there really is none on the Quorum boxes. They push out updates every once in a while. Generally, they contact us and say, "Hey, we have a couple of updates to put on there." It's usually 30 minutes every now and then. I wouldn't even say that happens on a regular basis. They've done their homework and their hardware works pretty dependably.

The solution’s initial setup is easy. It takes around 30 to 40 minutes to deploy the solution. Installing any agent or making a DR site takes a couple of hours and not more than that.

I found the initial setup to be incredibly easy, compared to other backup solutions. It's as simple as giving it an IP address. It gives you the option to download the agent and you put the agent onto that server. You double click, you hit about three buttons, and instantly, the next thing it's saying is, "What's your retention time, and how often do you want to back up?" That was about it.

It's incredibly intuitive and straightforward. You're not running through hundreds of screens to get what you're after. There aren't hundreds of options out there that the typical user would ever even need to touch. That is by far one of the big reasons I've stuck with this solution, because it's so incredibly easy to use.

To get all 30 servers done it took me about two hours. It took me longer to get it out of the box and into the rack. I had already given them the IP information beforehand, so they had it pre-programmed. They said, "Plug these network cables into this specific VLAN, power it up, go to this website, and we'll call you at 2 o'clock on this day."

The training, from knowing absolutely nothing to being up and running, took about an hour-and-a-half. Then it took me, maybe, half an hour to an hour to get all the servers on.

Integrating the solution within our network was really easy. I gave them an idea of what the VLANs were for my servers, even before they shipped the appliance to me. They did the vast majority of the work before me. It came with a sheet of paper that said, "The first three interfaces need to be on VLAN one, the last interface needs to be on VLANs one and nine." I went into my network switch gear and I set tag ports for both of those specific devices, and I plugged it in. After that, I just made sure that I could see traffic on my network interfaces. It was a breeze.

I was quite impressed by the fact that everything related to the product's initial setup phase was simple and very straightforward.

For the deployment process, my company had to indulge in some preparation work, after which we got the servers set up, and it took only an hour to finish the setup process.

I received the product's documents, which I used to set up the solution. Every other process related to the deployment of the solution happened remotely.

The initial setup was really straightforward. I received the servers and, in one day, I had the servers physically deployed to each location. Within two days, we had every server up and running and backing up its current node, and we do have a fairly high amount of bandwidth availability. We had finished with the servers on a Thursday and Friday. By Monday, all of them had sent all of their data to their DR systems. Everything was replicated.

In a matter of five days, we went from having the old system up and running, to dismantling the old system, bringing the new system online, and copying everything over.

When we talked about the deployment, there was a team of engineers I was working with. They took our previous environment — they had all of the information from that — and they sent me a document that I had to fill out, which was super-easy. I gave them a list of IP addresses that they needed. I gave them subnets, gateways, server names, and what I would like the onQ servers to be named. They reviewed that information and came back to me with some changes that they would like to see. We reviewed it and talked and, within a day or two, we had something set that we were going to deploy. Once we did that, they started the work on their end and when I got the servers, they were 90 percent configured.

There were two or three engineers I spoke with for implementation. Then I spoke with an engineer for deployment and another engineer for the miscellaneous odds and ends that we had to finish up with. They were all from Quorum. On our side, it was just me involved. 

As for the integration into our network, I didn't have to do anything. I plugged it in. I'm dead serious. I plugged it in and that's it. You can't get any better that that. Because I sent them all the information for IP addressing, subnetting, servers, set up, how many servers at each location, where the DRs were going to go, how they were going to transfer, it was all done on their test network. They plugged everything in and created all of the links to the devices and then they sent them to me.

Including the ordering of the servers, the whole process took about a month. Once they got the information from me, they had to order servers and receive them, install and configure the software, and get confirmation on where they were going to be shipped.

And I'm the only one involved in maintenance of the solution. I rarely have to do anything with these. They are incredibly low maintenance.

This system is easy to install and it can be completed in a few hours. It can be fully implemented within one day.

The initial setup is easy and straightforward, very seamless.

The initial setup is okay and straightforward, but there are some restrictions because we don't have in-depth access to configuring or troubleshooting. As a partner, we need full access to the system. In addition, we got support from the OnQ team for the initial setup.

I rate the initial setup an eight out of ten. When we have another box implementation, we'll have a more accurate picture of how easy or complex the setup is.

Quorum OnQ works as a backup system for us. It is used for a limited number of systems, and all other systems are on cloud.

It was very easy to integrate and configure and set up. It's straightforward. Having had the process explained to me the first time, I have been able to manage the system on my own ever since.

The deployment took a day.

The implementation plan was to get the device plugged in and turned on. The Quorum technician would then connect and help with any final configuration. We had already had a few configuration talks beforehand regarding what was required with the device we bought. Then we just needed to start the backups on each of our servers.

The initial setup is straightforward.

The initial setup was relatively straight forward. That was one of the selling points of Quorum with the appliance device. I did some due diligence and figured out sizing capacity, so they could size the appliance correctly. They had me run some tools for capacity-planning in my environment. They took all that information and they came up with the right size solution for the appliance that I needed.

To provision the appliance, they had me drop it into my network and spin it up, which is very easy to do. Once they had connectivity to it we finished the configuration on it. They then gave me the ability to manage the appliance and start getting backups from my VM environment onto it. 

So the implementation rollout was a very easy, handheld process. They did a lot of handholding and it was very white-glove. It was very easy, which was great.

The initial setup is a bit complex. It gets easier once you familiarize yourself with it.

The initial setup is very simple. They walk you right through it.

Implementation of OnQ was one of the easiest I have ever been involved in. Quorum was involved throughout the entire process, even sending a tech onsite to complete the install.

The initial setup is very simple. It's a prebuilt solution. Everything comes as a plug-and-play. We just need to connect it to the data sector with the normal IP configuring and then start the agent configuration. It's very simple, I would say.

The initial setup is quite straightforward.

The initial setup process was quite simple and very straightforward. The deployment took less than an hour. There wasn't really any maintenance and we didn't need to run any updates at that time. Once the agents were installed and configured, everything was running fine—restoration worked, and snapshots worked quite well. 

On our end, there was just one technical person working on this product. 

The initial setup is very straightforward. Deployment time depends on the number of servers but typically a 10-server implementation would take four to six hours.

The initial setup was very simple because we had all the technical support. But we do have issues like client connections to do the security, which takes time, but after that, the infrastructure is ready to go, and there haven't been issues.

It doesn't take more than a week to deploy the device. But to deploy the Quorum OnQ for a customer, and if it's a large client, it takes about a month to do the network setup and more.