When importing multiple scan to JSM from cloud, the existing data is overwritten.

[Harla Batinovic]

I have two servers running Discovery Tool scans. They are uploaded via the cloud to the same Schema in JSM. They use the same token on both servers for the transfer. There is no overlap of servers being scanned.

Server 1:

• LINUX scan of 6 servers at 12:05 AM - takes about 5 minutes to scan
• Win scan of 6 servers at 12:20 AM - takes about 5 minutes to scan
• Win scan of 60 servers at 12:40 AM - takes about 2 hours to scan

Server 2:

• Win scan of 6 servers at 12:15 AM  - takes about 5 min
• Win scan of 56 servers at 1:00 AM - takes about 2 hours

All 5 server scans are imported into the same schema in JSM. However, when I look after they are completed, many of the status in Host tab say  NOT FOUND. 

It appears only last scan is showing the results and deletes the results from the other imports. 

Has anyone else had this issue and how did it get resolved? 

[Kristen Riddle]

It sounds like you're dealing with an issue where multiple Discovery Tool scans are being imported into the same schema in Jira Service Management (JSM), and the results are overwriting each other. The "NOT FOUND" status likely means that when the last scan is imported, it replaces the data from the previous scans instead of merging it.

By making a few changes to how you're handling imports and data, you should be able to prevent one scan's results from overwriting another's. Hopefully, this helps you get to the bottom of the issue!

[Chris Troyer]

Hi Kristen,

We are experiencing this same issue as well. We are running 7 separate scans sequentially overnight, and each scan causes the devices in the prior scan to be marked as Not Found.

Can you please provide some specific information on how we can change our imports and data to prevent later scans from marking devices in previous scans as Not Found?

Thank you for any help you can provide!