NetWorker - Updating The NetWorker Software-NetWorker 19.4
NetWorker - Updating The NetWorker Software-NetWorker 19.4
NetWorker - Updating The NetWorker Software-NetWorker 19.4
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
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]
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.
Page 1 of 74
Contents
Preliminary Activity Tasks .......................................................................................................3
Read, understand, and perform these tasks.................................................................................................3
Page 2 of 74
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.
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.
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.
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 IV: Post Update Configurations and Reviewing the Migration Results.................................. 33
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
4 Contents
Page 9 of 74
Figures
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.
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:
You can use the following resources to find more information about this product, obtain support, and provide feedback.
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.
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.
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
Page 16 of 74
1
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
● 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:
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.
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.
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
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.
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.
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.
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.
NOTE:
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
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
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
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.
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.
Page 26 of 74
tar -xzf file_name.tar.gz
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.
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.
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:
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:
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:
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.
Linux em64T & AMD64 (64-bit), RHEL 6, 7, SLES 11, 12 ● JRE 1.8.x
● JRE 9.x
● Mozilla Firefox
Solaris 10, 11, 12 for Solaris SPARC, Solaris Opteron (64-bit) ● JRE 1.8.x
● 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
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.
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.
1. Stop the NetWorker and NMC daemons, by typing the command below, based on the initialization system running on your
Linux machine:
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 :
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.
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.
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
Page 32 of 74
Troubleshooting NMC installation and configuration issues
This section describes how to troubleshoot and resolve common NMC installation and configuration issues.
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
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:
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.
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
NOTE: For more information on installing NetWorker Management Web UI, see NetWorker Installation Guide
Page 35 of 74
6
Updating NetWorker for UNIX
This chapter includes the following topics:
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
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
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
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.
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.
where:
● The location of the nsrauthtrust command differs on Linux and Windows:
○ Linux—/usr/sbin
○ Windows—C:\Program Files\EMC NetWorker\nsr
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
● 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
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
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.
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.
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.
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.
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.
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.
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.
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.
3. Click OK.
4. Click Close.
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.
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.
Default value: NO
Page 47 of 74
Table 8. Configuration options (continued)
Options for 9.x and later Equivalent 8.2 Description
and earlier
option name
Page 48 of 74
Table 8. Configuration options (continued)
Options for 9.x and later Equivalent 8.2 Description
and earlier
option name
Default value: No
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.
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.
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.
Page 51 of 74
Figure 8. Copying the group DN
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.
"query-tenant=IDD" -D
"query-domain=ldapdomain"
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.
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.
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.
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.
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.
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
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
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.
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.
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.
9.x and later 9.x and later pre command and post command
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.
This value handles the Schedule, Pool, Retention, and Storage Node values in the
following way:
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.
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.
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.
NMCASA:/gst_on_server_name/lgto_gst
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.
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.
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.
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.
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:
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.
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.
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
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.
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.
nsradmin -p nsrexec
p type: nsr peer information; name: nmc-server-name
delete
yes
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:
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:
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.
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.
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
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.
● 9000
● 9001
● 5432
The NetWorker Security Configuration Guide provides more information about how to determine the required ports for
NetWorker hosts.
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
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.
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
Page 70 of 74
● systemd—systemctl start gst
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.
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
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.
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.
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.
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.
Page 73 of 74
Dell Technologies Confidential Information version: 5.0.6.32
Page 74 of 74