NetWorker - Updating The NetWorker Software-NetWorker 19.4

Download as pdf or txt
Download as pdf or txt
You are on page 1of 74

NetWorker ® SolVe Generator

Solution for Validating your engagement

Topic
Updating the NetWorker software
Selections
Which version are you updating to?: NetWorker 19.4
Which version are you updating from?: 8.2.x
Operating system?: RHEL/OEL
NetWorker installation type?: NMC Server/NetWorker Server

Generated: October 27, 2021 11:18 AM 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: October, 2021

Dell Technologies Confidential Information version: 5.0.6.32

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

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

Dell Technologies Confidential Information version: 5.0.6.32

Page 2 of 74
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.32

Page 3 of 74
Dell Technologies Confidential Information version: 5.0.6.32

Page 4 of 74
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.32

Page 5 of 74
Dell EMC NetWorker
Updating to NetWorker 19.4 from a Previous
NetWorker Release
19.4

November 2020
Rev. 01

Page 6 of 74
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.

© 2017 2020 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 74
Contents

Figures..........................................................................................................................................5

Tables........................................................................................................................................... 6
Preface.........................................................................................................................................................................................7

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

Chapter 1: Updating NetWorker server NMC server on RHEL/OES/CentOS ............................ 12

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


Interoperability and Backward Compatibility......................................................................................................... 13
Clone performance considerations.......................................................................................................................... 14
NMC Client.................................................................................................................................................................... 14
Dell EMC Licensing Solution...................................................................................................................................... 14

Chapter 3: Software requirements.......................................................................................... 15


NetWorker Server Upgrades.....................................................................................................................................15
NetWorker Authentication Service.................................................................................................................... 16
Java Requirements for a NetWorker Server................................................................................................... 16
NMC server upgrades................................................................................................................................................. 17
NMC Server Features and System Requirements......................................................................................... 18
NMC Browser and JRE Requirements.................................................................................................................... 18

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

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


Updating NetWorker on CentOS, OEL, RHEL, and SuSE from NetWorker 8.2.x....................................... 20
Preparing the Linux host for a NetWorker software or NMC server software update....................... 20
Updating the NetWorker software.................................................................................................................... 21
Updating the NMC server................................................................................................................................... 24
Optional, installing the Block Based Backup software................................................................................. 28

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


Updating the NetWorker Management Web UI software................................................................................. 30

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

Part III: Updating Methods ......................................................................................................... 32

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

Chapter 7: Post Update Tasks................................................................................................. 34


Verifying the variables in nssrc file..........................................................................................................................34
Preparing to connect to the NMC server..............................................................................................................34

Contents 3

Page 8 of 74
Clearing the Java cache.......................................................................................................................................34
Improve clone performance...................................................................................................................................... 35
After upgrading from 8.2.x........................................................................................................................................35
NMC server only, removing the conversion database files.........................................................................35
Configuring the NMC server to manage additional NetWorker servers.................................................. 35
Connecting to the NMC server GUI..................................................................................................................37
Connecting to the NetWorker server after an update and reviewing the migration results.............. 39
Updating the NetWorker User Group resources for migrated NMC users............................................. 40
Configuring Force Backup Level.........................................................................................................................41
Reconfiguring LDAP or AD authentication....................................................................................................... 41
Starting the NMC client after the first time................................................................................................... 49
NetWorker Server and Resource Migration....................................................................................................49

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


Troubleshooting authorization errors and NetWorker server access issues................................................. 61
Troubleshooting NMC GUI and NetWorker server connection issues........................................................... 62
There is problem contacting the server, server_name. Please verify that server is running.............62
An error occurred while validating user credentials. Verify that NetWorker Authentication
Service is running.............................................................................................................................................. 63
Tuning the JVM heap memory........................................................................................................................... 63
Unable to display to Console server web page.............................................................................................. 64
Unable to connect to the NMC server.............................................................................................................64
Application blocked for security.........................................................................................................................65
Unable to launch NetWorker Management Console.....................................................................................65
Unable to connect to server: Unable to set user privileges based on user token for username:
Unable to validate the security token...........................................................................................................68
Networker displays the earlier version even after an upgrade...................................................................68

4 Contents

Page 9 of 74
Figures

1 Welcome to the NMC Server Configuration Wizard page.............................................................................38


2 Define Database Backup Server page................................................................................................................ 38
3 Specify a list of managed NetWorker servers page........................................................................................39
4 Migration Log File window.....................................................................................................................................40
5 Force Backup Level attribute................................................................................................................................ 41
6 Copying the group DN............................................................................................................................................ 46
7 Configuring the External Roles attribute........................................................................................................... 46
8 Copying the group DN............................................................................................................................................ 47
9 Configuring the External Roles attribute............................................................................................................47
10 Copying the group DN............................................................................................................................................ 48
11 Copying the group DN............................................................................................................................................ 49
12 Data Protection Policy............................................................................................................................................ 51

Figures 5

Page 10 of 74
Tables

1 Revision history...........................................................................................................................................................7
2 Style conventions.......................................................................................................................................................9
3 Backward Compatibility...........................................................................................................................................13
4 Supported Browsers and JRE versions............................................................................................................... 18
5 List of software packages for each installation type...................................................................................... 22
6 Linux NMC server default file locations............................................................................................................. 24
7 Supported Operating system and JRE versions...............................................................................................24
8 Configuration options............................................................................................................................................. 42
9 Migration log files.................................................................................................................................................... 50
10 Migration of Group attributes...............................................................................................................................52
11 Migration of Scheduled Clone attributes........................................................................................................... 53
12 NetWorker Server Versions.................................................................................................................................. 54
13 Client override behaviors....................................................................................................................................... 55
14 Backup levels............................................................................................................................................................ 58

6 Tables

Page 11 of 74
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 November 10, 2020 First release of this document for NetWorker 19.4 .

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

Preface 7

Page 12 of 74
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.4 with CloudBoost 19.4 Integration Guide
Describes the integration of NetWorker with CloudBoost.
● NetWorker 19.4 with CloudBoost 19.4 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.

8 Preface

Page 13 of 74
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.

Preface 9

Page 14 of 74
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.

10 Preface

Page 15 of 74
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 NMC server on RHEL/OES/CentOS
• Preparing to Update the NetWorker Software
• Software requirements

Preparing to Update the NetWorker software 11

Page 16 of 74
1
Updating NetWorker server NMC server on
RHEL/OES/CentOS

12 Updating NetWorker server NMC server on RHEL/OES/CentOS

Page 17 of 74
2
Preparing to Update the NetWorker
Software
This chapter includes the following topics:
Topics:
• Interoperability and Backward Compatibility
• Clone performance considerations
• NMC Client
• Dell EMC Licensing Solution

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 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)

Preparing to Update the NetWorker Software 13

Page 18 of 74
Table 3. Backward Compatibility (continued)
Backward Pre-19.3 server + Pre-19.3 server + 19.3 server + >2038 19.3 server + forever
Compatibility >2038 forever
19.3 x64 client Not Supported (1) Not Supported (1) Supported Supported (new
forever value)

1. A NetWorker 19.3 client communicating with a pre-NetWorker 19.3 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.
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.4, Recover Pipe to Save (RPS) clone is disabled by default. When you update the NetWorker Server from 8.2.x
to NetWorker 19.4, RPS is disabled. When you update the NetWorker Server from 9.0.x or 9.1.x to NetWorker 19.4, 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.4, 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.

Dell EMC Licensing Solution


NetWorker 9.0.x and later servers use the Dell EMC Licensing Solution.
The Dell EMC Licensing Solution is a licensing standard that stores all licensing information for the environment in one license
file, which is stored on both the NetWorker server and, if using a served license, the License Server.
All new installations of NetWorker use the Dell EMC Licensing Solution. The chapter "Dell EMC Licensing Solution" in the
NetWorker Licensing Guide provides information on how to implement the Dell EMC Licensing Solution for new and upgraded
installations of the NetWorker software. The "Dell EMC Licensing Solution" chapter also describes the Dell EMC Licensing
Server and the use of the license file.

14 Preparing to Update the NetWorker Software

Page 19 of 74
3
Software requirements
This section contains the following chapters:
Topics:
• NetWorker Server Upgrades
• NMC server upgrades
• NMC Browser and JRE Requirements

NetWorker Server Upgrades


Review this section for information about changes to operating system support and changes to the NetWorker Server
functionality in that started with 9.0.x.

Changes in operating system support


NetWorker 19.4 supports the installation of the NetWorker Server and NMC Server software on Windows x64 or Linux x64 only.
You cannot update a pre-19.4 AIX, HP-UX, or Solaris NetWorker Server to NetWorker 19.4. Deploy a new NetWorker Server on
a supported Windows or Linux operating system. The NetWorker Installation Guide provides the required steps to install the
NetWorker software.
If you use an 8.1.x and 8.2.x NetWorker Server on an operating system that NetWorker 19.4 does not support, you have two
options:
● Perform a cross platform migration of the NetWorker Server data to NetWorker 19.4 server on a supported Windows or
Linux host. Contact Professional Services for more information about cross platform migrations of the NetWorker Server
data.
● Install and configure the NetWorker 19.4 server software on a supported Windows or Linux host and maintain the NetWorker
8.1.x and 8.2.x server for recovery purposes.
The NetWorker E-LAB Navigator provides more information about the operating system versions that the NMC 19.4 server
software supports.

Changes to NetWorker Server databases and resources


The NetWorker 19.4 server uses a SQLite database to store information in the media database. When you update the NetWorker
Server software to 19.4 from previous supported versions, the upgrade process automatically converts the media database.
In NetWorker 9.0.1, the format of the jobsdb changed from a SQLite database to a Postgres database. Previous versions of the
jobsdb, including the 9.0.x version are not compatible with NetWorker 19.4. The update process does not migrate the jobsdb
data. When you update from a previous release to NetWorker 19.4, the updating process renames the jobsdb and the NetWorker
Server uses a new database. After you update the NetWorker Server, the following behavior is seen:
● When you update from NetWorker 8.x, you cannot view details about previously run groups. The NetWorker 19.4 resources
associated with these backup groups report a status of never run.
● When you update the NetWorker Server from the 8.x or 9.0.1 versions:
○ Details about the policy, workflow, and action resources will report a status of never run.
○ Recovery resources created before the update appear as expired.
NOTE: When you update the NetWorker Server on a Windows or Linux host, to NetWorker 19.4, you cannot revert to
NetWorker 8.2.x. Contact Customer Service for more information. If the NetWorker Server is reverted back and Customer
Service attempts a rollback, there is no guarantee that you can recover the data that was backed up while the NetWorker
datazone was running the NetWorker 19.4 software, but Customer Service will provide a commercially reasonable effort
attempt.

Software requirements 15

Page 20 of 74
Changes to NetWorker backup method
Previous releases of NetWorker use group-based configurations to perform scheduled backup and clone operations. NetWorker
19.4 uses policy-based configurations to perform schedule backup and clone operations. When you upgrade the NetWorker
Server, the upgrade process migrates resource configurations to new policy configurations. The Differences between
NetWorker 19.4 and Previous Releases Technical Note on the Online Support website provides detailed information about the
changes in method and resource configurations with NetWorker 19.4.

Changes in Savegoup attributes After policy migration:


After upgrading the NW server from 8.x to 9.x , schedule and default pool values of savegroup will be changed to default in the
migrated workflows, under Backup policy. However, these legacy values will be preserved with the client override behavior
option Legacy Backup rules in the backup action.

Changes in cloning save sets with backup levels 2–9


NetWorker 19.4 does not support backup levels 2 to 9. Before you update the NetWorker Server, clone all backup level 2–9 save
sets, if required.

Language support
● NetWorker 19.2.1 and 9.2.1 supports English and Japanese.
● When you upgrade to NetWorker running with Japanese language support package to 9.x, 18.x , 19.1.x, 19.2.x and 19.3,
version, then a few of the NetWorker messages will be displayed in English.

NetWorker Authentication Service


NetWorker 19.4 uses the NetWorker Authentication Service to authenticate NetWorker Management Console (NMC) and
command line interface (CLI) users.
To use a Linux NetWorker Server, install and configure the NetWorker Authentication Service package on the NetWorker Server
host before you install NMC Server software.
The NetWorker Authentication Service requires NetWorker Runtime Environment or 64-bit Java 8. 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.
Before you install the NetWorker Server software, ensure that an application does not exist on the NetWorker Server that uses
an Apache Tomcat instance on port 9090. The NetWorker Authentication Service listens on port 9090 by default. The section
"Troubleshooting NMC GUI and NetWorker Server connection issues" provides more information.
NOTE: If the installation does not detect NetWorker Runtime Environment, 64-bit Java 8 on the host, the installation will
not continue.

Java Requirements for a NetWorker Server


The installation for the NetWorker Server software and the Linux configuration script for the NetWorker Authentication Service
software check for the required Java version on a host. When the process or script does not detect the minimum required Java
version (64-bit) on the host, the installation cannot continue. 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.
The following sections describe how to ensure that you are using the correct version of the Java software on a Windows or
Linux NetWorker server.
NOTE: To install or upgrade to NetWorker 19.4, you must have either have NetWorker Runtime Environment or latest
version of 64-bit Java 8 or 9 installed on the system.

16 Software requirements

Page 21 of 74
NMC server upgrades
Review this section for information about changes to operating system support and changes to the NMC Server database in
19.4.

Updating the NMC Server


A 19.4 NMC Server uses the NetWorker Authentication Service on a NetWorker 19.4 server for authentication. Before you
update the NMC Server, update the NetWorker Server.
On a Linux NetWorker Server, ensure that you configure the NetWorker Authentication Service and start the NetWorker
services on the NetWorker Server before you update the NMC Server.

Changes in operating system support


NMC 19.4 only supports Windows and Linux NMC Servers. You cannot upgrade a pre-9.x AIX, HP-UX, or Solaris NMC Server to
19.4. Deploy a new NMC Server on a supported Windows or Linux operating system. The NetWorker Installation Guide provides
the required steps to install the NetWorker software.
NOTE: The NetWorker E-LAB Navigator provides more information about the operating system versions that the NMC
Server software supports.

Changes with the NMC database


The NMC 19.4 server uses a PostgreSQL database to store NMC data. An 8.x NMC Server uses a Sybase database. As a result,
after you update the NMC Server software on a Windows or Linux host to version 19.4, you cannot directly roll back an 19.4
NMC Server to a previous version of the NMC Server software.
NOTE: When you update the NetWorker Server on a Windows or Linux host, to NetWorker 19.4, you cannot revert to
NetWorker 8.2.x. Contact Customer Service for more information. If the NetWorker Server is reverted back and Customer
Service attempts a rollback, there is no guarantee that you can recover the data that was backed up while the NetWorker
datazone was running the NetWorker 19.4 software, but Customer Service will provide a commercially reasonable effort
attempt.
NetWorker Management Console( NMC) version 19.1 and above ships with Postgres version 11.1 which has a dependency on
Microsoft Visual Studio 2015 runtime. Ensure that the required runtime is installed before installing NMC server. By default,
Windows Server 2012 R2 does not have VC2015 runtime installed. Runtime installation is required on Windows Server 2012 R2.
The runtime is included in Windows Server 2016 and 2019 and separate installation is not required. If the runtime is not available,
then NMC Installation fails during new installation. You can either get the latest windows updates or install the security updates
and the Visual C++ Redistributable for Visual Studio 2015 or 2017 in the following sequence:
1. KB2919442
2. KB2919355
3. KB2999226
4. Install Visual C++ Redistributable for Visual Studio 2015 or 2017
If the dependencies are not installed, then
● New installation of NMC server and an upgrade from NMC version 8.x fails.
● If you are upgrading from NMC version 9.x, then the installation retains Postgres version 9.2.xx.

Linux NMC The NetWorker software package provides a utility called gstdbunload, which converts the NMC data
server from a Sybase database format to a platform independent format, called an Unload Database. Before you
considerations update the NMC Server software on Linux, convert the NMC database.

Software requirements 17

Page 22 of 74
NMC Server Features and System Requirements
The NetWorker Management Console server (NMC Server) enables you to manage, monitor, and generate reports for multiple
NetWorker Servers across multiple datazones and from a single host.
The NMC Server embeds the following software:
● Apache server, which downloads NMC jar files and starts the NMC Server daemons or services.
● PostgreSQL database, which stores reports and the NMC Server configuration information.
The NMC Server software package is supported on a Linux or Microsoft Windows host. The NMC Server software requires the
NetWorker Client software.
You can install the NMC Server software on the NetWorker Server. The minimum system requirement for a NMC Server host is
a 4 CPU processor and 8GB of RAM.
If NMC server is handling a large scale NetWorker server with a large number of users, then size the NMC server with 32 GB
RAM and 8 core CPU, with greater than or equal to 1.5 GHz.
It is recommended that you install the NMC Server software on a host that is not the NetWorker Server in the following
scenarios:
● When the NMC Server manages a NetWorker Server with 50 or more clients.
● When the NMC Server monitors multiple datazones.
For more information on NMC sizing, see NetWorker Performance Optimization Planning Guide.

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.

18 Software requirements

Page 23 of 74
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 19

Page 24 of 74
4
Updating NetWorker for Linux
This chapter includes the following topics:
Topics:
• Updating NetWorker on CentOS, OEL, RHEL, and SuSE from NetWorker 8.2.x

Updating NetWorker on CentOS, OEL, RHEL, and


SuSE from NetWorker 8.2.x
Use the following procedures to update the NetWorker and NMC Serversoftware from version 8.2.x.

Preparing the Linux host for a NetWorker software or NMC server


software update
Before you update the NetWorker software or NMC server software on Linux, review the following information.

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.
To prepare the NetWorker server, perform these steps from a command prompt on the NetWorker server as root on UNIX or
administrator on Windows.
1. Put the NetWorker databases in a consistent state:
nsrim -X
nsrck -m
nsrck -L6

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


nsrls

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


nsrports

4. Perform a backup of the bootstrap, the client file indexes, and the resource database, type savegrp -O group_name
where group_name is the name of a group that contains all the NetWorker clients in the datazone. If a group that contains
all the clients does not exist, run multiple savegrp commands, specifying a different group each time. This will ensure that
you back up the clients indexes for each client in the datazone.

NOTE: Ensure the media pool associated with the group has appendable media available.

5. 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

20 Updating NetWorker for Linux

Page 25 of 74
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.

NetWorker server only, back up the LDAP or AD configuration


If the NetWorker datazone uses LDAP or AD to authenticate access to the NetWorker server and NMC server and if you are
updating from 8.x to 9 or later, then create a copy of the configuration file /opt/nsr/cst/Config.xml.
NOTE: If you are upgrading from 9.x to later, then the config file located in /opt/nsr/cst/Config.xml will not be
available .

Red Hat Enterprise Linux 7 and later and CentOS Package Requirements
The NetWorker installation requires some packages that the default operating system installation might not include.
Manually download and install the following Linux operating system packages. The NetWorker installation fails when these
packages do not exist on the host:
● ksh
● glibc.i686 0:2.17-55.el7 or later
● nss-softokn-freebl.i686 0:3.15.4-2.el7 or later
● libncursesw.so.5
NOTE:

● For PowerPC (PPC) hosts, install the 32-bit Pluggable Authentication Modules (PAM) library,
pam-1.1.8-12.el7_1.1.ppc or later, on the host. NetWorker requires the 32-bit package, even when the 64-bit
PAM package exists on the host.
● Starting with Red Hat Enterprise Linux 7, the cockpit package provides a web console for system administration. The
cockpit package uses 9090 as the default port to run its service. Since the Networker authentication service also runs
on the port 9090 by default, there is a possibility of potential port conflict. In such cases, it is recommended to change
the port number of the authentication service using the steps that are mentioned in the Changing the NetWorker
Authentication Service port section of the NetWorker Security Configuration Guide.

Updating the NetWorker software


You can use the rpm -U command to update the NetWorker client, server, and storage node software without first removing
the previous version of the software.
Before you remove the NetWorker software, remove the NetWorker module software. The NetWorker module software includes
the NetWorker Module for Database Applications software. The appropriate module installation guide describes how to uninstall
the module software.
Before you start the NetWorker Server update, install the Java provided in NetWorker Runtime Environment or the latest
version of the 64-bit Java 8 on the host. Before you install the Java software, stop NMC and any running NetWorker Server
daemons.
NOTE: If the NetWorker server is also the NMC server, use the procedure described in Updating the NMC server on page
24 to update the NetWorker server.
1. Download the NetWorker software package from the Online Support website to a temporary location.
Ensure that there is sufficient disk space on the host.
2. Change to the temporary location that contains the software package, and then unzip and extract the files by typing the
tar command.
For example:

Updating NetWorker for Linux 21

Page 26 of 74
tar -xzf file_name.tar.gz

3. Stop the NetWorker service.


4. Use the rpm -qa | grep lgto command to display the list of installed NetWorker packages.
5. From the directory that contains the latest version of extracted NetWorker software packages, type:
rpm -Uvh package [package]...
where:
● package [package]... is a list of the software package for the installation type.
NOTE: The Block-Based Backup (BBB) package requires a different command. Do not include the package in the
update command.
● You specify optional packages such as language packs and man pages in rpm command after the required packages for
the installation type.
● You can use the rpm -U command to install new NetWorker package, for example the Extended Client software and the
NetWorker Authentication Service software.
This table provides a list of the software packages that you are required to specify for each installation type.

Table 5. List of software packages for each installation type


Installation type Packages
Client software and Extended Client software lgtoclnt*.rpm lgtoxtdclnt*.rpm

Storage Node software lgtoclnt*.rpm lgtoxtdclnt*.rpm


lgtonode*.rpm

Server software lgtoclnt*.rpm lgtoxtdclnt*.rpm


lgtonode*.rpm lgtoserv*.rpm lgtoauthc*.rpm
lgtoadpt*.rpm lgtolicm*.rpm
NOTE:
● The lgtolicm package is optional and installs the EMC
NetWorker License Manager software.
● The lgtoadpt package is required when NMM clients
exist in the datazone.

Block-Based Backup software lgtoclnt*.rpm lgtobbb*.rpm


NOTE: Before you install the BBB software, ensure that
you install the OS lsb package. On RHEL, install the
lsb package. On SUSE, install the lsb-release
package.

Man pages lgtoman*.rpm

Simplified Chinese language support lgtozh*.rpm

French language support lgtofr*.rpm

Japanese language support lgtoja*.rpm

Korean language support lgtoko*.rpm

6. After you update the NetWorker software, it is recommended that you delete the contents of the /nsr/tmp directory.
7. For a NetWorker server only, configure the NetWorker Authentication Service:
a. To start the NetWorker Authentication Service configuration script, type/opt/nsr/authc-server/scripts/
authc_configure.sh.
b. At the Specify the directory where the Java Standard Edition Runtime Environment software is installed
prompt, Press Enter to accept the default location, /opt/nre/java/latest.
c. The configuration process uses port 9090 for communication. If the configuration process detects that the port is in use,
a warning similar to the following appears: Warning: Port 9090 is already in use.
Perform the following steps to specify a different port.
i. At the Do you wish to specify a different port number prompt, press Enter to accept the default response, Yes.

22 Updating NetWorker for Linux

Page 27 of 74
ii. At the Specify the port that Apache Tomcat should use for communication? prompt, specify the port number.
NOTE: Valid port numbers are between 1024 and 49151. If the configuration process detects that the port that
you specified is in use, a prompt asks if you want to select a different port number.

d. At the Specify the keystore password prompt, type the keystore password.
Specify a password that contains at least six characters and does not contain dictionary words.

e. At the Confirm the password prompt, type the keystore password.


f. At the Specify an initial password for administrator prompt, type a password for the administrator user account. You
will use this password to log in to the NMC Server.
Ensure the password complies with the following minimum requirements:
● Nine characters long
● One uppercase letter
● One lowercase letter
● One special character
● One numeric character

g. At the Confirm the password prompt, type the password for the administrator account.
8. Start the NetWorker daemons: /etc/init.d/networker start
When you start the NetWorker daemons on a NetWorker server, the process will migrate some NetWorker 8.2 resource
attributes values to create new NetWorker 19.4 resources. The chapter Reviewing the Migration Status provides more
information about how to review the results of the migration process.
9. Confirm that the NetWorker daemons have started, by typing the command below, based on the initialization system running
on your Linux machine :
● sysvinit—/etc/init.d/networker status
● systemd—systemctl status networker

For a NetWorker server, the nsrctld daemon starts. The nsrctld daemon starts other processes that the NetWorker
server requires. Output similar to the following example appears when the daemons are started:

+--o nsrctld (29021)


+--o epmd (29029)
+--o rabbitmq-server (29034)
+--o beam (29038)
+--o inet_gethost (29144)
+--o inet_gethost (29145)
+--o jsvc (29108)
+--o jsvc (29114)
+--o nsrd (29123)
+--o java (29135)
+--o nsrmmdbd (29828)
+--o nsrindexd (29842)
+--o nsrdispd (29853)
+--o nsrjobd (29860)
+--o nsrvmwsd (29968)
+--o eventservice.ru (29154)
+--o jsvc (29158)
+--o jsvc (29159)
+--o java (29838)
+--o node-linux-x64- (29885)
+--o nsrexecd (29004)
+--o nsrlogd (29899)
+--o nsrsnmd (30038)

If you do not see this output, type /etc/init.d/networker start

10. For NetWorker Server installations only, install and configure the Dell EMC Licensing Solution. The NetWorker Licensing
Guide provides more information.
The startup process migrates the NetWorker Server media database to a new format. Messages similar to the following appear
in the daemon.raw file when the migration completes successfully:

NSR Media database completed extended consistency checks.

Updating NetWorker for Linux 23

Page 28 of 74
NSR Original media database has been renamed to 'NetWorker_installation_directory/mm/
mmvolume6.Aug_11_15

NOTE: Do not perform any NetWorker commands while the media database conversion is in progress. The migration might
fail and messages similar to the following appear in the daemon.raw:

NSR info Migration unsuccessful: Unable to rename original media database


'NetWorker_installation_directory\mm\mmvolume6': The process cannot access the file
because it is being used by another process. (Win32 error 0x20)

If the migration fails, stop the NetWorker command, then stop and restart the NetWorker Server daemons to perform the
media database conversion again.
If you update a NetWorker Server that is also the NMC Server and the update procedure fails, review the daemon.raw file to
determine if the migration completed.

Updating the NMC server


The NMC server uses the NetWorker Authentication Service on the NetWorker server for user access and user management.
Before you update the NMC server, ensure that you update the NetWorker server software and start the NetWorker daemons
on the NetWorker server.

NMC server requirements

The following table provides a list of the default file locations.

Table 6. Linux NMC server default file locations


NetWorker package Location
NMC server (LGTOnmc) /opt/lgtonmc

The NMC server software supports the following operating systems:

Table 7. Supported Operating system and JRE versions


Operating system Supported JRE and browsers
Linux x86 (32-bit) RHEL 6, 7, 7.6 ● JRE 1.8.x
SLES 11, 12, 12 SP4 x64 ● Mozilla Firefox

Linux em64T & AMD64 (64-bit), RHEL 6, 7, SLES 11, 12 ● JRE 1.8.x
● JRE 9.x
● Mozilla Firefox

Mac OS X 10.13, 10.7, 10.8, 10.9, 10.10, 10.11, 10.12 ● Firefox


● Safari

Solaris 10, 11, 12 for Solaris SPARC, Solaris Opteron (64-bit) ● JRE 1.8.x
● Mozilla Firefox

Windows 7, for x86, em64T & AMD64 (64-bit) ● JRE 1.8.x


● JRE 9.x
● Microsoft Internet Explorer 7
● Mozilla Firefox

Windows 8, 8.1, Windows 10, Windows Server 2012, Windows ● JRE 1.8.x
Server 2012 R2, Windows Server 2016, Windows Server 2019 ● JRE 9.x
x64

24 Updating NetWorker for Linux

Page 29 of 74
Table 7. Supported Operating system and JRE versions (continued)
Operating system Supported JRE and browsers

● Firefox
● Microsoft Internet Explorer 10 in Desktop mode only

NOTE: You might require UTF-8 converters for the operating system.

The NetWorker E-LAB Navigator provides the latest information on supported NMC server operating systems.

Preparing the NMC server


Before you update the NMC server software from an 8.1.x or 8.2.x release, perform a manual backup of the NMC server
database, and then convert the NMC database.

Performing a manual backup of the NMC database


Perform the following steps to back up the NMC database.
1. Set the LD_LIBRARY_PATH environment variable to NMC_install_dir/lgtonmc/bin:NMC_install_dir/
sybasa/lib.
The default NMC installation directory is /opt/lgtonmc
2. Use the savepsm command to perform the backup.

savepsm -I "NMC_install_dir" -b pool_name

where NMC_install_dir is the NMC server installation directory.

NOTE: If the installation directory path contains spaces, then enclose the path in quotations.

The NetWorker Command Reference Guide or the UNIX man pages provides information about the savepsm command.

Preparing the NMC database


The NMC database in 19.4 is a Postgres database. NetWorker server 8.2.x and earlier uses a Sybase database.
Perform the following steps to convert the Sybase database into an Unload Database. The upgrade process will prompt you for
the location of the converted files, and then import the Unload Database into a Postgres database.
NOTE: To update the NMC server without converting the database, use the touch command to create the /opt/
lgtonmc/logs/dbunloaded.tag file.

1. Stop the NetWorker and NMC daemons, by typing the command below, based on the initialization system running on your
Linux machine:

Initialization system Command


sysvinit /etc/init.d/networker stop

systemd systemctl stop networker

Initialization system Command


sysvinit /etc/init.d/gst stop

systemd systemctl stop gst


2. Copy the gstdbunload file from the directory to which you extracted the NetWorker 19.4 software, into the
installation_path/bin folder on the NMC server. By default, the installation_path is in the following location:
● AIX, HP-UX, and Linux: /opt/lgtonmc
● Solaris: /opt/LGTONMC

Updating NetWorker for Linux 25

Page 30 of 74
3. Create a directory that will contain the Unload Database files. Specify a location that has sufficient disk space to store the
converted database. To store the Unload Database files, the conversion process requires free disk space equal to 1.5 times
the size of the original database.
NOTE: The update process creates a new user for the Postgres database, and uses this new user to read the contents
of the directory that contains the Unload Database. Ensure that everyone has execute level permissions to the directory
and the directory contents.

4. From a command prompt, in the installation_path/bin folder, type the following command:

./gstdbunload
target_conversion_dir

where target_conversion_dir is the directory that you created in the previous step.
NOTE: If the the NMC daemons are running the database conversion process fails with an error messages similar to the
following :

SQL error: Unable to start specified database: autostarting database failed.


139495:gstdbunload: Database unload failed. Please check /
target_conversion_directory/reload.log for any reported errors.

To resolve this issue, stop the NMC daemons and run the gstdbunload command again.

The status of the conversion appears in stdout and in the target_conversion_dir/reload.log file.
5. For pre-19.4 Solaris, HP-UX, and AIX NMC servers only, copy the target_conversion_dir to the target Windows or Linux
NMC server.

Updating the NMC server software


Use the rpm -U command to update the NMC server software without first removing the previous version of the software.
1. Use the rpm -qa | grep lgto command to display the list of installed NetWorker packages.
2. From the directory that contains the latest version of extracted NetWorker software packages, type:
rpm -Uvh lgtoclnt-*.rpm lgtonmc*.rpm package [package]...

where package [package]... is a list of NetWorker 8.2.x optional software packages or additional NetWorker 19.4 packages.
For example:
● To update the NMC server, and install the optional man pages and install the Extended Client software, type:
rpm -Uvh lgtoclnt-*.rpm lgtonmc*.rpm lgtoman*.rpm lgtoxtclnt*.rpm
● To update an NMC server that is also the NetWorker server, type:
rpm -Uvh lgtoclnt-*.rpm lgtonode*.rpm lgtoxtclnt*.rpm lgtoauthc*.rpm lgtoserv*.rpm
lgtonmc*.rpm lgtoman*.rpm
NOTE: A message similar to the following might appear during the update process: lgto_gst" deleted from
file /root/.odbc.ini This is expected behavior and an informational message only.

3. When the NMC server is also the NetWorker server, perform the following steps to configure the NetWorker Authentication
Service:
a. To start the NetWorker Authentication Service configuration script, type/opt/nsr/authc-server/scripts/
authc_configure.sh.
b. At the Specify the directory where the Java Standard Edition Runtime Environment software is installed
prompt, Press Enter to accept the default location, /opt/nre/java/latest.
c. At the Specify the keystore password prompt, type the keystore password.
Specify a password that contains at least six characters and does not contain dictionary words.

d. At the Confirm the password prompt, type the keystore password.


e. At the Specify an initial password for administrator prompt, type a password for the administrator user account. You
will use this password to log in to the NMC Server.
Ensure the password complies with the following minimum requirements:

26 Updating NetWorker for Linux

Page 31 of 74
● Nine characters long
● One uppercase letter
● One lowercase letter
● One special character
● One numeric character

NOTE: You will use the administrator account to log in to the NMC Server.

f. At the Confirm the password prompt, type the password for the administrator account.
4. Start the NetWorker daemon on the Linux host:
/etc/init.d/networker start

Configuring the NMC server


When you update from 8.2.x, use the nmc_config command to configure the NMC server software and convert the NMC
database from Sybase to Postgres.
Before you start the NMC configuration script, ensure that the nsrexecd daemon is running on the NMC host and the
NetWorker daemons are running on the NetWorker Server. Use the /etc/init.d/networker status command in sysvinit
or systemctl status networker in systemd to confirm that the daemons are started. If required, use the /etc/
init.d/networker start command in sysvinit or systemctl start networker in systemd to start the NetWorker
daemons. The configuration requires communication with processes on the NetWorker Server. When the NMC Server is not the
NetWorker Server, ensure that the NMC Server can communicate with the NetWorker Server.
1. Start the configuration script, by typing the following command:
/opt/lgtonmc/bin/nmc_config
2. If the NetWorker services are not started on the NMC Server, the NetWorker services are not running on
this host. Do you want to start them now? prompt appears. To start the NetWorker services, press Enter.
3. From the Specify the directory to use for the NMC database prompt, specify a path or press Enter to
accept the default path /nsr/nmc/nmcdb.
4. For updates from NMC 8.2.x, perform the following steps:
a. On the Do you want to migrate data from a previous LGTOnmc 8.x.x. release prompt, type y.
b. On the Specify the directory that contains the unloaded data prompt, specify the path to the directory that
contains 8.x.x conversion files that are created by the gstdbunload command.
5. From the Specify the host name of the NetWorker Authentication Service host prompt, specify the
name of the NetWorker Server that you want to use for NMC and NetWorker Server user authentication.
NOTE: If the configuration script does not detect the NetWorker Authentication Service on the host that you specified,
or the authentication service does not use the default port 9090, a warning message appears. The configuration script
prompts you to specify a different authentication server host. Type Y and when prompted, type the hostname and port
of the NetWorker Authentication Service host.

6. When prompted to start the NMC Server daemons, type y.


7. Confirm that the daemons have started, by typing the following command: ps -ef | grep lgtonmc.
Output similar to the following appears when the daemons have started:
nsrnmc 7190 1 0 Nov23 ? 00:00:06 /opt/lgtonmc/bin/gstd
nsrnmc 7196 1 0 Nov23 ? 00:00:00 /opt/lgtonmc/apache/bin/httpd -f /opt/lgtonmc/apache/
conf/httpd.conf
nsrnmc 7197 7196 0 Nov23 ? 00:00:00 /opt/lgtonmc/apache/bin/httpd -f /opt/lgtonmc/apache/
conf/httpd.conf
nsrnmc 7212 1 0 Nov23 ? 00:00:00 /opt/lgtonmc/postgres/11.1/bin/postgres -D /nsr/nmc/
nmcdb/pgdata
root 18176 18141 0 02:47 pts/0 00:00:00 grep lgtonmc

Updating NetWorker for Linux 27

Page 32 of 74
Troubleshooting NMC installation and configuration issues
This section describes how to troubleshoot and resolve common NMC installation and configuration issues.

ERROR: Command /opt/lgtonmc/bin/gstdbinit -U postgres -n 5432 /nsr/nmc/nmcdb failed


This message appears when the nmc_config command is initializing the NMC server database.
Error messages similar to the following appear in the /nsr/nmc/nmcdb/pgdata/db_output.log file:

Auto configuration failed 6729:error:0200100D:system library:fopen:Permission


denied:bss_file.c:126:fopen('/space/tpkgs/openssl/098zc/install/openssl.cnf','rb')
6729:error:2006D002:BIO routines:BIO_new_file:system lib:bss_file.c:131:
6729:error:0E078002:configuration file
routines:DEF_LOAD:system lib:conf_def.c:199:

Error messages similar to the following appear in the /opt/lgtonmc/logs/install.log file:


waiting for server to start........ stopped waiting pg_ctl: could
not start server Examine the log output. 107558:gstdbinit: The
binary '/opt/lgtonmc/postgres/bin/pg_ctl' did not launch or
complete successfully

When you manually run the command /opt/lgtonmc/bin/gstdbinit -U postgres -n 5432 /nsr/nmc/nmcdb, the
following error appears: /opt/lgtonmc/bin/gstdbinit: error while loading shared libraries:
libltdl.so.3: cannot open shared object file: No such file or directory
This issue appears when the LD_LIBRARY_PATH variable is not correctly set.
To resolve this issue, perform the following steps:
1. Determine the NMC installation path, by default the NMC installation path is /opt/lgtonmc.
2. Add the NMC odbc directory to the LD_LIBARARY_PATH variable. For example, when the NMC installation path is the
default location, type the following command:
export LD_LIBRARY_PATH=/opt/lgtonmc/postgres/odbc
3. Initialize the NMC database, by typing the following command:
NMC_installation_path/bin/gstdbinit -U nsrnmc -n 5432 NMC_installation_path/nmcdbXX
where: NMC_installation_path is /opt/lgtonmc by default and XX is a number that you specify to create a new
subdirectory.
For example, if the NMC server uses the default location and the /opt/lgtonmc/nmcdb1 directory exists, type the
following command:
/opt/lgtonmc/bin/gstdbinit -U postgres -n 5432 /opt/lgtonmc/nmcdb2
4. Start the NMC database, by typing the following command:
NMC_installation_path/postgres/bin/pg_ctl -D NMC_installation_path/nmcdbXX/pgdata -l
logfile start
where: NMC_installation_path is /opt/lgtonmc by default and nmcdbXX is the subdirectory that you created in the
previous step.
For example, if the NMC server uses the default location and the nmcdb directory nmcdb2, type:
/opt/lgtonmc/postgres/11.1/bin/pg_ctl -D /opt/lgtonmc/nmcdb2/pgdata -l logfile start

Optional, installing the Block Based Backup software


On supported SuSE, RHEL, and CentOS operating systems, you can install Block Based Backup (BBB) software. The NetWorker
E-LAB Navigator provides more information about supported operating systems.
Before you install the BBB software, ensure that you install the OS lsb package. On RHEL, install the lsb package. On SUSE,
install the lsb-release package.
1. Ensure that the NetWorker client package is installed on the target host.
2. From the directory that contains the extracted NetWorker software packages, use the yum installer application or the rpm
command to install the NetWorker packages.
● To use yum, type:

28 Updating NetWorker for Linux

Page 33 of 74
yum localinstall --nogpgcheck lgtobbb*.rpm

NOTE: When the yum program cannot install missing package dependencies, the yum command fails and provides a
list of missing packages. Manually install the package dependencies, and run the yum command again.
● To use rpm, type:

rpm -ivh lgtobbb*.rpm

NOTE: When the operating system packages that NetWorker requires are missing, the rpm command provides a list
of missing packages and does not install the NetWorker software. Manually install missing package dependencies
then run the rpm command again.

Updating NetWorker for Linux 29

Page 34 of 74
5
Updating NetWorker for Windows
This chapter describes how to update the NetWorker software for Windows and includes the following topics:
Topics:
• Updating the NetWorker Management Web UI software

Updating the NetWorker Management Web UI


software
You can upgrade the NetWorker Management Web UI software by running the NWUI-19.4.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 nw194_win_x64.zip to a temporary location on the target host.
4. In the directory that contains the unzipped NetWorker software, run NWUI-19.4.exe

NOTE: For more information on installing NetWorker Management Web UI, see NetWorker Installation Guide

30 Updating NetWorker for Windows

Page 35 of 74
6
Updating NetWorker for UNIX
This chapter includes the following topics:

Updating NetWorker for UNIX 31

Page 36 of 74
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:

32 Updating Methods

Page 37 of 74
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 33

Page 38 of 74
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
• Preparing to connect to the NMC server
• Improve clone performance
• After upgrading from 8.2.x

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.

Preparing to connect to the NMC server


You cannot connect to the NMC GUI with any of the following, previously supported, operating systems:
● AIX
● HP-UX
● Solaris
Before you try to connect to the NMC server from a supported host, ensure that JRE is correctly configured.
NOTE: Post-upgrade, the maximum heap memory configuration resets to default minimum value of the NetWorker. For
information on configuration for the scaled setup, see the Performance Optimization Planning Guide.

Clearing the Java cache


Before you update the NMC server, review this section for information about NMC clients and how to clear the java cache.
The NMC server update process replaces the gconsole.jnlp file in the Java web Start cache on the NMC server. As a
result, after an NMC server update, the NMC client fails to start the NMC GUI with an error message similar to the following:
Unable to launch NetWorker Management Console

To prevent this issue, on each host that you use as an NMC client, clear the local java cache. This workaround enables the NMC
client to download the new gconsole.jnlp file from the NMC server.
The procedure is different for UNIX and Windows.

NOTE: To clear the java cache for NetWorker Runtime Environment, see NetWorker Runtime Environment Readme Guide

34 Post Update Tasks

Page 39 of 74
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.4, 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.

After upgrading from 8.2.x


Review this section after upgrading the NetWorker software from 8.2.x for information about resource migration, changes to
the NetWorker software, clean up of migration files, LDAP considerations, and how to log in to the NMC server.

NMC server only, removing the conversion database files


After you successfully migrate the NMC 8.2.x server database, you can remove the pre-conversion and conversion database
directories.
1. Remove the pre-19.4 NMC database directory.
By default, the database directory appears in the following location:
● AIX, HP-UX, and Linux: /opt/lgtonmc/lgto_gstdb
● Solaris: /opt/LGTONMC/lgto_gstdb
● Windows: C:\Program Files\EMC NetWorker\Management \lgto_gstdb

2. Remove the conversion directory that contains the converted database files that are created by the gstdbunload
command.
NOTE: If you converted an NMC database on a pre-19.4 NMC server on AIX, HP-UX, or Solaris, remove the conversion
directory on the source NMC server and the NMC 19.4 server.

Configuring the NMC server to manage additional NetWorker


servers
The NMC Server can use only one NetWorker Authentication Service to provide authentication services. When the NMC Server
manages more than one NetWorker Server, configure a trust between each NetWorker Server that the NMC Server will manage
and NetWorker Server that will provide authentications services to the NMC Server. After you establish each trust, update the
user groups on each NetWorker Server to include the users and groups that require access to the NetWorker Server.
1. To establish the trust, type the following command on each NetWorker Server that is not local to the NetWorker
Authentication Service that NMC uses for authentication:

nsrauthtrust -H Authentication_service_host -P Authentication_service_port_number

where:
● The location of the nsrauthtrust command differs on Linux and Windows:
○ Linux—/usr/sbin
○ Windows—C:\Program Files\EMC NetWorker\nsr

Post Update Tasks 35

Page 40 of 74
● Authentication_service_host is the hostname of the NetWorker Server that authenticates the NMC Server host.
● Authentication_service_port_number is the port number used by the NetWorker Authentication Service. The default port
number is 9090.
For example:
nsrauthtrust -H nwserver.corp.com -P 9090

2. Grant the NetWorker Authentication Service user groups access to the NetWorker Server, by typing the nsraddadmin
command:
nsraddadmin -H Authentication_service_host -P Authentication_service_port_number

For example:
nsraddadmin -H nwserver.corp.com -P 9090

The nsraddadmin command updates the following user groups:


● Application Administrator—Adds the distinguished name (DN) of the NetWorker Authentication Service Administrators
group.
● Security Administrator—Adds the DN of the NetWorker Authentication Service Administrators group.
● Users—Adds the DN of the NetWorker Authentication Service Users group.
3. (Optional) To add other users or groups from the NetWorker Authentication Service to the Application Administrator and
Security Administrator user groups on the NetWorker Server, you must determine the DN for the user or group, and then
use the nsraddadmin command with the -e option to add the user or group.
For example, to add a user to the Application Administrator and Security Administrator user groups on the NetWorker
Server, perform the following steps:
a. Use the authc_mgmt command with the -e find-all-users option to display a list of users and the associated user ID in
the local user database:
authc_mgmt -u administrator -p password -e find-all-users
The query returns 2 records.
User Id User Name
1000 administrator
1001 Patd

NOTE: The location of theauthc_mgmt command differs on Linux and Windows:

● Linux—/opt/emc/authc/bin
● Windows—C:\Program Files\EMC\Authc\bin

b. Use the authc_mgmt command with the -e find-user option to display user details for the administrator account,
including the user DN:
authc_mgmt -u administrator -p password -e find-user -D user-id=user_id

where user_id is the user ID value for the Patd account.


For example:
authc_mgmt -u administrator -p 1.Password -e find-user -D user-id=1001

User Id : 1001
User Name : Patd
User Domain :
User First Name: Patrick
User Last Name : Dunn
User Email : Patd@local
User Details :
User DN : cn=Patd,cn=Users,dc=bu-iddnwserver2,dc=IddLab,dc=local
User Enabled : true
User Groups : [100, 101]

c. Use nsraddadmin command to add the user DN of the administrator account to the Application Administrators and
Security Administrators user group on each remote NetWorker Server, that the NMC Server manages:
nsraddadmin -e user-dn

36 Post Update Tasks

Page 41 of 74
For example:

nsraddadmin -e "cn=Patd,cn=Users,dc=bu-iddnwserver2,dc=IddLab,dc=local"
Added role 'cn=Patd,cn=Users,dc=bu-iddnwserver2,dc=IddLab,dc=local' to the
'Application Administrators' user group.
Added role 'cn=Patd,cn=Users,dc=bu-iddnwserver2,dc=IddLab,dc=local' to the 'Security
Administrators' user group.

The NetWorker Security Configuration Guide provides detailed information about how to add additional local database
users, LDAP and AD users to the User Group resources on the NetWorker Server.
The NetWorker Security Configuration Guide provides detailed information about how to add additional local database users,
LDAP and AD users to the User Group resources on the NetWorker Server.

Connecting to the NMC server GUI


Complete the following procedure to connect to the NMC Server GUI from an NMC client. By default, the NetWorker
Authentication Service uses the local user database for user authentication. Specify the NetWorker Authentication Service
administrator account to log in to the NMC Server. The NetWorker Security Configuration Guide describes how to configure the
NetWorker Authentication Service to use LDAP or AD for user authentication.
The Troubleshooting NMC GUI Connection Issues chapter provides information about how to troubleshoot issues when you
cannot connect to the NMC GUI.
1. From a supported web browser session, type the URL of the NMC Server:
https://server_name:https_service_port
where:

● server_name is the name of the NMC Server.


● https_service_port is the port for the embedded HTTP server. The default https port is 9000.

For example: https://houston:9000


The gconsole.jnlp file downloads to the host. When the download completes, open the file.
2. On the Login window, specify the NetWorker Authentication Service administrator username and password, and then click
OK.
NOTE: After you update the NMC server, the administrator account that you used to connect to the NMC server on
8.1.x and 8.2.x does not exist and is replaced by the NetWorker Authentication Service administrator account.

3. If you did not install a supported version of JRE on the host, then a dialog box that prompts you to install JRE appears.
Cancel the application installation, install JRE, and then rerun the application installation.
4. On the Welcome to the NMC Server Configuration Wizard page, click Next.
The following figures shows the Welcome to the NMC Server Configuration Wizard page.

Post Update Tasks 37

Page 42 of 74
Figure 1. Welcome to the NMC Server Configuration Wizard page

5. On the Define Database Backup Server page, specify the name of the NetWorker Server that will back up the NMC
Server database, and then click Next.
The following figure shows the Define Database Backup Server page.

Figure 2. Define Database Backup Server page

6. On the Specify a list of managed NetWorker Servers page:


a. Specify the names of the NetWorker Servers that the NMC Server will manage, one name per line.
NOTE: If the NMC Server is also the NetWorker Server, specify the name of the NetWorker Server.

b. Leave the default Capture Events and Gather Reporting Data options enabled.
Consider the following options:

● To allow the NMC Server to monitor and record alerts for events that occur on the NetWorker Server, select Capture
Events.

38 Post Update Tasks

Page 43 of 74
● To allow the NMC Server to collect data about the NetWorker Server and generate reports, select Gather Reporting
Data.

The following figure shows the Specify a list of managed NetWorker servers page.

Figure 3. Specify a list of managed NetWorker servers page

7. If you created NMC users on an NMC 8.1.x and 8.2.x server, a pop-up window appears asking you if you want to migrate the
NMC users to the NetWorker Authentication Service local database. Click Yes to start the user migration wizard.
NOTE: If you click No, you can migrate the NMC users later.

8. On the Migrate Users page, select the users that you want to migrate.
NOTE: By default all users are selected for migration. The migration deletes unselected user accounts.

9. For each user, perform the following steps:


a. In the Password field, specify an initial password.
Ensure the password complies with the following minimum requirements:
● Nine characters long
● One uppercase letter
● One lowercase letter
● One special character
● One numeric character

b. Leave the default selection for Password Change Required, which ensures that when the user connects to the NMC
Server for the first time, that the log in process prompts the user to change their password.
c. In the Groups field, if the user will manage user accounts, select the Administrators group.
The log in process migrates the selected NMC users into the NetWorker Authentication Service local database, and the NMC
GUI appears. The following sections describe how to connect to a NetWorker server and configure User Group membership for
the migrated NMC users.

Connecting to the NetWorker server after an update and reviewing


the migration results
When you connect to the NetWorker server for the first time after an update, you can review the results of the NetWorker
server resource migration.
1. In the Enterprise window, select the NetWorker server, and then select Launch Application

Post Update Tasks 39

Page 44 of 74
The NetWorker Migration Succeeded window appears.
2. Click Open Migration Log File to review migration log file and the status of the server resource migrations.
The following figure provides an example of the Migration Log File window.

Figure 4. Migration Log File window

3. Click OK.
4. Click Close.

Updating the NetWorker User Group resources for migrated NMC


users
The NetWorker server uses the membership in the External Roles field of the user group resources to determine the privileges
that are assigned to the NetWorker Authentication Service local database users. After the log in process migrates NMC users
into the NetWorker Authentication Service local database, update the User Group resources on each managed NetWorker
server, to provide the migrated NMC users with the privileges to each NetWorker server.
Perform the following steps while logged in to the NMC server with the Administrator account.
1. In the NMC GUI, create an NMC group that contains the local database users. This group allows you to quickly add multiple
users that require the same privileges to one or more user groups:
a. On the NMC GUI, click Setup.
b. On the User and Roles navigation pane, right-click Groups and select New.
c. In the Name field, specify a unique name for the group.
In the Local Users section, select all the user accounts to add to this group, and then click OK.
2. In the Administration window, perform the following steps:
a. On the toolbar, select Server.
b. On the left navigation pane, expand User Groups.
c. Right-click the user group to which the NMC users require membership, and select Properties.
d. In the Configuration section, click the Add (+) button beside the External Roles attribute.
e. Select each local database user or group that requires the privileges that are assigned to the user group, and then click
OK.
To select multiple successive users or groups, hold the Ctrl key while you select the first and last user or group. To
select multiple individual users or groups in any order, hold the Shift key while you select each user or group.
For more information on External Roles and User Groups, see NetWorker Security Configuration Guide
The distinguished name (dn) for each selected user and group appears in the External Roles field.

40 Post Update Tasks

Page 45 of 74
Configuring Force Backup Level
NetWorker 8.1.x and 8.2.x provided the Force incremental option in the Group resource. The option provided you with the
ability to schedule multiple backups for clients in a 24 hours period, but limit the number of full backups to the first scheduled
backup. Each subsequent backup in the 24 hour period is an incremental backup. NetWorker 19.4 provides you with the ability to
define a backup level for a backup action that differs from the scheduled level. NetWorker 19.4 does not migrate the value in the
Force incremental option to the action resource.
For workflows that have more than one scheduled backup within a 24-hour period, use the Force Backup Level attribute to
allow more than one backup to occur at two different backup levels in a 24-hour period. When you select a backup level in the
Force Backup Level attribute, the first backup is performed at the scheduled backup level. Each subsequent occurrence of the
backup action in the next 24 hours occurs at the level defined in the Force Backup Level attribute. For example, if the level
defined by the schedule is Full and the Force Backup Level attribute is set to Incr, the first backup started by the action
occurs at a level full and subsequent backups, within 24 hours of the start of the full backup are incremental. By default this
option is cleared, which means that if the action runs multiple backup operations in a 24 period, all the backups occur at the
scheduled backup level.
To define a level for multiple backups that occur in a 24 hour period, perform the following steps:
1. In the Administration window, click Protection.
2. In left pane, expand Policies.
3. Expand the policy and then select the workflow.
4. In the Actions pane, right click the action that is schedule to run multiple times in a 24 hour period, and then select
Properties.
The Specify the Action Information window in the Policy Actions wizard appears.
5. From the Force Backup Level list select a backup level.
6. Click Next on each subsequent window, and then click Configure.
The level that you chose appears in the Force Backup Level column for the action, in the Action pane. The following figure
provides an example of the Action pane, where the Force Backup Level attribute is set to Incr for the backup action.

Figure 5. Force Backup Level attribute

Reconfiguring LDAP or AD authentication


In a NetWorker 8.1.x and 8.2.x datazone, the NMC server maintained the LDAP and AD configuration information and managed
authentication. In NetWorker 9.x and later datazone, the NetWorker Authentication Service performs these tasks. After you
update the NMC server, use the details in the config.xml file to reconfigure LDAP or AD authentication in the NetWorker
Authentication Service database.
Perform the following steps on the NetWorker server host on which you configured the NetWorker Authentication Service that
manages the LDAP or AD configuration information.
1. Open the config.xml file that you made a copy of before you updated the NMC server.
2. Search for the string <class-id class="LDAP"/>.
3. Copy the configuration information that appears after <class-id class="LDAP"/>, between the <properties> and </
properties> tag to a text file.
For example, output similar to the following appears after the <class-id class="LDAP"/> tag:

<properties>;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?;


;LDAPAuthorityConfig;
;bindDn;cn=administrator,cn=users,dc=iddlab,dc=local;/bindDn;
;bindPassword;XOYKgAutHUOdJeEEdXNKdg==$FpRMvNwY5DvjqwXR2BVypw==;/bindPassword;
;serverName;idd-ad.iddlab.local;/serverName;
;authorityName;;/authorityName;
;ldapDebugLevel;0;/ldapDebugLevel;
;protocol;ldap;/protocol;
;portNumber;389;/portNumber;

Post Update Tasks 41

Page 46 of 74
;ldapTimeout;30000;/ldapTimeout;
;certificateFile;;/certificateFile;
;userSearchPath;CN=Users,DC=IddLab,DC=local;/userSearchPath;
;groupSearchPath;CN=NetWorker,DC=IddLab,DC=local;/groupSearchPath;
;userObjectClass;Person;/userObjectClass;
;userIdAttribute;cn;/userIdAttribute;
;groupMemberAttribute;Member;/groupMemberAttribute;
;groupObjectClass;group;/groupObjectClass;
;groupNameAttribute;cn;/groupNameAttribute;
;clientCertificate;;/clientCertificate;
;clientKeyFile;;/clientKeyFile;
;/LDAPAuthorityConfig;</properties>

You use the information that is contained between the <properties> </properties> tag to configure LDAP/AD in the
NetWorker Authentication Service database
4. Use a text editor to modify the LDAP or AD template file.
NetWorker provides a template file that you can modify with the configuration values that are specific to your environment,
and then run to configure AD authentication.
The location and name of the file differs on Windows and Linux:
● LDAP template file:
○ Windows—C:\Program Files\EMC NetWorker\nsr\authc-server\scripts\authc-create-ldap-
config.bat.template
○ Linux—/opt/nsr/authc-server/scripts/authc-create-ldap-config.sh.template
● AD template file:
○ Windows—C:\Program Files\EMC NetWorker\nsr\authc-server\scripts\authc-create-ad-
config.bat.template
○ Linux—/opt/nsr/authc-server/scripts/authc-create-ad-config.sh.template

5. In the template file, replace the variables that are enclosed in <> with the values that are specific to the configuration.
The following table provides information about each configuration option.

Table 8. Configuration options


Options for 9.x and later Equivalent 8.2 Description
and earlier
option name
-D "config-tenant-id=tenant_id" N/A Required. The ID of the tenant that you created
for the LDAP or AD configuration in the local
database. By default, NetWorker Authentication
Service creates one tenant that is called
Default with a tenant ID of 1.

-D "config-active-directory=y/n" N/A Optional. A yes or no value that specifies if the


external authority is AD. When you set this
option to
y for an AD configuration, NetWorker
Authentication Service uses Microsoft specific
enhancements for LDAP to perform optimized
queries.

Default value: NO

-D "config-name=authority_name" N/A Required. A descriptive name, without spaces


for the LDAP or AD configuration.

The maximum number of characters is 256.


Specify ASCII characters in the config name
only.

42 Post Update Tasks

Page 47 of 74
Table 8. Configuration options (continued)
Options for 9.x and later Equivalent 8.2 Description
and earlier
option name

-D "config-server-address=protocol:// protocol Required. A string that specifies the protocol,


hostname, or IP address of the LDAP or AD
hostname_or_ip_address:port#/base_dn" serverName
server, the LDAP port number, and the base
portNumber DN.

The base DN specifies the base suffix from


which all the operations originate.

For the protocol, specify LDAP for LDAP or AD


authorities and LDAPS for LDAPS.

NOTE: Use only FQDN in case of LDAPS


configuration.

-D "config-domain=domain_name" N/A Required. A descriptive name, without spaces


for the domain attribute in the local database. It
is recommended that you specify the domain
name that is used by the LDAP or AD authority.

The maximum number of characters is 256.


Specify ASCII characters in the domain name
only.

-D "config-user- bindDn Required. The full distinguished name (DN) of a


dn=cn=name,dc=domain_component1,dc=domain_c user account that has full read access to the
omponent2..." LDAP or AD directory.
-D "config-user-dn-password=password" bindPassword Required. The password of the bind account.
-D "config-user-search-path=user_search_path" userSearchPath Required. The DN that specifies the search
path that the authentication service should use
when searching for users in the LDAP or AD
hierarchy. Specify a search path that is relative
to the base DN that you specified in the config-
server-address option. For example, for AD,
specify cn=users.

-D "config-user-id-attr=user_ID_attribute" userIdAttribute Required. The user ID that is associated with


the user object in the LDAP or AD hierarchy.
For LDAP, this attribute is commonly uid. For
AD, this attribute is commonly
sAMAccountName.

-D "config-user-object-class=user_object_class" userObjectClass Required. The object class that identifies the


users in the LDAP or AD hierarchy. For
example, inetOrgPerson.

-D "config-group-search-path=group_search_path" groupSearchPath Required. A DN that specifies the search path


that the authentication service should use
when searching for groups in the LDAP or AD
hierarchy. Specify a search path that is relative
to the base DN that you specified in the
config-server-address option.
-D "config-group-name- groupNameAttribu Required. The attribute that identifies the
attr=group_name_attribute" te group name. For example, cn.

-D "config-group-object-class=group_object_class" groupObjectClass Required. The object class that identifies


groups in the LDAP or AD hierarchy.
● For LDAP, use groupOfUniqueNames or
groupOfNames.

Post Update Tasks 43

Page 48 of 74
Table 8. Configuration options (continued)
Options for 9.x and later Equivalent 8.2 Description
and earlier
option name

● For AD, use group.

-D "config-group-member- groupMemberAttri Required. The group membership of the user


attr=group_member_attribute" bute within a group.
● For LDAP:
○ When the Group Object Class is
groupOfNames the attribute is
commonly member.
○ When the Group Object Class is
groupOfUniqueNames the attribute is
commonly uniquemember.
● For AD, the value is commonly member.

-D "config-user-search- N/A Optional. The filter that the NetWorker


filter=user_search_filter_name" Authentication Service can use to perform user
searches in the LDAP or AD hierarchy. RFC
2254 defines the filter format.
-D "config-group-search- N/A Optional. The filter that the NetWorker
filter=group_search_filter_name" Authentication Service can use to perform
group searches in the LDAP or AD hierarchy.
RFC 2254 defines the filter format.

-D "config-search-subtree=y/n" N/A Optional. A yes or no value that specifies if the


external authority should perform subtree
searches.

Default value: No

-D "config-user-group-attr=user_group_attribute " N/A Optional. This option supports configurations


that identify the group membership for a user
within the properties of the user object. For
example, for AD, specify the attribute
memberOf
NOTE: When you define this attribute,
NetWorker Authentication Service does not
have to browse the entire hierarchy to
determine group membership for a user.

-D "config-object-class=object_class" N/A Optional. The object class of the external


authentication authority. RFC 4512 defines the
object class.

Default value: objectclass.

The following provides an example of a modified template file:


authc_config -u administrator -p "1.Password" -e add-config
-D "config-tenant-id=33"
-D "config-name=iddconfig"
-D "config-server-address=ldap://idd-ad.iddlab.local:389/dc=iddlab,dc=local"
-D "config-domain=idddomain"
-D "config-user-dn=cn=administrator,cn=users,dc=iddlab,dc=local"
-D "config-user-dn-password=1.Password"
-D "config-user-group-attr=memberof"
-D "config-user-id-attr=sAMAccountName"
-D "config-user-object-class=person"
-D "config-user-search-filter="

44 Post Update Tasks

Page 49 of 74
-D "config-user-search-path=cn=users"
-D "config-group-member-attr=member"
-D "config-group-name-attr=cn"
-D "config-group-object-class=group"
-D "config-group-search-filter="
-D "config-group-search-path="
-D "config-object-class=objectclass"
-D "config-active-directory=y"
-D "config-search-subtree=y"
6. Save the file, and then remove the .template extension.
7. Run the template script file.
After configuring the NetWorker Authentication Service to use LDAP authentication, configure the NMC and NetWorker server
to authorize the users.

Configuring authentication in NMC


After you create users in the NetWorker Authentication Service database or configure the NetWorker Authentication Service to
use an external authority for authentication, configure the NMC server to enable user access.
1. Connect to the NMC server with a NetWorker Authentication Service administrator account.
2. Click Setup.
The Users and Roles window appears.
3. In the left navigation pane, select Users and Roles > NMC Roles. In the NMC Roles window, right-click the role, and then
select Properties.
4. For local database users only, in the Local Users section, select the users.
5. For LDAP and AD users, in the External Roles attribute, specify the DN of the LDAP/AD users or group that require
privileges to the NMC server.
Click OK, and then close the NMC GUI.
6. Connect to the NMC server. When you are prompted for a username and password, specify the credentials for a user that is
in the hierarchy of the DN that you specified in the External Roles attribute.
For the username, use the following format:
tenant_name\domain_name\user_name

where:
● tenant_name is the name of the tenant that you specified when you configured the external authentication authority
configuration on the NetWorker Authentication Service. If you use the Default tenant, you are not required to specify the
tenant name.
● domain_name is the name of the domain that you specified when you configured the external authentication authority
configuration on the NetWorker Authentication Service.
● user_name is the name of the user in the LDAP or AD directory, which you added to the External Roles attribute or is a
member of the group that you added to the External Roles attribute.

For example, to specify an AD account that is named Liam in an external authentication authority that you configured in an
authentication service domain that is called IDDdomain and a tenant that is called IDD, specify the following username: IDD
\IDDdomain\Liam.
Troubleshooting login errors provides information about how to troubleshoot login issues.

Example: Configure the External Roles attribute for LDAP authentication


To add the AlbertaTestGroup1 LDAP group to the Console Security Administrators group on the NMC server, perform the
following steps.
1. To connect to the LDAP server, use LDAP Admin.
2. Navigate to the LDAP group, right-click on the group name, and then select Copy dn to clipboard. The following figure
provides an example of the LDAP Admin window.

Post Update Tasks 45

Page 50 of 74
Figure 6. Copying the group DN

3. Connect to the NMC server with the NetWorker Authentication Service administrator account.
4. On the Setup window select Users and Roles > NMC Roles > Console Security Administrator.
5. In the External Roles attribute, paste the group dn value. The following figure provides an example of the group dn entry
for the AlbertaTestGroup1 group.

Figure 7. Configuring the External Roles attribute

Example: Configure the External Roles attribute for AD authentication


To add an AD group that is named NetWorker to the Console Security Administrators group on the NMC server, perform the
following steps.
1. To connect to the AD directory, use ADSI Edit.
2. Navigate to the AD group, right-click the group name, and then select Properties.
3. On the Attribute Editor window, select distinguishedName from the attribute list, and then select View.
4. On the String Attribute Editor window, with the entire dn highlighted, right-click in the value field, and then select Copy.
The following figure provides an example of copying the group DN in the ADSI Editor.

46 Post Update Tasks

Page 51 of 74
Figure 8. Copying the group DN

5. Click Cancel, and then close ADSI Editor.


6. Connect to the NMC server with the NetWorker Authentication Service administrator account.
7. On the Setup windows select Users and Roles > NMC Roles > Console Security Administrator.
8. In the External Roles attribute, paste the group DN value. The following figure provides an example of the group DN entry
for the NetWorker group.

Figure 9. Configuring the External Roles attribute

Post Update Tasks 47

Page 52 of 74
Configuring LDAP and AD user access to the updated NetWorker server
In NetWorker 8.1.x and 8.2.x, you specified the name of LDAP and AD users and groups in the Users attribute of the User Group
resource on the NetWorker server. In NetWorker 19.4, specify the dn of the LDAP and AD users and groups in the External
Roles attribute of a User Group resource.
1. On the NMC Console toolbar, select Enterprise.
2. Right-click the NetWorker server, and then select Launch Application.
3. On the NetWorker Administration window, select Servers.
4. In the left navigation pane, select User Groups.
5. On the User Groups window, right-click the user group to which you want to add the LDAP or AD user and group and
select Properties.
6. In the External Roles attribute, specify the dn of the LDAP or AD user or group.
7. Click OK.
8. Close the NetWorker Administration and NMC windows.
9. Connect to the NMC server with an LDAP or AD user and then connect to the NetWorker server .
10. Confirm that you can view server resources, for example Directives.

Example: Adding LDAP group to the External Roles attribute


The following example uses LDAP Admin, a third party tool that allows you to view information about users and groups in the
LDAP directory service.
1. To connect to the LDAP server, use LDAP Admin.
2. Navigate to the LDAP group, right-click on the group name, and then select Copy dn to clipboard. The following figure
provides an example of the LDAP Admin window.

Figure 10. Copying the group DN

3. Close the LDAP Admin window.


4. Paste the dn value for the group into the External roles attribute.
authc_mgmt -u administrator -p "Password1" -e query-ldap-users -D

"query-tenant=IDD" -D

"query-domain=ldapdomain"

Example: Adding AD group to the External roles attribute


The following example uses ADSI Edit, a Windows tool that allows you to view information about users and groups in AD
directory service. Microsoft TechNet provides the most up to date information about how to use ADSI Edit.
1. To connect to the AD directory, use ADSI Edit.
2. Navigate to the AD group, right-click the group name, and then select Properties.
3. On the Attribute Editor window, select distinguishedName from the attribute list, and then select View.

48 Post Update Tasks

Page 53 of 74
4. On the String Attribute Editor window, with the entire dn highlighted, right-click in the value field, and then select Copy.
The following figure provides an example of copying the group DN in the ADSI Editor.

Figure 11. Copying the group DN

5. Click Cancel, and then close ADSI Editor.


6. Paste the dn value for the group into the External roles attribute.

Starting the NMC client after the first time


After you use an NMC client to connect to the NMC server, use one of the following methods to reaccess the NMC server:
● Type the following url in the address bar of the web browser:
https://server_name:https_service_port
● Double-click NetWorker Console in the Java Web Start Application Manager.
● On Windows NMC clients, double-click the NetWorker Management Console desktop icon.
When you use a web browser on a host (NMC client) to connect to the NMC Server, ensure that you log in with a valid
username and password. Specify the username in one of the following formats:
○ For LDAP/AD authentication: domain\username
○ For local user database authentication: username
○ For tenant configurations: tenant\domain\username

NetWorker Server and Resource Migration


After upgrading from NetWorker 8.2.x to NetWorker 19.4, when you start the NetWorker processes on the NetWorker Server,
the process converts NetWorker 8.2.x resources to the new NetWorker 19.4 policy-based resources.
The following NetWorker 8.2.x resource types do not exist in NetWorker 19.4:
● Group, also referred to as the savegroup or save group
● Schedule clone
● VMware policy
● NAS Device

Post Update Tasks 49

Page 54 of 74
NetWorker migrates the configuration information for each resource into new resources, which support the NetWorker Data
Protection Policy framework.
The migration process creates log files on the NetWorker Server, which provide information about the status of resource
conversions. The log files are located in the /nsr/logs/migration folder on LINUX and the C:\Program Files\EMC
NetWorker\nsr\logs\migration directory on Windows.
The following table describes the files thatNetWorker creates during the resource migration process.

Table 9. Migration log files


File name Purpose
migration_summary_date.log Provides a summary of the resource conversion status.
group_groupname.raw Provides detailed information about the migration of attributes in an NetWorker
8.2.x Group resource, including the following information:
● A summary of NetWorker 8.2.x attribute settings.
● A list of NetWorker 8.2.x attributes that are deprecated in 19.4 and are not
converted.
● A summary of attributes with defined values that override the equivalent
attribute in the Client resource.

clone_groupname.raw Provides detailed information about the migration of attributes in an NetWorker


8.2.x scheduled Clone resource, including the following information:
● A summary of NetWorker 8.2.x attribute settings.
● A list of NetWorker 8.1.x and 8.2.x attributes that are deprecated in 19.4 and are
not converted.

NAS_device_groupname.raw Provides detailed information about the migration of attributes in an NetWorker


8.2.x scheduled NAS Device resource, including the following information:
● A summary of NetWorker 8.2.x attribute settings.
● A list of NetWorker 8.2.x attributes that are deprecated in 19.4 and are not
converted.

VMWare_Policy_groupname.raw Provides detailed information about the migration of attributes in an NetWorker


8.2.x VMware Policy resource, including the following information:
● A summary of NetWorker 8.2.x attribute settings.
● A list of NetWorker 8.2.x attributes that are deprecated in 19.4 and are not
converted.

Overview of protection policies


A protection policy allows you to design a protection solution for your environment at the data level instead of at the host level.
With a data protection policy, each client in the environment is a backup object and not simply a host.
Data protection policies enable you to back up and manage data in a variety of environments, as well as to perform system
maintenance tasks on the NetWorker server. You can use either the NetWorker Management Web UI or the NMC
NetWorker Administration window to create your data protection policy solution.
A data protection policy solution encompasses the configuration of the following key NetWorker resources:

Policies
Policies provide you with a service-catalog approach to the configuration of a NetWorker datazone. Policies enable you to
manage all data protection tasks and the data protection lifecycle from a central location.
Policies provide an organizational container for the workflows, actions, and groups that support and define the backup, clone,
management, and system maintenance actions that you want to perform.

50 Post Update Tasks

Page 55 of 74
Workflows
The policy workflow defines a list of actions to perform sequentially or concurrently, a schedule window during which the
workflow can run, and the protection group to which the workflow applies. You can create a workflow when you create a new
policy, or you can create a workflow for an existing policy.
A workflow can be as simple as a single action that applies to a finite list of Client resources, or a complex chain of actions that
apply to a dynamically changing list of resources. In a workflow, some actions can be set to occur sequentially, and others can
occur concurrently.
You can create multiple workflows in a single policy. However, each workflow can belong to only one policy. When you add
multiple workflows to the same policy, you can logically group data protection activities with similar service level provisions
together, to provide easier configuration, access, and task execution.

Protection groups
Protection groups define a set of static or dynamic Client resources or save sets to which a workflow applies. There are also
dedicated protection groups for backups in a VMware environment or for snapshot backups on a NAS device. Review the
following information about protection groups:
● Create one protection group for each workflow. Each group can be assigned to only one workflow.
● You can add the same Client resources and save sets to more than one group at a time.
● You can create the group before you create the workflow, or you can create the group after you create the workflow and
then assign the group to the workflow later.

Actions
Actions are the key resources in a workflow for a data protection policy and define a specific task (for example, a backup or
clone) that occurs on the client resources in the group assigned to the workflow. NetWorker uses a work list to define the task.
A work list is composed of one or several work items. Work items include client resources, virtual machines, save sets, or tags.
You can chain multiple actions together to occur sequentially or concurrently in a workflow. All chained actions use the same
work list.
When you configure an action, you define the days on which to perform the action, as well as other settings specific to the
action. For example, you can specify a destination pool, browse and retention period, and a target storage node for the backup
action, which can differ from the subsequent action that clones the data.
When you create an action for a policy that is associated with the virtual machine backup, you can select one of the following
data protection action types:
● Backup — Performs a backup of virtual machines in vCenter to a Data Domain system. You can only perform one VMware
backup action per workflow. The VMware backup action must occur before clone actions.
● Clone — Performs a clone of the VMware backup on a Data Domain system to any clone device that NetWorker supports
(including Data Domain system or tape targets). You can specify multiple clone actions. Clone actions must occur after the
Backup action.
You can create multiple actions for a single workflow. However, each action applies to a single workflow and policy.
The following figure provides a high level overview of the components that make up a data protection policy in a datazone.

Figure 12. Data Protection Policy

Post Update Tasks 51

Page 56 of 74
Backup Group Resource Migration
During the migration process, NetWorker creates resources to replace each Group resource, and then migrates configuration
attributes from the NetWorker 8.1.x and 8.2.x resources to the new NetWorker 19.4 resources.

Resource migration for Group resources when Snapshot is not enabled


This section summarizes the group attribute values that migrate to 19.4 resources attributes, when the group is not Snapshot
enabled.

Table 10. Migration of Group attributes


19.4 Resource 19.4 Resource name Migration process overview Attribute values migrated from
type Attribute values migrated from Group resource
Group resource
Policy Backup One policy resource that is called Not applicable
Backup appears and contains all
migrated information for all NetWorker
group resources that back up file
system.
Protection Group Name of the Group One Protection Group resource appears Comment
resource for each migrated Group resource. Each
Protection Group contains the same
client resources that were associated
with the pre-19.4 group resource.
Workflow Name of the Group One Workflow resource appears for ● Autostart
resource each migrated Group resource. Each ● Start Time
Workflow resource is associated with
● Next Start
the Protection Group resource that was
created for the migrated Group ● Interval
resource. ● Restart Window
● Probe Interval—To the Interval
attribute
● Probe Start Time—To the Start
Time attribute
● Probe End Time—To the End
Time attribute

Probe Probe The Probe action resource appears when Not applicable
the Probe based group attribute was
enabled in the pre-19.4 migrated group.
Action— Backup The Traditional Backup action appears ● Parallelism
Traditional for a Group resource that does not have ● Retries
backup the Snapshot attribute enabled.
● Retry delay
● Success Threshold
● Option attributes:
○ No save, Verbose, Estimate,
Verify Synthetic Full, Revert
to full when Synthetic Full
fails
● Schedule
● Schedule Time
● Retention policy
● Inactivity Timeout
● Soft Runtime Limit—To Soft
Limit
● Hard Runtime Limit—To Hard
Limit

52 Post Update Tasks

Page 57 of 74
Table 10. Migration of Group attributes (continued)
19.4 Resource 19.4 Resource name Migration process overview Attribute values migrated from
type Attribute values migrated from Group resource
Group resource

● File Inactivity Threshold—To


Inactivity Threshold
● File Inactivity Alert Threshold—
To Inactivity Alert Threshold

Action—Clone Clone The Clone action resource appears when Clone Pool—To the Destination
the Clone attribute was enabled in the Pool attribute
Group resource.

Scheduled Clone migration


The migration process creates one Clone policy for all the Scheduled Clone resources.
In NetWorker 8.x, if you create clones using the Clone section and not as part of the backup configuration, a separate clone
policy is created when you upgrade to NetWorker 9.x. To access the clone, move it under a valid backup, or create new clones.

Table 11. Migration of Scheduled Clone attributes


19.4 resource 19.4 Resource name Migration process overview Attribute values migrated from
type the Scheduled Clone resource
Policy Clone One Policy resource appears for all Not applicable
migrated Scheduled Clone resources.
Protection Group Clone_Name_of_ One Protection Group appears for each Comment
Scheduled_Clone_resour migrated scheduled Clone resource.
ce Each Protection Group contains the
same save set list that was associated
with the pre-19.4 Scheduled Clone
resource.
Workflow Name of the Scheduled One Workflow resource appears for ● Comment
Clone resource each migrated Scheduled Clone ● Start Time
resource. Each Scheduled Clone
● Interval
workflow is associated with the
Protection Group resource that is
created by the migrated Scheduled
Clone resource.
Action Clone The Clone action appears for a Schedule ● Retention Policy
Clone resource. ● Destination Pool
● Source Storage Node

The NetWorker VMware Integration Guide provides detailed information about VMware resource migrations.
The NetWorker Snapshot Management Integration Guide provides detailed information about Snapshot resource migrations.
The NMM documentation provides detailed information about NMM resource migrations.

Changes to the Client and Pool resources after migration


NetWorker uses a number of attributes that are defined in multiple resources to determine which pool receives the data that is
generated by an action task, and how NetWorker backs up the data. The migration process preserves the values that are
defined for the attributes and introduces new attributes in the Action resource.
NetWorker provides the following attributes, which work together to determine how NetWorker manages a backup and
determines which device to use to receive the backup data:
● Client resource—Pools, Retention, Save set, and Level attributes on the General tab of the Client Properties window.
The migration process retains the values in these legacy attributes.

Post Update Tasks 53

Page 58 of 74
NOTE: The Modify Client wizard does not display the Pools, Retention, Save set, and Level attributes.
● Action resource—Destination Pool and Retention attributes on the Specify the Backup Options and Specify the
Clone Options wizard windows. The backup levels are defined for the action schedule on the Specify the Action
Information wizard window.
● Pool resource—Clients, Save sets, and Retention policy attributes on the Legacy tab. The values that appear in these
attributes were defined in NetWorker 8.1.x and 8.2.x. After the migration completes, the NetWorker 19.4 server retains the
values and these legacy attributes become read-only. You cannot modify the values in these fields after migration.
The Action resource includes an attribute that is called Client Override Behavior. The value that is selected for this attribute
determines which resource attribute has precedence over the attributes in other resources that determine the same behavior.
By default, the migration process enables Legacy Backup Rules on an Action resource. Legacy Backup Rules allow
NetWorker to use the values during the pool selection criteria process.
NOTE: By default, the NetWorker Administration window does not show the legacy attributes. To view the legacy
attributes in the Client Properties window, go to the View menu and select Diagnostic Mode.

Pre processing and post processing script changes


NetWorker 9.0.1 and later does not support the savepnpc command.
After you update the NetWorker server, clients that use savepnpc command to perform backups will fail to backup. Modify
these client resources to customize the backup behavior by running pre processing and post processing commands. An error
message similar to the following appears in the savepnpc.log file: pstclntsave: RAP query returned NULL
worklist.
To backup these clients in NetWorker 9.x, edit the Client resource, and perform the following steps:
● In the Backup command attribute, remove the savepnpc command.
● In the Pre command attribute, type the name of the script file that contains the commands to run before the start of the
backup.
● In the Post command attribute, type the name of the script file that contains the commands to run after the backup
completes.
The section "Backup command customization: in the NetWorker Administration Guide provides more about the Pre command
and Post command attributes and how to configure a client that requires pre processing and post processing commands.

Table 12. NetWorker Server Versions


NetWorker Server Versions NetWorker client version configures Client properties need to be updated
with the NetWorker Server
8.2.x 8.2.x backup command savepnpc

9.x and later 8.2.x backup command savepnpc

9.x and later 9.x and later pre command and post command

Client Resource Overrides


NetWorker 19.4 enables you to define a schedule, destination pool, retention policy, and destination storage node for each
backup action that you configure.
NetWorker 8.1.x and 8.2.x allowed you to define a schedule, destination pool, retention policy, and destination storage node
value for each Group and Client resource.
When you assigned a value to any of these attributes in the Group resource, that value was applied to all data generated by
each client in the group.
When you assigned a value to any of these attributes in the Client resource, that value was applied to all data generated by the
client and took precedence over the value that was defined in the equivalent Group resource attribute.
The updating process retains these Client resource values but sets the attributes values to read-only.
The Client resource has the following attributes in common with the Action resource:
● Schedule
● Pool

54 Post Update Tasks

Page 59 of 74
● Retention
● Storage Node
The NetWorker 19.4 Action wizard provides you with the ability to define which resource attribute takes precedence, the value
that is defined in the Action resource or the value that is defined in a Client resource. The selection that you make in the Client
Override Behavior list determines which attribute values take precedence. The following table summarizes each option.

Table 13. Client override behaviors


Option Behavior
Client Can Override The values in the Client resource for Schedule, Pool, Retention policy, and the
Storage Node attributes take precedence over the values that are defined in the
equivalent Action resource attributes.
Client Cannot Override The values in the Action resource for the Schedule, Destination Pool,
Destination Storage Node, and the Retention attributes take precedence over
the values that are defined in the equivalent Client resource attributes.
Legacy Backup Rules This value only appears in actions that are created by the migration process. The
updating process sets the Client Override Behavior for the migrated backup
actions to Legacy Backup Rules.

This value handles the Schedule, Pool, Retention, and Storage Node values in the
following way:

● If a value is defined in the Retention Policy attribute of the Group resource,


then the value that is defined in the Retention attribute of the Action resource
takes precedence. If a value is not defined in the Group resource, then the
attribute that is defined in the Client resource takes precedence.
● If a value is defined in the Schedule attribute of the Group resource, then the
value that is defined in the Schedule attribute of the Action resource takes
precedence. If a value is not defined in the Group resource, then the attribute
that is defined in the Client resource takes precedence.
● If a value is defined in the Pool attribute of the Client resource, the value that is
defined in the Client resource is used. If a value is not defined in the Client
resource, then the action sends the data to a pool that best matches the pool
selection criteria.
NOTE: You can edit the Action resource and change the Client Override
Behaviour attribute to Client Can Override or Client Cannot Override,
but after you save the change to the Action resource, you cannot set the
attribute back to Legacy Backup Rules.

Changes to the schedule resource and levels


NetWorker allows you to configure attributes in the Action resource that define the schedule for the task, and for a backup or
clone task, the level.
When you configure an Action resource in NetWorker 19.4, the Action wizard provides you with the ability to define the
schedule, schedule overrides, and level for the data that is generated by the task.
In NetWorker 8.1.x and 8.2.x, you assigned a pre-configured or user-configured backup schedule to the Group and Client
resources. When you assigned the schedule or a level to the Group resource, the values were applied to all the backup and clone
data generated by each client in the group. When you assigned the schedule or level to the Client resource, the values were
applied to all the backup and clone data generated by the client and took precedence over the values that were defined in the
Group resource.
The updating process migrates existing values in the Schedule and Level attributes in the Group resource to the Action
resource. NetWorker 19.4 does not support backup levels 2–9. When the update process encounters a schedule with a backup
level 2–9, NetWorker changes the level to 1. The update process retains the level and schedule attributes that were defined in
the Client resource.
The Client resource overrides section describes how NetWorker 19.4 determines the schedule that a task uses when an action is
performed on a client and both the Client resource and Action resource define a schedule.

Post Update Tasks 55

Page 60 of 74
Changes to save set policies
NetWorker 19.4 does not separate the length of the browse time for a save set from the length of the retention time for a save
set. Information about a backup or clone save set remains in the client file index and media database for the length of time that
is defined by the retention policy.
When you configure an Action resource in NetWorker 19.4, the Action wizard provides you with the ability to define the
retention policy for the data that is generated by the task.
In NetWorker 8.1.x and 8.2.x, you assigned a browse and retention policy to the Group and Client resources. When you assigned
a browse or retention policy to the Group resource, the value that is applied to all the data that is generated by each client in
the group. When you assigned a policy to the Client resource, the value that is applied to all the data that is generated by the
client.
The updating process performs the following tasks:
● Migrates the existing value in the Retention Policy attribute in the Group resource to the Action resource.
● Modifies the browse time for all save sets in the media database to match the retention time.
● Modifies the Browse policy in the Client resource to match the existing value in the Retention Policy attribute, and make the
attribute read-only.
● Retains the value that is defined in the Retention Policy attribute that was defined in the Client resource.
The Client resource overrides section describes how NetWorker 19.4 determines the retention policy that a task uses when
an action is performed on a client and both the Client resource and Action resource define a retention policy.

Changes to the save set expiration process


NetWorker 19.4 expires save set information in the media database and client file index as a separate action, in the Server
backup workflow, which is part of the Server Protection policy.
In NetWorker 8.1.x and 8.2.x, the NetWorker server ran an nsrim process once every 24 hours to remove information about
eligible save sets from the client file index and mark eligible save sets as recoverable or recyclable in the media database.
NetWorker 19.4 creates a Policy resource that is called the Server Protection policy. The Server Protection Policy contains the
Server Protection group. The Server Protection group is associated with the Server backup workflow, which starts the
Expiration action daily at 10 a.m.

Expiration
The expiration action expires save sets in the media database based on retention time of the save set. When the retention time
of the save set has been reached, NetWorker uses the nsrim process to expire the save set. When a save set expires, the
nsrim process performs the following actions:
● Removes information about the save set from the client file index.
● If the save set data resides on an AFTD, removes the save set information from the media database and removes the save
set data from the AFTD.
● If the save set data resides on a tape device, the nsrim process marks the save set as recyclable in the media database.
When all save sets on a tape volume have expired, the volume is eligible for reuse.
● If the disk type(AFTD and DD Boost) volume is marked read-only, nsrim does not reclaim or recover the space by deleting
expired save sets.
An expiration action is created automatically in the Server maintenance workflow of the Server Protection policy. An expiration
action only supports Execute and Skip backup levels.

Changes to bootstrap and index backups


NetWorker 19.4 performs a bootstrap and index backup as separate backup action in the Server backup workflow, which is part
of the Server Protection policy.
In NetWorker 8.1.x and 8.2.x, NetWorker performs a bootstrap backup when the operations in a group that contains the
NetWorker server completes. If the NetWorker server Client resource does not appear in an active Group resource, the
bootstrap backup every time a group completes, even when the backup level is set to skip.

56 Post Update Tasks

Page 61 of 74
NetWorker 19.4 creates a policy resource that is called the Server Protection policy. The Server Protection Policy contains the
Server Protection group. The Server Protection group is associated with the Server backup workflow, which starts the Server
database backup action daily at 10 a.m.

Server database backup


A server database backup action performs a bootstrap backup and can also include the client file indexes.
A bootstrap backup contains the following NetWorker server components:
● Media database
● Server resource files. For example, the resource (res) database and the Package Manager database (nsrcpd)
● NetWorker Authentication Service database
NetWorker automatically creates a server backup action in the Server Backup workflow of the Server Protection policy. By
default, a full backup of the media database, resource files, and the NetWorker Authentication Service database occurs daily. A
full backup of the client file indexes occur on the first day of the month. An incremental backup of the client file indexes occur
on the remaining days of the month. The default retention policy for the server database backup is one month.
The migration process may not assign the bootstrap backup to the pool that was configured in NetWorker 8.1.x and 8.2.x. You
can edit the Server database action in the NetWorker Administration window and change the destination pool value or use the
nsrpolicy command to update the pool. For example:
nsrpolicy action update server-backup -p "Server Protection" -w
"Server backup" -A "Server db backup" --destination_pool pool_name

Changes to the NMC database backup


NetWorker 19.4 performs an NMC database backup as separate backup action in the NMC Server backup workflow, which is
part of the Server Protection policy. The NMC database backup action creates a staging directory for the database files,
performs a backup of the staging directory, and then deletes the contents of the staging directory.
In NetWorker 8.1.x and 8.2.x, the NMC server configuration process created a Client resource for NMC database backups on
the NetWorker server. The Client resource contained the following value in the Save set attribute:

NMCASA:/gst_on_server_name/lgto_gst

where server_name is the short name of the NMC server host.


When the update process detects a Client resource for the NMC backup, NetWorker migrates the Client resource, but does not
add it to the Protection Group associated with NetWorker 8.1.x and 8.2.x Group resource that contained the NMC Client
resource. The migration process makes the following attribute changes to the Client resource for the NMC server database
backup:
● Updates the value in the Save set attribute. The Save set field for the client contains the path to the database staging
directory. By default, the staging directory is in C:\Program Files\EMC NetWorker\Management\nmcdb_stage
on Windows and /opt/lgtonmc/nmcdb_stage on Linux.
NOTE:

The file system that contains the staging directory must have free disk space that is a least equal to the size of the
current NMC database. The section "Changing the staging directory for NMC database backups" describes how to
change the staging directory location.

The NetWorker Administration Guide describes how to change the staging directory
● Clears the values in the Level and Retention attributes.
When you log in to the NMC server for the first time after an update, the configuration wizard prompts you to define the
NetWorker server that will backup the NMC database. When you configure the NMC database backup, the NetWorker server
performs the following actions:
● Creates a group called NMC server.
● Adds the Client resource to the NMC server group.
● Creates a workflow that is called NMC server backup in the Server Protection policy. The workflow contains the NMC
server backup action, which performs a full backup of the NMC server database every day at 2 P.M.
● Adds the NMC server group to the NMC server backup workflow.

Post Update Tasks 57

Page 62 of 74
Customizing the NMC database backup
After you update the NetWorker server, modify the NMC-specific resources in the Server Protection policy to define the
backup configuration.
1. In the NetWorker Administration window, click Protection.
2. In the left navigation pane, expand Policies, and then expand Server Protection.
3. In the right window pane, on the Actions tab, edit the NMC server backup action.
The Policy Action Wizard appears, starting with the Specify the Action Information window.
4. Specify a weekly, monthly, or reference schedule for the action:
● To specify a schedule for each day of the week, select Define option under Select Schedule and period as Weekly by
day.
● To specify a schedule for each day of the month, select Define option under Select Schedule and period as Monthly
by day.
● To specify a customized schedule to the action, select Select option under Select Schedule and choose a customized
schedule using the drop-down menu that is already created under NSR schedule resource.
5. Click the icon on each day to specify the backup level to perform. The following table provides details about the supported
NMC server backup level that each icon represents.

Table 14. Backup levels


Icon Label Description

Full Perform a full backup on this day. Full


backups include all files, regardless of
whether the files changed.

Incr Perform an incremental backup on this


day. Incremental backups include files
that have changed since the last
backup of any type (full or
incremental).

Skip Do not perform a backup on this day.

NOTE: The NMC Server database backup only supports the full and skip backup levels. If you edit the NMC Server
backup action and change the levels in the backup schedule to a different level, for example synthetic full, NetWorker
performs a full backup of the database.

6. Click Next.
The Specify the Backup Options page appears.
7. From the Destination Storage Node box, select the storage node with the devices on which to store the backup data.
8. From the Destination Pool box, select the media pool in which to store the backup data.
9. From the Retention boxes, specify the amount of time to retain the backup data.
After the retention period expires, the save set is removed from the client file index and marked as recyclable in the media
database during an expiration server maintenance task.

10. Click Next.


The Specify the Advanced Options page appears.
11. In the Retries field, specify the number of times that NetWorker should retry a failed probe or backup action, before
NetWorker considers the action as failed. When the Retries value is 0, NetWorker does not retry a failed probe or backup
action.
NOTE: The Retries option applies to probe actions, and the backup actions for the Traditional and Snapshot action
types. If you specify a value for this option for other actions, NetWorker ignores the values.

12. In the Retry Delay field, specify a delay in seconds to wait before retrying a failed probe or backup action. When the Retry
Delay value is 0, NetWorker retries the failed probe or backup action immediately.

58 Post Update Tasks

Page 63 of 74
NOTE: The Retry Delay option applies to probe actions, and the backup actions for the Traditional and Snapshot action
types. When you specify a value for this option in other actions, NetWorker ignores the values.

13. In the Inactivity Timeout field, specify the maximum number of minutes that a job that is run by an action can try to
respond to the server.
If the job does not respond within the specified time, the server considers the job a failure and NetWorker retries the job
immediately to ensures that no time is lost due to failures.
Increase the timeout value if a backup consistently stops due to inactivity. Inactivity might occur for backups of large save
sets, backups of save sets with large sparse files, and incremental backups of many small static files.
NOTE: The Inactivity Timeout option applies to probe actions, and the backup actions for the Traditional and
Snapshot action types. If you specify a value for this option in other actions, NetWorker ignores the value.

14. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple
rollover is implemented at an action level.
15. From the Failure Impact list, specify what to do when a job fails:
● To continue the workflow when there are job failures, select Continue.
● To stop the current action if there is a failure with one of the jobs, but continue with subsequent actions in the workflow,
select Abort action.
NOTE: The Abort action option applies to probe actions, and the backup actions for the Traditional and Snapshot
action types.
● To stop the entire workflow if there is a failure with one of the jobs in the action, select Abort workflow.

NOTE: If any of the actions fail in the workflow, the workflow status does not appear as interrupted or canceled.
NetWorker reports the workflow status as failed.

16. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default
value of 0 (zero) indicates no amount of time.
17. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value
of 0 (zero) indicates no amount of time.
18. (Optional) Configure overrides for the task that is scheduled on a specific day.
To specify the month, use the navigation buttons and the month list box. To specify the year, use the spin boxes. You can
set an override in the following ways:
● Select the day in the calendar, which changes the action task for the specific day.
● Use the action task list to select the task, and then perform one of the following steps:
○ To define an override that occurs on a specific day of the week, every week, select Specified day, and then use the
lists. Click Add Rules based override.
○ To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add
Rules based override.
NOTE:

○ You can edit or add the rules in the Override field.


○ To remove an override, delete the entry from the Override field.
○ If a schedule is associated to an action, then override option is disabled.

19. From the Send Notifications list box, select whether to send notifications for the action:
● To use the notification configuration that is defined in the Policy resource to send the notification, select Set at policy
level.
● To send a notification on completion of the action, select On Completion.
● To send a notification only if the action fails to complete, select On Failure.

20. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box
appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the
notifications to a log file or you can send an email notification.
The default notification action is to send the information to the policy_notifications.log file. By default, the
policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows.

Post Update Tasks 59

Page 64 of 74
Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:
● To send notifications to a file, type the following command, where policy_notifications.log is the name of the
file:
nsrlog -f policy_notifications.log
● On Linux, to send an email notification, type the following command:
mail -s subject recipient
● On Window, to send a notification email, type the following command: smtpmail -s subject -h mailserver
recipient1@mailserver recipient2@mailserver...
where:
○ -s subject—Includes a standard email header with the message and specifies the subject text for that header.
Without this option, the smtpmail program assumes that the message contains a correctly formatted email header
and nothing is added.
○ -h mailserver—Specifies the hostname of the mail server to use to relay the SMTP email message.

○ recipient1@mailserver—Is the email address of the recipient of the notification. Multiple email recipients are
separated by a space.

21. Click Next.


The Action Configuration Summary page appears.
(Optional) Create a clone action to automatically clone the save sets after the NMC server backup. The NetWorker
Administration Guide describes how to configure a clone action for the NMC server backup.

60 Post Update Tasks

Page 65 of 74
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 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 61

Page 66 of 74
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 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:

62 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 67 of 74
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.
● 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.

Troubleshooting NMC GUI and NetWorker Server connection issues 63

Page 68 of 74
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:

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.

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.

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.

64 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 69 of 74
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.

Error: error while loading shared libraries: libsasl2.so.2: wrong ELF class:
ELFCLASS64
This message occurs on 64-bit Linux systems, when you do not install the 32-bit version of the cyrus-sasl package.
To resolve this issue, perform the following steps.
1. Log in to the NMC server, as root.
2. Install the 32-bit operating system cyrus-sasl package.
3. Start the NMC daemons, by typing the command below, based on the initialization system running on your Linux machine:
● sysvinit—/etc/init.d/gst start

Troubleshooting NMC GUI and NetWorker Server connection issues 65

Page 70 of 74
● systemd—systemctl start gst

This action also starts the postgres and httpd processes.

NOTE: If /etc/init.d/gst file is missing for sysvinit systems or gst file is not enabled for systemd systems, run the
script - /opt/lgtonmc/bin/nmc_config

Multiple Postgres processes appear. Two or more httpd processes appear. By default, these httpd processes run as
nsrnmc.

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 LINUX, an orphaned httpd process is running on the console server. End the process by sending the SIGTERM signal,
kill -TERM.
Do not use the kill -9 command.

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.

66 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 71 of 74
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.

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:
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.

Troubleshooting NMC GUI and NetWorker Server connection issues 67

Page 72 of 74
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.

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.

68 Troubleshooting NMC GUI and NetWorker Server connection issues

Page 73 of 74
Dell Technologies Confidential Information version: 5.0.6.32

Page 74 of 74

You might also like