ESM migration does not update existing items

[Hakim Cherrat]

Hi,

 

Does anyone perhaps can explain how it's possible that if you migrate the same service with ESM from one environment to 2 separated production cluster environments, that on the second cluster the new service is not overwritten but instead is created beside the older service (older services have a lower version number 1.7.1.0 but the same custom resolution path's) ?
Also interesting to mention is that the service-id of the original service that has been migrated is not the same on both the first as on the second cluster

 

Snippet of the results of the ESM migration history tot the second cluster:

Label:  service-1.7.1.1-acp-prd Date:  2018-07-02 19:57:33 From:  3-ACP - server3 To:  6-PRD3 - server16 cluster

Migration Options:
Folders migrated: yes
New services enabled: yes
Existing items overwritten: yes

 

Migration Summary:
Destination folder: /
Services migrated: 23
Policy fragments migrated: 23

 

Migrated Data:
published service, service-a-1.7.1.1(#5b6df186326c23b8d6c13614685efdf9) was created
published service, service-b-1.7.1.1(#5b6df186326c23b8d6c13614685efeaa) was created
published service, service-c-1.7.1.1(#5b6df186326c23b8d6c13614685efee5) was created

 

Snippet of the results of the ESM migration history tot the first cluster:

Label:  service-1.7.1.1-acp-prd Date:  2018-07-02 19:56:15 From:  3-ACP - server3 To:  4-PRD1 - server09 cluster

Migration Options: Folders migrated: yes New services enabled: yes Existing items overwritten: yes   Migration Summary: Destination folder: / Services migrated: 23 Policy fragments migrated: 23   Migrated Data: published service, service-a-1.7.1.1(#86a5fbe33b80272156ab147872abc88b) was updated published service, service-b-1.7.1.1(#86a5fbe33b80272156ab147872abc977) was updated published service, service-c-1.7.1.1(#86a5fbe33b80272156ab147872abc815) was updated

 

Original service-id service

service-a-1.7.1.1 52b0f7edfd68248b99aaf783b70ec67c

service-b-1.7.1.1 52b0f7edfd68248b99aaf783b70ec72d

service-c-1.7.1.1 52b0f7edfd68248b99aaf783b70ec4cf

 

Thx

[Stephen Hughes]

Good afternoon,

 

The way that the ESM works is that when it migrates a new service to an environment it builds a mapping in the ESM database that tracks the corresponding service OIDs along with the policy GUIDs. If a service is created or migrated outside of the ESM, the ESM is unaware of the linkage so it will not update the existing service but create a new service and policy. We added the capability to remap environments that get out of sync either from using different methods of migration (GMU, CMT, etc) or creating new. To enable this option please review this KB article: Enterprise Service Manager (ESM): Error when migra - CA Knowledge 

 

Sincerely,

 

Stephen Hughes

Broadcom Support