Paradyne 6800 - Manual (Page 297)

COMSPHERE 6800 Series Network Management System
7-26 January 1997 6800-A2-GN22-30
The following databases will not be migrated:
•
Reports/Trouble Tickets customized with 4GL or SQL
•
The active alerts database will not be migrated as the Release 4.2 NMS generates
up-to-date active alert data at start-up
Cleaning Up the Database
To ensure that those databases not migrated are rebuilt, the customer should back up any
customized Trouble Tickets and Trouble/Inventory Reports to a removable medium.
Backing Up the Database
The NMS database must be backed up to a cartridge tape prior to migrating it from
Release 3.0/3.1 to Release 4.2:
1. From the 6800 NMS Main Menu, select Backup system database and follow the steps
for performing a System Database Backup as indicated in Chapter 4 of the COMSPHERE
6800 Series Network Management System User’s/System Administrator’s Guide.
2. When the backup is complete and the 6800 NMS Main Menu is displayed, select Restore
system database and follow the steps for performing a System Database Restore as
specified in Chapter 4 of the COMSPHERE 6800 Series Network Management System
User’s/System Administrator’s Guide. This action will ensure that the tape produced by
the backup in Step 1 is readable as the process of migration will destroy the existing
3.0/3.1 database on disk.
3. Do not proceed with the Migration until you have a valid, readable Backup.
Migrating the Database
NOTE
The NMS application must not be running.
To migrate the NMS database, perform the following steps:
1. At the Console Login: prompt,
TYPE: root
PRESS: Enter
2. At the Password: prompt,
TYPE: root password
PRESS: Enter