What is the best way to move Dynamic CI Groups from one instance to another and maintain the relationship on the svc_ci_assoc table?

[Cinlin]

I recently moved a bunch of Dynamic CI groups from Dev to Prod but the relationships on the svc_ci_assoc table did not follow in the update set so I ended up having to delete and rebuild them to get the relationship in the table to get them to work with alerts and show up on the operator workspace.

What is the best way to move the dynamic CI groups from instance to instance and keep the relationships?  

[Barry Kant]

Hi Cinlin,

the question suggests that your DEV is an exact copy as PROD if it comes to the CMDB, otherwise it doesn't make sense. The concept of Dynamic Ci Groups is that the svc_ci_assoc table is filled by schedule (5 min interval). Everything matching the query will be related within 5 minutes. 

You can export the svc_ci_assoc table based on the service_id, but it would require that all CIs on DEV are similar as on PROD, otherwise the CI sys_id doesn't match.

My personal opinion is that the alerts from DEV are not interesting on PROD, but maybe I overlook some use cases here. 

BR,

Barry

[suvro · Accepted solution]

Take xml export of CI Groups and svc_ci_assoc table and import it in  Prod

[Cinlin]

Thank you both we are starting to follow CSDM and build all of the new application services and dynamic ci groups in dev before we move them all up the stacks.  It has always been very hard to move the services and we end up having to recreate in every instance which is very time consuming.  I am going to try moving in xml files and export the svc_ci_assoc table.