You can run more than one discovery at the same time, which is called concurrent discovery. For example, because a large discovery can take several hours to complete, you might want to start smaller discoveries before the large discovery completes. Before you run concurrent discoveries, you must correctly configure them.
You can run a concurrent discovery using a different discovery profile than the one used to start the first discovery.
To manage concurrent discoveries, use the Discovery Management Console or the api.sh script. For more information about using the api.sh script, see Command-line interface API.
You can run concurrent discoveries on the same target system. If two or more discoveries are monitoring some of the same IP addresses, each discovery operates independently.
If a password change occurs while a discovery is running, and a concurrent discovery is started, the sensors in that concurrent discovery will immediately use the new credentials, assuming that those sensors did not start before the password change occurred.
TADDM does not support concurrent discovery with a profile-based access list.
If changes are made to the custom server template while a discovery is running, any concurrent discovery that is started continues to use the existing version of the custom server template. The next separate, and non-concurrent, discovery that is started uses the new version of the custom server template.