What happens if you clone with different versions between instances

[Ereshkigal]

Hi.

I'm learning about upgrading and cloning for the Tokyo release.

Ask me about clones.

It's a little exaggerated, but will the clone not be executed or fail if the versions are different between the instances due to schedule reasons?

In the first place, as a premise, if there is a description such as not cloning with different instances, I would like you to cooperate.

ex)
・Source Instance：SanDiego
・Target Instance：Tokyo

Thank you!

[Maik Skoddow]

Hi

the documentation on https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/managing-data... says:

"The System Clone application can target an instance running a different instance version from the source."

But to be honest to prevent any additional troubles I would make sure, that both instances are on the same version

Maik

[Tony Chatfield1]

Hi, a clone overwrites the target, so the target instance becomes a copy of the source and will function just like the source.
Normally you would expect your source (production) instance to always have the earliest or same release  installed, and the target would only be different if a patch or upgrade had been deployed to it for testing\validation prior to the production instance being upgraded.

[Dipu Joy]

As clones are done using the backup of the Source instance; after the DBI Restore, the nodes will be downgraded/upgraded based on the glide.war property of the restored DBI. This will make sure that after the clone the target instance will be on same version as the Source instance.

[Rain Vaine]

Hello @Dipu Joy 

If the target instance is in the latest version (Xanadu) and source instance is in older version (Washington), is it possible for the target instance to still be unavailable after it shows 'completed' in source?
To give you additional information, what we also performed is a full clone.

Regards,
Vaine