Moving discovery artifacts across instances
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2020 05:27 AM
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
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2020 05:41 AM
Hi,
We have done this using update set. Big time no to import set.
I will suggest push everything to update set.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2020 07:17 AM
Thanks for your response, i dont see the option to add them to update sets, is that something i have to enable or how do i go about it?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2020 08:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2020 08:02 AM
I think it is a matter of preference which method you use to migrate the discovery data into a new environment. As Ashutosh Munot mentioned he used an update set. Our team just migrated Discovery a month ago into a new instance and found using XML was the easiest way for us to migrate the data.
If you use XML to move the discovery data, I suggest creating an XML file for each table and import the XML in the target instance in the following order:
- Discovery Schedules [discovery_schedule].
- IP ranges [discovery_range_item].
- Range set [discovery_range].
- Locations [cmn_location].