Backout and Rollback Procedures Overview of Backout and Rollback Procedures The rollback plan for VistA applications is complex and not able to be a “one size fits all” solution. The general strategy for a VistA rollback is to repair the code with a follow-up patch. The development team recommends that sites log a Remedy ticket if it is a nationally released patch. If not, the site should contact the product support team directly for specific solutions to their unique problems. Backout Procedure During the VistA installation procedure of the KIDS build, the installer can back up the modified routines using the a Transport The installer can restore the routines ‘Backup Global’ action. using the MailMan message that was saved prior to the installation of the patch. The backout procedure for global, data dictionary and other VistA components is more complex and will require issuance of a follow-up patch to ensure all components are properly removed. All software components (routines and other items) must be restored to their previous state at the same time and in conjunction with the restoration of the data. This backout process may need to include a database cleanup process. Please contact the product support team for assistance if the installed patch that needs to be backed out contains anything at all besides routines before trying to backout the patch. If the installed patch that needs to be backed out includes a pre or post install routine, please contact the product support team before attempting the backout. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, you may elect to use the following option: Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. Note: When prompted for the INSTALL enter the patch #. Rollback Procedure The rollback procedure for VistA patches is complicated and may require a follow-up patch to fully roll back to the pre-patch state. This is due to the possibility of Data Dictionary updates, Data updates, cross references, and transmissions from VistA to offsite data stores. Please contact the product development team for assistance if needed.
Backout and Rollback Procedures Overview of Backout and Rollback Procedures The rollback plan for VistA applications is complex and not able to be a “one size fits all” solution. The general strategy for a VistA rollback is to repair the code with a follow-up patch. The development team recommends that sites log a Remedy ticket if it is a nationally released patch. If not, the site should contact the product support team directly for specific solutions to their unique problems. Backout Procedure During the VistA installation procedure of the KIDS build, the installer can back up the modified routines using the ‘Backup a Transport Global’ action. The installer can restore the routines using the MailMan message that was saved prior to the installation of the patch. The backout procedure for global, data dictionary and other VistA components is more complex and will require issuance of a follow-up patch to ensure all components are properly removed. All software components (routines and other items) must be restored to their previous state at the same time and in conjunction with the restoration of the data. This backout process may need to include a database cleanup process. Please contact the product support team for assistance if the installed patch that needs to be backed out contains anything at all besides routines before trying to backout the patch. If the installed patch that needs to be backed out includes a pre or post install routine, please contact the product support team before attempting the backout. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, you may elect to use the following option: Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. Note: When prompted for the INSTALL enter the patch #. Rollback Procedure The rollback procedure for VistA patches is complicated and may require a follow-up patch to fully roll back to the pre-patch state. This is due to the possibility of Data Dictionary updates, Data updates, cross references, and transmissions from VistA to offsite data stores. Please contact the product development team for assistance if needed.
ib_2_0_p525_rn.docx