How to swap a primary and secondary SpectroSERVER

Products

• CA eHealth
• CA Spectrum

Issue/Introduction

Customer will be under-going disaster recovery for Spectrum and would like some assistance on how to swap the primary and secondary SpectroSERVERs.

Environment

Release :

Component : Spectrum Core / SpectroSERVER

Cause

n/a

Resolution

If at any point in time you want to see what the location server map looks like, from the SS-Tools directory, just run: ./MapUpdate -v

 

Run through each SpectroSERVER set individually...NOT at the same time, starting with the MLS pair.

 

1. Stop the Archive Manager on the primary and secondary SpectroSERVER

2. In OneClick, navigate to the VNM model in the Explorer view, open it and select the model below it (which is the LocalLscpe model).

3. In the Information view of the LocalLscpe model, open the "Loaded Landscapes" area.

4. Set the primary SS to precedence 30 in the Loaded Landscape view:

5. Wait 5 to 10 minutes -- THIS IS VERY IMPORTANT TO ALLOW LOCSERVER TO UPDATE

To determine when it's ok to continue, run the $SPECROOT/SS-Tools/MapUpdate -v to verify the locserver map now shows the primary has precedence 30. Check on a couple of the SpectroSERVERs. They should all show the primary now has precedence 30.

6. Remove the ArchMgr from the Locserver map with precedence 10. To do this, navigate to the SS-Tools directory

./MapUpdate -remove landscapehandle -p 10

./MapUpdate -remove 0x100000 -p 10

7. Start ArchMgr on the "new" primary SS and then on the "new" secondary SS.

8. Verify it adds the ArchMgr back in with precedence 30: $SPECROOT/SS-Tools/MapUpdate -v

9.  On ALL SpectroSERVERs, update the $SPECROOT/LS/.locrc and edit the MAIN_LOCATION_HOST_NAME=  to be the "new" primary.

 

Kill the LocServer process on all SpectroSERVERs, starting with the MLS and backup MLS.

If the map doesn't look correct on any of the SpectroSERVERs, kill the LocServer process again.

10.  Change the "locServerName=" in the $SPECROOT/tomcat/webapps/spectrum/META-INF/context.xml to point at the "new" mls

11. Cycle tomcat

 

That should be all you need to do then you can move onto the next pair - keep in mind that steps 9 and 10 only need to be done after the MLS swap.  

 

Tomcat cache will not be updated properly until the tomcat service is cycled. If you want to cycle it after each pair, that is fine but you MUST cycle it at the end again after all precedences have changed and all servers have swapped.

Additional Information

If at any time after waiting the 10 minutes you find locserver is not showing correct info, you can kill it and processd will start it back up.   Then run MapUpdate -v to see if it shows the proper info.

BACKOUT plan:

Shut down the SpectroSERVER and ArchMgr pair that you need to revert.

Reload the SSdb on both the primary and secondary server.

Remove the "old" precedence 30 entries from the location server map. For example:

./MapUpdate -remove landscapehandle -p 30

Start the primary SS back up.

Once the primary is back up, start the secondary.