CA Service Management

I'm looking for different ways to do upgrade to 17.1 cumulative 1 from 14.1. We recently tried to upgrade and had issues with the installation and were unsuccessful.

We are trying to go to not only a new version but also High Availability at the same time. The biggest issue is the downtime/ready only access that our end users have to experience after we migrate the DB to the new SQL server. Ideally we would like to be able to do some kind of incremental data migration. The ideal scenario would be to copy the DB to the new SQL server, run the configuration of an existing install of 14.1 on the new servers to point to the new SQL server. Run the install for 17.1 on all servers, run the install of 17.1 cumulative 1 on all servers. Then migrate any data that has been added to the current SD SQL server in the time taken for the install over to the new DB.

Any suggestions greatly appreciated as we need to get this installed before the end of the year.

Your plan sounds like the Swing box method described in the documentation, you should check it out Upgrade CA SDM Using the SWING Box Method - CA Service Management - 14.1 - CA Technologies Documentation . Any issues appearing during the actual migration (on your test box) should be tackled/resolved with CA Support during your testing phase.

Thanks, Cristi.

Please also check out the CA Service Management 17.1 documentation on how to upgrade using Swing Box Method, and other perquisites & considerations while upgrading from lower versions to 17.1 

Use the Swing Box Method to Upgrade to CA SDM 17.1 - CA Service Management - 17.1 - CA Technologies Documentation

After looking at the Swing documentation, I guess my one follow up question would be, does the Swing method allow for incremental copying of the Production data? If we follow the Swing method and we still allow end users to enter data in the current SD production install, when the new version is finally on the new servers, is there a way to get that extra data that has been added since the time of the initial migration of data?

Thanks

Ben

Hey Ben,

Even with swing approach, basically you do have to stop SDM usage during the time the migration of SDM is going on.  It does not natively support any way to let the SDM instance be available for data manipulations and do incremental updates.

_R