Migrating and Upgrading

This section contains the following topics:
casp1042
  • For upgrade and migration scenarios,
    DX NetOps Spectrum
    automatically uses Legacy Landscape Handle type. All pre-10.2 landscape handles belong to Legacy Landscape Handle type.
  • However, migration is supported for Huge Landscape Handle type within 10.2, that is, if you have selected Huge Landscape handle type during a fresh 10.2 installation and are migrating 10.2 SSdbs from one server to another.
Migrate and Upgrade on Windows
You can migrate the existing
SpectroSERVER
database and Archive Manager database and other upgradeable components to a different system, and then upgrade
DX NetOps Spectrum
. This way, you can continue to manage your network with the existing
DX NetOps Spectrum
version during the installation process.
You cannot move a
DX NetOps Spectrum
installation from one system to another or from one directory to another. Instead, first, copy or move the
DX NetOps Spectrum
databases and then run the installation program to reinstall
DX NetOps Spectrum
over the relocated database.
The C:\Program Files\CA directory is automatically created during a first-time installation of
DX NetOps Spectrum
.
DX NetOps Spectrum
components that are also common to other CA products are intentionally installed into this directory. This directory is automatically updated as needed during a
DX NetOps Spectrum
upgrade. Do not remove files from this directory.
Follow these steps:
  1. Create a user model from the OneClick Users tab. Name it the same name as the owner of the directory where you are installing the new
    DX NetOps Spectrum
    version.
  2. Preserve the existing SpectroSERVER database (see the topic 'Preserve the existing SpectroSERVER database' on How to Perform In-Place Upgrades page).
    When backing up the
    SpectroSERVER
    database for migration, include both the modeling catalog and the models. A catalog-only or models-only migration is not supported.
  3. Preserve the
    DX NetOps Spectrum
    Events and Statistics database (see the topic 'Preserve the
    DX NetOps Spectrum
    Events and Statistics database' on How to Perform In-Place Upgrades page).
  4. Extract the dbsavefile.SSdb file from the dbsavefile.SSdb.gz file in the SS-DB-Backup directory.
  5. Copy the saved SSdb file to the dbsavefile.SSdb file. If the SSdb file had backup compression that is enabled, uncompress the SSdb file by running gzip -d <
    database_file.gz
    > and then perform the copy. For example, cp db_20080105_1153.SSdb dbsavefile.SSdb.
    The dbsavefile.SSdb file must not be compressed. If dbsavefile.SSdb is compressed, the database is not migrated during installation.
  6. Create an installation directory, <
    $SPECROOT
    >, for the new version of
    DX NetOps Spectrum
    .
    Ensure that the folder in which the installation kit is copied and extracted does not have any spaces.
    DX NetOps Spectrum
    installation fails if the installer (.exe) file is in a location with spaces in its absolute/full path.
    You cannot install
    DX NetOps Spectrum
    into a directory that contains a space anywhere in the path. Spaces within the directory path cause the installation to fail.
  7. Create an SS subdirectory in
    $SPECROOT
    .
  8. Copy the custom directory from the earlier
    DX NetOps Spectrum
    installation directory to the
    $SPECROOT
    directory of the upgraded
    DX NetOps Spectrum
    installation.
  9. Copy or FTP (in binary mode) the dbsavefile.SSdb file to the
    $SPECROOT
    \SS subdirectory.
    Migrating an existing
    SpectroSERVER
    database migrates all of the existing models into the new
    SpectroSERVER
    database when you install a new version of
    DX NetOps Spectrum
    . This migration includes the models containing topology views including icon placement, groupings, and annotations.
  10. Create a DDM subdirectory in the SS subdirectory.
  11. Copy or FTP (in binary mode) dbsavefile.mbi or dbsavefile.tgz to the new
    $SPECROOT
    \SS\DDM directory.
    The directory structure now resembles the following structure:
    MBI Support in DDM
  12. (Optional) To migrate the OneClick web server, copy the contents of the <
    $SPECROOT
    >\custom directories from the computer with the old OneClick web server installation. Paste these contents into the <
    $SPECROOT
    >\custom directories on the computer with the new OneClick web server installation.
Do
not
copy the <
$SPECROOT
>/custom/common/config/custom-jnlp-config.xml file to another computer when you migrate and upgrade
DX NetOps Spectrum
. This file can contain memory settings that are not compatible with the computer where you are copying the custom directories.
The mapping of custom background images (<
$SPECROOT
>\custom\images\background) to topology views is maintained in the
SpectroSERVER
database. For more information about the <
$SPECROOT
>\custom directories, see the .
DX NetOps Spectrum
is migrated and upgraded.
Migrate and Upgrade on Linux
You can migrate existing
DX NetOps Spectrum
databases and other upgradeable components to a different system, and then upgrade
DX NetOps Spectrum
. This way, you can continue to manage your network with the existing
DX NetOps Spectrum
version during the installation process.
Prerequisite Packages
The following 64 bit packages must be installed before upgrading
DX NetOps Spectrum
.
yum install motif
yum install motif-devel
yum install ksh
On the RHEL 8 machines, the following package must be installed while upgrading
DX NetOps Spectrum
with Reporting Manager.
yum install libnscl
Do not move a
DX NetOps Spectrum
installation from one system to another or from one directory to another. Instead, first, copy or move the
DX NetOps Spectrum
database and then run the installation program to reinstall
DX NetOps Spectrum
over the relocated database.
The /opt/CA directory is automatically created during a first-time installation of
DX NetOps Spectrum
.
DX NetOps Spectrum
components that are also common to other CA products are intentionally installed into this directory. This directory is automatically updated as needed during a
DX NetOps Spectrum
upgrade. Do not remove files from this directory.
Follow these steps:
  1. Create a user model from the OneClick Users tab. Name it the same name as the owner of the directory where you are installing the new
    DX NetOps Spectrum
    version.
  2. Preserve the existing SpectroSERVER database (see the topic 'Preserve the existing SpectroSERVER database' on How to Perform In-Place Upgrades page).
    When backing up the
    SpectroSERVER
    database for migration, include both the modeling catalog and the models. A catalog-only or models-only migration is not supported.
  3. Preserve the
    DX NetOps Spectrum
    Events and Statistics database (see the topic 'Preserve the
    DX NetOps Spectrum
    Events and Statistics database' on How to Perform In-Place Upgrades page).
  4. Extract the dbsavefile.SSdb file from the dbsavefile.SSdb.gz file in the SS-DB-Backup directory.
  5. Copy the saved SSdb file to the dbsavefile.SSdb file. If SSdb had backup compression that is enabled, first uncompress the SSdb by running gzip -d <
    database_file.gz
    > and then perform the copy. For example, cp db_20080105_1153.SSdb dbsavefile.SSdb.
    The dbsavefile.SSdb file must not be compressed. If dbsavefile.SSdb is compressed, the database is not migrated during installation.
  6. Create an installation directory, <
    $SPECROOT
    >, for the new version of
    DX NetOps Spectrum
    , with subdirectories for the two database files as follows:
    mkdir -p <$SPECROOT>/SS/DDM
    Do not use /opt/SPECTRUM as the installation directory name. This location is reserved for a directory that is automatically created during installation. Also, ensure that the directory owner name is the same name as the owner of the directory where you are installing the new
    DX NetOps Spectrum
    version.
    You cannot install
    DX NetOps Spectrum
    into a directory that contains a space anywhere in the path. Spaces within the directory path cause the installation to fail.
  7. Copy or FTP (in binary mode) the dbsavefile.SSdb file to the <
    $SPECROOT
    >/SS directory.
    Migrating an existing
    SpectroSERVER
    database migrates all the existing models into the new
    SpectroSERVER
    database when you install a new version of
    DX NetOps Spectrum
    . This migration includes the models containing topology views including icon placement, groupings, and annotations.
  8. Copy or FTP (in binary mode) the dbsavefile.mbi or dbsavefile.tgz file to the <
    $SPECROOT
    >/SS/DDM directory.
    The directory structure now resembles the following structure:
    MBI Support in DDM
  9. (Optional) To migrate the OneClick web server, copy the contents of the <
    $SPECROOT
    >/custom directories from the computer with the old OneClick web server installation. Paste these contents into the <
    $SPECROOT
    >/custom directories on the computer with the new OneClick web server installation.
    Do
    not
    copy the <
    $SPECROOT
    >/custom/common/config/custom-jnlp-config.xml file to another computer when you migrate and upgrade
    DX NetOps Spectrum
    . This file can contain memory settings that are not compatible with the computer where you are copying the custom directories.
    The mapping of custom background images (<
    $SPECROOT
    >/custom/images/background) to topology views is maintained in the
    SpectroSERVER
    database. For more information about the <
    $SPECROOT
    >/custom directories, see the .
DX NetOps Spectrum
is migrated and upgraded.
Post Migration Tasks
It is recommended that you perform a DDM database table conversion as a post-migration task. However, ignore this task if the DDM database is already converted to InnoDB.
Archive Manager Table Conversion
While performing the post-migration task, the Archive Manager stops for some time because of the time taken by the script to convert the tables. This conversion time depends on the size of the tables. To improve the performance of Archive Manager it is recommended you convert the Archive Manager database tables MySQL engine from MyISAM to InnoDB. To enhance the performance of event retrieval, the event table is partitioned.
Prerequisite:
Ensure that there is a free disk space which is three times greater than the event table size.
Procedure:
  1. Open any bash- shell and navigate to the
    $specroot/SS/DDM/scripts
    location.
    • Before running the script, it is recommended to take a back-up of the Archive Manager database as a precaution against any potential loss of data.
    • If your DDM database contains less than 10 days of data, refer to the KB000115500 article for instructions
      to perform a successful data conversion.
  2. To convert the DDM database tables engine from MyISAM to InnoDB, run the following script:
    convert_current_myisam_to_innodb.pl
  3. After the conversion of tables, you are prompted to start the Archive Manager. Enter 'Y' to start the Archive Manager.
Support for Migrating DDM .mbi File (InnoDB)
10.4.1 provides support for migrating the DDM .mbi file from a previous release to this release. With the availability of this support, we recommend that you use InnoDB for DDM and use ddm_load.pl and ddm_save.pl for backup and restore. The ddm_load.pl and ddm_save.pl (<SPECROOT>\SS\DDM) leverage mysqlbackup.exe, which is more efficient to take backups and restore.
Considerations
  • Migration of DDM .mbi file is not supported from a Windows computer to a Linux computer.
  • The ddm_load, ddm_save, and ddm_backup binaries coming with the previous releases have been deprecated in 10.4.1. You can now use ddm_load.pl instead of ddm_load and ddm_save.pl instead of ddm_save and ddm_backup.