Installing and Uninstalling EMC NetWorker KM

This chapter provides information about prerequisites and packages required to operate EMC NetWorker KM for PATROL, as well as detailed step-by-step procedures for installing and uninstalling the KM.

To be able to use EMC NetWorker KM for PATROL, you will have to:

  • Ensure that requirements are met
  • Get the installation packages from the Sentry’s Website
  • Install the KM
  • Load the KM on the PATROL console(s).

Preparing for Installation

Meeting the Prerequisites

System Requirements

EMC NetWorker KM for PATROL supports the following operating systems:

Operating System Version
AIX 5.1 and higher
HP-UX 11 and higher
Linux All distributions
Oracle Solaris 8 and higher
Windows 2008 and higher

Software Requirements

EMC NetWorker KM for PATROL supports:

Software Version
EMC NetWorker 8 and higher
BMC PATROL Agent Any version
BMC PATROL Console Any version
BMC Portal 2.3 and higher
BMC ProactiveNet Performance Management 9.5 and higher
BMC TrueSight Operations Management 10 and higher
Java 1.8 and higher

If you are running the EMC NetWorker KM with sudo user account, or on AIX, LINUX, or Microsoft Windows x64 managed nodes, please verify these additional software requirements:

Purpose Software Version
When running EMC NetWorker KM with sudo user account on Solaris, HP-UX, AIX or Linux managed nodes Sudo (superuser do) 1.6.7 and higher
When running EMC NetWorker KM on Linux managed nodes Korn shell binary (/bin/ksh). Any
When running EMC NetWorker KM on Microsoft Windows x64 managed nodes Reg.exe patch KB948698 Any

Changes Required
For EMC NetWorker

No changes need to be done to EMC NetWorker to use EMC NetWorker KM for PATROL.

To Improve the KM Performance

Some changes must however be made to BMC PATROL to improve the performance of EMC NetWorker KM for PATROL. The PATROL Agent tuning variable /AgentSetup/AgentTuning/pslInstructionMax should be disabled by setting it to 0 (zero) or increased to at least 5,000,000. These settings apply to all EMC NetWorker servers and storage nodes where the KM is installed. This adjustment will allow the KM data collectors to execute without incurring an internal scheduling delay.

This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows), xpconfig (on Unix) or PATROL Configuration Manager (PCM). Alternatively, you can use one of the following single line PSL command through the PATROL Console OS> prompt to update this tuning variable.

To disable the pslInstructionMax variable

%PSL pconfig("REPLACE","/AgentSetup/AgentTuning/pslInstructionMax",0);

To set the tuning variable to at 5,000,000

%PSL v="/AgentSetup/AgentTuning/pslInstructionMax";if(get(v)<5000000){pconfig("REPLACE",v,5000000);}

In large EMC NetWorker systems, the value of 5,000,000 for the tuning variable pslInstructionMax may still be insufficient. In such situations, error messages will appear on the PATROL Console System Output Window (SOW) reporting that some NetWorker KM data collectors are in an infinite loop. In this case you can set the tuning variable to 0 (zero) to disable this functionality.

For the Access Control List (ACL)

The KM stores all configuration information in the PATROL Agent configuration database (pconfig), under the /NSR/<node-id> and /Runtime/NSR/<node-id> paths. PATROL Agent user (default: patrol) should be able to read and write to these pconfig variables at anytime. If Access Control List (ACL) is used to control which users are authorized to connect to a PATROL Agent, please make sure that the mode for PATROL Agent user includes “C” in the PATROL Agent variable /AgentSetup/accessControlList. Refer to the PATROL Agent Reference Manual for more details.

To support bash shell platforms when ksh is not installed

To collect EMC NetWorker stats when ksh is not installed on UNIX/Linux servers, you need to create a soft link for /bin/ksh to /bin/bash:

ln –s  /bin/bash /bin/ksh

Security Requirements

A user account with administrative privileges must be configured in BMC PATROL or BMC TrueSight Operations Management to read and execute EMC NetWorker application programs and access file systems. Depending on the operating systems used, several options will be available.

The following user accounts can be used:

  • On Unix platforms:

    • a root user
    • a non-root user, such as patrol, that has sudo privileges on EMC NetWorker to execute application programs and access file systems
    • a non-root account, such as patrol, configured in EMC NetWorker application to administer the EMC NetWorker application.
  • On Windows platforms:

    • an administrator user
    • a non-administrator account, such as patrol, configured in EMC NetWorker application to administer the EMC NetWorker application. Refer to the EMC NetWorker System Administrator’s Guide for details on how to set up this type of account.

The user login details are configured in the KM. The password is encrypted and stored in the PATROL Agent.

Access Permissions

The EMC NetWorker KM user needs “read & execute” permission to executable and library files under the paths listed below. The EMC NetWorker installation path INSTALL_PATH, referenced in the tables below is usually:

  • /nsr or /opt/nsr or /opt/networker (on Unix)
  • C:\Program Files\nsr (on Microsoft Windows).

Here are the executable and library files accessed by the EMC NetWorker KM for PATROL User:

UNIX Microsoft Windows
INSTALL_PATH/bin INSTALL_PATH\bin
INSTALL_PATH/lib
/usr/bin
/usr/sbin
/usr/sbin/nsr
/usr/lib/nsr
/etc/LGTOuscsi

If the KM is enabled to failover in a clustered environment, the login user needs execute permissions to the following cluster commands:

  • /opt/VRTSvcs/bin/hagrp (in Veritas Cluster Server)
  • vxdctl (in Veritas Cluster File System)
  • /usr/cluster/bin/clrg (in Oracle Solaris Cluster)
  • cluster (in Microsoft Cluster)

The EMC NetWorker KM for PATROL includes some scripts which should be executable by the PATROL Agent user and the NetWorker KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/NSR.

To list all OS commands used by the EMC NetWorker KM for PATROL, execute the following PSL code from the PATROL Console, using the PSL Task menu, after installing and loading the KM.

foreach var (grep("^/Runtime/NSR/.*CommandControls/",pconfig("LIST")))
{
  ctl=get(var);
  opt=ntharg(grep("Option",ctl),"2-"," =");
  nsa=ntharg(grep("NoSudoAttempt",ctl),"2-"," =");
  sua=ntharg(grep("SingleUserAttempt",ctl),"2-"," =");
  typ=ntharg(grep("CommandType",ctl),"2-"," =");
  cmd=nthargf(grep("CommandText",ctl),"2-","=","=");
  if(osp=="") { osp=trim(nthargf(grep("OSPlatform",ctl),"2-","=","="), " "); }
  fields=lines(ntharg(var,"1-","/"));
  old_host=host;
  host=(fields == 5)? ntharg(var,"3","/") : "localhost";
  if(host!=old_host)
  {
    if((osp!="WINDOWS") && sudoers) { printf("\n\nCommands used with sudo:\n%s",sort(sudoers)); }
    printf("\n\nOn %s:\n\n", host);
    i=0; sudoers=""; osp="";
  }
  if((typ == "")||(typ == "OS"))
  {
    met="";
    if(opt == "NoLogin") { met = "(run as patrol user)"; }
    elsif(nsa == "YES") { met = "(run as configured user without sudo)"; }
    elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; }
  else
  {
    scmd=cmd;
    s=index(scmd,"%sudo");
    if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); }
    sudoers=union(sudoers,ntharg(ntharg(scmd,1,">|"),"1-"," "," "));
  }
  printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,fields,"/"),met,cmd);
  }
}
if((osp!="WINDOWS") && sudoers) { printf("\n\nCommands used with sudo:\n%s",sort(sudoers)); }
Paths and Files Accessed by PATROL Agent User
Unix Microsoft Windows
INSTALL_PATH/res INSTALL_PATH\res
INSTALL_PATH/index INSTALL_PATH/index
INSTALL_PATH/mm INSTALL_PATH/mm
INSTALL_PATH/logs/daemon.log INSTALL_PATH/logs/daemon.log
INSTALL_PATH/logs/messages INSTALL_PATH/logs/messages
INSTALL_PATH/logs/summary INSTALL_PATH/logs/summary
INSTALL_PATH\logs\savegrp.log
/var/adm/messages (on Solaris)
/var/adm/syslog/syslog.log (on HP-UX)

On Windows platforms the EMC NetWorker installation is identified by checking the Microsoft Windows Registry. Depending on whether you are using a 32/64-bit OS and/or 32/64-bit Application, the Registry entries are stored in different locations:

“HKEY_LOCAL_MACHINE\SOFTWARE\Legato\NetWorker\” and “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Legato\NetWorker\”.

The configured login user should have sufficient privileges to run regedit command on the managed node.

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the KM user, configure the account as a sudoer through the visudo utility using code appropriate for your platform as detailed below. This user should be able to execute EMC NetWorker commands and OS commands listed above.

The code below also applies to all non-root users who may execute EMC NetWorker KM administration and report menu commands using their sudo privileges. The KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriate KM user names. The EMC NetWorker installation path INSTALL_PATH, referenced below is normally /nsr,/opt/nsr or /opt/networker and PATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

Warning: This non-root sudo user configured in the KM will be able to execute EMC NetWorker commands. To prevent unauthorized access, ensure that this user is only used within the KM and not made public for general use.
Warning: Entering the non-root sudo user with ‘Use Sudo’ option selected into the login configuration dialog before updating the sudoers file, will generate sudo errors. Also if the sudo user is configured differently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudo user password.
On Solaris
User_Alias NSRKMUSERS = user1, user2, user3
Defaults:NSRKMUSERS !lecture,!authenticate,!requiretty,\
env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset
NSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\
/usr/sbin/nsr/*,/etc/LGTOuscsi/*\
INSTALL_PATH/bin/*,\
PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/*

user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. PATROL_HOME paths are only required for local monitoring.

Replace PATROL_HOME/lib/NSR/* with the Remote Temp Directory Path, default /var/tmp/*, when monitoring remotely.

On HP-UX
User_Alias NSRKMUSERS = user1, user2, user3
Defaults:NSRKMUSERS !lecture,!authenticate,!requiretty,\
env_keep+="PATH SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset
NSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\
/usr/sbin/nsr/*,/etc/LGTOuscsi/*\
INSTALL_PATH/bin/*,\
PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/*

user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. PATROL_HOME paths are only required for local monitoring.

Replace PATROL_HOME/lib/NSR/* with the Remote Temp Directory Path, default /var/tmp/*, when monitoring remotely.

On AIX & Linux
User_Alias NSRKMUSERS = user1, user2, user3
Defaults:NSRKMUSERS !lecture,!authenticate,!requiretty,\
env_keep+="PATH LIBPATH INSTALL_PATH KM_HOME KM_TEMP",env_reset
NSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\
/usr/sbin/nsr/*,/etc/LGTOuscsi/*\
INSTALL_PATH/bin/*,\
PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/*

user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. PATROL_HOME paths are only required for local monitoring.

Replace PATROL_HOME/lib/NSR/* with the Remote Temp Directory Path, default /var/tmp/*, when monitoring remotely.

Disk Space Requirements

EMC NetWorker KM for PATROL requires approximately:

  • 3 MBytes of available disk space on each monitored PATROL Agent system
  • 5 MBytes of available disk space on each PATROL Console system
  • 400 KBytes of available disk space on each PATROL Central Console Server system
  • 1 MByte of available disk space on each PATROL Central Web Server system

It is installed under the PATROL installation path.

When monitoring a standard installation of EMC NetWorker, the PATROL Agent will generate approximately 250 KBytes of history data per day. An enterprise installation of EMC NetWorker on a server with multiple storage nodes, clients, jukeboxes, and standalone devices will generate more history data (as per other KMs used by the PATROL Agent). These history data files are recycled by PATROL depending on the PATROL Agent history retention period.

During execution, the KM creates and maintains temporary files under the KM_TEMP and KM_DEBUG paths. By default they are all under PATROL_HOME/lib/NSR, where PATROL_HOME path is usually /opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMC Software\Patrol3\ (on Microsoft Windows). Please make sure that you have sufficient space under KM_TEMP and KM_DEBUG paths.

If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using the Configuration > Paths menu from the server instance. These folders should have read, write and execute permissions for both the PATROL Agent user and the local KM login user.

Remote Monitoring Requirements

Remote monitoring is required for all servers or appliances on which no PATROL Agent can be installed. This feature is also interesting if you lack resources or time to deploy a PATROL Agent and EMC NetWorker KM for PATROL on several servers since it allows you to monitor multiple hosts from one agent.

Remote monitoring is not possible from a UNIX/Linux PATROL Agent system to a Windows-based EMC NetWorker server.

Please refer to the sections below for information about the remote monitoring requirements:

JAVA

EMC NetWorker KM requires Java 1.8 or higher and a Java Runtime Environment (JRE) to be installed on the same system that runs the PATROL Agent.

The KM will automatically detect the JRE path if it has been installed in the default location or under the BMC PATROL Agent installation path. If it has been installed in a different location, you will have to set JAVA_HOME as the PATROL Agent default account before starting the PATROL Agent.

You can download the Java Runtime Environment along with the KM on Sentry Software Web site.

SSH/WMI Connection

An SSH (UNIX/Linux platforms) or a WMI (Windows platforms) connection is required to monitor remote EMC NetWorker servers. When using an SSH connection, the SSH host key authentication must be disabled on the remote host.

To disable the SSH host key authentication:

  1. Open the global SSH configuration file (ssh_config) stored in the /etc/ssh/ directory on the remote host
  2. Add the line StrictHostKeyChecking no
  3. Save the file.

Getting the Installation Packages

The EMC NetWorker KM for PATROL installation packages are designed for use with the BMC Software Installation Utility. They need to be merged with the latest available version of the BMC Software Installation Utility.

Getting the BMC Utility Package

The latest version of the BMC Software Installation utility is required to install EMC NetWorker KM for PATROL. It can be downloaded from the Sentry Software Web site.

Choose the appropriate package depending on the platform you plan to install EMC NetWorker KM for PATROL on:

  • For UNIX/Linux systems: ins_ALL_<version>.tar
  • For Windows systems: ins_WINDOWS_<version>.zip

The packages are valid for all the PATROL components: Agent, Console, Console Server, etc.

Getting the EMC NetWorker KM Packages

Two packages are available to download on the Sentry Software Web site. They can be used to install the KM on every PATROL component (Agent, Console, etc.) according to the platform you are using.

  • For UNIX/Linux systems: emc-networker-<version>-thorium.tar
  • For Windows systems: emc-networker-<version>-thorium.zip

Getting the JRE Package

Java Runtime Environment version 1.8.00 or higher is required for the KM to operate properly.

A package with a suitable Java Runtime Environment, designed for use with the BMC Software Installation Utility, is made available to download on the Sentry Software Web site.

Installing EMC NetWorker KM

Like most Knowledge Modules for PATROL, you need to install EMC NetWorker KM for PATROL on the following components of your PATROL architecture:

  • Every managed system with a PATROL Agent
  • Every PATROL Console (Classic) that will show information and alerts
  • The Console Server
  • PATROL Central Web Edition

To install EMC NetWorker KM for PATROL

  1. Extract the setup files:

    • On Windows:

      1. Unzip the BMC Installation Utility: ins_Windows_<version>.zip.
      2. Unzip the emc-networker-<version>-thorium.zip package in the same folder.
      3. (Optional) If you need to install the latest Java Runtime Environment program, unzip the jre_windows_WINDOWS_<version>.zip package in the same folder. The content of the packages merges into a subfolder named bmc_products. Windows may ask for your confirmation to overwrite files and folders. This is normal behavior and you can accept all overwrite confirmation requests.
    • On Linux:

      1. First, untar the BMC Installation Utility: tar xvf jre_unix_LINUX-SOLARIS_<version>.tar.
      2. Next, untar the EMC NetWorker KM for PATROL package named: emc-networker-<version>-thorium.tar.
  2. Browse to the bmc_products folder where the files have been extracted.

  3. Launch the setup.exe program (Windows) or setup.sh script (UNIX).

  4. The welcome screen of the installer appears. Click Next to continue.

    Installation Wizard - Welcome

  5. Read the license agreement, click the Accept option and then click Next to continue.

    Installation Wizard - License Agreement

  6. Select Install products on this computer now and click Next to continue.

    Installation Wizard - Selecting Installation Options

  7. Specify the BMC Software Products installation directory. Click Next to continue.

    Installation Wizard - Selecting the Installation Directory

  8. Installing EMC NetWorker KM for PATROL does not require any customization. Select Default and click Next to continue.

    Installation Wizard - Selecting an Installation Type

  9. Select one or several of the following options:

    • Managed System to install EMC NetWorker KM for PATROL on a PATROL Agent.
    • Console Systems to install EMC NetWorker KM for PATROL on a PATROL Classic Console.
    • Common services to install EMC NetWorker KM for PATROL on the Console Server or on PATROL Central Web Edition.

    Installation Wizard - Selecting Roles

  10. Click Next to continue.

  11. Install the KM:

    • Check the EMC NetWorker KM for PATROL box (it should be selected by default).
    • Select the Java Runtime Environment program if you want to install it along with the KM (this option is only provided when you have previously downloaded and merged the package with the BMC Installation Utility).
    • Click Next to continue.

    Installation Wizard - Selecting Products and Components

  12. Review the installation parameters and click Start Install to launch the installation procedure. Click Next.

    Installation Wizard - Reviewing Installation Options

  13. The setup program displays the actions performed and indicates the percentage of completion. Once the installation is complete, click Next to view the installation results.

    Installation Wizard - Installation Status

  14. The wizard displays the installation results. Click View Log to display a detailed log of the installation procedure. Click Next and then Finish to exit the setup program.

    Installation Wizard - Installation Results

  15. Click the Finish button to complete and close the installation wizard.

    Installation Wizard - Completing and closing the Installation Wizard

Loading / Unloading EMC NetWorker KM for PATROL

Loading EMC NetWorker KM for PATROL

In order to monitor your EMC NetWorker environment within your PATROL Console, EMC NetWorker KM for PATROL must be loaded on the appropriate managed system. Loading a Knowledge Module in PATROL Central Operator both loads the Knowledge Module on the managed system and adds the name of the Knowledge Module to your management profile.

Before loading the EMC NetWorker KM for PATROL:

  1. Make sure you properly installed the KM on PATROL Console and PATROL Agent systems.
  2. Start the PATROL Console and update the connection to all PATROL Agent systems where EMC NetWorker KM is installed.
  3. Check the value of the PATROL Agent tuning variable, /AgentSetup/AgentTuning/pslInstructionMax, and if necessary, increase it.

On PATROL Classic

  1. In the Console menu bar, click File > Load KM.
  2. In the Files of Type list, select KM Files.
  3. Select EMC NetWorker KM for PATROL (NSR_LOAD.kml).
  4. Click Open.

EMC NetWorker KM for PATROL will be loaded to the PATROL Console, and all connected PATROL Agents. The EMC NetWorker container instance will be created. Any previous EMC NetWorker KM configuration will be upgraded and their instances will be created.

If you want to save the new list of loaded files as the PATROL Console user preference:

  1. From the PATROL Console menu bar, choose File > Save Configuration
  2. Load the NSR_LOAD.kml file on each PATROL Console.
  3. Configure the KM.

On PATROL Central

  1. In the Common Tasks tab of the PATROL Central Operator Taskpad, click the Load Knowledge Modules icon.
  2. To start the wizard, click Next.
  3. Select the check boxes for the managed systems that you want to load EMC NetWorker KM for PATROL on. Click Next.
  4. Select the check box for EMC NetWorker KM for PATROL (NSR_LOAD.kml).
  5. Click Finish.

    EMC NetWorker KM for PATROL will be loaded to the PATROL Central Console Server, and all connected selected managed systems. The EMC NetWorker container instance will be created. Any previous EMC NetWorker KM configuration will be upgraded and their instances will be created.

  6. Configure the KM.

Configuring the PATROL Agent to Preload the KM

If you want EMC NetWorker KM for PATROL to operate all the time, without a PATROL Console connection, you will have to add it to the PATROL Agent configuration variable /AgentSetup/preloadedKMs.

To configure the PATROL Agent to preload the KM:

  1. In the Console, right-click the EMC NetWorker icon > Configuration > Preloading.
  2. Click Add to add the KM files to the list of preloaded KMs.

Note: The same menu is used to remove the KM files from the preloaded KMs list

Unloading EMC NetWorker KM

This section describes the procedures for unloading (not uninstalling) the EMC NetWorker KM from the PATROL Agent, PATROL Console or PATROL Central Console. Read this section if you no longer want to use some parts of the KM; if you want to completely uninstall the KM, refer to the uninstall procedure.

When the KM is unloaded:

  • from a PATROL Agent: PATROL stops monitoring the EMC NetWorker application on that system when there is no connection to a PATROL Console with EMC NetWorker KM loaded.

  • from a PATROL Console: the PATROL Console stops displaying and monitoring the EMC NetWorker application on any PATROL Console connected system.

From the PATROL Agent

To unload the KM from the PATROL Agent:

  1. In the Console, right-click the EMC NetWorker icon and select KM Commands > Configuration > Preloading…
  2. Click Remove.
  3. Restart the PATROL Agent.
  4. Repeat these steps on every PATROL Agent system (managed node) where EMC NetWorker KM is to be unloaded.
Note: You can also use the utility wpconfig (on Microsoft Windows) or xpconfig to unload the KM. You will then have to remove NSR_LOAD.kml from the PATROL Agent configuration variable /AgentSetup/preloadedKMs.

The KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need to unload some parts of the KM from the PATROL Agent, set their instance limits to 0 (zero).

From the PATROL Console

Application classes are unloaded individually. This allows for a partial unloading of the KM to enable it to run as a reduced installation.

To unload EMC NetWorker KM completely or partially:

  1. Remove the unwanted application classes that starts with NSR_ in the list of loaded application classes as described below:

    With the PATROL Console for Unix:

    • From the PATROL Console main window, choose Attributes> Application Classes…
    • Select a EMC NetWorker KM application class to be removed and choose Edit > Delete .
    • Repeat for all classes to be removed.

    With the PATROL Console for MS Windows:

    • From the PATROL Console tree view, choose the KM tab and expand the folder Application Classes.
    • Right-click on a EMC NetWorker KM application class to be removed and choose Delete.
    • Repeat for all classes to be removed.
  2. Select File > Save Configuration to save the modified list of loaded application classes as the PATROL Console user preference.

  3. Repeat these steps on every PATROL Console system where EMC NetWorker KM is to be unloaded.

From the PATROL Central Console

A KM can be unloaded from particular managed systems or for all systems across the monitored environment. Application classes may be unloaded individually, or by selecting all classes at once. This allows for a partial unloading of the KM to enable it to run as a reduced installation on some or all of the managed systems.

To completely or partially unload EMC NetWorker KM for PATROL from some or all of the managed systems:

  1. Right-click the PATROL Main Map, and choose Unload Knowledge Modules…

  2. Select the managed systems where EMC NetWorker KM is to be unloaded, and click Next>.

  3. Select the application classes to be removed that starts with NSR_ for the appropriate managed systems, click Next> and Finish.

  4. Repeat the above steps for each PATROL Central Management Profile where the KM is to be unloaded.

Uninstalling EMC NetWorker KM

To uninstall EMC NetWorker KM:

  1. Go to BMC_ROOT/Uninstall
  2. Launch the uninstall.exe program (Windows) or the uninstall.sh script (UNIX).
  3. The welcome screen appears. Click Next to continue.

    Wizard — Welcome Step

  4. Specify the BMC Software Products folder.

    Uninstall Wizard — Specifying folder

  5. To uninstall the KM, select EMC NetWorker KM for PATROL.

    Uninstall Wizard — Selecting Products and Components Directory

  6. Click Start Uninstall to run the uninstall program.

    Uninstall Wizard — Reviewing Selected Products & Components and Start Uninstalling

  7. A page displays the list of products/components processed and the percentage of completion. Click Next to continue.

    Uninstall Wizard — Status

  8. A page displaying SUCCESS indicates that EMC NetWorker KM for PATROL is now uninstalled.

    Uninstall Wizard — Uninstall Results

Keywords:
storage networker km patrol