NetWorker ® SolVe Generator

Solution for Validating your engagement

Topic
Updating the NetWorker software
Selections
Which version are you updating to?: NetWorker 19.5
Which version are you updating from?: 9.x and later
Operating system?: Windows
NetWorker installation type?: NetWorker Server

Generated: February 8, 2022 2:24 PM GMT

REPORT PROBLEMS

If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]

Copyright © 2021 Dell Inc. or its subsidiaries. All Rights Reserved.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION (“EMC”)
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE
INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-
INFRINGEMENT AND ANY WARRANTY ARISING BY STATUTE, OPERATION OF LAW, COURSE OF
DEALING OR PERFORMANCE OR USAGE OF TRADE. IN NO EVENT SHALL EMC BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF EMC HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice. Use, copying, and distribution of any EMC software described in this
publication requires an applicable software license.

Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other
trademarks may be the property of their respective owners.

Publication Date: February, 2022

Dell Technologies Confidential Information version: 5.0.6.33

Page 1 of 41
 Contents
Preliminary Activity Tasks .......................................................................................................3
Read, understand, and perform these tasks.................................................................................................3

Inserted PDF #1......................................................................................................................5

Dell Technologies Confidential Information version: 5.0.6.33

Page 2 of 41
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.

Read, understand, and perform these tasks

1. Table 1 lists tasks, cautions, warnings, notes, and/or knowledgebase (KB) solutions that you need to
be aware of before performing this activity. Read, understand, and when necessary perform any
tasks contained in this table and any tasks contained in any associated knowledgebase solution.

Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity

2. This is a link to the top trending service topics. These topics may or not be related to this activity.
This is merely a proactive attempt to make you aware of any KB articles that may be associated with
this product.

Note: There may not be any top trending service topics for this product at any given time.

NetWorker Top Service Topics

Dell Technologies Confidential Information version: 5.0.6.33

Page 3 of 41
Dell Technologies Confidential Information version: 5.0.6.33

Page 4 of 41
Inserted PDF #1

Note: The next section is an existing PDF document that is inserted into this procedure. You may see
two sets of page numbers because the existing PDF has its own page numbering. Page x of y on the
bottom will be the page number of the entire procedure.

Dell Technologies Confidential Information version: 5.0.6.33

Page 5 of 41
Dell EMC NetWorker
Updating to NetWorker 19.5 from a Previous
NetWorker Release
19.5

June 2021
Rev. 01

Page 6 of 41
Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid
the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 1990 - 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Other trademarks may be trademarks of their respective owners.

Page 7 of 41
 Contents

Tables........................................................................................................................................... 5
Preface.........................................................................................................................................................................................6

Part I: Preparing to Update the NetWorker software................................................................... 10

Chapter 1: Updating NetWorker server on Windows ................................................................ 11

Chapter 2: Preparing to Update the NetWorker Software........................................................ 12

Interoperability and Backward Compatibility......................................................................................................... 12
Clone performance considerations.......................................................................................................................... 13
NMC Client.................................................................................................................................................................... 13

Chapter 3: Software requirements.......................................................................................... 14

NMC Browser and JRE Requirements.................................................................................................................... 14
Add the NMC server to Exception Site list......................................................................................................14

Part II: Updating the NetWorker software....................................................................................15

Chapter 4: Updating NetWorker for Linux................................................................................16

Chapter 5: Updating NetWorker for Windows.......................................................................... 17

Updating NetWorker from 9.x and later version on Windows...........................................................................17
Updating the NetWorker software.....................................................................................................................17
Updating the NetWorker Management Web UI software..................................................................................19

Chapter 6: Updating NetWorker for UNIX................................................................................ 21

Part III: Updating Methods ......................................................................................................... 22

Part IV: Post Update Configurations and Reviewing the Migration Results.................................. 23

Chapter 7: Post Update Tasks................................................................................................. 24

Verifying the variables in nssrc file..........................................................................................................................24
Improve clone performance...................................................................................................................................... 24

Chapter 8: Troubleshooting NMC GUI and NetWorker Server connection issues..................... 25

Troubleshooting authorization errors and NetWorker server access issues................................................ 25
Troubleshooting NetWorker daemon or service startup issues....................................................................... 26
Troubleshooting NMC GUI and NetWorker server connection issues........................................................... 28
There is problem contacting the server, server_name. Please verify that server is running.............28
An error occurred while validating user credentials. Verify that NetWorker Authentication
Service is running.............................................................................................................................................. 28
Tuning the JVM heap memory........................................................................................................................... 29

Contents 3

Page 8 of 41
 Unable to verify Authentication Server's hostname and/or port ............................................................. 29
Unable to display to Console server web page.............................................................................................. 29
Unable to connect to the NMC server.............................................................................................................30
Application blocked for security..........................................................................................................................31
Unable to launch NetWorker Management Console......................................................................................31
Using IPv6 addresses to connect to the NMC GUI...................................................................................... 34
Unable to connect to server: Unable to set user privileges based on user token for username:
Unable to validate the security token...........................................................................................................34
JAVA_HOME environment variable might not be set correctly. Ensure that JAVA_HOME is
set to 64-bit JRE directory. ...........................................................................................................................34
Networker displays the earlier version even after an upgrade...................................................................35

4 Contents

Page 9 of 41
 Tables

1 Revision history.......................................................................................................................................................... 6
2 Style conventions.......................................................................................................................................................8
3 Backward Compatibility.......................................................................................................................................... 12
4 Supported Browsers and JRE versions............................................................................................................... 14

Tables 5

Page 10 of 41
 Preface
As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of
the software or hardware currently in use might not support some functions that are described in this document. The product
release notes provide the most up-to-date information on product features.
If a product does not function correctly or does not function as described in this document, contact a technical support
professional.
NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this document,
go to the Support website https://www.dell.com/support.

Purpose
This document describes how to update the NetWorker software.

Audience
This document is part of the NetWorker documentation set and is intended for use by system administrators during upgrading of
the NetWorker software.

Revision history
The following table presents the revision history of this document.

Table 1. Revision history

Revision Date Description
01 June 30, 2021 First release of this document for NetWorker 19.5.

Related documentation
The NetWorker documentation set includes the following publications, available on the Support website:
● NetWorker E-LAB Navigator
Provides compatibility information, including specific software and hardware configurations that NetWorker supports. To
access E-LAB Navigator, go to https://elabnavigator.emc.com/eln/elnhome.
● NetWorker Administration Guide
Describes how to configure and maintain the NetWorker software.
● NetWorker Network Data Management Protocol (NDMP) User Guide
Describes how to use the NetWorker software to provide data protection for NDMP filers.
● NetWorker Cluster Integration Guide
Contains information related to configuring NetWorker software on cluster servers and clients.
● NetWorker Installation Guide
Provides information on how to install, uninstall, and update the NetWorker software for clients, storage nodes, and servers
on all supported operating systems.
● NetWorker Updating from a Previous Release Guide
Describes how to update the NetWorker software from a previously installed release.
● NetWorker Release Notes

6 Preface

Page 11 of 41
 Contains information on new features and changes, fixed problems, known limitations, environment and system requirements
for the latest NetWorker software release.
● NetWorker Command Reference Guide
Provides reference information for NetWorker commands and options.
● NetWorker Data Domain Boost Integration Guide
Provides planning and configuration information on the use of Data Domain devices for data deduplication backup and
storage in a NetWorker environment.
● NetWorker Performance Optimization Planning Guide
Contains basic performance tuning information for NetWorker.
● NetWorker Server Disaster Recovery and Availability Best Practices Guide
Describes how to design, plan for, and perform a step-by-step NetWorker disaster recovery.
● NetWorker Snapshot Management Integration Guide
Describes the ability to catalog and manage snapshot copies of production data that are created by using mirror technologies
on storage arrays.
● NetWorkerSnapshot Management for NAS Devices Integration Guide
Describes how to catalog and manage snapshot copies of production data that are created by using replication technologies
on NAS devices.
● NetWorker Security Configuration Guide
Provides an overview of security configuration settings available in NetWorker, secure deployment, and physical security
controls needed to ensure the secure operation of the product.
● NetWorker VMware Integration Guide
Provides planning and configuration information on the use of VMware in a NetWorker environment.
● NetWorker Error Message Guide
Provides information on common NetWorker error messages.
● NetWorker Licensing Guide
Provides information about licensing NetWorker products and features.
● NetWorker REST API Getting Started Guide
Describes how to configure and use the NetWorker REST API to create programmatic interfaces to the NetWorker server.
● NetWorker REST API Reference Guide
Provides the NetWorker REST API specification used to create programmatic interfaces to the NetWorker server.
● NetWorker 19.5 with CloudBoost 19.5 Integration Guide
Describes the integration of NetWorker with CloudBoost.
● NetWorker 19.5 with CloudBoost 19.5 Security Configuration Guide
Provides an overview of security configuration settings available in NetWorker and Cloud Boost, secure deployment, and
physical security controls needed to ensure the secure operation of the product.
● NetWorker Management Console Online Help
Describes the day-to-day administration tasks performed in the NetWorker Management Console and the NetWorker
Administration window. To view the online help, click Help in the main menu.
● NetWorker User Online Help
Describes how to use the NetWorker User program, which is the Windows client interface, to connect to a NetWorker
server to back up, recover, archive, and retrieve files over a network.

NOTE: Data Domain is now PowerProtect DD. References to Data Domain or DD systems in this documentation, in the UI,
and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the UI has
not yet been updated to reflect this change.

Preface 7

Page 12 of 41
Typographical conventions
The following type style conventions are used in this document:

Table 2. Style conventions

Bold Used for interface elements that a user specifically selects or clicks, for example, names of
buttons, fields, tab names, and menu paths. Also used for the name of a dialog box, page,
pane, screen area with title, table label, and window.
Italic Used for full titles of publications that are referenced in text.
Monospace Used for:
● System code
● System output, such as an error message or script
● Pathnames, file names, file name extensions, prompts, and syntax
● Commands and options
Monospace italic Used for variables.
Monospace bold Used for user input.
[] Square brackets enclose optional values.
| Vertical line indicates alternate selections. The vertical line means or for the alternate
selections.
{} Braces enclose content that the user must specify, such as x, y, or z.
... Ellipses indicate non-essential information that is omitted from the example.

You can use the following resources to find more information about this product, obtain support, and provide feedback.

Where to find product documentation

● https://www.dell.com/support
● https://www.dell.com/community

Where to get support

The Support website https://www.dell.com/support provides access to product licensing, documentation, advisories,
downloads, and how-to and troubleshooting information. The information can enable you to resolve a product issue before
you contact Support.
To access a product-specific page:
1. Go to https://www.dell.com/support.
2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx)
or by keyword.
To search the Knowledgebase:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Knowledge Base.
3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by
typing a product name in the search box, and then selecting the product from the list that appears.

8 Preface

Page 13 of 41
Live chat
To participate in a live interactive chat with a support agent:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Contact Support.
3. On the Contact Information page, click the relevant support, and then proceed.

Service requests
To obtain in-depth help from Licensing, submit a service request. To submit a service request:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Service Requests.
NOTE: To create a service request, you must have a valid support agreement. For details about either an account or
obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the
Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to https://www.dell.com/support.
2. On the Support tab, click Service Requests.
3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Online communities
For peer contacts, conversations, and content on product support and solutions, go to the Community Network https://
www.dell.com/community. Interactively engage with customers, partners, and certified professionals online.

How to provide feedback

Feedback helps to improve the accuracy, organization, and overall quality of publications. Go to https://
contentfeedback.dell.com/s to provide feedback.

Preface 9

Page 14 of 41
 I
Preparing to Update the NetWorker software
This section provides you with the information to review before you update a NetWorker host and provides detailed information
about the update procedure on each supported operating system.
This section includes the following chapters:
Topics:
• Updating NetWorker server on Windows
• Preparing to Update the NetWorker Software
• Software requirements

10 Preparing to Update the NetWorker software

Page 15 of 41
 1
Updating NetWorker server on Windows

Updating NetWorker server on Windows 11

Page 16 of 41
 2
Preparing to Update the NetWorker Software
This chapter includes the following topics:
Topics:
• Interoperability and Backward Compatibility
• Clone performance considerations
• NMC Client

Interoperability and Backward Compatibility

Before you update any host in the data zone, review information about the interoperability and backward compatibility. If you
are updating the operating system on a host, update the operating system first, and then update the NetWorker software.
NetWorker supports Data Domain systems with a minimum version of DDOS 6.0. Before you update the NetWorker software
on the NetWorker hosts, ensure that all Data Domain systems run a supported DDOS version. The NetWorker E-LAB
Navigator provides more information about the supported DDOS versions, the NetWorker version interoperability and backward
compatibility requirements.
NOTE:
● The module installation guides provide detailed information about how to upgrade NetWorker module clients, for
example, NetWorker Module for Microsoft (NMM), NetWorker Module for SAP (NMSAP), and NetWorker Module for
Databases and Applications (NMDA).
● NetWorker 19.3 and later supports the storage node of NetWorker version 19.2 and, 19.1 with RPS disabled.
● vProxy save sets are always cloned through RPS. Even when the RPS is disabled, vProxy save sets are still cloned
through RPS. RPS cloning has the front-end process as the nsrclone and backend process as nsrrecopy. Nsrecopy is
spawned on the source storage node, the node managing the backup devices involved in cloning. The node can be a
NetWorker server, or it can be remote. For remote storage node, it is important to have the same NetWorker version as
that of the server. Incompatibilities between the two NetWorker versions can lead to undesirable results.
● For RPS clones, the server and storage node should be running the same version of NetWorker.
With NetWorker versions prior to 19.3, the save sets cannot be configured for retention time beyond the year 2038. When you
try to set a date beyond the year 2038, NetWorker returns an invalid retention time and the corresponding operation fails. From
NetWorker 19.3 onwards, you can set a retention time beyond the year 2038 which means up to 136 years from the current
date of execution for the respective action and the special value of forever is updated from 19th Jan 2038 to ~292 billion years.
Refer to the following table for information on backward compatibility of older clients:

Table 3. Backward Compatibility

Backward Pre-19.3 server + Pre-19.3 server + 19.3 server + >2038 19.3 server + forever
Compatibility >2038 forever
Pre-19.3 x86 client Not Supported Supported(old forever Not Supported (2 and Supported (new
value) 3) forever value)
Pre-19.3 x64 client Not Supported Supported(old forever Not Supported (3) Supported (new
value) forever value)
19.3 x86 client Not Supported (1) Not Supported (1) Not Supported (2) Supported (new
forever value)
19.3 x64 client Not Supported (1) Not Supported (1) Supported Supported (new
forever value)

1. A NetWorker 19.5 client communicating with a pre-NetWorker 19.5 server is not an officially supported configuration.
2. Backup actions are not supported due to 32 bit operating system limitation. However, clone actions are supported.

12 Preparing to Update the NetWorker Software

Page 17 of 41
3. Backup actions are not supported. However, clone actions are supported.
NOTE: Old forever value is 19th Jan 2038 and new forever value is ~292 billion years.

Clone performance considerations

In NetWorker 19.5, Recover Pipe to Save (RPS) clone is disabled by default. When you update the NetWorker Server from 8.2.x
to NetWorker 19.5, RPS is disabled. When you update the NetWorker Server from 9.0.x or 9.1.x to NetWorker 19.5, the updating
process preserves the value that you defined for the Disable(RPS) Clone attribute.
To modify the RPS clone attribute, see the NetWorker Administration Guide for more information.

NOTE: When you perform a fresh installation of NetWorker Server 19.5, RPS cloning is disabled by default.

NMC Client
A NetWorker Management Console (NMC) client is any host in the environment that uses a web browser and NetWorker
Runtime Environment or Java™ Runtime Environment (JRE) to display the NMC Server GUI. Multiple users can access the NMC
Server GUI simultaneously, from different browser sessions.

Preparing to Update the NetWorker Software 13

Page 18 of 41
 3
Software requirements
This section contains the following chapters:
Topics:
• NMC Browser and JRE Requirements

NMC Browser and JRE Requirements

An NMC client is any host in the datazone in which you use a web browser to connect to the NMC GUI to manage the NMC
server and NetWorker servers.
The following table summarizes the supported Java (JRE) versions and browsers .

Table 4. Supported Browsers and JRE versions

Browsers JRE Version 64 Bit
● Mozilla Firefox ● Java 8 Build 211
● Chrome
● Safari
● Microsoft IE
● Microsoft IE Edge

NOTE:
● The minimum java requirement is Java 8 Build 211.
● JRE requirements are not applicable when you install NetWorker Runtime Environment.

Add the NMC server to Exception Site list

Java security settings block the NMC server application.
Therefore, you must add the NMC server address to the JRE Exception Site list.
NOTE: These changes are not required if you are using NMC Launcher. For more information on installing NMC launcher,
see NetWorker Runtime Environment Readme Guide
1. Open the Java Control Panel.
2. On the Security tab, click Edit Site list.
3. Click Add.
4. In the Location field, specify the URL to the NMC server in the format https://server_name:9000
where server_name is the hostname of the NMC server.
NOTE: If you connect to the NMC server by using the IP address of the NMC server, add an entry for the IP address in
the following format:

https://ip_address:9000

NOTE: Enclose the IPv6 address within [] brackets. For example, IPv6: https//[<IPv6_address>]:9000

5. Click OK.
6. In the Security Warning window, click Continue.
7. Click OK.

14 Software requirements

Page 19 of 41
 II
Updating the NetWorker software
The updating procedures for the supported NetWorker operating systems are unique. Refer to the appropriate operating
systems chapters to update the NetWorker software.
This section contains the following chapters:
Topics:
• Updating NetWorker for Linux
• Updating NetWorker for Windows
• Updating NetWorker for UNIX

Updating the NetWorker software 15

Page 20 of 41
 4
Updating NetWorker for Linux
This chapter includes the following topics:

16 Updating NetWorker for Linux

Page 21 of 41
 5
Updating NetWorker for Windows
This chapter describes how to update the NetWorker software for Windows and includes the following topics:
Topics:
• Updating NetWorker from 9.x and later version on Windows
• Updating the NetWorker Management Web UI software

Updating NetWorker from 9.x and later version on

Windows
Use the following procedures to update the NetWorker or NMC software.
NOTE: If the NetWorker Server and the NMC Server are on different hosts, you must update the NetWorker software on
the NetWorker Server host before the NMC Server host.

Updating the NetWorker software

On Windows, the procedure to update the NetWorker software depends on the version you are updating to and from.
Each NetWorker version consists of numerical values in the following versioning schema: major.minor.service_pack.hotfix. For
example, the 6th cumulative build of NetWorker 9.1 is 9.1.0.6
Consider the following scenarios:
● When you update from a version of the NetWorker software that shares the same service pack number as the newer
software version, first remove the older version of the NetWorker software. Once removed, install the new version of the
NetWorker Server software. For example:
○ When you want to update a NetWorker host from NetWorker 9.1 (9.1.0.0) to cumulative hotfix version 9.1.0.6.
○ When you want to update a NetWorker host from cumulative hotfix version 9.1.0.1 to 9.1.0.6.
The NetWorker Installation Guide describes how to remove the previous version of the NetWorker software and install the
new version.
● When you update from a version of the NetWorker software that does not share the same service pack number as the
newer version, you can use the installation command to update the NetWorker software, without first removing the previous
version of the software. For example, when you want to update from NetWorker cumulative hotfix version 9.0.1.0 to
NetWorker 9.2. (9.2.0.0).
To update the NetWorker software on a host to a version that does not share the same service pack number, review the
following sections.
NOTE: The update process will only update existing NetWorker components. You cannot change the installation type during
an update. The NetWorker Installation Guide describes how to change the installation type and how to add additional
NetWorker components.
Follow these procedures to update the NetWorker software or the NMC Server software.

Updating NetWorker for Windows 17

Page 22 of 41
Updating the NetWorker server software from 9.x
Follow these procedures to prepare and then update the NetWorker Server.

Preparing the NetWorker server

Before you update the NetWorker server, ensure that the media database and client file indexes are in a consistent state, and
that you have a backup of the databases.
1. Connect to the NetWorker server as root on UNIX and administrator on Windows, and then open a command prompt.
2. Put the NetWorker databases in a consistent state:
nsrim -X
nsrck -m
nsrck -L6

3. Record the current location of the NetWorker client file indexes:

nsrls

4. Record the range of ports the NetWorker software uses:

nsrports

5. Perform a server backup by starting the Server backup workflow.

Ensure that the media pool associated with the backup action has appendable media available.
6. Record the latest bootstrap save set ID (ssid) including the file number, the record number, and the associated volume label.
For example:
mminfo -B

date time level ssid file record volume

10/11/11 16:29:40 full 4254377781 0 0 bootstrap_vol.001

In this example:
● The save set ID (ssid) is 4254377781.
● The file number is 0.
● The record number is 0.
● The label of the volume that contains the bootstrap save set is bootstrap_vol.001.

Updating the NetWorker server software

You can use the NetWorker-19.5.exe to update the NetWorker server software without first removing the previous version
of the software. When you install the NetWorker Server software, the installation also installs the NetWorker Client, Storage
Node, BBB, NetWorker Authentication Service, and Extended Client software.
will update Before you start the NetWorker Server installation, install the Java provided in NetWorker Runtime Environment or
the latest version of the 64-bit Java 8 on the host.
If the NetWorker server is also the NMC server, update both options simultaneously. Updating the NMC server on a NetWorker
server describes how to update the NetWorker server and NMC server software on the same host.
1. Log in to the target host with a user that has administrator privileges.
2. If the NetWorker server is also an NMDA client, remove the NMDA software.
3. Download the NetWorker software package from the Online Support website to a temporary location.
The package name is nw195_win_x64.zip.
4. Extract the NetWorker packages found in nw195_win_x64.zip to a temporary location on the target host.
5. In the directory that contains the unzipped NetWorker software, run NetWorker-19.5.exe.

18 Updating NetWorker for Windows

Page 23 of 41
 NOTE: While you can run the NetWorker-19.5.exe from a network location, to lessen the installation time, copy the
file to a location that is local to the target host. If you used Windows Explorer to copy the files in the .zip file from a
network share, you cannot run the binary until you edit the properties of the file, and then click Unblock.

6. In the Welcome Wizard page, select I agree to the license terms and agreements, and then click Next.
7. In the Configure Windows Firewall page, select Configure the Windows firewall, and then click Next.
NOTE: If you do not configure the firewall to allow inbound and outbound NetWorker software traffic, scheduled
backups might fail.

8. In the Wizard Options page, perform the following steps:

● To install additional language packs, select Language packs.
● To install NetWorker Management Web UI, select NetWorker Web UI
9. Required: The Configure NetWorker Authentication Service page is displayed in the following scenarios:
● The default NetWorker Authentication port, 9090 is in use. In the Apache Tomcat Port field, type another port number
for Tomcat to use, and the click Next.
● The default password for the Java Common Truststore on the host is not the default password (changeit). When the
password is not changeit, the installation displays a JRE Certificate Store Error window. Click Ok, and then in the
Trust store password field, type the password for the Java Common Truststore, and then click Next.
NOTE: The NetWorker installation process will not create user for installing and starting Apache Tomcat.

10. In the NetWorker Management Web UI Options page, specify the authentication host and authentication port.
11. Click Upgrade.
The Upgrade progress bar is displayed and you might see the progress window for several minutes. When the upgrade
completes, the Complete the Setup page provides the status of upgrade and a link to the primary setup logfile.
NOTE: A Windows installer has stopped working message might be displayed during the update on some hosts with
certain versions of the MSI installer. If you see this message, close the window and allow the update to complete.
12. (Optional) In the Complete the Setup page, to define a list of NetWorker Servers that have client-tasking rights to this
host, click Select Backup Server. Client-tasking rights include the ability to back up the host. In the NetWorker Server
Selection page, perform one of the following tasks, and then click OK:
● In the Enter a server name field, type the NetWorker Server name and then click Add. It is recommended that you
specify both the short name and the full name of the NetWorker Server to avoid DNS issues.
● To add a NetWorker Server that is not listed in the Available Servers list:
a. Type the hostname of the NetWorker Server in the Enter a server name text box.
b. Click Add.
● To browse for available NetWorker Servers:
a. Click Update List.
b. From the Available Servers list, select a NetWorker Server.
● To add or remove a NetWorker Server from the Available Servers list to the Selected Servers list, click the arrow
buttons.
The NetWorker_installation_directory\res\servers file contains a list of trusted NetWorker Servers.

The first entry in the servers file becomes the default NetWorker Server for the host.
13. Click Finish.
14. Update the NMC Server Server. The NetWorker Licensing Guide provides more information.

Updating the NetWorker Management Web UI

software
You can upgrade the NetWorker Management Web UI software by running the NWUI-19.5.exe file.
1. Log in to the target host with a user that has administrator privileges.
2. Download the NetWorker software package from the Online Support website to a temporary location.
3. Extract the NetWorker packages found in nw195_win_x64.zip to a temporary location on the target host.
4. In the directory that contains the unzipped NetWorker software, run NWUI-19.5.exe

Updating NetWorker for Windows 19

Page 24 of 41
 NOTE: For more information on installing NetWorker Management Web UI, see NetWorker Installation Guide

20 Updating NetWorker for Windows

Page 25 of 41
 6
Updating NetWorker for UNIX
This chapter includes the following topics:

Updating NetWorker for UNIX 21

Page 26 of 41
 III
Updating Methods
Refer to the following chapters to update from a 32-bit version of the NetWorker software to a 64-bit version and to use
Package Manager to update the NetWorker software.
This section contains the following chapters:

22 Updating Methods

Page 27 of 41
 IV
Post Update Configurations and Reviewing
the Migration Results
Refer to the following chapters for post update configuration information, how to connect to the NMC GUI and NetWorker
server, how to review the migration results, and troubleshooting NMC GUI and NetWorker server connectivity issues.
This section has the following chapters:
Topics:
• Post Update Tasks
• Troubleshooting NMC GUI and NetWorker Server connection issues

Post Update Configurations and Reviewing the Migration Results 23

Page 28 of 41
 7
Post Update Tasks
After you update the NetWorker and NMC Servers, review this chapter to ensure that you can connect to the NMC Server. If
you updated the NetWorker software from 8.1.x or 8.2.x, this section provides detailed information about changes that occur in
the NetWorker software.
This chapter contains the following topics:
Topics:
• Verifying the variables in nssrc file
• Improve clone performance

Verifying the variables in nssrc file

Post upgrade, you must verify that the variables NSR_SHOW_LEGACY_DEVICES and NSR_SHOW_FSC_DEVICES are set to
yes in the /nsr/nsrrc file.

Improve clone performance

For a new installation of NetWorker, the Disable (RPS) Clone attribute is selected by default. For NetWorker 9.0.1 and later,
the Disable (RPS) Clone attribute is cleared by default. If you are upgrading to NetWorker 19.5, the Disable (RPS) Clone
attribute keeps the previously assigned setting.
To improve clone performance, consider the following facts:
● For concurrent cloning workloads, select the Disable (RPS) Clone attribute.
● Ensure that the number of source and destination volumes match. This step avoids contention between the source and
destination volumes and reduces the chances of clone failure.
To clear or select the Disable (RPS) Clone attribute, perform the following steps.
1. Open the Administration window.
2. Right-click the NetWorker server name in the left pane.
3. Select Properties.
4. In the Configuration tab, clear or select the Disable RPS Clone attribute.

24 Post Update Tasks

Page 29 of 41
 8
Troubleshooting NMC GUI and NetWorker
Server connection issues
This chapter includes the following topics:
Topics:
• Troubleshooting authorization errors and NetWorker server access issues
• Troubleshooting NetWorker daemon or service startup issues
• Troubleshooting NMC GUI and NetWorker server connection issues

Troubleshooting authorization errors and NetWorker

server access issues
This section provides a list of possible causes and resolutions for error messages that are related to NetWorker Server
authorization issues.

Insufficient permissions
This message is displayed when the user that you used to log in to the NMC server is a member of many operating system
groups and you try to perform NetWorker operations.
When a user belongs to many groups, the total number of characters in the group names can exceed the buffer size that
NetWorker allots for the group names. NetWorker excludes characters and group names that exceed the buffer size.
To resolve this issue, edit the Usergroup resource to which the user belongs, and then specify the DN for the user in the
External Roles field.

Token has expired

This message is displayed when the NMC GUI is open and the token expires for the authenticated user.
To resolve this issue:
1. Click OK. The Enter Credentials window is displayed.
2. In the Enter Credentials window, specify the user password, and then click OK. The NetWorker Authentication Service
validates the user credentials and, if the validation succeeds, generates a new session token.

Unable to connect to server: Unable to set user privileges based on user

token for SYSTEM: security token has expired
This message is displayed when the NetWorker Administration window is open and the token expires for the authenticated
user.
To resolve this issue:
1. Click OK. The NetWorker Administration window closes.
2. In the Console GUI, select the NetWorker server, and then select Launch NetWorker Administration. The Enter
Credentials window is displayed.
3. In the Enter Credentials window, specify the password of the user, and then click OK. The NetWorker Authentication
Service validates the user credentials and if the validation succeeds, generates a new token for the session.

Troubleshooting NMC GUI and NetWorker Server connection issues 25

Page 30 of 41
Unable to query resource database: security token has expired
This message is displayed when you run a CLI tool as an authenticated user but the user token has expired.
To resolve this issue, run the nsrlogin command to generate a new token for the user.

Unable to connect to server: Unable to authenticate with server "server-

name": Authentication error
This issue is seen if the NMC (gstd) service and NetWorker server (nsrd) service are installed on separate hosts. When you
log in to NMC and click the tabs and options the error: "Unable to connect to server: Unable to authenticate with server
networker-server: Authentication error: why = Server rejected credentials" is displayed. This issue arises due to peering conflict
or incorrect permission settings.
To resolve the issue, clear the peering information:
1. Run the following command on theNetWorker Server:

nsradmin -p nsrexec
p type: nsr peer information; name: nmc-server-name
delete
yes

2. Run the following command on the NMC server:

nsradmin -p nsrexec
p type: nsr peer information; name: nmc-server-name
delete
yes

NOTE: The hostname is case sensitive. You must use the hostname that is displayed in the NMC console.

If the issue persists, then run the following command on the NetWorker Server:

nsrauthtrust -H nmc-server-name -P 9090

nsraddadmin -H nmc-server-name -P 9090

Troubleshooting NetWorker daemon or service

startup issues
This section provides a list of possible causes and resolutions for error messages that are related to issues starting NetWorker
processes.

Error spawning NetWorker_Installation_directory\rabbitmq-

server-3.2.4\erts-5.10.4\bin\epmd -daemon (error 0)
This error message appears in the daemon.raw file on a Windows NetWorker server when 8.3 filename support is disabled on
the drive that contains the NetWorker binaries or the 8.3 short name for the NetWorker_installation_directory is absent.
By default, the NetWorker_installation_directory structure contains the EMC NetWorker directory, which Windows shortens
to EMCNET~1. When 8.3 filename support is disabled on the drive that contains the NetWorker binaries or the 8.3 short name
for the NetWorker_installation_directory is absent, Windows cannot find the path to the NetWorker binaries, and NetWorker
services fail to start.
Use the dir command in the directory that contains the NetWorker_installation_directory, to determine if the 8.3 short name
is absent for the NetWorker_installation_directory.
For example:

26 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 31 of 41
● The following dir output shows that the EMC NetWorker directory does not have an 8.3 name:

C:\Program Files>dir /x EMC*

Volume in drive C has no label.
Volume Serial Number is 5C7F-A00F

Directory of C:\Program Files

05/02/2016 10:10 AM <DIR> EMC NetWorker

● The following dir output shows that the EMC NetWorker directory has the 8.3 name EMCNET~1:

C:\Program Files>dir /x EMC*

Volume in drive C has no label.
Volume Serial Number is 5C7F-A00F

Directory of C:\Program Files

05/02/2016 10:10 AM <DIR> EMCNET~1 EMC NetWorker

To resolve this issue, enable 8.3 filename support, and then set the short name for the NetWorker_installation_directory:
1. Ensure that all NetWorker services are stopped.
2. From a command prompt, change to the root directory of the drive that contains the NetWorker installation files.
For example, cd C:\

3. Use the fsutil command to enable 8.3 filename support.

For example: fsutil behavior set disable8dot3 0

4. Use the fsutil command to set the short name of the installation directory to the actual name of the installation directory.
For example to set the EMC NetWorker directory to the short name EMCNET~1, type: fsutil file setshortname
"EMC NetWorker" EMCNET~1
5. Type the command "NetWorker_installation_dir\nsr\rabbitmq-server-3.2.4\bin\rabbitmq-
server.bat" status, and then confirm that the output does not display the Error spawning message.
6. Start the NetWorker services.
NOTE: Check each directory name in the path to the NetWorker_installation_directory. If a directory name is not a valid
8.3 short name, you must set a short name for it.

Issues with GST Database Services

In windows platform, if the GST database services are not running, then check for the following.
1. Check whether the nmcdb & nmcdb11 is present under <NMCINSTALLDIR> . The default locatoin is C:\Program
Files\EMC NetWorker\Management\
2. If the directories are present, then rename nmcdb to nmcdb_bkp & nmcdb11 to nmcdb.
3. Open the services window (services.msc), and then manually start the GST Database services.
.

Troubleshooting NMC GUI and NetWorker Server connection issues 27

Page 32 of 41
Troubleshooting NMC GUI and NetWorker server
connection issues
Review this section for information to help you troubleshoot issues that prevent you from connecting to the NMC GUI.

There is problem contacting the server, server_name. Please verify

that server is running.
This error message appears after an upgrade when you attempt to connect to the NMC Server.
The NMC Server daemons are not running and the following error messages appear in the gstd.log file when you start the
NMC Server daemons:

gstd NSR error 111 Unable to get authentication service host name
and port number. A valid host name and port number are required.
gstd NSR error 118 Run the command 'gstauthcfg' in the Console bin
directory to set the authentication service host name and port
number.
gstd NSR warning 39 wakeup error in ACM -- request shutdown
gstd NSR warning 23 *** gstd stopping

To resolve this issue, perform the following steps on the NMC Server:
1. From a command prompt change to the directory that contains the NMC Server installation files. The default directory
location is C:\Program Files\EMC NetWorker\Management\GST\bin.
2. Type the following command: gstauthcfg.exe -c -h authentication_host -p authentication_port
where:
● authentication_host is the host name of the NetWorker Server that provides authentication services to the NMC Server.
● authentication_port is the port number used by the NetWorker Authentication Service on the NetWorker Server. The
default port number is 9090.
3. Start the gstd service.

An error occurred while validating user credentials. Verify that

NetWorker Authentication Service is running.
This error message appears when the NMC server cannot validate user credentials with the NetWorker Authentication Service.
This message can occur for more than one reason:
● The NetWorker Authentication Service daemon did not start on the NetWorker Server that authenticates the NMC
Server because another application has started an Apache Tomcat instance on the same service port. In the situation,
the following error message also appears in the Catalina log file: SEVERE: Failed to initialize end point
associated with ProtocolHandler ["ajp-bio-8009"] java.net.BindException: Address already
in use: JVM_Bind <null>:8009
The location of the Catalina log file differs on Windows and Linux:
○ Linux: /nsr/authc/tomcat/logs/catalina.out
○ Windows: C:\Program Files\EMC NetWorker\nsr\authc-server\tomcat\logs\catalina.date.log
To resolve this issue, perform the following steps:
1. Use the netstat command on the NetWorker Server to determine which application is using the same port as the
NetWorker Authentication Service:
○ On Linux: netstat -anbo | grep port_number
○ On Windows: netstat -anp | findstr port_number
2. Remove the application that starts the other Apache Tomcat instance or change the listening port that the application
uses.
3. Restart the NetWorker processes on the NetWorker Server.

28 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 33 of 41
● The firewall configuration prevents the NMC Server from contacting the NetWorker Authentication Service on the
NetWorker Server.

To resolve this issue, ensure that the firewall rules allow communication between the NMC server and NetWorker server on
the port that you configured for the NetWorker Authentication Service. The default port is 9090.

Tuning the JVM heap memory

You must set the JVM heap memory to a maximum of 1 GB if you are using a 32-bit with a 32 bit JRE.
1. Update the Xmx2048m parameter in the jnlp file on the NetWorker server.
You must change the Xmx2048m in<j2se version="1.8+" java-vm-args="-XX:
+IgnoreUnrecognizedVMOptions --add-modules=java.se.ee -Xms256m -Xmx2048m"/> to Xmx1024m
In the example, you can see that the value of Xmx2048m is updated to Xmx1024m

<j2se version="1.8+" java-vm-args="-XX:+IgnoreUnrecognizedVMOptions

--add-modules=java.se.ee -Xms256m -Xmx1024m"/>
2. Restart the NMC (GST) service on the NetWorker server.
3. Restart the NetWorker client.
4. Download the jnlp file by using the following link https://NMC:9000/
5. Run the jnlp file to launch the NMC.

Unable to verify Authentication Server's hostname and/or port

This error message appears when you try to connect to the NMC GUI but the Windows firewall on the NetWorker server is
preventing inbound connections by the java.exe file.
The following detailed message also appears:

If you were prompted, but did not install the certificate, try again by
selecting view certificate and installing it under root certification
authority.
If no prompt was made for certificate validation, then verify that the
Networker Authentication service is running on the configured host and port

Alternately, this error message might appear:

An error occurred while validating user credentials. Verify that NetWoker Authentication
Service is running.
[Failed to connect to NW_SERVER; No error Server Message: Make sure that server is
running.]

To resolve this issue, use the netsh command to create an inbound rule for the java.exe process on the NetWorker server.
For example:
netsh advfirewall firewall add rule name="Java - Allow with
Networker 9" dir=in action=allow program="%PATH\java.exe"
enable=yes

where %PATH is the path to the java.exe file. For example, C:\Program Files\Java\jre1.8.0_73\bin

Unable to display to Console server web page

If the NMC Server web page, for example, https://houston:9000, does not display on the NMC client, use the following
procedure.
1. Verify that the gstd, postgres, and httpd processes are started on the NMC Server.
2. Confirm that you specified the correct port number to connect to the NMC Server. The default port number that you use to
connect to the NMC Server is 9000, but the installation process allows you to specify a different port number.
To determine the service port:

Troubleshooting NMC GUI and NetWorker Server connection issues 29

Page 34 of 41
 a. Review the NMC configuration file on the NMC Server. The location of the file differs on Windows and Linux:
● Linux: /opt/lgtonmc/etc/gstd.conf
● Windows: C:\Program Files\EMC NetWorker\Management\GST\etc\gstd.conf
b. Confirm the port numbers that are defined for the NMC Server:
db_svc_port=port_number
http_svc_port=9000

c. Try to connect to the NMC Server by using the defined port.

3. Review the gstd.raw file.
If the gstd.raw file reports the following error, you must check that the firewall configuration does not block the required
ports:

Aborting due to: Connection timed out, then confirm that the required ports are open
on the firewall to enable the console client to connect to the Console server.

By default, the required ports are:

● 9000
● 9001
● 5432

The NetWorker Security Configuration Guide provides more information about how to determine the required ports for
NetWorker hosts.

Unable to connect to the NMC server

An attempt to connect to the NMC server from the web page can fail with the following error messages.

Javascript is required. If security settings of the browser do not allow

JavaScript, or JavaScript is disabled, please enable it.
This error message appears when you try to connect to the NMC Server with Internet Explorer and JavaScript is disabled.
Use the following procedure to enable JavaScript.
1. From the Internet Explorer menu bar, select Tools > Internet Options.
2. On the Security tab, click Custom level.
3. Click Scripting > Active Scripting, select Enable.
4. Click OK.

Error: Could not authenticate this username and password

This error message appears when you try to log in to the NMC GUI. To resolve this issue, perform one or more of the following
tasks.
● Ensure that you specify the correct username and password.
● Clear the Java Temporary Internet files on the NMC client.
● Delete any desktop shortcuts that were used to connect to the NMC server before the NMC server update, and then
re-create the shortcuts.

30 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 35 of 41
Error: Problem contacting server (ip_address): Connection timed out:
connect
This error occurs when the IP address or hostname of the NMC Server changes and you do not reconfigure the .jnlp file on
the NMC Server.
Use the following procedure to reconfigure the .jnlp file.
1. Log in to the NMC Server as root on Linux or administrator on Windows.
2. Run the gstconfig command from the following directory location:
● Linux: /opt/lgtonmc/bin

● Windows: C:\Program Files\EMC NetWorker\Management\GST\bin

3. Start the gstd daemon on the NMC Server.

● On Linux (sysvinit): /etc/init.d/gst start
● On Linux (systemd): systemctl start GST
● On Windows: Start the EMC GST service.

Internal server error when connecting to the NMC server using the FQDN
Some versions of Internet Explorer 11 cannot connect to the NMC Server when you specify the FQDN of the NMC Server in the
URL.
A message similar to the following appears:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete
your request.
Please contact the server administrator, @@ServerAdmin@@ and inform them of the time the
error occurred, and
anything you might have done that may have caused the error to occur.
More information about this error may be available in the server error log.

To resolve this issue, disable Enable Enhanced Protected Mode.

1. From the Internet Explorer Tools menu, select Internet Options.
2. On the Advanced tab, in the Settings group box, clear Enable Enhanced Protected Mode.
3. Close the Internet Explorer application.
4. Open the Internet Explorer application and connect to the NMC server.

Application blocked for security

This message appears on an NMC client when the Java cache was not cleared after an update to the NMC Server software.
Error messages similar to the following also appear in the message box: Failed to validate certificate. The
application will not be executed.
To resolve this issue, clear the Java cache on the NMC client.

Unable to launch NetWorker Management Console

This message appears on an NMC client when the Java Cache was not cleared after an update to the NMC server software.
To resolve this issue, clear the Java Cache on the NMC client.

Troubleshooting NMC GUI and NetWorker Server connection issues 31

Page 36 of 41
Unable to start gstd process on NMC Server
This section describes how to troubleshoot issues that occur when the NMC client cannot connect to the NMC Server because
the gstd process does not start.
When the gstd daemon does not start on the NMC Server, review the following log files to obtain the exact error message:
● gstd.raw
● web_ouput
The following directories contain the NMC Server log files:
● Linux: /opt/lgtonmc/logs
● Windows: C:\Program Files\EMC NetWorker\Management\GST\logs
Common NMC Server start-up errors include the errors that are described in the following sections.

Error: 'Web server exited unexpectedly.'

The following error appears when the httpd process is not running on the NMC Server.
This error appears “Web server exited unexpectedly". Possible reasons include: previous
instance of %s is still running. Please see 'web_output' file in this product's logs
directory for the web server's output messages.”
Common reasons for httpd start-up failures include:
● Another process is using the default 9000 httpd web service port.
● On Windows, another application is using the Apache server and the httpd daemon requires more time to start up. Use the
following procedure to enable the delayed start option for the EMC gstd process.
1. In the Services applet:
a. Right-click the EMC gstd service.
b. Select Properties.
2. On the General tab, change the Startup type to Automatic (delayed start).
3. Click OK.
4. Stop the EMC gstd service.
5. Start the EMC gstd service.
6. When you update the NetWorker software, enable the delayed start setting again.

Error: error while loading shared libraries: libsasl2.so.2: wrong ELF class: ELFCLASS64
This message appears on 64-bit Linux systems when the 32-bit version of the cyrus-sasl package is not installed. Use the
following procedure to resolve this issue.
1. Install the 32-bit version of the cyrus-sasl package.
2. Start the gstd daemon:
● sysvinit—/etc/init.d/gst start
● systemd—systemctl start gst

Error: 'gstd: Internal error: could not get database handle.'

This error appears when the postgres process cannot start. Review the db_output.log file for specific errors.
Common reasons for this error include the following.
● Insufficient disk space in the file system that contains the NMC database directory.
● An orphaned postgres process is running on the NMC server.
○ On Linux, end the process by sending the SIGTERM signal, kill -TERM.
NOTE: Do not use kill -9.
○ On Windows, stop the EMC GST database service and then start the service.
● The NMC server is running an unsupported version of JRE.

32 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 37 of 41
Warning: unable to detect Java Runtime Environment
This message appears when the JRE is not installed on the NMC client.
For Windows only, the JRE version that is installed on the Console client does not match the Microsoft Internet Explorer
version.
This message appears on 64-bit Windows systems when you use one of the following combinations:
● 64-bit version of the browser to connect to the NMC server, but the 32-bit version of JRE is installed.
● 32-bit version of the browser to connect to the NMC server, but the 64-bit version of JRE is installed.
To resolve this issue:
● Install JRE on the NMC client.
● For Windows only, install the correct JRE program for the installed Microsoft Internet Explorer version.
○ For the 32-bit version of the browser, install the 32-bit version of JRE.
○ For the 64-bit version of the browser, install the 64-bit version of JRE.
Use the following procedure to determine the Microsoft Internet Explorer version on the Windows NMC client.
1. Right-click the Microsoft Internet Explorer shortcut and select Properties.
2. Review the Target Path field.
The target path is on of the following locations:

● C:\Program Files (x86)\Internet Explorer\ for the 32-bit version of Microsoft Internet Explorer.

● C:\Program Files\Internet Explorer\ for the 64-bit version of Microsoft Internet Explorer.

Unable to connect to server: Failed to contact using UDP ping

This message appears when the NMC GUI fails to connect to the NetWorker Server because the NetWorker daemons are not
running on the NetWorker Server.
To resolve this issue, start the daemons on the NetWorker Server and try to connect to the NetWorker Server again.

Cannot log in to the NMC server with Firefox

On a Linux NMC client, a message similar to the following can appear when you use Firefox to log in to the NMC Server.
Internal Server Error The server encountered an internal error or misconfiguration and was
unable to complete your request. Please contact the server administrator, @@ServerAdmin@@
and inform them of the time the error occurred, and anything you might have done that may
have caused the error. More information about this error may be available in the server
error log.
Use the following procedure to resolve this issue.
1. Remove the classic plug-in file, libjavaplugin_oji.so, which is located in the Firefox plugins directory and remove any
associated symbolic links.
2. Create a symbolic link to the Java Plugin libnpjp2.so file in the Firefox plug-ins directory:

cd Firefox/plugins
ln -s JRE/lib/arch/libnpjp2.so .

where:
● Firefox is the installation path.
● JRE is the Java installation path.
● arch is the directory appropriate to the computer architecture.
● For SuSE11 only, install these operating system packages:
○ glibc-locale-2.11.1
○ glibc-locale-32bit-2.11.1
Without these packages, a message similar to the following appears and you cannot log in to the NMC Server:

Troubleshooting NMC GUI and NetWorker Server connection issues 33

Page 38 of 41
 Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete
your request.
Please contact the server administrator, @@ServerAdmin@@ and inform them of the time the
error occurred, and anything you might have done that may have caused the error. More
information about this error may be available in the server error log.

Trust failure between NMC and gstd

When you launch NMC after gstd is reinstalled or upgraded, the following error message appears:

The certificate presented by the NMC server on the host <host name> has chnaged since
the last time this user interface was run. This could happen if the NMC server on this
host was re-installed or if the NMC server certificate was updated for some reason.
Click "Yes" if you trust the server or "No" to exit.

This occurs because of a trust failure between NMC and gstd.

To resolve the issue, delete the old certificate from the host before launching NMC. The certificate file (NMC.ks) is located
under the <user's_home_directory>/.NMC directory.

Using IPv6 addresses to connect to the NMC GUI

If the NMC Server uses IPv4 and IPv6 addresses, you can configure the JRE application on the host that you use to connect to
the NMC GUI to use the IPv6 address to connect to the NMC Server.
Perform the following steps on the host that you use to connect to the NMC GUI.
1. Close down any web browser sessions that use Java.
2. Configure the JAVAWS_VM_ARGS environment variable.
● On Windows, perform the following steps:
a. Browse to Control Panel > System > Advanced System Settings.
b. On the Advanced tab, click Environment Variables...
c. In the System Variables section, click New.
d. In the Variable name field, type JAVAWS_VM_ARGS.
e. In the Variable value field, type -Djava.net.preferIPv6Addresses=true
f. Click OK to close the Environment Variables window, and then click OK to close the System Properties window.
● On Linux and UNIX, type: export JAVAWS_VM_ARGS="-Djava.net.preferIPv6Addresses=true"
3. Start the browser and connect to the NMC GUI.

Unable to connect to server: Unable to set user privileges based on

user token for username: Unable to validate the security token
This error message appears when you try to connect to a NetWorker server that is not the host that authenticates the NMC
users.
To resolve this issue, establish a trust between the NMC server and the NetWorker server, and then configure user access.
"Configuring the NMC server to manage additional NetWorker servers" provides more information.

JAVA_HOME environment variable might not be set correctly.

Ensure that JAVA_HOME is set to 64-bit JRE directory.
This message appears when the JAVA_HOME environment variable is not set to the 64-bit JRE version. On the NetWorker
Server, the nsrd daemon does not start. During the installation process, the following error message might appear:
Service 'NetWorker Backup and Recover Server' (nsrd) failed to start. Verify that you have
sufficient privileges to start system services. To resolve this issue, set the JAVA_HOME environment
variable to the directory for the 64-bit JRE software.

34 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 39 of 41
1. Log in to the target host with a user that has administrator privileges.
2. Browse to Control Panel > System > Advanced System Settings.
3. On the Advanced tab, click Environment Variables...
4. In the System Variables section, click New.
5. In the Variable name field, type JAVA_HOME.
6. In the Variable value field, type the path to the Java directory.
For example, C:\Program Files\Java\jre1.8.0_xx
7. Click OK.
8. Click OK to close the Environment Variables window, and then click OK to close the System Properties window.

Networker displays the earlier version even after an upgrade

The NetWorker version under Protection > Clients displays the earlier version for both the server and the client even after an
upgrade. This is an expected behavior. The updated version of the server and the client is displayed in the NMC UI only after the
first workflow is triggered and completed.

Troubleshooting NMC GUI and NetWorker Server connection issues 35

Page 40 of 41
Dell Technologies Confidential Information version: 5.0.6.33

Page 41 of 41