Understanding Disk/Capacity Alerts During Clone and Restore Operations<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article explains disk and capacity alerts that occur during or shortly after an instance clone or restore. For general database growth and capacity guidance, see Mastering Data Management in ServiceNow. Why this happens During a clone or restore, the platform allocates temporary space on the target instance's database host before the backup is restored. Per the clone workflow (Exploring Instance Clone), step 4, "Pre-Clone," prepares space for the new database before restoring it. This is expected, temporary disk/capacity growth, not a sign of a problem with your instance. Common cause: Normal transient spike If the disk/capacity alert coincides with a clone or restore you requested (or that was scheduled for your instance), no action is needed. The spike is self-clearing: Space usage rises during the Pre-Clone and Restore steps.Once the clone completes and Post-Clone cleanup scripts run, temporary space is released and usage returns to normal. Decision guide SymptomLikely causeActionOne-time disk/capacity spike, coincides with your own requested clone/restoreNormal Pre-Clone space allocationWait — self-clears after Post-Clone cleanupOne-time spike, no clone/restore on your instanceShared-host contention from a neighbor's cloneNot actionable on your sideRecurring connection-limit errors post-clone (not just a one-time spike)A known issue with capacity allocation during clone automationRequest a capacity review/upsize