Moving discovery artifacts across instances

[Abbey2]

Hey guys, I have completed creating discoverys schedules, locations, ip range items and range sets in lower environment for discovery. What is the most efficient way to move them to the next instance. Update sets, xmls, import sets and in what order is best ? Thanks

[Abbey2]

Thanks Chuck, in order from 4 to 1 right? If i go this rout3, i'll need to to the discovery_schedule_range at position 0. Also, the mid servers, since they have different references has to be done manually? I have over 100 schedules, so thinking to do a import set for that after the schedule has been loaded

[Ashutosh Munot1]

HI,

Again, MID Server SYS id will be different in your instances. So you need to manually change them.

You have 100 scheduled right then i will again say put them into one update set along with ranges, etc and just import that one update set. Easy life.

If you want to do xml imports then you have to make sure you dont lose connections between them.

I will say dont import locations because the locations should be already there and must be common in all instance if you have the instance in sync

Thanks,
Ashutosh

[chuckm]

For these 4 tables, the order of import does not matter when using XML. The references between each table (sys_id) to the other tables is contained in the XML. Once all 4 XML files are imported everything will be linked up properly - you will not lose any connection between the tables.

For the MID servers moving to the target instance, update the config.xml on each MID server to re-point to the new target instance.  And yes - the MID servers will have a different reference (sys_id) and will have to be updated manually.

[cynlink1]

Would the tables for exporting Cloud Discovery schedules?