Administration · LessonBy Praveen T, ServiceNow Trainer, 9 yrs · Published · ServiceNow · all levels
Instance clones
Refresh a sub production instance from production without losing work or leaking data.
Quick answer
Refresh a sub production instance from production without losing work or leaking data.
Key takeaways
- A clone replaces the target completely, back up work first
- Preservers protect environment specific records
- Exclude large log tables to shorten clone time
- Post clone checks belong in a written runbook
What a clone does
A clone copies production data and configuration over a target instance. Everything on the target is replaced, including update sets that were not committed and captured elsewhere. Plan the clone like a release, not like a refresh button.
Exclude and preserve
Two lists control the outcome. Clone exclusions skip table data, typically large log and audit tables. Data preservers keep target rows that must survive, for example the LDAP server pointing at a test directory, integration endpoints and MID server records.
Clone checklist
Run through this every time.
- Export or commit any update set on the target that is not already promoted
- Confirm preservers cover credentials, endpoints and email properties
- Announce a freeze window to developers
- After the clone, verify email sending is disabled and test integrations point at test systems
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What protects a target record from being overwritten by a clone?
Frequently asked questions
Do update sets survive a clone?
Only if they exist on another instance or were exported. Anything sitting only on the target is gone.
How do we stop test integrations calling production systems?
Preserve the connection and credential records on the target, and keep endpoints in properties you reset as part of the post clone routine.