Roll back the package manually

You can use the Management of Change (MoC) Package tool (dnapackage) to roll back MoC package contents offline manually.

Note: To run the dnapackage rollback command, you must be a member of the DNA Authority - SCADA Emergency Package Admin group.

Only the most recent package can be rolled back from an MoC zone. If the change you want to roll back is not in the most recent package, repeat the rollback process until the package containing the change is rolled back.

Best Practice: If you want to undo a specific change from an MoC zone or set of MoC zones without rolling back an entire package, consider creating a new changeset/package with just that specific change applied and then publishing that single change.

To roll back the MoC package contents manually

1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

   Windows PowerShell for DNA opens.

2. Execute the following commands:

   set-silo RealTime

   dnapackage rollback --package <package file path>

   Where:

   • --package <package file path> is the fully qualified path to the package file you want to roll back on the system.

     For example: dnapackage rollback --package C:\temp\installed.pkg

If the command was successful, a message similar to the following will appear:

Successfully rolled back changeset 2

Successfully rolled back changeset 1

Successfully rolled back package from C:\temp\installed.pkg

Note: If the package rollback succeeds, the savedata command will be run on the RealTime computer where the changes were made, and the package status will be Rollback Successful in the MoC zone (for more information, refer to Understanding the status of an MoC package).

If the installation of a changeset within a package exceeds the InstallerInstallationTimeout interval, the package status will be Timed Out in the MoC zone. The Timed Out package status does not indicate that the installation of the changeset has failed, only the configured time out has elapsed for the installation of the current changeset, and manual intervention may be required to determine whether the installation is blocked. If the package store audit log is being updated with subsequent events after the time out event, installation is progressing, and no action is required. If the package store audit log does not show progress after waiting for a reasonable period, consider contacting the AVEVA Enterprise SCADA Support Team to determine how to proceed.