Back out a rolling upgrade

It is possible to back out configuration changes on a given server application instance, depending on the state of the configuration deployment on that instance.

About this task

Guidewire does not recommend that you back out an ongoing deployment on a server instance except in extraordinary circumstances. If you do so, you need to test that the server configuration returns to a safe state.

Procedure

  1. Open the Server Tools Upgrade and Versions screen.
  2. Click Initiate Backout.
  3. In the Shut Down New Nodes screen that opens:
    1. Review the screen and verify that there are no application servers that are running the new, target, configuration.
      If there are any servers running the new configuration, the screen lists the server IDs.
    2. After you shut down all of the servers listed on the screen, if any, click Refresh.
    3. After PolicyCenter verifies on-screen that there are no cluster servers running the new configuration, click Continue.
  4. In the Verify Typekeys screen that opens:
    1. Review the on-screen table for information on orphaned type keys.
    2. After you fix any listed issues, refresh the screen to verify your fixes.
  5. Click Start back out process.
  6. If the back out operation does not succeed, navigate to the Upgrade and Versions screen:
    1. Click the view icon for the attempted upgrade operation:
    2. Review the Upgrade Instance report that opens, paying especial attention to the items listed under Additional Information.
    3. If any of the listed items contains a clickable link, open that report and resolve any outstanding issues. For example, open the File Mismatches link, if available, and resolve any outstanding issues listed on the report.
  7. After you resolve any outstanding issues, click Initiate Backout on the Upgrade and Version screen again.
    If the back out process succeeds, the Upgrade and Version screens indicates that the back out operation was successful.