DX NetOps

Hello everyone,

I am doing a document to plan the next migration of our Spectrum. Actually we are working in 9.3 version, with 4 Spectro Servers in distributed and fault tolerant environment. An One Click server with Report Manager and one CABI server. This is our infrastructure, all of them virtual machines with RedHat 6

We want to use the migration for make an upgrade of the RedHat.

I am going to advise for this project, to mount 7 new servers.

--> 4 SpectroServers with 4 quad core processors,16Gb Ram, 100Gb HDD, and RedHat 7 (64bit)

--> 1 OneClick with 4 quad core processors,16Gb Ram, 80Gb HDD, and RedHat 7(64bit)

--> 1 OneClick+RpMngr with 4 quad core processors,16Gb Ram, 500Gb HDD, and RedHat 7 (64bit)

--> 1 CABI with 4 quad core processors,16Gb Ram, 80Gb HDD and Windows Server 2012 R2(64bit)

My purpose is mount all infrastructure in parallel with the Spectrum in production, and when all is working shut down the Spectrum 9.3 and switch on the Spectrum 10. I have done several migrations like this but I have never migrated the Report Manager and CABI. Can I migrate the ReportManager from the 9.3 version to 10? How can I move the Report Database to another server?. When I install the CABI in the new server how can I bring the configuration from the old server?, especially I am interested in the scheduled reports.

Do you have any experience to the migration the Spectrum for the 10 version? Do you have any suggestion?

Appreciate any idea, recommendation, or advise about this plan.

Thank you!

Susana

Hi Susana,

You can upgrade from CA Spectrum 9.3 to 10.0 and then to 10.1.

Yes, you can migrate the reporting database from CA Spectrum 9.3 to 10.0. See the link below:

https://docops.ca.com/display/CASP10/Install+OneClick+with+Report+Manager

Migrate Report Data from a Previous Report Manager Installation

During the installation of OneClick with Spectrum Report Manager, you are prompted to migrate report data from a remote (source) reporting database to the new CA Spectrum reporting database. The prompt applies to upgrade situations where data from a previous installation is preserved. This migration is optional. Therefore, you can either accept or decline the migration.

If you prefer to migrate data, enable access to the source report database from the remote server as described in this section.

Follow these steps:

1. Launch a MySQL client session on the source server with root account credentials. For example:

    

   oscmdline> ./mysql -uroot -p<localrootpassword>;

2. Let data be extracted from the source database by a remote account. You can provide temporary access to a remote root account.
   For example, if the CA Spectrum target OneClick Linux server is named target-linux.ca.com, issue the following command at the MySQL command line:

    

   mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'target-linux.ca.com' IDENTIFIED BY '<remoterootpassword>';

   Note: Provide the fully qualified host name.

3. Verify that this new permission is available to all existing sessions by issuing the following command:

    

   mysql> FLUSH PRIVILEGES;

4. (Windows Only) Verify that Windows Firewall settings on the source server allow remote connections to MySQL.
   
   1. Click Start, Control Panel, and then Windows Firewall.
   2. Under the Exceptions tab, click Add Port and configure values as follows:
      • Enter MySQL for the name.
      • Enter 3306 for the Port Number.
      • Select TCP.
   3. (Optional) Click Change to restrict the scope of access to MySQL.
   4. Specify the location of your CA Spectrum server.
   5. Configure the option to allow remote connections to MySQL only from the migration destination server. For more information, see Windows Help and Support.
   Access to the report database on the Windows server is enabled.

Prepare for the Migration

Before you start migrating the data, verify the connection between the source and destination server databases. Verify that the data you plan to migrate is updated.Follow these steps:

1. Verify the database connection to the remote host containing data that you plan to migrate. Issue the following command on the CA Spectrum server:

   telnet <remote-srm-host> 3306

   The following message indicates that the permissions have been set properly:

   Escape character is '^]'. 74.1.11-nt î☺  t#J0Mu'] ,☻  #2p^giYa]0t{▬  ☺♦#08S01Bad handshakeConnection closed by foreign host.

   The following message indicates that the permissions have not been set correctly:

   Q  ♦#HY000Host 'user.com' is not allowed to connect to this MySQL server Connection closed by foreign host.

   If you are unable to connect to the MySQL server, verify that your MySQL permissions are configured correctly on your previous SRM MySQL database. Verify that the privileges are flushed before you reattempt to connect.
2. Stop all reporting processes on the remote, source server by removing all entries from the Spectrum Report Manager Admin Tools, CA Spectrum Status option.
3. Wait for 5 minutes to verify that any outstanding data changes are committed to the report database.
   The root database account on the remote destination server can extract report data on the source server.
   The connection is verified.

Yes, you can migrate the CABI 3.3 data to the new CABI 4.1 SP3. See the link below:

https://docops.ca.com/display/CASP10/Post+Installation+Configuration+for+CABI

• Deploy Spectrum Content
• Configure the Database Driver
• Customize CABI Setup for CA Spectrum

Perform the required configuration to deploy the Spectrum Customization on CABI machine.

Note: This utility restarts the CABI’s Server Intelligence Agent.

Follow these steps:

1. Copy the PostInstall folder from <CABI VCD>\utilities folder to the local disk.
2. (On Windows) Run the following command:
   PostInstall.bat
   Example:
   C:\spectrum_utilities\PostInstall>PostInstall.bat
   Microsoft (R) Windows Script Host Version 5.8
   Copyright (C) Microsoft Corporation. All rights reserved.
   Do you want to migrate data from CABI 3.x? (y/n)
   y
   Do you want to install CA Sample Templates? (y/n)
   n
   Enter CABI 4.1 Administrator password and press Enter key
   ******
   CABI 4.1 Post installation is completed with errors
3. (On Unix or Linux) Run the following command as the root user.
   postinstall.sh < folder where CABI is installed>.
   Example: postinstall.sh /opt/cabi41
   
   Log files for this utility can be found in C:\Program Files (x86)\CA\SC\CommonReporting4\SAP BusinessObjects Enterprise XI 4.0\logging directory (by default in Windows platform).

After installing and verifying the CABI, you must Deploy Spectrum Content, Configure Database Driver and Customize CABI Setup for Spectrum.

Thanks,

Silvio

Hi Susana,

You can now upgrade from 9.3.0 to 10.1 directly. See the post below:

Spectrum 10.1 - Direct Upgrades from 9.3

Thanks,

Silvio

Hi,

I have a question to the migration process. When you say you mount the new servers, they surely have a different Ip Address and Hostname so that you can access the old and new severs at the same time, right?

How did you do the Migration then? I believe that the migration and upgrade of the SSDB and DDM DB will only work when the new servers have the same hostname and/or IP address as the SSDB and DDM DB. This must match.

I need to do a migration and upgrade myself and I can only think of one way to solve this: Change the network and hostname configuration before you start with the migration and upgrade process so that the new servers have old IP and hostnames. So the old servers need to be stopped at that point.

What do you think?

I think that I also have to raise a ticket with Support as the exact procedure is unclear to me.

Thanks,

Achim

Hi,

One of the advantages with Migration installation is you could continue to manage your network with the existing CA Spectrum version during the installation process.

It is not necessary that the hostnames and/or IP Addresses should be same for the old and the new servers.

If you have Spectrum integrated with other products, you would need to redo the integration on the New Server.

The below communities link explains Scenarios for upgrading to CA Spectrum 10.2:

https://communities.ca.com/docs/DOC-231172056

For further information on Migration Installation, you could refer the below:

To Upgrade to Spectrum 10.1.x:

https://docops.ca.com/ca-spectrum/10-1-and-10-1-1/en/installing-and-upgrading/upgrading-ca-spectrum/migrating-and-upgrading-ca-spectrum

To upgrade to Spectrum 10.2:

https://docops.ca.com/ca-spectrum/10-2/en/installing-and-upgrading/upgrading-ca-spectrum/migrating-and-upgrading-ca-spectrum

Thank you,

Best Regards,

Hamza Sirajuddin

Hi,

thanks for the quick reply. That document is great!

So what I will do is this:

• Leave existing Spectrum installation as it is (Servers keep running)
• Do the Migration and Upgrade on the new servers (they have different ip adresses & hostnames but that's ok)
• Stop SpectroServers and OneClick Servers on old servers
• Swap ip adresses & hostnames (new servers will get ip address & hostnames of old environment)
• Start SpectroServer and OneClick Servers on new servers

All things considered, this should work, right?

Thanks,

Achim

Hi,

No problem. Spectrum heavily relies on hostname and name resolution, after migration installation, if you would like to change the hostname, you need to follow the below document:

https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1233986.html?intcmp=searchresultclick&resultnum=2

Thank you,

Best Regards,

Hamza Sirajuddin

Ok, this is much work. Therefore I am tending to switch ip & hostname configuration before the migration.

So this leads to have the steps in this new order:

• Stop SpectroServers and OneClick Servers on old servers
• Swap ip adresses & hostnames (new servers will get ip address & hostnames of old environment)
• Do the Migration and Upgrade on the new servers

This has 1 huge drawback and that is downtime, but we could do the migration step by step: Primaries first, Secondaries next

I will try this approach in the test environment. But in this case I have never specifically seen if a Secondary SpectroServer that is still on 9.4.4 switches back to a Primary SpectroServer on 10.2 that comes online after the migration.

Thanks,

Achim

Hi Achim,

I am afraid the above method would create more issues for you.

Changing the hostname of the Spectrum Server without changing the entries in the files .hostrc, .locrc, ... could lead to communication issues in the existing Production Servers.

In a fault-tolerant environment, the SpectroSERVERs should be at the same level, else failover / switch-back will not happen.

For an upgrade process, the procedure recommended is to first upgrade the OneClick Web Servers, after that upgrade the primary SpectroSERVERs, and finally upgrade the secondary SpectroSERVERs. (You could refer: https://docops.ca.com/ca-spectrum/10-2/en/installing-and-upgrading/upgrading-ca-spectrum/upgrade-best-practices-fault-tolerant-deployments )

Based on this, perhaps you could migrate the OneClick Server first followed by migrating the Primary SpectroSERVER

I am assuming you are planning to migrate to Spectrum 10.2

My suggestion would be to perform the Migration installation of the Primary SpectroSERVER, establish fault-tolerant server following the below procedure:

https://docops.ca.com/ca-spectrum/10-2/en/administrating/distributed-spectroserver-administration/establish-fault-tolerance#EstablishFaultTolerance-ChangetheHostNamesofthePrimaryandSecondarySpectroSERVERs 

Do not start the Primary SpectroSERVER yet, please open a case with us for PTF_10.2.003, for more information, please refer:

https://communities.ca.com/message/241949782?et=watches.email.thread

Lastly, when all the Servers are up and running fine, you could change the hostnames of the new servers to that of the old servers following the below link:

https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1233986.html?intcmp=searchresultclick&resultnum=2

Hope the above helps,

Thank you,

Best Regards,
Hamza Sirajuddin

Hi,

thanks for all the information.

I will start to migrate the servers of our test environment now. When I have completed this I will change the IP & Hostnames of the (new) servers.

In the meantime, I have opened a Support ticket to request this Hot Fix, but I think that I won't need it, because I actually doing a migration.

Thanks,

Achim

Hi Achim,

The above looks good to me. Yes, you are correct, you may not need the PTF_10.2.003 as Spectrum Migration is been performed

Thank you,

Best Regards,

Hamza Sirajuddin

I was not able to get far:

Spectrum 10.2 Install Dialog Problem 

Hi Achim,

Have provided a suggestion in the new thread below, hope it helps:

https://communities.ca.com/thread/241771023

Thank you,

Best Regards,

Hamza Sirajuddin

I was able to do the migration and I was also changing the hostname and IP addresses afterwards.

I get the Primary SS running, but not the Secondary SS.

On both servers I see the following error when running $SPECROOT/bin/VBNS/nsutils:

list: caught org.omg.CORBA.OBJECT_NOT_EXIST:   vmcid: 0x0  minor code: 0  completed: No

There is something wrong with the nameserv, but I cant find out what is going on.

Thanks,
Achim