Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products

How to upgrade Networker server from 8.x to 9.1 for windows

Summary: How to upgrade Networker server from 8.x to 9.1 for windows

This article applies to   This article does not apply to 

Instructions

Prerequisites before upgrade:

1. Please download and install JRE 8 or above on NetWorker Server that is going to be upgraded to 9.1
2. The Windows OS to host NetWorker server 9.1 must be a 64bit Windows 2008 or Windows 2012 platform

Note: If the current NetWorker server is not on a 64bit Windows 2008/Windows 2012 platform, then it is required to migrated the NetWorker server to such a platform before proceed to upgrade to 9.1.

3. If current NetWorker Server is on 8.0.x version, please upgrade to 8.2.x first, then upgrade to 9.1.
Otherwise, NetWorker Server 8.1/8.2 can be directly upgraded to 9.1

Preparing the NetWorker server before upgrading to 9.1:

Before you update the NetWorker server, ensure that the media database and client file indexes are in a consistent state and that you have a backup of the databases.

To prepare the NetWorker server, perform these steps from a command prompt on the NetWorker server as root on UNIX or administrator on Windows.

1. Put the NetWorker databases in a consistent state:
nsrim -X
nsrck -m
nsrck -L6

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

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

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

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

5. Record the latest bootstrap save set ID (ssid) including the file number, the
record number, and the associated volume label.

For example:

mminfo -B
date time level ssid file record volume
10/11/11 16:29:40 full 4254377781 0 0 bootstrap_vol.001

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.

Upgrade Procedure for NetWorker Server 8.1/8.2 to 9.1:
In this scenario, we are upgrading NetWorker Server from 8.2.1 to 9.1 on a Windows 2008 R2 platform
1. Obtain an installation package of Networker 9.1.x for Windows 64-bit platform.

2. Extract the package to a local directory on the existing 9.0 Networker server Windows 64-bit host

3. Browse and find the NetWorker-9.1.x.exe

4. Right-click at the file NetWorker-9.1.x.exe and select 'Run as administrator'

kA5j00000008WoZCAU_1_0
5. Read the license term and agreements.
Check the box 'I agree to the license term and agreements' to proceed with the upgrade.

kA5j00000008WoZCAU_1_1
Click Next.

6. Click 'Configure the Windows Firewall' or 'Do not Configure the Windows Firewall'.

kA5j00000008WoZCAU_1_2
Click Next.

7. 'Server and client' should be automatically select and greyed out along with other options that previously installed on the 8.x Networker server. Check other options if required.
Note: 'Install Location' and 'Avamar Client Location' are also greyed out and they should match the ones on previous 8.x Networker server.

kA5j00000008WoZCAU_1_3
Click Next.

8. Click 'OK' if the Notice of License Server pop-up windows appears to proceed.

kA5j00000008WoZCAU_1_4

9. Check the 'Host Name' field is correct for 'Configure Networker Authentication Service' section.
The 'Apache Tomcat Port' field is greyed out and it should match the one on previous 8.x Networker server.

kA5j00000008WoZCAU_1_5
Click Next.

10. If JRE alert windows pops up for JRE update, either click 'OK' to continue the NetWorker 9.1 upgrade process or 'Cancel' to cancel the NetWorker 9.1 upgrade process and manually update JRE first.

kA5j00000008WoZCAU_1_6
In this scenario, click 'OK' to continue the NetWorker 9.1 upgrade process.

11. Create Keystore password
kA5j00000008WoZCAU_1_7
Click Next.

12. Create a NetWorker Authentication Service administrator account password.

kA5j00000008WoZCAU_1_8
Click Next.

13. Check and fill in the 'NMC Install Folder' field, 'Authentication Host' field and 'Authentication Port' field.
kA5j00000008WoZCAU_1_9
Click Next.

14. Check and fill in the 'Database Destination Folder' field, 'Client Service Port' field and 'Web Server Port' field
kA5j00000008WoZCAU_1_10
Click Next.

15. Choose to migrate NMC Database from 8.1/8.2 to new NMC Database format for 9.0/9.1
In this scenario, select "Migrate the Database Automatically"

kA5j00000008WoZCAU_1_11
Click Upgrade.

16. Upgrade process is started. Monitor the process to complete.
kA5j00000008WoZCAU_1_12

17. Check Launch NetWorker Management Console box. Click "Finish" to complete the upgrade.
kA5j00000008WoZCAU_1_13

18. Enter the NMC Server Configuration wizard
kA5j00000008WoZCAU_1_14
Click Next.

19. Review the settings in NMC Server service account
kA5j00000008WoZCAU_1_15
Click Next.

20. Define NMC Database Backup Server

kA5j00000008WoZCAU_1_16
Click "Finish" to complete the configuration

21. NMC console is launched
kA5j00000008WoZCAU_1_17
22.  Ready to launch NetWorker Administration
kA5j00000008WoZCAU_1_18

23. The "NetWorker Migration Succeeded" window pops up.
kA5j00000008WoZCAU_1_19

24. Click "Open Migration Log File" button to review the migration log
kA5j00000008WoZCAU_1_20
This log file can be printed and/or saved. Click OK to close the log.

25. Back to the "NetWorker Migration Succeeded" window
kA5j00000008WoZCAU_1_21
Click Close

26. The NetWorker Administration GUI is launched. Check the version is 9.1 and all configurations are maintained.
kA5j00000008WoZCAU_1_22

Additional Information

Issue that has encountered during the upgrade:

In this upgrade scenario, the upgrade process went through with no error up to step 17. Then NMC failed to launch and all NetWorker daemons (e.g.nsrexecd, nsrpsd, nsrd,etc) were not able to start up.

Only after renaming the nsrladb folder under <EMC NetWorker>\nsr\res and able to start up all NetWorker daemons and proceed with the NMC Database configuration.

Note: Renaming nsrladb might cause peer information on all clients. Only do that if you are getting stuck on step 17, and you cannot think of any other ways to work out the problems
Article Properties
Article Number: 000019546
Article Type: How To
Last Modified: 24 Sept 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.