Splunk Enterprise 10.4 documentation states there is no supported method for rolling back an installation to a prior release.
This is not only a policy position — it is tied to internal state changes introduced across recent versions that are not backward-compatible.
Two changes are the primary technical reasons why an in-place overwrite downgrade is unsafe:
1. Fishbucket checkpoint backend change (introduced in 10.2)
Fishbucket stores file-monitoring checkpoints. From Splunk Enterprise 10.2 onward, the Fishbucket database backend was replaced with a newer repository.
After upgrade, new checkpoints are written using the newer backend.
Overwriting with an older package can cause checkpoint loss, causing file-monitoring state to revert and re-ingest already-processed data, resulting in duplicate events.
2. KV Store engine and binary changes enforced by 10.4
Splunk Enterprise 10.4 removes MongoDB 4.2 binaries from the installation package and requires KV Store server version 7.0 or higher before upgrading.
Splunk Enterprise 10.2 and later can also move to KV Store server version 8.0. Overwriting a 10.4 installation with an older package can leave the system with mismatched binaries, data files, certificate expectations, or runtime assumptions incompatible with the downgraded version.
For these reasons, overwriting an older Splunk package onto an already-upgraded 10.4.x installation is not a supported recovery method.
Step 1 — Confirm the rollback warning in the 10.4 upgrade documentation
Review the About upgrading to 10.4 READ THIS FIRST page. The page states explicitly that there is no supported method for rolling back an installation to a prior release.
Step 2 — Review the Fishbucket backend change
Review the Fishbucket section in both the 10.2 and 10.4 READ THIS FIRST pages. Confirm the following:
Step 3 — Review the KV Store transition required by 10.4
Review the Upgrade the KV store server version page. Confirm the following:
Step 4 — Confirm recommended pre-upgrade preparation
Review the How to upgrade Splunk Enterprise page. Verify that Phase 1 of the documented procedure requires backing up configurations, indexed data, and KV Store, and validating that backups can be restored before the upgrade window begins.
Do not perform an in-place overwrite downgrade from Splunk Enterprise 10.4.x to an earlier version.
Once a 10.4.x instance has started and begun writing new state (fishbucket, KV Store, or other internal metadata), do not overwrite it with an older Splunk Enterprise package. Doing so can result in data corruption, KV Store failures, or an unrecoverable instance.
If you need to revert to a prior version, restore from a backup taken before the 10.4.x upgrade.
Pre-upgrade preparation
If critical issues occur after upgrading to 10.4.x
KV Store prerequisite checks before upgrading
Recommended upgrade best practice
Verification after following this procedure
Confirm the following after completing the upgrade process:
About upgrading to 10.4 READ THIS FIRST
About upgrading to 10.4 READ THIS FIRST — Fishbucket section
About upgrading to 10.2 READ THIS FIRST
Upgrade the KV store server version
How to upgrade Splunk Enterprise
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |