Is there a way of copying instance configuration and data without cloning to another(NO Updateset or XML)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2022 11:51 PM
We have a requirement where client doesn't want us to clone the instance from our Base instance to target instance due to some security constraints. So I do like to know is there a way of copying the whole instance to another without cloning? or can we copy DB of our Base instance and then point it to target instance?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2022 12:01 AM
Hi
You can export XML for all records in a table. Navigate to the list of records you want to export. For example, type 'kb_knowledge.LIST' in the filter navigator box to open all of the kb_knowledge records in a new tab. Filter, if needed, to show only the articles you want to export. Export > XML as normal. It will export all of those records. Go to your target instance, from any list view (doesn't have to be kb_knowledge records, but easier to verify import if you are there), select "Import XML" from the menu option.
As far as Import Set table, you are creating the staging table, which will be a custom table. After you create the import set, you will create the Data Source and Transform Map. The transform map is where you will map from your custom staging table (u_kb_knowledge) to the actual ServiceNow table (kb_knowledge).
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2022 12:06 AM
Hi, this requirement is a bit confusing.
If the client does not want the instance cloned, then that indicates they do not want the instance copied. As far as security goes any options that are not clone based will be less secure as the data will flow through an environment external to the vendor data centre.
Perhaps someone needs to explain cloning and table exclusion to them properly?
They could also log a support request for SNC to restore a backup to a dev instance, which would be no different to cloning but may make them less paranoid.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2022 04:44 AM
Hi, Thanks alot for your response.
Cloning is what they don't want even reasons are not properly given and explained.
We can Copy the SQL DB of source instance and point it to Target instance, this is what I have got info on browsing but still not clear how exactly it will be executed and if they will be any data loss on the source instance. Hi Portal case has been raised .
Thanks for your inputs !!!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2022 01:31 PM
Cloning is not only the most secure solution, it is the vendor solution specifically designed to move configuration and data between instances.
Any alternatives for moving data between instances would be less secure as they must transverse external infrastructure.
Copying between instances also introduces additional risk as the target instance must be manually configured to mirror the sources configuration and data structure exactly.
If you are supporting a ServiceNow implementation for an irrational customer who will not listen to basic common sense then I would suggest finding another client ASAP, as it is your organizations credibility that will be at risk if you allow the client to dictate inappropriate actions and it goes wrong.
Perhaps if you provide a time estimate
< 5 minutes to set up an OOB clone.
< 1 hour to set up a clone, if you need to exclude data on specific tables.
100 hours + to configure and test an alternative solution that is less secure and may not work.