NetWorker Upgrade to 19.4 and a look at the enhancements

NetWorker version 19.4 is in GA as on 10th Nov 2020 with end of life on 30th Nov 2023. First let's take a look at upgrading NetWorker to version 19.4.

NetWorker Management Web UI enhancements

  • Using the dashboard to view a summary of active sessions and alerts
  • Viewing alerts
  • Monitoring active sessions, devices, and server messages
  • Creating and updating label templates, media pools, storage nodes, and devices NOTE: Device creation is supported only for Data Domain devices.
  • Creating and updating lockboxes
  • Creating and updating user groups
  • Index browsing for File system recovery

Stoplight API Explorer for NetWorker

Starting with NetWorker 19.4, the REST API documentation is available from the new developer portal: . The PDF versions of the NetWorker REST API Getting Started Guide and the NetWorker REST APIReference Guide will not be made available on the Support website.

REST API support for Exchange protection

Starting with NetWorker 19.4, you can use the NetWorker REST APIs to perform all critical operations such as client configuration, backup, restore, cloning, setting retention time, and so on that are required for Exchange workload protection.

NetWorker Virtual Edition enhancements

  • Availability of NetWorker Virtual Edition (NVE) in VMware vSphere, Microsoft Azure, and AWS with SLES12 SP5 base operating system
    • Support for fresh deployment of NVE
    • Support for direct upgrade from released NVE versions of 9.x, 18.x, and 19.x
  • Availability of NVE appliance in AWS marketplace of Paris (EMEA) region
  • Support for AWS m5.xlarge and m5.2xlarge type instances

NetWorker GDPR Data Integrity Compliance

NetWorker 19.4 has been enhanced to audit the events that can be performed on a save set. Please refer the release notes for 19.4 for more details about this.

Client states

Starting with NetWorker 19.4, you can now designate a state for a client. There are three states:

  • Active—Client is part of an active backup and has save sets associated with it.
  • Retired—Client is no longer part of an active backup, but still has save sets associated with it
  • Decommissioned—Client is no longer part of an active backup and does not have save sets associated with it
A client in the retired or decommissioned state is not part of a NetWorker DNS lookup or startup validation. This ensures efficient backup and validation operations as long as DNS failure lookup operations are avoided. There is also a reduction in failed backups given that these clients are not part of policies. The NetWorker startup time has reduced by two to three times when 40% of the clients are in the retired or decommissioned States.

Separate browse and retention time

You can now configure browse and retention time separately for traditional and NDMP backup and clone actions

NetWorker client FQDN compliant with RFC 1123

In the earlier versions of NetWorker, the NetWorker server, the NetWorker storage node, and the NetWorker client could be configured with a FQDN of up to 63 characters. Starting with NetWorker 19.4, the NetWorker storage node and the NetWorker client are RFC 1123 compliant and can be configured with a FQDN of up to 255 characters. However, the FQDN for the Networker Server is limited to 63 characters.

Disk space monitoring

Individual alerts are generated for each NetWorker client whose occupied disk space goes beyond 80%. These alerts are not persistent and get cleared automatically when the occupied disk space goes below 80%. After the services are up and running, if there is low space, one of the alerts, Info, Warning, or Emergency is generated based on the disk volume occupied. Disk space monitoring on a server node is for nsr and index, if both are in different volumes. Otherwise, it is for the disk that contains the nsr directory. Similarly, for all the standalone clients, it is for the disk which contains the nsr directory.

Clear persistent alerts

To clear persistent alerts from the Alerts window of NMC after a certain period, an attribute, Event clear interval, has been introduced in the nsr resource. Only the alerts generated due to the core dump of NetWorker processes are considered persistent. After the specified duration in the Event clear interval is exceeded for a generated alert, the respective alert is cleared. The default value for the attribute is 72 hours and the attribute can take any value from 1 hour to 14 days.

Block based support for XFS file system

NetWorker 19.4 provides block based backup support for XFS file system enabled save sets.

NetWorker support for the Ubuntu 18.04 LTS platform

Starting with NetWorker 19.4, NetWorker server, NetWorker storage node, and NetWorker client deployments are supported on the Ubuntu 18.04 LTS platform.

Restore support for independent persistent disks

vProxy backs up only the independent persistent disk configuration without any data. That is, the independent persistent disk is restored as raw unformatted disk in the guest operating system without any data. On restoration, the independent persistent disk has the original size and is part of the virtual machine configuration with the same disk number. If you select a VM that has independent persistent disks for image restore, you are notified about the presence of independent persistent disks.

Disabling SNMP traps while the NetWorker server is in maintenance mode

NetWorker 19.4 enables you to disable SNMP traps when the NetWorker server is set in maintenance mode.

NetWorker Front-end Capacity nsrcapinfo enhancements for date range and granular reports

NetWorker 19.4 allows you to provide the start date and end date for nsrcapinfo measurements. It also provides client level granularity with parameters such as Daily Peak Usage, Daily Maximum Cumulative Report, Overall Peak Usage, and Overall Maximum Cumulative Report.

Thank you for visting, you can also check out my YouTube channel - crazyRov Studios for Data protection and cloud related technical videos.