Post-clone Discovery configuration
Summarize
Summary of Post-clone Discovery configuration
When cloning a ServiceNow instance, Discovery schedules from the source are copied to the target instance, but additional configuration is required to ensure these schedules operate correctly. This is essential for maintaining optimal performance of both Cloud-based and IP-based Discovery schedules post-clone.
Show less
IP-based Discovery Schedules Configuration
After cloning, the configuration you perform depends on the MID Server selection method used in the original Discovery schedule:
- Specific MID: Update the MID Server record for each Discovery schedule on the target instance.
- Cluster: Create the cluster, attach MID Servers to it, and update the cluster name in each Discovery schedule. Alternatively, remove the MID cluster record from the Clone Exclude Tables to clone the cluster.
- Use Behavior: Create or attach the required behaviors and functionalities on the target instance, then link them to the Discovery schedules, as these are not cloned automatically.
- Auto-select: Verify that all MID Servers on the target instance are properly configured with the correct IP ranges, supported applications, and capabilities.
Cloud Discovery Schedules Configuration
Post-clone, you must update the Cloud Service Account records to reference the correct Discovery credentials and update MID Servers used by Discovery schedules. Similar MID Server selection methods apply as with IP-based Discovery:
- Specific MID, Cluster, Use Behavior, Auto-select: Follow the same update and verification steps as for IP-based Discovery schedules, ensuring proper setup on the target instance.
Credential and MID Server Considerations
- Credential aliases are cloned, but their credentials are not. You must verify and update credential aliases to point to the correct credentials on the target instance.
- No MID Server related tables are cloned. MID Servers must be reconfigured or recreated on the target instance.
Why This Matters
Proper post-clone configuration ensures Discovery schedules function as intended, avoiding failures and maintaining accurate discovery data. This prevents operational disruptions and supports ongoing IT infrastructure management.
When a clone occurs, Discovery schedules are copied from the source instance to the target instance. Additional configuration is necessary for these schedules to function correctly on the target instance, helping you properly configure Cloud-based and IP-based Discovery schedules and maintain optimal performance.
For general information about instance cloning, see the Clone FAQS-Frequently Asked Questions [KB0715621] article in the Now Support Knowledge Base.
For instructions on how to deactivate or cancel a Discovery schedule after creating a clone, see the A Post-Clone script to Deactivate and Cancel Discovery Schedules [KB0789119] article in the Now Support Knowledge Base.
Post-clone target configuration for IP-based Discovery schedules
After completing the Request a clone process, post-clone configuration is determined by the MID Server selection method you chose in the Discovery schedule on the source instance.
| MID Server selection method | Next steps |
|---|---|
| Specific MID | Update the MID Server record for each Discovery schedule. |
| Cluster | Create the cluster, attach the MID Server to the cluster, and then update the cluster name in the Discovery schedule. Alternatively, remove the MID cluster [ecc_agent_cluster] record from the Clone Exclude Tables [clone_data_exclude]. For more information, see Exclude a table from cloning (legacy). |
| Use Behavior | Create the behaviors, create a functionality or attach an existing functionality, then go back to the Discovery schedule and attach the behavior to the Discovery schedule. Note: Discovery functionalities aren’t cloned with an instance. |
| Auto-select | Verify all MID Servers on the target instance are set up with target IP ranges, supported applications, and capabilities. |
Post-clone target configuration for Cloud Discovery schedules
After completing the Request a clone process, you must access the Cloud Service Account [cmdb_ci_cloud_service_account] table and update the service accounts with the proper reference to the Discovery credentials. You must also update the MID Servers for the Discovery schedule. Additional post-clone configuration is determined by the MID Server selection method that you chose in the original Discovery schedule.
| MID Server selection method | Next steps |
|---|---|
| Specific MID | Update the MID Server record for each Discovery schedule. |
| Cluster | Create the cluster, attach the MID Server to the cluster, and then update the cluster name in the Discovery schedule. Alternatively, remove the MID cluster [ecc_agent_cluster] record from the Clone Exclude Tables [clone_data_exclude]. For more information, see Exclude a table from cloning (legacy). |
| Use Behavior | Create the behaviors, create a functionality or attach an existing functionality, then go back to the Discovery schedule and attach the behavior on the target instance. Note: Discovery functionalities aren’t cloned with an instance. |
| Auto-select | Verify that all MID Servers are set up with target IP ranges, supported applications, and capabilities. |
Clone Exclusions
Credential aliases are cloned but their credentials aren’t cloned. If Discovery schedules have credential aliases, you must go to the Connection & Credential Aliases [sys_alias] table and confirm the alias points to the correct credentials. After cloning, update the Discovery schedules and add credentials within the target instance.
Additionally, no MID Server related tables are cloned. For more details, see the MID Servers and Clones [KBKB0786475] article in the Now Support Knowledge Base.