Non-Prod Cloning: Backup Timing and Sequence Questions

[LeighAnnB]

I need guidance or best practices around the cloning of non-production instances.

I have a clone scheduled tonight from Production → Test. I understand that the clone is based on the last nightly backup of the source instance (Prod), and that before the clone happens, a backup of the target instance (Test) is taken in case a rollback is needed.

We’ve had issues with previous clones, so I want to make sure everything transfers correctly before I schedule the clone for our Dev instance and to allow everyone an extra day to preserve their existing WIP work in DEV.

The guidance I was originally given was to clone Prod → Test → Dev. My concern is that if I follow this, the Dev clone will be based on Test’s backup BEFORE the Prod → Test clone, not the cloned data from Prod. My own logic dictates that I would need to wait a day between Prod → Test and Test → Dev to ensure the nightly backup captures the correct data.

Is this correct, or would it be better to clone Prod → Dev directly the next day?

Any advice or recommended best practices would be greatly appreciated.

[Dr Atul G- LNG · Accepted solution]

Hi @LeighAnnB 

Cloning Guidelines

Based on best practices and client-side recommendations, the cloning sequence should be followed as below:

• Production → Test

• Production → Development

❌ Avoid cloning Test → Development.

Rationale:
Production should always be considered the single source of truth. Therefore, all cloning activities must originate from the Production environment only.

[LeighAnnB]

thank you @Dr Atul G- LNG. 

I remember feeling like that information was wrong, but it was when we had just gone live with SN and I knew less than nothing.  We were still getting support from an outside implementation team and a continuing improvement team.  I probably just didn't know enough at the time and completely misunderstood them.  

Thanks for taking the time to reply and always being so quick!

[Dr Atul G- LNG]

Keep Growing!!