Phase 2 - Prepare for the development instance upgrade

For a better understanding of your production upgrade duration, request a clone of your production instance onto a non-production instance that has similar hardware and your full database. Confirm your current and target release versions, because you will later use this information when scheduling your upgrade in HI.

  1. On your production instance, create a system clone and select your development instance as the Target instance.
    The clone provides you with an exact copy of production. Performing an upgrade on your clone allows you to simulate an upgrade on your production configuration in a non-production environment. Refer to System clone for details.
    Important: For effective upgrade testing, use this clone to test on a system that reflects the production instance as closely as possible. If your non-production and production instances are the same size, include the production audit log and the attachment data on your production clone. To ensure that all production data is included with the clone, make sure that you clear all the Exclude check boxes on the Request Clone form. On your non-production instance, replicate typical user behaviors that occur on your production instance to enhance an estimate of your upgrade duration.
  2. Confirm the current release version of your production instance.
    1. Navigate to System Diagnostics > Stats > Stats.
    2. Locate the Build name, Build date, and Build tag.
  3. Confirm the target release version that you want to upgrade to.
    1. Match the build name to the release name in the release notes.
    2. Match the build date and tag to the build date and tag in the release notes.
  4. Set expectations for performance during upgrades.

    During an upgrade, your performance may be impacted because your nodes initiate the distribution upgrade. All nodes are restarted during an upgrade, but your multi-node instances are available during an upgrade because ServiceNow instances operate on a multi-node system. This multi-node system staggers node distribution upgrades, ensuring that there is at least one active pair of nodes for multi-node instances during an upgrade.

    To help you set accurate expectations for performance during upgrades, be aware of the differences between the nodes on your non-production and production instances. Instances with one node experience a short period of downtime during the upgrade, but multi-node instances do not have UI downtime. For details on your nodes and their status, see the Upgrade Progress screen.