To set it up initially, we had to do some tweaking. A lot of that was just understanding what we needed to do in order to accomplish what we were expecting, but once we got everything in place, it was actually quite easy. Now, I add new machines all the time. You just install the agent, set up your schedule, and you're good to go.

Its initial setup was pretty straightforward as I recall. I had the AppAssure crew for doing the setup. They were very astute at doing it. I just had to answer the questions, and they pretty much set it up. As I recall, I don't think there were any major blips or stumbling blocks that we had to deal with.

It probably took about a week on and off. We would set something up, and then we would test it for the evening and tweak it as needed the following day. So, it probably took three to four days.

In terms of the implementation strategy, the primary focus was obviously on the data. We put that on first and ensured that we've got a good clean backup of the drives that held the actual data files. From there, we moved on to backing up the server itself in terms of operating system partitions and that kind of thing.

It was pretty straightforward. The software is pretty intuitive, and you can do agent or agent-less installs. If you have a physical virtual machine, such as a physical VMware hypervisor, you can back up all the machines on that hypervisor, or you can install agents. With the agents, you can get a little bit more granular with the reporting information. So, it is pretty easy, no matter which way you want to go.

The deployment duration depends on the method you choose. If you're doing it agent-less, it can take as little as a few minutes. With an agent, it would probably take 15 to 20 minutes per server because you usually have to install the software, and then you have to reboot. So, it includes the reboot time.

Our implementation strategy was to back up all machines and then synchronize the two units with each other. We have an onsite unit and an offsite unit, and they back each other up. So, we had to back up all machines and then synchronize the two units so that they back each other up, and the offsites are stored at each other's location.

The initial setup was straightforward. We pretty much just followed through with the wizards and the configuration. It was very easy to get the Rapid Recovery host up and going and then use the deployment wizard to deploy the agents out to the workstations that we were trying to protect, following the knowledge base articles of how to configure it with our VMware ESX environment was pretty straightforward as well.

For us to get everything fully deployed and everything actually protected it took a day or two. But out-of-the-box, we were up and running with Rapid Recovery, getting things done within about four hours.

Our strategy was to just get it done. The physical installation and then the actual software deployment, and we had a stair-step of which assets had to be up and running immediately. We wanted things to be protected immediately on the local server and then we needed to do the replication to the offsite server, but that was lower down in the process because we knew we were going to have to create the initial replication to an external drive and then move that to the offsite and import it into the offsite server before we could actually start live replication between onsite and offsite hosts.

The initial setup is not really easy. You don’t know about the software. You need to set up the software on the server. Then server-wise, you will define the repository desk where you are making the backups. After that, you need to define the client or the server client from which you need to take the backup from. Once complete, you can store it anytime.

You can use this to conduct a backup every week, every day, or every hour, and if there is any problem we can restore the fix on the server at any time according to the time lost.

The deployment did not take much time and can be completed almost in one hour.

The initial setup for Quest Rapid Recovery was straightforward. Deployment only takes thirty minutes if you do an OS patch, otherwise, it'll only take fifteen to twenty minutes maximum.

On a scale of one to five, with one being very complex and five being very easy, I'd give the initial setup of Quest Rapid Recovery a score of five.

I was not involved in the initial deployment but the upgrading process was pretty easy overall. Obviously, the only down part about when you have to upgrade the clients is you have to reboot the virtual machines, which does cause a little bit of downtime. So, our company's in a 24/7 environment. We do have to reboot some of our servers when we deploy the new agent.

The time it takes to upgrade depends if there are Windows updates, unfortunately. If the Windows updates haven't been done in a little bit, it takes a little while. It can take anywhere from 30 minutes to an hour. But typically it takes 10 to 15 minutes for a virtual machine to reboot.

Both installing and upgrading are simple and straightforward to do. It is not a complex process to set it up. The complete deployment takes less than 15 minutes.

Based on the customers that I have now, my implementation strategy focuses on VMware. VMware connects to Rapid Recovery using vCenter. It is set up so that customers retain their data for one month.

Because Rapid Recovery doesn't have a secondary backup, I also have the archiving solution as part of this. 

I would rate the easiness of the initial setup as an eight out of ten. 
During our initial setup of Quest Rapid Recovery, we encountered some smaller issues, mainly related to version compatibility and system changes. Setting up Quest Rapid Recovery was quick and done within a day. We started by ensuring the required prerequisites were in place. One server was dedicated to Rapid Recovery, and another acted as a proxy for communication. After installing the Rapid Recovery client on both servers and establishing communication, we configured settings and set up a backup schedule, deciding on file-level or full backups as needed. The process was straightforward, making the deployment efficient and completed within a day. One person with the right skills is all it takes for the deployment.

It's quite easy to deploy the agents and everything on the virtual and hardware servers. You just have to remember a few pointers. One thing that you have to do, if you're performing an upgrade on the cores, is to make sure that you upgrade the off-site repository first. After that, you move to your on-premise server, where you do the update of the core there. You have to work from back to front, starting with the off-site server. Other than that, it is pretty simple.

The deployment did not take very long to complete. Most of the time can be spent if you have an issue with the virtual machine, and you want to get rid of all of its snapshots, then delete it from the vault. That will take a long time to replicate a base image of, for example, a SQL Server. That takes a couple of days, but it's down to the VPN as well, because of the bandwidth consumption. This is an issue that I have become accustomed to and I don't have too many problems with that side of things. You get what you pay for.

The initial setup was straightforward. Deployment took about two days. You only need one person for deployment. Maintenance is operationally delivered. It means you just restore, and make sure the backup is okay, and you're good. You need one person for maintenance and one for administration once the solution is deployed.

This was handed over to me. Someone else installed it initially, and since then, I have been managing and taking care of it. We will be changing the hardware very soon. The hardware is out of warranty for almost two years. I might get involved in the new installation.

I didn't set up the system originally. When I came in, they were already using the system so I didn't know that it was an inappropriate configuration. Once I was able to talk to technicians, they described what the best practices were so we modified the machines with the local disk instead of USB, then it was much better.

Even though we did this deployment over a weekend, we were able to get everything done over a weekend so it didn't impact the usual Monday through Friday work week. It was very important that there were no big impacts nor distractions to the work environment because it is just disruptive to users' work. In this situation, all the users' case files and data were on that drive, so it had to be restored. Otherwise, they wouldn't have been able to work. This is why zero to very little downtime is important, because it just completely disrupts the business.

It does require a little bit of upfront time to get everything configured via best practices. Once it is set up, it is fairly reliable as long as your Internet connection and network stay stable.

The initial setup was very straightforward and simple. It was just the standard "next, I agree, next," and setup. The retention policy is in plain English.

The solution is complex. We tried hard to set up the solution, and it took us a while to activate. Deployment took a couple of days as we had to leave it and come back until we finally succeeded in implementing it. You only need one IT person and an external consultant for deployment and maintenance.

The initial setup is relatively simple. It's not hard. 

The initial setup was complex. It took a while to deploy because we had a lot of challenges. We didn't get it to a perfect, 100% point. We are managing it the way it is.  

The initial setup is very easy. It's not complex. Installation only takes maybe five or six minutes. Edge installation takes another five or so minutes as well, so you are up and running in ten minutes.