Dell NetWorker Reviews

Primarily, I use the solution in order to backup to tape, usually for long-term backups.

With NetWorker, I'm still trying to use it more now, as I wasn't so much in the past.

I like how easily I am able to recognize the labels, the barcodes on the tape. With NetWorker, once you know your tapes and you have your record of them, you should be able to identify them easily.

The updated graphical interface is better than it used to be.

The initial setup is very straightforward. 

The solution is very stable.

We find the product to be scalable. 

Technical support is very helpful.

In older versions, the graphical user interface isn't so good. 

There should be more vendors incorporated into the solution.

I've been using the solution for about two years or so. 

We have found the stability to be quite good. The performance is reliable. There are no bugs or glitches. It doesn't crash or freeze. 

The solution scales well. If a company needs to expand it, it can do so. 

We have five people working on the solution in our company.

We do not plan to increase usage at this time. In fact, we may switch to another solution.

We have been satisfied with technical support. They've been helpful and responsive. 

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

I can't speak to the licensing costs.

We are considering switching to Commvault. We're looking into it a bit more. However, that would depend on what the client would like to do. It's not up to us.

I've been using the solution as a customer and an end-user.

I work on the latest version of the solution, however, I can't speak to the exact version number. 

Currently, I'm just trying to find out if, let's say you've done a backup with NetWorker in the past, how are you'll be able to migrate that data to Commvault.

I'd rate the solution at an eight out of ten.

I am using Dell NetWorker for backing up mission-critical business databases.

The most valuable feature of Dell NetWorker is its quick configuration and handling of large databases.

Dell NetWorker could improve the GUI to include rack recovery.

I have been using Dell NetWorker for a few months.

The solution is highly stable.

We have four engineers using this solution in my company and we plan to increase our usage.

Dell NetWorker is a scalable solution.

The support from the vendor was quick.

I used IBM Spectrum Protect prior to Dell NetWorker. We choose to use Dell NetWorker because it has quicker recovery time objectives and the integration into DD is a lot better.

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

We had some assistance when we did the implementation. However, after a while, we can do it ourselves.

We have observed a return on investment by utilizing Dell NetWorker, and we deem it a worthwhile expenditure compared to not having the solution.

The solution follows a subscription model for licensing. We pay annually to use the solution and the price is high.

I would recommend this solution to others.

I rate Dell NetWorker an eight out of ten.

We run a software-based service. You need a network of software, and for that, you need one physical server with the connectivity of fiber cables and fiber cords. The server configuration has to be high.

I like that it's stable and scalable. 

It could be more user-friendly. 

I have been handling Dell NetWorker for about a year and a half. 

Dell NetWorker is a stable product. 

On a scale from one to ten, I would rate its stability at seven.

Dell NetWorker is a scalable product.

On a scale from one to ten, I would rate its scalability at seven.

I have a capacity-based license, but I don't know the exact cost of that license.

On a scale from one to ten, I would give Dell NetWorker a seven.

We use Dell NetWorker for backup on tape libraries and for integration with old systems. 

The solution requires better technical support. There also needs to be improvements made to the integration with the environment. This includes an improvement made to the restored models for a lot of applications.

I have been using Dell NetWorker for 10 years.

Dell NetWorker is not the best solution, but it is decent. Many customers depend on it for backup.

Dell NetWorker is a software, it is not scalable. This is not required.

Technical support for Dell NetWorker is not good. The technicians are in the USA. When you open a ticket, they send the concern to India. There, the team does not have enough knowledge to support you.

Neutral

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.

Dell NetWorker has two types of licensing models. One is a capacity license and the other is a circuit license for virtual machines.

I do not recommend Dell NetWorker as a solution. I rate the product a five out of ten overall.

The GUI is the best feature. It's very good and easy to use.

It is very easy to manage and easy to configure the backup.

We are having some issues with some of the features. For example, the reporting, or the display of current licensing on the portal need improvement.

The reporting is not to our satisfaction and our main area of concern. It doesn't provide any form of analysis.

There is a delay in the offering from Dell.

Support is definitely an area of concern because of the time it takes to resolve our issues. We should not have to wait long periods of time to have issues resolved. When a complaint is logged the issue should be resolved within a reasonable amount of time.

I have been using Dell EMC NetWorker for 20 years.

We are currently working with version 19.0.

Version 19 has been stable, but there were several versions in between that had some issues, such as versions five, eight, and nine. In addition to the stability issues, there were some concerns with the performance.

Scalability for us is limited because we are using this solution for system backup. and not beyond that. We don't have any cloud, and we do not have any snapshot; it is simply a file system backup.

We have not yet explored scalability. Our requirement is a very basic one.

We have contacted technical support for the issues that we are facing with some of the features and their response to us was that they are faced with some delays in resolving these issues. This is the reason that we are exploring other backup solutions.

We have several cases that are pending and have been for a very long time.

Support from Dell needs improvement. We are not getting the type of response that we were expecting from Dell.

The responses we have received from Dell have not been encouraging.

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

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

The licensing model can be traditional licensing or capacity-based licensing. We have traditional licensing rather than capacity-based because of our long history.

We are currently evaluating other products as we would like to replace Dell EMC NetWorker with another backup software. We would like to carry out some PoCs to see which is the best. Feature-wise, we would like to know which is the best on the market.

We are also evaluating other products to see which features this solution is lacking.

I would recommend this solution, but if asked specifically about the support then I would not recommend this solution's support.

As far as performance is concerned, and the working functionality point of view, definitely it is a good solution.

We have also used this solution for the last 20 years. Definitely, there is a level of comfort.

However, as of late, maybe when Dell had taken over from EMC, we have noticed there is an issue as far as support is concerned. We are not getting good support, which is what we are supposed to get from them, especially since we have been long-standing customers of EMC NetWorker. Regardless of what we were supposed to get, we are not getting it.

I would rate Dell EMC NetWorker a seven out of ten.

We use Dell EMC NetWorker for several solutions we have had such as Exchange, Microsoft SQL, Linux, Windows File, File data backups, and Oracle Databases.

It's easy to use.

NetWorker is coming to end-of-life in a couple of years, and even Dell has said that they are not going to continue with it. They no longer develop it.

They put their efforts into the new Power Protect products instead. 

Support for the cloud could be better and with the existing features, it could be a bit more robust. Also, the flexibility could be improved.

They need more support for image backups.

The company has used this solution for 15-20 years.

We are not working with the latest version.

It's a pretty stable solution.

It's not scalable. Once you have created a backup server and you have configured it for a specific load, then you can't change it. 

You have to estimate how big the load is that you are going to have. If that increases, suddenly, you will need to create a new server. 

I wouldn't suggest that it is scalable. Scalability is an area that needs improvement.

We are an admin group and we have several technicians that look into it as well. We have 40 users in our organization.

Experience with technical support varies, sometimes they are very good and other times they are not that good.

However, their higher levels of Technical support are very good.

I used other solutions in earlier employments. This company has been using NetWorker for as much as 20 years.

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.

They are not cheap. I don't know the fees specifically but they should definitely be cheaper. Everything should be cheaper :-)

Since they are going to stop developing this solution, I cannot recommend it to others.

I would rate Dell EMC NetWorker a seven out of ten.

DD Boost integration for capacity reduction and backup window.

This product has provide our backup and recovery capabilities for Service Restoration and Disaster Recovery for more than a decade. We have evolved with the product over the years and it continues to meet our requirements.

Automate/role-based Virtual Machine protection and automated DR recovery capabilities.

Initial install was in 2001 with Legato 6.4. We just completed the latest upgrade to EMC Networker 9.1.

All x.0 versions that we have deployed have had issues which get worked out in the subsequent releases. We generally never deploy the x.0 version and wait instead for the x.1 SP 1 release.

Early on, we had limitations in the number of servers as a single DataZone could manage when pushed up to deploy multiple DataZones. Those numbers have significantly increased but for large environments, this could still be a limit. The number of connections that the solution uses with the VMware Hypervisor can cause issues with vCenter's performance, but that is more a limitation with VMware than EMC NetWorker.

Over the years, it’s been up and down. For this latest version, I would suggest that it’s average, with not a large number of EMC specialists understanding how all the latest features in the product are supposed to work.

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

Don’t install the newest x.0 version of the product. Make sure you understand you own requirements and expectations of data protection in terms of Service Restoration and Disaster Recovery to ensure you are implementing the solution appropriately to meet those requirements.

Backup jobs can be scheduled and automated

Monitoring of backups and configuration tasks are centralized

Compatibility of the solution covers large OS/DataBases/Applications

In a large enterprise DataCenter there is traditionally a lot of applications/databases which are owned by different administrators.

Without a centralized backup solution, each application/DB owner has to ensure its backup separately and if a problem occurs, he has to execute recovery tasks. In these conditions, the application rower has to make some extra jobs : backup scripting, verifying backups have finished successfully, recovery jobs... This does impact his efficiency and the global enterprise efficiency.

If a centralized backup solution like Networker is deployed, the backup/recovery tasks will be on the responsibility of only one resource which is the backup administrator. This does directly involve that each application/DB owner can spend more time on his real job: optimizing the platform that he owns.

With Networker 8.0 I had an issue related to VMware VADP backups.
An Image level backup of a RHEL VM finished successfully, but when I tried to restore it the transfer speed was very low, and the restore operation took 20 hours to restore 17 GB which represents 50% of total VM size. I was then obliged to abort the restore operation because there was backup jobs planned and Networker was deployed with only one tape drive in this case (the tape drive can't write backups and perform restores simultaneously).

I contacted the support team to analyze this performance issue. They said that this happened because it was a Linux machine backed up with Windows Vcenter Proxy. For me this is not acceptable... I hope this will be resolved in the 8.2 version of Networker, because restore speed is important (RTO)

4 years

Deployment tasks are not really hard. Networker is well documented.

7/10

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.

IBM TSM; HP data protector; Symantec Netbackup/Backupexec are main competitor to Networker.

I remember a customer asked me to advise him between deploying Networker or TSM. The customer wanted to integrate a Data Domain device to his backup solution. I advised him to use Networker because TSM is not compatible with DDBoost protocol which improves DataDomain performance: Deploying TSM in this case was a limitation!