Dear all,
in case you are running a CA Spectrum R9.2 DSS installation (covering multiple Landscapes) with Fault-Tolerant Paring the upgrade (or migration) to CA Spectrum R9.3 will cover a very important new feature to allow this upgrade without downtime. In any case please have a look to the CA Spectrum R9.3 Installation Guide which covers extended documentation for the upgrade.
The very important detail to allow a comfortable migration is:
CA Spectrum R9.3 can read "Event-" and "Alarm-data" from a CA Spectrum R9.2 secondary-SpectroSERVER.
This allows you to do the migration as follows for a DSS FT-paired Spectrum installation:
- stop down the primary and watch secondary takes over
- watch the OC-server will followup to switched/yellow status for the Landscape
- now do the migration for the primary_SpectroSERVER to R9.3 (+ H01 i.e.)
- when done start the processd-service and start the ArchiveManager on the primary_new_R9.3_SpectroSERVER and find all "cached" events from Secondary will be retrieved and saved.
(you can still continue your logon to a OC-server running at R9.2.3* at this time)
- now start the primary_new_R9.3_SpectroSERVER (and the new R9.3_OC-Server) and find all alarms from Secondary_R9.2_SpectroSERVER (which are raised during its runtime) are synced into Primary_SpectroSERVER database..
- stop down the Secondary_SpectroSERVERs - and make use the new R9.3_Oneclick-server for new logon.
(do the migration for the Secondary_SpectroSERVER / stop down the old_R9.2_Oneclick-server)
(find few more technical details in the Installation Guide - special point is to update ./SS/.vnmrc on the Secondary_SS to disable alarm-sync).
Kind regards, Joerg
P.S: In the past this no_downtime_migration was implemented via secondary_SpectroSERVER migration first.