The B6200 was designed to ingest data from different networks and we had three. Some we had to do some additional VLAN tagging.

No issues during deployment of the 4430 device into the enterprise environment.

While the setup was simple because of HP's involvement, it's been complex to run because of a third-party. They put it in a shiny new case and started changing some things. If they'd have left it alone, it would have been fine.

Our partner brought the technology to us, bought it on our behalf, and are running it on our behalf. They told us that they have a lot of knowledge and that they know how to run it, but in reality they don't and have not followed best practices. So now, they're kind of moved out. We're getting our hands around it ourselves, and it's behaving a lot better.

No Issues , Its pretty easy .

Early on, the firmware had some issues, but it has been steadily improved by HPE.

No real issues other than the change in mindset for our backup administrators and the increase in the number of jobs that are now configured. For a typical remote site the following seven jobs exist:

1. Daily Differential Backup (Monday to Thursday) to local StoreOnce
2. Daily Post-Backup Object Copy to Datacentre A
3. Daily Post-Backup Object Copy from Datacentre A to Datacentre B
4. Weekly Full Backup (Friday) to local StoreOnce
5. Weekly Post-Backup Object Copy to Datacentre A
6. Weekly Post-Backup Object Copy from Datacentre A to Datacentre B
7. Weekly Post-Backup Object Copy from Datacentre B to LTO Tape

There is also now the requirement to upgrade HP Data Protector to provide certified support for newer StoreOnce OS releases. HP Data Protector upgrades typically bring with them enough problems on their own.

I have not encountered any deployment issues.

No issues encountered.

When we first obtained the B6200 we did fill the disks due to our lack of understanding of how the the storage sets worked, which caused us an issue as the system at the time shutdown the F/C connections to stop any further data being sent to it. HP had to become involved in restoring the system, but this problem has now been addressed with new firmware.

The deployment of the solution is done by HP, they insisted on it, the initial planning was the task of the client, there were some bumps along the road, but in the end it was deployed rather quickly.

Due to the huge number of sites we have, we needed something easy to deploy. Configuring a new unit is a matter of minutes.

I have not really encountered any deployment, stability or scalability issues. We haven’t faced any major issues.

We've had no issues with deploying it.

We've had no issues deploying it.

We've had no issues with deployment.

I have not encountered any deployment or scalability issues. The product is really stable.

No issues encountered.

Not especially.

We have no issues with deployment.

Segmentation was one of the requirements. The HP team promised us that it is possible, but it wasn't available.

Not so much deployment more on the support end of things.

No issues encountered.

No issues during the deployment.

No

In the beginning, we had a lot of problems with bad firmware.

No issues encountered.

No issues encountered.

HP Solution delivery team implement this solution, deployment was quite smooth within time constraints.

No issues encountered.

StoreOnce deploys without any issues.

Until now we did not have any problems with StoreOnce. However, have had a problem with the HP Data Protector. In order to import tapes from StoreOnce, we had to identify the ID of the items in each store on the appliances, and then create them manually on the HP Data Protector.