To migrate Release 22.9 or later analytics servers to an NSP cluster

Purpose

The following steps describe how to migrate from Release 22.9 or later analytics servers to containerized entities in an NSP deployment.

Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses.

Note: Each running NSP analytics server and each running NSP auxiliary database in the NSP system must be at the same release.

Note: After an analytics server migration:

  • Scheduled report creation continues, but uses the new report versions, which may differ from the former versions.

  • Saved reports remain available, but lack any new features of the upgraded report versions; it is recommended that you recreate and save the reports.

  • If a report changes significantly between releases, the report may no longer function. See the NSP Release Notice for limitations regarding specific reports.

Note: You require root and nsp user privileges on each analytics server station.

Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands:

  • # —root user

  • bash$ —nsp user

Steps
Uninstall all but one analytics server
 
1 

On all but one analytics server stations in the data center, perform the analytics server uninstallation procedure in the NSP Installation and Upgrade Guide for the installed release.

Stop remaining analytics server
 
2 

Log in as the root user on the remaining analytics server station.

3 

Open a console window.

4 

Enter the following:

bash$ /opt/nsp/analytics/bin/AnalyticsAdmin.sh stop ↵

The following and other messages are displayed:

Stopping Analytics Application

When the analytics server is completely stopped, the following is displayed:

Analytics Application is not running

Note: You must not proceed to the next step until the analytics server is completely stopped.

Back up analytics data
 
5 

Transfer the following file from the NSP deployer host to the /opt/nsp/ directory on the remaining analytics server station:

NSP-CN-DEP-release-ID/NSP-CN-release-ID/tools/analytics/analyticsBackupForMigration.sh

Note: You must transfer and use the new script version, and not any existing version on the analytics server station.

6 

Enter the following on the remaining analytics server station:

# cd /opt/nsp ↵

7 

Enter the following:

# chown nsp:nsp analyticsBackupForMigration.sh ↵

8 

Enter the following:

# chmod +x analyticsBackupForMigration.sh ↵

9 

Enter the following to switch to the nsp user:

#  su - nsp ↵

10 

Enter the following:

bash$ /opt/nsp/analyticsBackupForMigration.sh ↵

11 

Enter the following:

bash$ tar -tzf /opt/nsp/analyticsBackup.tar.gz ↵

The backed-up files are listed.

12 

Verify that the output matches the following; if any file is not present, contact support:

  • opt/nsp/.jrsks

  • opt/nsp/.jrsksp

  • opt/nsp/analytics/config/install.config

  • opt/nsp/analytics/backup/analytics_backup_version_timestamp.zip

    where

    version is the current analytics software version

    timestamp is the current timestamp

13 

Close the open console windows.

Transfer backup file to NSP cluster
 
14 

Transfer the analyticsBackup.tar.gz file to the following directory on the NSP cluster host:

/opt/nsp/NSP-CN-release-ID

15 

Log in as the root user on the NSP cluster host.

16 

Open a console window.

17 

Enter the following to copy the analytics backup tar file to the Analytics pod:

# kubectl cp /opt/nsp/NSP-CN-release-ID/analyticsBackup.tar.gz -n namespace analytics-server-0:/opt/nsp/analytics-server/analyticsBackup.tar.gz ↵

where namespace is the Kubernetes namespace of the analytics-server-0 pod

18 

Close the open console windows.

Perform data migration
 
19 

Sign in to the NSP as an administrator.

20 

Open Data Collection and Analysis Management, Analytics Server Management.

The Status reads as follows:

Migration needed

21 

Click Migrate.

A dialog box appears.

22 

Confirm the action.

The analytics data migration to the NSP cluster begins, and the Status changes to:

Migration in progress.

When the migration is complete, the Status changes to:

Ready for reporting

23 

Verify that the Analytics reporting is operating as expected.

End of steps