HPE GreenLake Reviews

It replaces our entire server infrastructure. Everything that we do today has now been replaced by GreenLake, as far as our data center is concerned.

I haven't got all my workloads on it yet, so I don't really know how it performs when it's fully loaded. It is certainly looking very positive, but I just don't know yet.

The performance of our batch workloads with SLAs (for our batch reporting) will start to be met.

It helps with our IT team's productivity, as they can focus on their day-to-day jobs rather than adding the management of the infrastructure into their task list. Thus, they can focus on the more business critical components of their role.

We like the way that we can OPEX the service. 

Its performance is a significant improvement over the legacy stack that we had.

It sort of lines up with our direction to move to the cloud. By using a hybrid cloud service to get us there, this allows us to run our legacy workloads on-premise. Those which are not really suited to a proper cloud.

It is pretty simple to use. The team is able to pick up OneView pretty fast, and they are extracted away from the underlying working, which is cool for us.

It offers flexibility in IT operations, but it hasn't done it yet. We should see this in the future.

We are still managing the VMs in our IT operations.

We don't have all our workloads on there at the moment. We have had a few little teething issues, but they have been rectified very quickly by the HPE support team. Therefore, it seems okay. We will know more in a year or so.

It certainly appears to scale well beyond what we need it to do.

The technical support has been very good and proactive. We have had problems that have been resolved in appropriate timelines.

It is replacing an existing, legacy SAN and compute stack. The existing stack, Fujitsu, was coming out of support, and we couldn't get parts for it anymore.

The initial setup was done for us, so it was straightforward from our behalf.

The interconnects were a challenge originally, but they sorted that out, and It was fine. We did have to spend a bit more money, but it wasn't really a problem.

We used a third-party. However, they had to engage HPE, as they weren't able to do the work themselves. 

They have some learning to do in relation to the new HPE kit. It is relatively new. There are always problems and challenges with this type of implementation, and the end result has been good. I can only say the outcome has been fine.

I don't think we'll know until we get to the end of the contract if the service has saved us money.

We also evaluated Fujitsu, IBM, and Dell EMC.

We went with HPE GreenLake because the OPEX model for us just works. It helps us start to align with the company vision for an OPEX, cloud-based service.

We compared this against a pure, public cloud solution, and hands down, this was better for us because of our legacy workloads.

Understand what your compute workloads will be and be really clear on that. Otherwise, you will procure starting up with too much or little. Just make sure you understand what your compute will be so you can get your contract set up the right way.

It is doing what we need it to now, over and above what we had before.

While provisioning is quicker, we are not provisioning much new infrastructure into the kit at this stage.

We expect our capacity will actually go down over time, not up. Though, if we change direction or had an acquisition, it provides flexibility without having to go back for a CAPEX spend to get more infrastructure.

I don't think it has eliminated corporate provisioning. We can provision what we need and get more if we need it. Our intention would be to use less, not more. I don't think we have had to over buy. If we hadn't had gone down the pathway of a traditional SAN, we probably wouldn't have purchased what we are running with the GreenLake kit now, since our stacks would disappear over the next few years due to business transformation.

We primarily use HPE GreenLake to take server backups in our environment. It involves backing up servers from Jira, specifying the time range, and utilizing VMware ESXi to perform the backup. The backups are stored on NetApp, and we have multiple storage locations.

The most valuable feature for me is the ability to perform backups with a graphical user interface (GUI). It makes the process easy. 

The support service needs improvement. The support team isn't very active in addressing cases. It should also provide a web application. 

I have been using HPE GreenLake for about one year.

The tool's stability is around four out of ten. There have been instances where the system was slow, especially during restores.

I would rate the scalability at around four out of ten. It's not good. My company has two users. 

The initial setup was complex. It required the involvement of three people. 

In terms of pricing, it's a bit on the higher side.

I haven't used a different solution before HPE GreenLake. We chose it because our data center is based on HPE servers. 

While the concept of HPE GreenLake is good, the product has some issues. I would recommend comparing it with other solutions. I rate it a nine out of ten. 

The most valuable feature of HPE GreenLake is the integration.

HPE GreenLake can improve the price.

I have been using HPE GreenLake for approximately seven years.

HPE GreenLake is highly stable.

The scalability of HPE GreenLake is very good. My clients have been using the solution for a long time and it has been flexible.

The technical support of HPE GreenLake is good.

The setup of HPE GreenLake is straightforward. However, there is some complexity. The length of time necessary for the deployment depends upon the scope of work for the customer. For example, what activity we need to do. However, in general in a common standard scenario, the configuration doesn't take too much time.

We have enough knowledge of the HPE GreenLake platform to configure it for our customers.

We provide our customers with a customized HPE GreenLake so that they don't need to tweak anything in the infrastructure.

My clients are receiving a return on investment, this is why they are using it. You only have to pay for what you use in HPE GreenLake. It is highly flexible and is why it is a successful solution.

HPE GreenLake payment model is you pay for what you use. You can purchase a yearly, quarterly, or half-year license. The overall price of the solution is a little high and hopeful there can be better margins in the future.

I rate HPE GreenLake a nine out of ten.

There is always a scope for improvement in solutions.

One of our successful use cases was a customer that already had HPE SimpliVity and multiple clusters of it at different locations. They wanted to consolidate these workloads while also having a replication site. We proposed a consolidation model and recommended the HPE GreenLake solution, which they found appealing. The customer liked the idea of having the hardware on-site but also having a cloud-like experience where they could pay for the infrastructure on a monthly basis and have it maintained and supported by the HPE team.

One of the most valuable features of HPE GreenLake is that it provides clients with the security of having their data on-site while still having the convenience of having someone else take care of the infrastructure. Some customers prefer this as they feel more secure with their data on-site. Additionally, it allows the customers to have the best of both worlds, they receive a cloud-like experience of subscription and consumption, and the performance of an on-prem solution for their more demanding workloads. This is one of the main benefits that drive clients to choose this solution.

The solution integrates well with Dell, Cisco switches, or other switches.

HPE GreenLake can improve by making some of the user's experience better. It can take some time to learn.

I have been using HPE GreenLake for approximately three years.

It can work well for both on-premise and cloud environments, as well as hybrid models. The solution is stable and can accommodate any solution lines that HPE offers, such as dHCI, HPE SimpliVity, ProLiant servers, Nimble, and electric storage arrays. Additionally, it can easily integrate with network switches, making it a very stable solution.

The complexity of the setup depends on the solution being deployed and factors such as the amount of networking required and the previous environment. The difficulty of deployment can vary depending on factors, such as the Microsoft Windows operating system version and the VMware version. HPE generally handles the installation, but Connection is also certified to do it. It can be straightforward as the customer can choose to have HPE or Connection handle the installation. The level of responsibility is flexible and depends on the customer's preference.

HPE GreenLake has been growing in popularity due to its subscription model. The flexibility of the solution allows it to adapt to the changing market trends towards more edge performance and workloads.

There are several aspects of HPE GreenLake, but the sales flow is generally okay. It was a learning experience for both Connection and HP to figure out how the flow should work. Once we were used to the process, there wasn't much to change. The solution is versatile, it can handle dHCI, HPE SimpliVity, and other HPE solutions. I don't see any major areas that need improvement.

I rate HPE GreenLake a nine out of ten.

If the customer has the right partner then the overall experience with the solution can be good. 

We're working in a new data center in Virginia and are using it for our primary storage and compute. We're a cloud services provider and we provide co-location and disaster recovery. We're using it on the cloud services and the disaster recovery sides of the business.

We haven't had great success with it. Both times that we've had to increase the hardware, the deployment took way longer than expected. In addition, we haven't yet gotten to a use point where the cost is below what it would cost us to provision the same set of services on HPE hardware outside of the GreenLake service.

In terms of our capacity management efforts, it's actually provided us too much capacity at this point in time, and we're working to try to fill that capacity. We're currently over-provisioned in that service.

It hasn't increased the flexibility of our IT operations because in that platform, on that set of racks, we're not able to add in different solutions that we would normally buy internally and deploy on that set of gear. So we have to create a separate set of gear for anything extra that we want to add into the environment.

I think the solution has cost us money. It hasn't decreased the time it takes to deploy IT projects.

The most valuable feature is the ability to grow into a lower price point at some point in time.

Also, there's more visibility into the solution than we have in some of the other areas, but not significantly so.

I feel like I'm paying for 20 percent that I'm not using, because it's always over-provisioned by at least 20 percent or a minimum commit of 80 percent. Once you get up above that, you're looking at provisioning more and then that increases it again. I would like some flexibility on pricing at those lower bands, and not having such a high commit-percentage, if that's economically feasible.

There is room for improvement in the ability to scale down without a significant increase in cost. Fulfillment of the hardware in a more timely manner is also an issue.

We solely use HPE hardware across our organization, so I don't know that its stability is different than any of the others. We have more experience with some of the other hardware - 3PAR, c7000, the blades, etc. - so we're more familiar with them. We've had some issues with trying to configure the Nimble correctly for a few of our applications that we're working on, but support has been pretty good in working with us to get through those.

In terms of scalability it's tough for us. Right now, it's actually counterproductive for our scalability. I'm hoping that once we reach the upper band in our contract that it will provide us some scalability there.

Technical support has been really good.

We had heard about GreenLake at conferences and thought it might be an opportunity for us to use more HPE resources. We chose to try it at this particular deployment, versus our normal, self-provisioning of the equipment. 

The initial setup was pretty straightforward.

We deployed it ourselves.

We have not seen ROI.

Right now we're paying about $180,000 per year.

HPE is our shortlist.

My advice would depend on what the application is. In our particular application, it hasn't been helpful thus far. If you have an application where you're going to be at a price point, right out of the gate, which makes it cost-effective and you're only going to continue to grow at a steady pace, then I think this solution makes sense. But if you're starting at the very bottom of the scale, where the price point is high and you're not going to use the services that come bundled with the products, then it might not be as cost-effective as it could be.

I would rate the service at three out of ten, simply because of the costs associated with it. I could implement what we have now at a third of the cost.