Question regarding cloning

[GaneshErike]

Hi,

We are performing cloning to dev instance.

Already there are targets created for previous cloning by other associate.

In that, I have updated my username and passwd.

Now, our Dev is in washington version, but in targets, as war version it is showing as utah version, because dev was in utah while doing previous cloning.

Do I need to change that war version for dev to washington.

Please let me know your suggestions on this.

Thanks.

[Ankur Bawiskar]

@GaneshErike 

Few points below

1) good practice is to ensure target instance matches source instance version. this avoids compatibility issues

2) change the WAR version for the Dev instance to Washington. This will align the target instance with the current state of your Dev instance

go through the pre-clone and post-clone checklist here

When requesting clone, the 'war version' of the Standby Database mismatch the version of the source ... 

Post-Cloning Checklist 

Checklist before cloning an instance with Digest / SSO / SAML / Multi SSO Integration to prevent den... 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Dr Atul G- LNG]

Hi @GaneshErike 

Whenever cloning, please ensure that both instances are on the same version to avoid any issues during the cloning process. Since you're using the WAR version, you will need to change the WAR version in the dev instance before proceeding.

This might be helpful.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0697301