We have planned to migrate spectrum 220.127.116.11 from windows machine to Linux machine.
please let me know the procedure to be followed. All components are installed in single server only.
Here are the steps for Migration and upgrade: please refer CA Spectrum installation guide for more details:
Prerequisites steps for Spectrum Installation
Ensure that you log in as Administrator or as a user with administrator privileges
User Account Control (UAC)
Verify that User Account Control (UAC) is turned off. UAC is a Windows security component that prompts you for permission when a task requires administrative rights.
Fixed IP Address on Windows
Ensure that the system on which you want to install CA Spectrum has a fixed IP address.
Set Display Properties for Microsoft Windows Server 2008
Select True Color (32-bit) from the Color quality drop-down menu on the Monitor tab. On the Screen resolution bar, slide to the minimum, 1024 by 768 pixels, and click OK.
If the user auditing feature is enabled on Windows, every action is audited, resulting in many entries in the Windows Event Log. We recommend that you disable the Windows user auditing feature because it retards CA Spectrum system performance.
Convert the File System to NTFS
Upgrading CA Spectrum
Pre-Upgrade and Post-Upgrade Tasks
Stop all running applications other than CA Spectrum Stop the following CA Spectrum applications: Shut down all OneClick clients by logging off all users from OneClick in the Client Details web page in the OneClick home page. Stop the SpectroSERVER and the Archive Manager by clicking Stop SpectroSERVER in the CA Spectrum Control Panel and then close the CA Spectrum Control Panel. Stop all VnmSh connections. ( See Command Line Interface User Guide) Close all Bash shells. Do not install third-party software that uses MySQL because the results can be unpredictable.
Upgrading from Earlier Versions
To upgrade from an earlier version, follow this process before you install this release: For SPECTRUM 8.0, upgrade to SPECTRUM 8.1. For other versions earlier than 8.1, upgrade to SPECTRUM 8.1.
Preserve Customized Support Files
Some custom CA Spectrum support files can be overwritten when installing a new version of CA Spectrum. These support files include AlertMap, EventDisp, Event Format, Probable Cause, or GIB files.
How to Perform In-Place Upgrades
Complete all preupgrade tasks Preserve your existing SpectroSERVER database Preserve the CA Spectrum events and statistics database Install CA Spectrum
Preserve the Existing SpectroSERVER Database
Ensure that the SpectroSERVER is running and open the CA Spectrum Control Panel. Make a copy of your current SpectroSERVER database by clicking Save Database in the CA Spectrum Control Panel.The Online Database Backup dialog appears. Verify that the option, Use Backup Compression, is selected. Accept the default or enter a directory path in the Backup Directory field. Windows—C:/win32app/SPECTRUM/SS-DB-Backup Accept the default of 20 for the Minimum Required Disk Space or enter an appropriate value. Select Save to save all changes Click Begin Backup Now.
Preserve the CA Spectrum Events and Statistics Database
Stop the SpectroSERVER and the Archive Manager by clicking Stop SpectroSERVER in the CA Spectrum Control Panel. Execute cd <$SPECROOT>\SS\DDM in the command prompt, where <$SPECROOT> is the directory where CA Spectrum was installed. Enter the following command: ddm_save dbsavefile (ddm_save dbsavefile) Move the dbsavefile.tgz to an area other than the CA Spectrum installation directory. Stop the following CA Spectrum applications: Shut down all OneClick clients by logging off all users from OneClick in the Client Details web page in the OneClick home page. Stop all VnmSh connections. Close all Bash shells
Migrate and Upgrade
Delete all remote landscapes, if any exist, from the existing database. 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 CA Spectrum version. Preserve the existing SpectroSERVER database (Important! 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.) Preserve the CA Spectrum Events and Statistics database. Extract the dbsavefile.SSdb file from the dbsavefile.SSdb.gz file in the SS-DB-Backup directory. Copy the saved SSdb file to the dbsavefile.SSdb file. If the SSdb file had backup compression 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. (Important! The dbsavefile.SSdb file must not be compressed. If dbsavefile.SSdb is compressed, the database is not migrated during installation.) Create an installation directory, <$SPECROOT>, for the new version of CA Spectrum. (Important! 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 CA Spectrum version.) You cannot install CA Spectrum into a directory that contains a space in the name. Create an SS subdirectory in <$SPECROOT>. Copy the custom directory from the earlier CA Spectrum installation directory to the < $SPECROOT> directory of the upgraded CA Spectrum installation. Copy or FTP (in binary mode) the dbsavefile.SSdb file to the <$SPECROOT>\SS subdirectory. (Note: Migrating an existing SpectroSERVER database migrates all of the existing models into the new SpectroSERVER database when you install a new version of CA Spectrum. This migration includes the models containing topology views including icon placement, groupings, and annotations.) Create a DDM subdirectory in the SS subdirectory.
Copy or FTP (in binary mode) dbsavefile.tgz to the new <$SPECROOT>\SS\DDM directory. Install CA Spectrum. (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. Important! We recommend that you do not copy the <$SPECROOT>/custom/common/config/custom-jnlp-config.xml file to another computer when you migrate and upgrade CA Spectrum. This file could contain memory settings that are not compatible with the computer to which you are copying the custom directories. Note: 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 OneClick Customization Guide. CA Spectrum is migrated and upgraded.
OneClick Web Server Upgrades
All OneClick clients must be shut down before upgrading the OneClick web server because Java Web Start applications cache application jar files on the client. These jar files are automatically updated when you restart the application. You can shut down all OneClick clients by selecting Client Details and clicking Log Off Clients.
If you migrating from one OS to another but not upgrading the version of Spectrum, use the following:
1. Install 18.104.22.168 on the new Linux system
2. Install any post 22.214.171.124 debug or PTF patches on the new Linux machine that you had installed on the old Windows machine
Basically you want to duplicate the same Spectrum version and patch install on the new Linux machine as you have on the old Windows machine.
3. Create a SpectroSERVER database save on the old Windows machine. Copy the SpectroSERVER database save file to the new Linux machine and load.
4. If you want to migrate the DDM database, create a DDM database save on the old Windows machine. Copy the DDM database save file to the new Linux machine and load.
5. Copy all custom event files in from the $SPECROOT/custom/Events directory from the old Windows machine to the $SPECROOT/custom/Events directory on the new Linux Machine.
6. Copy all OneClick customizations like custom menus, columns, tables etc from the $SPECROOT/custom/console/config and $SPECROOT/custom/common/config directories on the old Windows machine to the $SPECROOT/custom/console/config and $SPECROOT/custom/common/config directories on the new Linux machine.
I do not recommend copying over configuration files for integrations like eHealth, Service Desk, SSO etc. These should be configured from scratch on the new Linux machine.
7. If using AlarmNotifier and you have customized the AlarmNotifier scripts, copy these scripts from the old Windows machine to the new Linux machine.
Retrieving data ...