There is no dedicated person required for the maintenance. It is an application.

We implemented the solution through a partner within one day. Before we ordered, the box was almost preconfigured. The hard disk and the enclosure were already populated. We just connected all the power cables and checked the hardware and rack layout for any damages. Once we powered it on, we configured it as per our requirement and connected it with our software.

It requires two or three engineers to deploy the solution.

We take help from HPE's technical services for the product's installation.

Vendors supplied resources for install and initial configuration assistance.

We used a vendor team who were 5/10. HP sent their design team, and they were helpful but the StoreOnce product was very new and they were learning the product. We were given bad information which led to a crash.

It was done as an in-house implementation. However, we currently work with an HP partner in all our enterprise purchases. They're called High Performance Technologies, Inc. in Palm City, Florida, and the IT team at this business are outstanding and they all keep up to date with their HP certifications. They work with HP to obtain the best pricing for the equipment we need to ascertain. With this business relationship, comes years of trust and we know that they understand our enterprise network topology and make recommendations based off that long term knowledge.

Our partner implemented it for us, and the results have not been good.

I had HPE do it.

We did the implementation of HPE StoreOnce in-house.

We leverage the HP Level Two StoreOnce Startup Service which gave us access to the HP StoreOnce engineers for a few days. We were able to workshop our requirements and vision and come up with a solution that would technically achieve what we wanted. Unfortunately, HP Federated Catalyst depends heavily on HP Data Protector and there doesn’t seem to be much cross-skill of engineers between Data Protector and StoreOnce.

Thankfully we have over eight years of in-house technical experience with Data Protector so we were able to leverage what we learnt during the StoreOnce Startup Service to expand upon the solution and deliver above and beyond what we thought was possible. To make use of Federated Catalyst I strongly recommend a deep understanding of HP Data Protector (it’s not as scary as it first appears to be).

I was within support team, which did implement as well as support the solution.

A reseller was used to assist with the deployment.

We had HP do the implementation, with a third party consultancy firm called System Professional. They had exceptional understanding of the entire platform.

One of our engineers performed the deployment of this solution for our customer.

The set-up was completed by HP services.

As mentioned earlier, the solution was implemented along with HP, their level of expertise was above par.

We have a staff dedicated for that, so that was an in-house job. The StoreOnce unit runs on Linux. We have Linux admins, and it is frustrating for them to see that the product works out of the box and there's no need to log in using SSH.

Therefore, I recommend in-house implementation. It's easy, and the iLO UI is very user-friendly.

We had an HP engineer come in for implementation. He was excellent.

An HP consultant came to assist with deployment.  Deployment assistance comes with it when you buy the solution. Our experience with the deployment consultant was good.

We did the implementation ourselves.

The implementation was done through a consultant.

We used HP's technical support for the startup services. They helped us with the implementation.

We don't have staff at our data center. That was a bit of a challenge for scheduling, but then that is agnostic of the product that you're trying to install. Through the startup services that we purchased from HP services help desk because we have to integrate this with our backup product which we were a semantic shop, so we had to integrate that, the StoreOnce technology with that. They were very helpful in getting that done. Yes, it's slips in very well. One of the things we really like about it is that you managed everything from the backup console. Our backup administrator, well he is aware, but he manages it just like it's another store. The deduplication, all that happens in the background.

We implemented it through a vendor; it was a smooth deployment.

We did it in-house.

HP implemented the solution, but it's fine if you go at it on your own. The thing is, if you run into problems, then you have to deal with HP support, which is something I wouldn't advise anyone to do.

We are a BAU house, so our focus is on keeping the business running. We don't have the skill set of an American architect who scoped out the project. We've partnered with an HP partner who does have the skill set once we purchased StoreOnce.

HP installed the device for us, and showed us various configuration options. The team was very knowledgeable.

We implemented it in-house. I think the solution was easy to implement using HP Data Protector 8.01 at the beginning. The tricky part is the upgrades. I recommend upgrading the FW to latest the stable release before configuring.

It was implemented through the local HP support team. They provided us with excellent support and knowledge of the product technology.

In-house.

Implemented through a third party vendor. There were some complications with delivery of the units and site surveys not being completed. After those issues things were fine.

We implemented it in-house.

We implemented it in-house.

HP did the installation.

HP Implementation team delivered this solution.

We used a vendor team who were 8/10.