The initial deployment was a little difficult. We had to install VMs in every vCenter cluster where we needed to have the management box. It took us a little bit of time to design it. It had ProServ with it. We followed the best practices. It was a medium project. It took us probably six to nine months to convert from NetBackup to NetWorker.

The initial setup is very easy. It's incredibly fast. We once attempted to install Commvault, but it took us several days, and we couldn't get it to work. 

While deploying NetWorker was a breeze and could be done in just a few minutes. I even demonstrated this to the Commvault team, and they were bewildered. They couldn't believe that I could set up a new NetWorker installation within 20 to 23 minutes. So, for me, it is simple and intuitive. I personally don't face any issues.

The deployment process for NetWorker is relatively straightforward and doesn't take an extensive amount of time. Downloading the package, uploading it to the server, and installing it are typically the basic steps in the deployment process.

The initial setup is straightforward. However, PPDM is a lot easier to deploy than NetWorker.

The initial setup is easy. As you go on to configure the databases, multiple teams are involved, like the database team, the Unix team, and the backup team. Even then, it's pretty easy and straightforward unless you run into some infrastructure issues.

The solution is deployed on the cloud and on-premises.

The time for deployment depends on the size of the environment. If it's a small environment, and everything is in place and works, it takes just two or three hours. If the customer has a larger enterprise, then, obviously, it will increase because you need to install extra storage nodes.

The initial setup is not complex. It's straightforward. Once you have all your prerequisites ready, then you are good to go.

The initial setup process is easy. The time taken for deployment depends on the kind of tool we want to integrate. Some configurations, including integration with data domain, on-premise, and on-cloud, are complicated. It took us a few weeks to complete the process. The software is simple to set up and has an OVA system allowing employees to configure IP addresses. Although, it is challenging to backup the device or library.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

I had technicians and engineers in my company to take care of the setup part of the product. The setup process of the product was straightforward. 

The product's setup phase can be completed in a day. My company hands over the product to the customer once they learn how it works.

The product can be deployed on an on-premises model. It can be deployed in the cloud or on-premises.

The initial setup can be difficult at times, especially when dealing with Data Domain port-based authentication. Managing where the Data Domain is located on the port side can be a particular difficulty. Deployment takes around two to three hours to complete whereas port installation take around two to three weeks. We have two users to do the implement and maintain.

The initial setup is a little complex as you have to deploy a virtual machine or  NetWorker on a physical server, depending on your architecture and environment. However, once that operating system is deployed, the NetWorker installation is quite simple. The deployment takes about half an hour, but the integration with the virtual machines and the environment takes two to three weeks.

The initial setup was not straightforward. It is complex.

We had two people managing the process. 

The ease of initial setup depends on your experience. The concept of NetWorker is slightly different from NetBackup, for example. If you have enough education about the product and understand the administration and installation procedures, it's quite easy. The time taken to set up the product depends on how complex the infrastructure is.

Setting up Dell EMC NetWorker is not complex. The setup was straightforward.

A company will find the initial setup wot be straightforward. It's not complex or overly difficult. The implementation process is easy.

It takes half an hour to one hour. You can do it yourself, but sometimes, you may run into issues and require tech support. We have five people for 24/7 support for our customers.

If it is a virtual machine and you're upgrading the Networker version, you have to take a snapshot image before you upgrade it so that you can roll back to the earlier version in case you run into a problem. EMC doesn't support upgrades.

I have been working with this product for a long time, so I find the installation very easy. This is also an area that has improved over time, as it has because easier than it used to be.

The length of time required for deployment varies between environments. Recently, I deployed it and it took approximately 20 minutes end-to-end, with configuration.

The initial setup is complex. Currently, my team is doing an upgrade and they are having a lot of trouble. They have attempted it multiple times but are still unable to complete the upgrade.

The initial setup of Dell NetWorker is straightforward. The process took a few days to complete.

The initial setup was easy.

The solution itself was easy to set up, but configuring a global disaster recovery environment was quite complex.

The implementation was difficult and, due to some reason, it was not done properly and we had to suffer a lot. The problems were only rectified only a month ago, after multiple follow- up with EMC teams.

I would rate the initial setup six out of ten because technical expertise is required for the process.

The initial setup of Dell NetWorker uses a software package that you can implement on the server, operating system, or on a virtual machine. The software implementation takes about 30 minutes. The integration with the whole environment depends on the size of the environment.

The initial setup is very complex but once that's done, the rest is easy. We've deployed this solution to 10 customers. 

The initial setup was very straightforward.

A partner did the initial setup, and we shared the venue. The setup was not difficult because we outsourced it to a consultant. So that consultant came in and deployed the solution for us.

The initial setup is very straightforward and simple. It's not difficult to set up at all. 

Backup systems are one of the most tricky to maintain as there are so many factors that can influence the backup process. Not only the backup - also the computers themselves, the operating systems, can play a role. It takes a moderate level of maintenance.

The initial setup is very straightforward and usually takes a couple of hours. 

The initial set up is easy, but when you do it for the first time you will need videos and some information to support the process. Once you do it once, you can do it really quickly the next time.

We have a lot of clients who use NetWorker. Especially in government and big companies, they rely on the NetWorker to do their backups. Two or three people are needed for deployment. 

The initial setup is a little bit complex, but it is very good. In terms of configuration, you have a basic administrator account. If you are going to be configuring Hyper-V or another technology then you have to have an admin account for those, as well. Without a proper administrator account, you will not be able to perform backup and restore functions.

There are also other things to consider, such as the network port and user compatibility. Hyper-V has issues to consider with respect to configuring the backup.

In a larger environment with multiple servers types and network security zones, it’s a complex installation to ensure stability with performance.

The initial setup is not an issue, it can be installed easily.

We have a total of 35 servers, that were installed individually.

The initial setup was a little complex, but engineers should find it ok.

The deployment of the solution is easy when integrated with the data domain systems. Additionally, the documentation is available and it is simple to follow. It took approximately one week to deploy it. 

The initial setup for a new deployment can be a bit complex but with experience, it's very smooth. It takes perhaps 20 minutes to install.

I did not participate in the installation. It was already installed when I arrived.

We have a team of 5 engineers to deploy and maintain this solution.

We didn't handle the implementation ourselves. I wouldn't be able to discuss the procedure or if it ultimately was complex or straightforward.

The reseller took about one month to help us internally understand how to work with the solution. We were grateful for the help as the solution is not easy to administer. 

We have two people who are responsible for the solution and the backups.

The initial setup is completely easy, not hard at all. 

The initial setup was straightforward. The configuration was not difficult. We used user guides which helped us with best practices. 

Initial setup of EMC NetWorker is really easy work if you have basic knowledge of OSs, LAN and SAN, if needed. (A basic IT background is really needed). Just a few clicks in Windows or the installation of a few RPMs in Linux. I really like that EMC provides specific RPM packages and not only binaries in its archive, which are installed by installation script.

The initial setup was complex. In fact, the NetWorker Management Console is divided into many tables. To configure a simple backup, you have to switch between many tables. You must have a good understanding of the configuration logic before you can manage this tool.

Initial setup was complex because I had to integrate Exchange Server and I had no knowledge on how it works.

I asked to the Exchange administrator to assist me on the deployment and together we setup up the Exchange backup job.

The initial setup is complicated. It is difficult to implement for clients.

The initial setup is complex. It requires a long brainstorming because you need to consider servers, storages, storage nodes, client servers, and the main backup server. It's quite complex. Brainstorming and designing will take time. You need the full verification and sometimes more than that if you have many servers where you need to install the client.

The initial setup doesn't take very long. It's only used by the backup admin.

You need to have some knowledge, but overall, the initial setup is not that complex.

Deployment depends on how many machines you want to back up — but that's not really a big issue. I think it's fast but it depends on if you have virtual machines, and on the size of the machines that you need to backup. The first thing you have to do is design. If you design everything properly, the setup is easy. Once this stage is complete, it's not a problem.

The setup was very difficult. 

Initial setup was straightforward. The documentation is good.

The initial implementation is not straightforward. It's a bit complex. I wouldn't say the process is easy. You have to create a map of the main points and storage. There are three levels of the agents. While it's easy to use for the customer, setting it up is a bit tricky.

The initial setup is easy, it's not complex.

The initial setup was a little complex but that was my issue. It's worth spending a couple of hours to go through everything thoroughly beforehand and take proper notes. If you don't follow the documentation, you can get into problems. Otherwise, it's pretty straightforward.
Deployment time depends on the situation. Implementation probably took three or four hours. Once it's running smoothly there's no maintenance required. 

The Installation is quite easy. 

The deployment took a maximum of three to four days.

The complete installation needed a bit of extra time due to some downtime for adding systems. But generally, the basic installation and configuration are done within three to four days.

The installation is straightforward.

The initial setup isn't straightforward or complex. It's somewhere in between. Deployment took about two weeks.

The initial setup was complex in 1996, but now our environment is simpler, thus requiring two servers.

Installing NetWorker is somewhat complicated. You need people with some technical expertise to do it. It takes one or two Dell-certified engineers to deploy and maintain it. 

It takes a few hours for a smaller implementation. I can plan and implement it.

It takes more time for a larger implementation.

We have one engineer to deploy and maintain this solution.

The initial setup is moderate.  It's not easy but it is not complex.

Complex in this version. It is not intuitive and logs are not easily accessible or decipherable.