Extra Long Clone Durations

[Erik Nelson]

Does anyone know why Clones are now coming in with a duration of 12 or 14 hours when historically they've been in the 4-6 hour duration quote and completion time? I've got some cloning coming up and slating it for 12 hours is a huge window to have to deal with.

[Tim Grindlay]

I've noticed this too and it's impacting our upgrade timeline as we can't schedule our clones and upgrades within a few hours of each other like we normally do. 

[christophenow]

Hello,

On our side, estimated clone duration rised to 5 hours, but in reality our clone was done in 1H30. There seems to be a huge delta (security margin? issue?) between estimation and reality. (at least on our environments). 

[Tim Grindlay]

Ours was estimated at over 17 and completed in approximately 2:30. I wonder if it has something to do with database compaction. We have been archiving and deleting a lot of data recently.

[Erik Nelson]

We haven't had much of that recently, but quoting 17 and then completing in a 2.5 is a wild range. For my upcoming clone I'm having to take the extra mitigation steps of starting it 6 hours earlier than I would have planned and doing an on-demand backup because I have work going live that morning. I'm sure it will still only take around 5 hours but not knowing where in that 12+ hour window things are going to happen is problematic.

[Tim Grindlay]

Something has changed on our instances in the last 24 hours. Our estimates are now back down to under 3 hours. I'm not sure if ServiceNow have fixed something on our instance or on their end, or if it's something we've done.