Contents Now Platform Administration Previous Topic Next Topic Roll back patch upgrades or plugin activations Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Roll back patch upgrades or plugin activations Use the Rollback Contexts module to roll back patch upgrades and plugin activations. Before you begin Rolling back is possible only between patches in the same software release. Rolling back is possible from London patch 2 to patch 1, but not from London to Kingston. Instances must be using Helsinki or later. Check with ServiceNow Technical Support before rolling back pre-London instances. The rollback must be done within seven days of the most recent upgrade.Use the glide.rollback.expiration_days sys_property to configure the number of days. The default is seven. You can only roll back to the previous version. For example, rolling back from patch 3 to patch 1 requires two rollbacks. Rollback only supports MySQL. Restore Deleted Records and Delete Recovery plugins must be activated. You can only roll back one active instance at a time. Rolling back contexts on multiple nodes is not supported. A rollback deletes data and may remove evidence of an upgrade or activation record, which makes it difficult to debug the problem that made the rollback necessary. To roll back to a patch version before the Assigned WAR, submit a request to ServiceNow Technical Support to do the rollback. Role required: maint Procedure Click Rollback & Recovery > Recovery Contexts > <context-you-want-to-rollback>. Under Related Links, click Rollback. Confirm the rollback. An indicator appears showing the progress of the rollback. glide.war updates to the rolled-back version. App node stats.do updates shortly after the rollback completes. The log shows the stages of the rollback process. After the rollback, restart the instance. Open a new tab and see if the context state changed to Rolled back. On this page Send Feedback Previous Topic Next Topic
Roll back patch upgrades or plugin activations Use the Rollback Contexts module to roll back patch upgrades and plugin activations. Before you begin Rolling back is possible only between patches in the same software release. Rolling back is possible from London patch 2 to patch 1, but not from London to Kingston. Instances must be using Helsinki or later. Check with ServiceNow Technical Support before rolling back pre-London instances. The rollback must be done within seven days of the most recent upgrade.Use the glide.rollback.expiration_days sys_property to configure the number of days. The default is seven. You can only roll back to the previous version. For example, rolling back from patch 3 to patch 1 requires two rollbacks. Rollback only supports MySQL. Restore Deleted Records and Delete Recovery plugins must be activated. You can only roll back one active instance at a time. Rolling back contexts on multiple nodes is not supported. A rollback deletes data and may remove evidence of an upgrade or activation record, which makes it difficult to debug the problem that made the rollback necessary. To roll back to a patch version before the Assigned WAR, submit a request to ServiceNow Technical Support to do the rollback. Role required: maint Procedure Click Rollback & Recovery > Recovery Contexts > <context-you-want-to-rollback>. Under Related Links, click Rollback. Confirm the rollback. An indicator appears showing the progress of the rollback. glide.war updates to the rolled-back version. App node stats.do updates shortly after the rollback completes. The log shows the stages of the rollback process. After the rollback, restart the instance. Open a new tab and see if the context state changed to Rolled back.
Roll back patch upgrades or plugin activations Use the Rollback Contexts module to roll back patch upgrades and plugin activations. Before you begin Rolling back is possible only between patches in the same software release. Rolling back is possible from London patch 2 to patch 1, but not from London to Kingston. Instances must be using Helsinki or later. Check with ServiceNow Technical Support before rolling back pre-London instances. The rollback must be done within seven days of the most recent upgrade.Use the glide.rollback.expiration_days sys_property to configure the number of days. The default is seven. You can only roll back to the previous version. For example, rolling back from patch 3 to patch 1 requires two rollbacks. Rollback only supports MySQL. Restore Deleted Records and Delete Recovery plugins must be activated. You can only roll back one active instance at a time. Rolling back contexts on multiple nodes is not supported. A rollback deletes data and may remove evidence of an upgrade or activation record, which makes it difficult to debug the problem that made the rollback necessary. To roll back to a patch version before the Assigned WAR, submit a request to ServiceNow Technical Support to do the rollback. Role required: maint Procedure Click Rollback & Recovery > Recovery Contexts > <context-you-want-to-rollback>. Under Related Links, click Rollback. Confirm the rollback. An indicator appears showing the progress of the rollback. glide.war updates to the rolled-back version. App node stats.do updates shortly after the rollback completes. The log shows the stages of the rollback process. After the rollback, restart the instance. Open a new tab and see if the context state changed to Rolled back.
