Updates and Rollback
CDR Search Tool includes a managed updater designed to protect the existing installation before a new version is applied.
The project page lists the current release, version notes and SHA-256 checksum. The main download links to the current release. A permanent Full Licence includes future Call Records updates and remains valid for updates to that licensed installation. Preserve the data folder so the installation identity and licence survive the update.
Before updating
Before applying an update:
- Confirm the new version is intended for the installed release.
- Ensure sufficient free disk space is available.
- Avoid updating during an active operational investigation where possible.
- Confirm no manual file copy or antivirus action is holding application files open.
Compatibility check
The updater performs a compatibility check before applying an update.
Do not bypass compatibility warnings unless the release documentation explicitly instructs you to do so.
Pre-update backup
A backup copy is created before the update is committed. This provides the source for rollback if the new version fails validation.
Update validation
After updating:
- Confirm the application starts.
- Sign in.
- Confirm the expected version is displayed.
- Confirm the SFTP receiver state.
- Run a basic search.
- Review logs for startup or migration errors.
Rollback
If the updated build cannot be validated, use the managed rollback process to restore the previous working copy.
Rollback protects application continuity, but operators should still maintain normal backups for important configuration and data.