The initial setup was very easy. The longest time it took to deploy was getting the network team to configure network ports for us, and the IP addressing. Once that was done, we were up and running within 30 to 40 minutes of the initial deployment.

Starting with the racking and stacking in the data center, the entire deployment probably took half a day for half a petabyte of data protection.

To develop our implementation strategy, we had an initial meeting with Rubrik on the design and requirements from their side, in terms of network connectivity requirements and IP addresses. We had done a little bit of pre-work with the network team to get that up and running, and ready for plugin once the equipment was delivered.

15 minutes is the time that you need to deploy a Rubrik cluster from unboxing to the first backup. In other words, the initial setup is very easy and straightforward. As soon as you have the network ready to accept the hardware, the right credentials to configure the different vCenters in the Nutanix cluster, and all the backup elements, 15 minutes is the time that you need to be up and running.

I've been involved with upgrades but not an install because we just have the one on-premise device. I've been involved in multiple proofs of concepts. For example, they launched a couple of features along the way where we were testing cloud workloads and converting our images to native AWS images so that we could use it as a disaster recovery site in the future, if needed. All of our backups are going to AWS.

Upgrades are very straightforward. Their support is always with us, so we haven't had any hiccups during the upgrades. They go very smoothly. I've been involved in multiple upgrades, and we were at some point running the bleeding edge software, when we were looking for some features that were available, without any issues. So we did upgrade to the latest and greatest version. Our general policy is to stay one version behind to iron out all the bugs. But with Rubrik we have attempted to run the latest version, to use the features, and it has been stable enough for us and the upgrades have gone smoothly.

We usually block out a two-hour maintenance window for upgrades. There have been major upgrades which required some database work, and they have taken more time. In the move from version 4 to version 5 their whole database infrastructure was changed.

The initial setup is extremely straightforward. We went through the exercises and were provided configuration details that were required from us. I think that they were as simple as supplying IP configuration information. Then, once they assembled all of the racks and wires, the Rubrik technician showed up, configured the system, and it was all done in probably less than 20 hours in total.

Because we're virtual, it meant that our implementation strategy was simple. Essentially, once the Rubrik system had been configured, all we had to do was to point it to VMware vSphere vCenter servers and from there, it automatically picked up all of the virtual machines that we had. Then, it was just a question of assigning them to SLAs and removing them from the old backup system. That final piece is not included in the 20 hours because 20 hours was just to get the Rubrik running. But, it was extremely easy to integrate.

The initial setup is straightforward. The hardware install and initial setup went very smoothly and quickly. 

The only issue, two and a half years ago, was that we didn't have a great recommendation on how to back up specifically large servers. There are two different ways that we could do it: 

1. With a full VM snapshot.
2. With a file set level, which basically goes through the server based on a filter and only backs up specific files. 

We initially did the file set method, even though we were backing up everything. That was not the most effective way of doing this. We reversed course and just started backing up everything via vSphere snapshots, which works so much better. However, we probably could have received a little better guidance initially on that front from the guy who came onsite to set the appliance up.

Initial setup, after the planning, was probably only about four hours before we started getting backups. It was about a full week before all the backups were complete. We have some very large file servers that we were backing up. Some of those took a long time to finish for that first full backup.

We switched from our previous backup platform. We just transitioned over to Rubrik, shutting off the backup of the old system one day, then starting to back up with Rubrik the next day. Because most of our servers or objects are in vSphere, our Rubrik integration with vSphere made this very easy.

The initial setup is straightforward.

Rubrik's initial deployment was straightforward.

The initial setup is straightforward. Rubrik sends out a technical engineer when you get the appliance to help you get it online. Within a couple of hours of them being on-site, we were backing up data locally, as well as to the cloud. By the time they left, we had tested restores and our environment was backing up locally and into the cloud.

We did not have an implementation strategy and just followed Rubrik's guidance on how to implement it. They had a plan that was based on information that we provided them about our environment. That way, when they were on-site, we maximized our time with them to get it deployed. We really just trusted Rubrik with it.

Setting up Rubrik was both a little bit straightforward and a little bit of complex. We had the team that sold us the product there with us during setup and we went to add in all of the nodes at the same time. That was something that even that team had thought we could do, and then they remembered, in the middle of adding all the nodes at the same time, that we needed to do it in groups. That does take time. We were putting in something like 16 or 20 nodes, and we had to do it four-at-a-time. We had already done the physical installation and all the cabling, and all that portion. But when we started to add in the nodes, we had to do four and then wait for it to finish on that, and then do another four and wait for it to finish on that.

I think that, with time, they may implement a system that cues them up and continues to add nodes as it can. But that seems to be a similar problem to what occurs with other products in the same category. We also have Cohesity in our environment, which we don't use as a backup product, we use it strictly as a NAS, and it suffers from that same issue.

Our Rubrik setup took a few days, between our getting network issues figured out on our side, getting all of the cable management figured out with our data center team, the physical installs, the configuration with the Rubrik partners, and then adding in those nodes four-at-a-time until we had them all in.

We could have done it with less staff but we did want to make sure that all of us were aware of how the implementation worked, so we brought in all five of our team, two Rubrik partners, and two of our reseller partners, as well.

For maintenance of Rubrik we require two to three people. One works on Rubrik pretty much all the time, and the other four of us just jump in as needed on little things here and there.

In terms of Rubrik users, in addition to the five of us who do administration, we've given out access to a few of our database groups, so far, where there are 10 to 15 people.

I've been here 13 years, and I actually deployed it. I've deployed five different sites, so we don't have just one. For the most part, it was pretty straightforward. It took about 30 minutes.

From Rubrik being delivered to it ingesting backups, it took about an hour. To get it out of the box, racked, configured, and ready to go was simple. To be perfectly honest, we have probably never used a product that was as simple as it to deploy.

We had a two-week window set to migrate our backups from the old system into Rubrik. Instead of it taking two weeks, it ended up taking three days, which saved us time tremendously.

The solution's initial setup was not so complex and not straightforward. Since we had a different solution, understanding this concept was a bit time-consuming. Otherwise, it was smooth and straight.

The networking wasn't straightforward because of the way our network is designed, but it was pretty straightforward after that.

For deployment, we only needed two people: myself and a networking colleague. One of my responsibilities is to design policies. This solution requires regular maintenance, and I'm the primary person who manages it. 

For a product like this, you need high-speed connectivity to your virtual environments and database servers.

I find the deployment process very straightforward. It was set up in just a few hours.

The process is basically to rack and stack, then assignment management and data VLAN to the Rubrik appliance.

The solution's initial setup is easy enough, and we paid for a Rubrik expert to install it for us. It was easy in most systems, but there were ongoing issues with the Oracle backups.

It was totally straightforward. There was absolutely no stress or chaos. It was an easy deployment and easy migration.

Our environment is pretty huge. We have about 8,000 to 9,000 servers. The deployment took a few months. It probably took five to six months, but the nice thing about it was that Rubrik's support was there all the time. They were involved at every step till we completed our migration.

The physical installation of appliances takes one day. And then configuration takes maybe another day but it also depends on how many data sources you have and if your policy is defined in advance. Sometimes we have to wait for data owners to define the requirement for backing up. Within one, two days, you can set it up and get it going.

With Rubrik, I was not involved in setting up the backup restore solution. From a database administrator's perspective, it is really easy to set it up if you want to configure backups for a database server. You have to install the agent, and then the server pops up in the Rubrik environment as a new server. Then, you can configure your backup configuration and backup policies, and you're good to go.

I rate the implementation a seven on a scale from one to ten, where one is difficult, and ten is easy.

The majority of the deployments, like 80 percent, are done on-premises.

The deployment process takes a maximum of two weeks.

The number of people required for deployment depends on the data volume and the number of clients required. So, generally, we keep two people.

The initial setup was really straightforward. From unboxed to being in production it took less than two hours. That was with some of the networking we had to do around it as well. 

But we did go a bit too fast in terms of deployment. Even though it's incremental forever, it has to do that first full backup. We pointed a little bit too much at it the first time around and it struggled to ingest it all and move forward. After 24 hours, we stopped and started again because we were still backing up through the old method as well. When we started again we slowed the pace down to happen over three or four days rather than one day. At that point we had ingested everything and, from there, it's been smooth sailing. We haven't had any problems. 

The biggest thing I always say, if anyone asks, "What would you do differently?" is to slow down the initial rollout to make sure that you're not overloading the first full backups. The incremental forever won't be in position as quickly, but it will be a bit more stable.

I was the only one involved in the deployment. My platform team handles maintenance of it. I've got a junior infrastructure engineer who essentially looks after it. Her role is to look after monitoring and backups. But it's not something we ever really have to look at these days.

The initial setup was very straightforward. It was the easiest setup that we had on all of the systems that we had looked at before we bought them. When we moved from our PoC to production, we actually handled the setup of the second brick when it came in. We didn't even need to engage their field engineers to help us.

There were two of us involved, me and a colleague who is the senior network engineer. The deployment took about four hours. We actually redeployed both of them, the whole system, within four hours. We tore up the old PoC stuff, refreshed it all, and then started over with it because some stuff had changed and we needed to restart it. We did the whole system within about four hours.

In terms of implementation strategy, we cut over from our old system as fast as we could. We started with our large and most important system. We let that sit there and bake and perform its initial backup. Once that was done, we started porting every machine over that we could. It was great with the way that the system worked. We just went through our list of systems that we needed to move. He started at the top and I started at the bottom and we just checked them off, made sure that we got them all in. We then stopped all of the legacy jobs on the previous system and we were up and running on the new system within less than a week.

The initial setup is easy. I created a blog post about it.

The initial setup was extremely straightforward as Rubrik sends a field engineer out to handle everything. This goes for expansions as well. We had our initial two sites from the PoC stood up in less than two hours per site. The only reason it wasn’t faster was due to how locked down our network is. Other products we stood up at the same time took far longer to set up, and I mean one was two weeks before we could use it.

The initial setup was straightforward, and it took approximately one hour to get up and running. There are many background steps to take regarding network configuration. I carried out the deployment and perform the maintenance for the solution by myself. 

The installation was pretty simple.

The deployment strategy was four nodes on each side of each location and we have two locations. We did a POC and it was set up in no time. It was ridiculously fast and simple. Now, we're up to 16 nodes in each location.

There's not much to it. It's not a 28 step process. There's a little bit to it but it's plug-and-play, as much as a solution could be. 

The initial setup was extremely straightforward. The install took place one afternoon and included an upgrade. Within three hours we had our VMware environment tied in, SLAs configured, and we were prepared for the initial round of backups that were going to take place over a weekend. By Sunday morning, we had our entire infrastructure protected by Rubrik.

The initial setup was straightforward. Deployment took a day or two.

The initial setup was between an easy to medium difficulty level. To install the Rubrik application, we created an account, then specified the contribution of our VMs. The microservices took the most amount of time during the setup part. Later on, defining the duration and frequency at which we want the snapshots to be taken was easy. 

The setup took three to four days.

The initial setup was straightforward. However, since Rubrik was new to use and different than the previous our solution, there were some new things we need to understand, such as SLA based orchestrating. We were used to scheduling it manually before, Once SLA is done the automation in place.

The full implementation process took us two and a half weeks.

Versus any other solution, Rubrik was a lot simpler to configure. The first system was up, on the network and configured and ready to backup in under 20 minutes, versus multiple days of configuration with another solution.

In terms of deployment of the solution, it was vendor-aided. Rubrik helped through our SEs. If I had to guess, it would probably be less than half-a-dozen people who were a big part of the deployment, data center access and data center deployment notwithstanding. Some people had to go and plug and rack things.

We aren't interested in lagging behind as far as updates go. We're pretty good about updating to the latest version. The only reason we haven't done so right now is because it's in use. We continue to use it and the organization I work for is big. There are a lot of teams using it. So it's hard finding the time in the day where we can disconnect everything, upgrade the system, and then reconnect everything. That's on our side where we're trying to juggle all the teams that are making use of the product.

The initial setup is very straightforward. 

We have installed three Rubrik devices so far. The setup took only two to three hours at each site. We were immediately able to start backing up after the initial setup.  

I rate the product's deployment an eight out of ten. 

It was not complex. It was very fast, which is also a good thing about Rubrik. It just takes one day for hardware mounting and connectivity. In three days, we completed everything, including the integration between vCenters.

The initial setup was done in one to two hours, with racking the equipment being the most time-consuming part of the install.

The solution's initial setup process is straight forward if you get all the essential requirements from the client. Although, it takes work to ensure we have included the right SPF and network requirements for the data center.

The initial setup is pretty straightforward.

The initial installation was very simple. 

I would create the ease of installation a five out of five.

Initial Setup was simple.  I think the box took longer to mount in the rack than it did to setup.  

The initial setup process is a ten out of ten. It takes a couple of hours to complete.

It is pretty easy to set up because it is a physical appliance. You just need to configure IP addresses. There is not much to set up on that. You just plug it into the network and assign IP addresses. After that, you just log in, and you're ready to go.

The initial setup was very straightforward. It was a solution in the box. We didn't have to complete much configuration, other than having the right port open on our destination servers and deploying the various agents. It was very easy to configure the vCenter connections and start backing up our virtualized environment.

The trickiest part was figuring out how crawler sits in there. We set up a standalone server for that and installed crawler there. I can recover an entire database and granular emails within 15 to 20 minutes, now that I've practiced.

We're having another one put in and the implementation strategy will be to upgrade the current Brik, have the new Brik upgraded to that version as well, plug it in and it will configure itself, essentially.

The installation is straightforward. You fill out the sheet with names and IPs, and Rubrik sets it all up. However, it does use a lot of network ports, at least one 10-gigabit and one 1-gigabit port per node. That adds up quickly with multiple Briks that can have four nodes each.

Make sure you create different networks and segmentation. The IPMI 1-gigabit networks need to be locked down and not allow other networks to be routed to them.

Deploying Rubrik typically takes a few hours to install the server and get started with backups, but achieving full functionality for all backup needs may take a few days. However, you can begin backup operations within minutes after server installation, making it quick to start protecting your data.

The initial setup takes approximately four hours. In four hours, we set up the configuration, connected it to VMware, and took the first backup. The whole process was very simple.

The initial setup process for Rubrik is very straightforward and it primarily involves networking configurations.

Deploying Rubrik was simple for us. We check and ensure correct IP configurations and VLANs. Network issues are usually the only hiccups. The implementation is smooth, needing minimal resources. On average, without upgrades, it takes about an hour for installation and setup.

Maintaining Rubrik is straightforward. With its four-node architecture, upgrades, and maintenance are easy as it handles updates by rebooting nodes individually.

I recommend Rubrik as a good solution, but it is crucial to work with knowledgeable partners for effective implementation. Understanding how to use it is key. Overall, I would rate Rubrik as an eight out of ten.

The initial setup was straightforward.

The initial setup is straightforward. We were up and running within an hour.

Easy install/setup - Literally an hour from the box arriving to ingesting the first data.

Straightforward. The deployment was about 20 questions and 20 minutes, and it was done.

It's been fast. It took about one hour and was installed for free by a Rubrik field engineer. It is important to note that they have no offices in Italy, so they came from Netherlands for installation.

Easy. Plug and play.

Straightforward.

Straightforward

The deployment was not easy, but it was not complex. The deployment took one day.

It was straightforward. It took a maximum of two days.

For its deployment, you need one to two technical engineers. For support, you need one technical engineer. 

Very simple and assisted by their engineers on site.

Rubrik is very simple to implement and setup.  

The initial setup was straightforward. The bootstrapping process was right to the point and direct.

We found the initial setup to be very straightforward. It wasn't complex for us in any way.

The deployment process took a few hours. It didn't take too long.

Deploying this solution is very, very easy. As I said before, you don't have to ask a lot of question of the customer. You just receive the solution, the brick. You put the brick in the customer's data center and you just ask some questions about networking, IP address, what do you want to back up? And the solution is ready to work quickly. The installation is very easy, and the sizing solution, which is my job because I am in pre-sales, is easy enough.

Setting up Rubrik is easy, and their support team helped us through the process.

The initial setup was straightforward and maintenance is required for quarterly patching.

The initial setup was easy. The PowerPoints take something like an hour or two. Whatever the goal is, if you find problems, and you find a heavy percent of the problems are networking problems, you have the ports that need to be opened, and the person in charge of opening the ports is on vacation. But from PowerPoint to real life, there is not a big difference. The PowerPoint says an hour or two but starting from scratch to do backups, takes a few hours.

It was a straightforward setup. It was simple to do.

The initial setup is very simple and easy to deploy. Very straightforward. It's literally, I don't want to say minutes, but from a simplicity point of view, I don't think you can get it simpler.

The initial setup is very straightforward. Deployment to about three hours, no more. The setup time really depends on net issues. 

The initial setup of Rubrik is straightforward. It requires one person to deploy the solution.

The initial setup was very straightforward. 

The initial setup was straightforward. There is a bootstrap script, which does all the IP address initialization. for all the metadata disk preparation and service openings. 

Literally racked, powered on, and all done in 30 minutes. I just needed my Vcenter details.

The initial setup is relatively straightforward takes a team of three anywhere from two weeks to a month depending on size.