Here, we have only worked with business clients. We had worked with customers who had complications, and we had customers who were in the early stages of either a fresh setup or a very complex configurations going through the very old versions of an agent and also the different vendor-specific storage boxes.

Most of them are no longer supported. They have only worked on older versions, such as six, version six, or 5.5. 

Now they want to import the data into the new service, and we provided them with a solution to import the data. We were successful in one of the customer locations. We used to do fictitious R&Ds because we didn't have the platform to work out and be comfortable and confident in those concepts.

I rate the product's initial setup phase a three on a scale of one to ten, where one is difficult, and ten is easy. The product's initial setup phase is complicated.

The documentation quality provided by OpenText Data Protector is not as good as OpenText VIM.

The solution is deployed on an on-premises model.

The solution can be deployed in two weeks, though it was already in place and a part of our company's environment.

My company requires two people to manage the product's deployment phase.

It is easy to setup and I would rate it a seven out of 10.

The initial setup was pretty simple for anyone technically minded.

We took these steps:

1. Built a server to host the Cell Manager (Windows, Linux, or Unix)
2. Installed the cell manager (Windows executable or Linux/Unix package)
3. Entered the needed information
4. Installed the needed components to the clients.

It only really gets complex when you start using integrations such as Zero Downtime backups or VMware.

The initial setup is easy. I rate the ease of setup a nine out of ten. The deployment takes around half an hour.

The initial setup process for the solution is easy. 

The time taken for the deployment depends upon the infrastructure. If you have a lot of servers and storage, a lot of effort is needed to take care of the integration part of the solution. Veeam's deployment process is easier since it has a better user-friendly GUI. But, again, it depends on what the customer exactly needs.

Our company only needs staff members while carrying out any upgradation or migration processes.

The setup was a little complex. You follow the steps, which are very logical and straightforward. However, once you get beyond that, you start to define your backup process and that's when you fall over. If you haven't put a lot of thought in that up front, such as defining that you want to perform disk-to-disk backup and then replicate to tape.

In our justification, we didn't make that clear. When we went to talk to our business distributor, we were then given our disk-to-disk setup. Then we wanted to change to disk to app, so we had to repeat the painful process again.

The deployment for Micro Focus Data Protector was easy.

The initial setup is straightforward if you understand Data Protector. The deployment takes around two days. You need a consultant for the deployment. 

I would rate my experience with the initial setup a nine out of ten, where one being difficult and ten being easy. 

It is very easy. 

Setting up Data Protector is straightforward. I rate it 10 out of 10 for ease of setup. 

The initial setup in general was simple. However, if you want encryption, you need to install something else, and there are other models for reporting. This can get a little complex since it is not a single solution that gives everything out-of-the-box.

We have four or five guys from our backup admin team who work in here regularly.

The initial setup was straightforward. The installation manuals are well done and there are several setup wizards at our disposal.

I was not there at that time. It shouldn't actually take much time, maybe a few weeks or one month.

Data Protector is quite simple and easy to deploy. The deployment is always the same. It's on a server, and the agents are deployed to the machines in a straightforward way. We have two engineers who deploy and manage all our backup solutions. 

It was complex. We had a consultant in for several weeks to get us working. We needed to get the ZDB type, and virtual backups working. The file system backups were no problem.

The solution's initial setup was easy, but it took two months to complete the process because of its poor technical support.

The initial setup is fairly straightforward because it was historically a Unix system. It takes about half a day to install. 

As for the initial setup, it's perfect for small- and medium-sized companies.

I've only worked with this particular company for eight months and they've had the solution for a number of years previous to my start. I did not play a role in the implementation and therefore can't speak to how easy or difficult the setup or deployment was for them.

I'm not sure how many people the company used for deployment or how many are needed for maintenance.

For me, setting up Micro Focus is straightforward when it comes to the Windows platform, but somewhat more complicated on Linux because I am not very accustomed to Linux. 

It will generally take one month for the planning phase, then another month for testing, after which we can implement it and move it into production.

The initial setup was fairly straightforward. We did not have any difficulties.

For us, it was easy, as I had extensive previous experience of the product. I first used the product when it was called Omniback I, (not Omniback II). And, as stated we deliberately built the initial deployment as a drop in replacement for NetBackup in the Data Centre.

The initial setup is quite straightforward, like Master Media Server. 

The initial setup is mostly straightforward. An example of a complex installation for me, would be Microsoft Exchange. Micro Focus Data Protector is still a bit of a gray area, but it's easier. It's not modular. You always need to copy the whole SAN in order for you to achieve success.

It's an easy deployment. It's a basic server from the client to the device. It's a little bit of a two-step pattern compared to the Symantec Back Exec deployment, which is the simplest way to install your backup solution. With Data Protector, there are a few additional steps. That said, implementation is easy once you know what you're doing.

The length of time it takes to deploy is approximately 45 minutes for a single server. With clustering, it might take two hours. Now with SAN storage, it might take you a half-day, due to the configuration.

Give me a basic set up, and I can do it within 30 to 45 minutes. I can set the servers up, install the binary, have it detect the media, and then I can deploy the agent and backup any machine.

I don't have the storage inside my server, the storage is connected somewhere else. Connecting the configuration, depending on how I presented the device to the Data Protector, could be 30 minutes to half a day.

For maintenance, ideally, one site should have three engineers. However, in our environment, I am the only backup administrator for five sites. I would say that's understaffed for the solution.

The setup was simple, i.e., both the setup and the administration are simple. That's one of the advantages (maybe the only one) of the HPE Data Protector.

The installation was very straightforward. You simply:

1. Point to a source to be secured
2. Define a pool of media
3. Define a backup device
4. Create a schedule

Poof! You’re in business.

I was somewhat involved with the setup. It was in-between straightforward complex. The initial configuration takes time, as does the customization and fine-tuning of the jobs.

We're doing a huge backup for SAP. We do a backup every 10 minutes of very critical data. We don’t do the whole backup, but rather the database log backup. This data is really huge. It took us time to fine-tune it and make it better. HPE assisted us with this process a year and a half ago.

The initial setup was complex. It's because it's not user-friendly. I think they can work a lot harder at making the solution more intuitive. Deployment took about two weeks. For deployment and maintenance, we only needed two people.

It was easy and there were no major difficulties.

The professional services department is excellent in terms of the setup and configuration. We updated the hardware technology to work with the software. I definitely couldn’t fault them in that respect. The issues are with troubleshooting and when you need support.

The initial setup was extremely straightforward. We have a great team of system engineers and they worked on getting the solution to run within our environment without any real issues. There weren't any real issues in getting the system setup and running.

It's straightforward for me.

The initial setup was complex. It was not easy. Data Protector itself is easy to install, but sometimes when we re-install it, it doesn't work and some agents do not work properly especially for Microsoft and for Unix.

Our deployment was done in 2008 and it took two to three days to finalize our deployment, the agents, and everything and to be sure that all backups were working well.

The initial set-up is very straightforward. Nothing special to be done, as it's got very friendly user interface.

I've been involved in redesign and all the upgrades, not the initial setup. It's quite straightforward.

Initial setup was straightforward.

The time it takes to set up a virtual machine with the software operating system is very quick if it's a new installation. But if it's an upgrade, it is quite difficult, because it takes time to convert the database to the new user. The performance of this product in the Windows platform is not great so we usually don't install it. With VMware, it is easy to attach the kit, the package ISO file. Then the setup is quite easy. In that sense, it's like the other products for this. It's probably more difficult than implementing in a network environment, with firewalls in between middle servers and clients, or between some manager and the new servers.

I found the initial setup to be ok. I would not say simple or complex, but medium.

Our goal is to have the simplest possible solution that will work without extra effort.

The installation is pretty straightforward and simple. It's not too complex or overly difficult. A company wouldn't have any trouble setting it up.

The deployment is fast and likely you can have it up and running in a day.

You don't need a big technical team to handle deployment and maintenance. You might just need two people who are engineers. 

The initial setup was rather complex because we had many different systems to include. But in the end, everything went fine.

Upgrading the solution is straightforward. We do it ourselves without any help.

It was so many years ago that I cannot say anything about the initial setup; but I do know that when we set up Data Protector in a new location, it works quite simply.

The initial setup is straightforward if you know what you are doing. However, due to the flexibility, you may find that you need someone who can guide you in terms of doing the minimum that is required, instead of just over-configuring it. 

In 2010, when I started using it, the backups were actually failing every day, only to find that there were too many mismatching configurations due to the flexibility. 

The deployment process can take a couple of days. For us, we are a large environment. While the installation itself doesn't take long, the configuration will take time in terms of configuring the backup devices and making sure that everything is working. We need to test and then add new clients. Most of the time required is just to configure the backup devices, like the disks to the virtual tapes, and add that line. However, the installation itself doesn't take long. That part you can do in half a day.

There are just a few people managing the backup environment, however, there are a couple of hundred systems that are being backed up. In terms of the people, we have about five users who look after the environment. However, it's stable. They are not busy with the environment every day. It's just to manage backups.

In general, the size of the team needed to watch the system depends on the size of your environment. The platform itself doesn't need a lot of people. One person is enough. That said, just looking after backups is what makes you look for more people. Looking after the platform, we've been using one person for a long time. 

I wasn't directly involved but I think it was straightforward, because the integrator who did the installation was an expert.

I've been involved in a few iterations of upgrades and that seems to have gone quite seamlessly.

The initial setup was quite easy.

The initial installation is straight forward. The complexity begins when the backup clients are added and backup jobs start to get configured. That’s when all the error messages start appearing.

One of Data Protector's key benefits is its simplicity. It may be the simplest product of this category to implement and operate.

The initial setup was complex in terms of IT, the business, and our technical support. I think it is possible for us.

The initial setup was very straightforward.

The initial setup was straightforward.

I was involved with the setup and it was reasonably straightforward. You install Cell Manager, then you create distribution servers, and then you roll out to a virtual machine. It's a pretty straightforward process.

I'd say for a typical organization of our size, where you're not able to send someone on multiple training courses and make them the full-time "backup guy", it's probably going to be a project that requires external consultancy. There are very many moving parts. It's a complicated architecture with confusing and not-always-consistent terminology.

The product is somewhat complex because of container object permission inheritance. Compared to a “normal” Windows software, it was a bit more complicated.

I have installed the solution myself. It was easy and took approximately 40 minutes. 

The installation was really straightforward. Just check the integration and you are done. The only consideration is that you must have a really powerful profile to do all the installations.

The solution is easy to implement.

The initial setup was relatively easy.

Reading the manual and following instructions will result in a working version.

The initial setup is complex. You have software to install on all of the machines and communication to set, including security communication. It's a delicate process, and it's not something common and easy to do. Normally we plan downtime with the customer. For a big enterprise, we take nearly a week to upgrade the solution.

Occasionally, we have problems when upgrading. Sometimes there's something that's not automated and you need a specialized person that can do the upgrade or the installation for you.

Initial setup was very simple. With GUI or Command Line Interface, it's just a few steps and the software is installed and ready for the setup the jobs.

It's a very simple deployment on file systems, Exchange, SQL server, and VMware, and more difficult on SharePoint, SAP and Oracle, and even these difficulties are derived from the Applications architecture itself. It depends on how large is your backup scope; the wider it is, the more time you need to dedicate to the implementation of the product. However, the Initial set-up itself is not complex.

The initial setup was really complex. I am not at all impressed by this solution. It was difficult to find anyone here in Denmark to help us with the setup because my experience was that everybody was moving away from this solution. So we had to do the installation ourselves.

The initial setup is very complex. It's hard to understand how the components work together and how each component is related together. I read a lot of information but I still don't really understand MFDP. I don't spend much time on it, therefore it's hard to understand. 

The information about MFDP is easy, but the application of it is not easy. When I deploy the software, I only understand it because I have written down all the information.

It just takes a few hours to finish the installation and the configuration.

The initial setup was simple for me because I am experienced and have used Data Protector for many years. It takes one hour maximum.

The initial setup is straightforward if you understand the architecture correctly.

The initial setup was complex and we needed support from HP to complete it.

It was mostly straightforward.

The initial setup was 12 years ago. That’s a long time ago.

The initial setup was complex.

The initial set-up is very intuitive.

We use it for all our

1. Oracle Database and applications
2. File servers
3. VMWare environment [SQL Servers, business & Intranet applications etc]

We had an issue during implementation of off-host LAN free backup of vSphere virtual machines using HP Data Protector. However that was mainly due to limited knowledge of the consulting company implementing the solution. After the implementation we didn’t face any issues.

It's pretty straightforward. It's never more than a few days, even in large environments.

Once you understand how the pieces fit together, it makes sense. When we purchased Data Protector, we also purchased installation assistance. I'd certainly recommend that to get the setup right. Information transfer is very important.

It was a little complex for everything, because it's the data-protector concept.

Because of the version we were on, it was quite complex at the beginning.

The initial setup was straightforward and quite simple.

Fairly straightforward when planned out and reviewed.

The first setup was complex.

Very easy.

It's very difficult to understand the interface initially. Without support, it is difficult to configure and understand the solution.

It was straightforward.

It's straightforward.

The initial setup wasn’t that complex, because Data Protector recognized all the tapes automatically, and we could adapt some settings.

It was straightforward - very little hassle to get it up and running.

straightforward:

- install the cell manager

- install the clients

Initial setup was straightforward.