Rollback Process: Explanation, Potential Risks, and Steps

Introduction

Rollback Process:

• Standard Practice: Rollbacks are not typically performed, especially not weeks after an upgrade.
• Database Backup: The rollback process includes a database backup, but due to script and data changes, it may not always be feasible.
• Data Loss: Rollbacks can result in potential data loss and significant data re-entry from the point of the last database backup, usually from before the upgrade.

Live Environment Impact:

• Timing: Rollbacks, if needed, are usually performed immediately after an upgrade.
• Critical Issues: Rollbacks are initiated only in cases of critical issues where the system is inoperable, and no workaround exists.
• Downtime: The rollback process incurs downtime, rendering the system inaccessible during the procedure.

Rollback Duration:

• Typical Time: The rollback process usually takes around an hour.
• Extended Duration: The duration may extend if issues arise during the process.

Data Restoration:

• Backup Point: Data is restored to the point of the last database backup, with frequent increments.

Rollback Steps

Rollback Steps

Note: These steps are applicable to existing on-premises customers. For hosted sites, we will handle this process for you.

1. Stop Application Services

   • Use MediapulseAdmin.exe in the Instance folder or Services.msc to stop the services.

2. Rename Instance Folder

   • On the application server, rename the current instance folder to something else.
   • Locate the backup folder of the previous version and rename it appropriately (e.g., C:\MediaPulse\Live_Backup_v10.6.15633.1 to C:\MediaPulse\Live).

3. Restore the Database

   • Restore the database using a backup from before the upgrade.

4. Delete Deployment Files

   • Manually delete files from the deployment folder (C:\inetpub\wwwroot\mediapulseclient).

5. Redeploy Smart Client

   • Use the MediapulseAdmin.exe Tool to redeploy the Smart Client.

6. Amend Web.config

   • Modify the web.config file to refresh IIS.

7. Reinstall Smart Client

   • If the Smart Client has been downloaded and installed, uninstall and reinstall it on that machine.

8. Modify Version.txt

   • If the Smart Client has not been downloaded, change the version.txt file to a number before the previous version deployed (e.g., from 10.4.1001 upgrade to 10.6.1000, set back to 10.4.1000).