What is an instance clone?
A clone copies a source instance (usually production) to a target instance (usually dev or test). The target's database is replaced with the source's database. This gives your dev/test team a fresh copy of production data to work with.
What IS cloned
- All database records (incidents, users, CIs, configurations)
- Custom tables and their data
- Update Sets in the source instance
- Attachments (configurable)
- All custom code (Business Rules, Script Includes, etc.)
What is WIPED by default
- Integration credentials (HTTP credentials, OAuth tokens)
- Scheduled job execution history
- Email configuration (send is disabled post-clone)
- MID Server credentials
- Encryption keys (configurable)
Clone excludes (protect your dev config)
Before cloning, set up Clone Excludes for things you do NOT want overwritten. Common excludes:
- Your dev Update Sets (the clone would wipe them with prod's sets)
- Dev-specific integration endpoints
- Test user accounts
Navigate to System Clone > Exclude Tables and Exclude Records to configure.
Post-clone checklist
- Verify email sending is disabled (System Properties > Email)
- Reconfigure integration credentials
- Restart MID Servers and reconfigure credentials
- Set your current Update Set
- Verify scheduled jobs are paused or redirected appropriately
- Test critical integrations against test endpoints, not production
Clone frequency
Most teams clone quarterly or before a major development effort. More frequent clones give developers fresher data but require more post-clone reconfiguration effort.