- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2022 07:31 AM
Are there any disadvantages if I UPGRADE using Clone technique?
currently we have DEV, QA and PROD.
I have cloned DEV from PROD. Upgraded my DEV, worked on all the issues in DEV. Now DEV is ready.
What if just clone DEV over QA, so that QA gets upgraded based on the clone?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2022 07:39 AM
ServiceNow does support cloning from a lower version to a higher version.
As you started with a clone from PROD to DEV, you should not encounter any significant issues cloning DEV to QA after the upgrade however - the best practice is generally to perform the upgrade in DEV, document all necessary fixes, perform the upgrade in QA and once again apply the same fixes - this gives you a good dry-run for your upgrade in PROD.
You would never want to upgrade PROD in this manner however and would always want to apply the upgrade manually.
In short, you could take this approach, but it would be recommended that you work through the upgrade in QA the same as you've done in DEV.
I hope this helps!
If this was helpful, or correct, please be kind and mark the answer appropriately.
Michael Jones - Proud member of the GlideFast Consulting Team!
Michael D. Jones
Proud member of the GlideFast Consulting Team!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2022 05:49 AM
As the clone is, indeed, applying the upgrade to the instance if you clone DEV (higher) to QA (lower) - if you preserve MID Server data on QA it will trigger those MID Servers to upgrade, just as if you otherwise scheduled the upgrade.
The primary drawback to upgrading QA via clone, as has been mentioned, is that you lose the opportunity to properly test and validate your upgrade process and fixes before attempting the same in PROD. Ideally you would repeat the process (Clone PROD to QA, apply the same set of fixes you applied in DEV, and validate) so as to ensure you have captured everything properly and encounter no issues the second time.
From a technical perspective there should be no functional difference between applying the upgrade in QA, or cloning the QA from the already upgraded DEV (which is itself a clone of PROD to which you have applied the upgrade).
I would ask the question why you would like to so, as opposed to using QA as an opportunity to validate your upgrade process at least once before applying it to PROD directly? To be clear, you will need to manually upgrade Production in the end, so why not practice on QA?
I hope this helps!
If this was helpful, or correct, please be kind and mark the answer appropriately.
Michael Jones - Proud member of the GlideFast Consulting Team
Michael D. Jones
Proud member of the GlideFast Consulting Team!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2022 10:57 AM
Thank you so much
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2022 12:14 AM
Plus you'll need to check that you've captured all of your fixes in appropriate update sets and work instructions for when you upgrade Production. The best way to do this is to treat QA like it's a Production upgrade - upgrade it in-place and apply your update sets and work instructions from Dev. If that doesn't work then you'll need to go back to Dev to refine them. Trying to upgrade through clone (which isn't possible anyway) would not give you a good guarantee that your Production upgrade will go smoothly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2022 10:56 AM
Thank you
