At the moment we have a requirement to migrate all elements/services from one DMA to another inside a DMS.
Other than doing an export, deletion of old elements and re-import, is there a more reliable and quicker approach?
Hi Reza,
In System Center > Agents on the status tab, you have a migrate button which allows you to migrate element within your DMS.
More info can be found here: https://docs.dataminer.services/user-guide/Advanced_Functionality/DataMiner_Systems/Migrating_elements_in_a_DataMiner_System.html
Hope this helps.
Hi Ladan, correct that the DMA ID remains the same, but that’s no problem, that’s actually a good thing because you might use the DMA IDElement ID as reference in e.g. Visual Overviews. When this remains the same while migrating to another DMA, nothing needs to be modified.
This is how it works. When an element is being created it will get the DMA ID of the current hosting DMA followed by a unique element ID on that DMA, in other words: DMA IDElement ID. This combination of IDs is being used throughout the DMS to reference an element, e.g. also in Visio files. So, you never ever want to change this ID again. Therefore, when migrating an element to another DMA, this combination of IDs remains the same and everything keeps working as expected.
In other words, if you see a DataMiner IDElement ID combination, the DataMiner ID only tells you on which DMA the element was originally created, but it could now be hosted on a completely different DMA. That’s what we call DELT, DataMiner Element Location Transparancy. A feature we introduced a long time ago in preparation for swarming.
Hi Wouter, Is that correct that when we perform migration, the DM ID from old DMA is also copied to migrated element in new DMA? If so, in case of migration, you can only migrate to the agent with the same DMA ID. Otherwise, better to rebuild everything if DM IDs of old and new agent are different. If you check migrated element property, you’ll notice that DM Id is still old DMA ID.