Upgrading to NerveCenterTM 3.8 - Upgrading from NerveCenter 3.6 or 3.7 - Backing Up Your NerveCenter Data and Files -
Exporting Your Data      Removing NerveCenter 3.6 or 3.7

Backing Up Your NerveCenter Data and Files

Before you upgrade, you should back up, or simply move, your data and any files that you might have customized or that you want to preserve for any reason.

 
  To back up your data:

Now you remove NerveCenter. See Removing NerveCenter 3.6 or 3.7.

The following table lists the files that you should consider backing up.

Files to Back Up Before Upgrading

File Name Default Location Description

*.ncdb and *.node

installation_path/db

The files that made up the NerveCenter database on UNIX.

Microsoft Access database (*.mdb) or Microsoft SQL Server database

installation_path/db

On Windows, the database is either a Microsoft Access database or a Microsoft SQL Server database.

*.asc, *.idb files

installation_path/db

installation_path/bin

Any serialized database files or database installation preference files.

*.mod, *.txt files

installation_path/model (Windows)

installation_path/models (UNIX)

The files that NerveCenter generates when you export a model.

*.mib, mibcomp.txt, ASN.1 files

installation_path/mib (Windows)

installation_path/mibs (UNIX)

The NerveCenter MIB and any files used to compile additional MIB definitions into the NerveCenter MIB.

Any text file you created that contains parenting information (pc.dat, for example)

Not applicable

If you have used the downstream alarm suppression models, you may have created a text file that lists the nodes in your network and their parents.

ovpa.lrf and any other network management platform files you might have customized

installation_path/ovpa (UNIX)

HP_OV_directory/lrf (Windows)

platform_directory

If NerveCenter is integrated with a network management platform, you may have customized some files (such as the LRF file used with HP OpenView).



Exporting Your Data Removing NerveCenter 3.6 or 3.7
29 July 2003