How to fix "SyngoDB error 2" during V6->V7 Upgrades
The error is rare, but if it happens this is how you can fix it.
Upgrading from Syncplify Server! v6 to v7 is usually a smooth, fully automated process. In fact, after collecting telemetry from thousands of real-world upgrades, we can confirm that more than 99.7% of transitions from V6 to V7 complete without a single glitch.
However, a small subset of customers (fewer than 0.3%) may encounter an issue during the migration of SyngoDB data. When this occurs, the installer’s log file will typically contain a line similar to this:
rpc error: code = Internal desc = syngodb: failed to export indices: kvstore: not found
If you run into this, don’t worry: nothing is broken, and your data is perfectly safe. What’s happening is that the V6 installation being migrated contains unexpected or legacy leftover metadata that the old SyngoDB version doesn’t recognize. This condition isn’t introduced by the V7 installer, it simply reflects older or inconsistent index data already present in that particular V6 instance.
Fortunately, there is a simple and reliable solution.
The 2-Step Fix
Update your existing V6 installation to the final V6 release
Download and install Syncplify Server! v6.2.60, which is the last and most stable V6 build we ever shipped.Run the V7 installer again
Once V6 is on v6.2.60, restart the V7 setup process. In every reported case, the upgrade has completed successfully after this step.
That’s it. No manual DB edits, no special tools, no risky operations.
Why The Extra Step?
The final V6 release (v6.2.60) includes several improvements to SyngoDB’s internal housekeeping routines. When you upgrade to 6.2.60 first, the built-in maintenance logic automatically normalizes the indices and metadata that older V6 versions may have left behind.
By the time you run the V7 installer again, the database is in a perfectly consistent state, and the upgrade proceeds exactly as expected.
And remember: more than 99.7% of all upgrades run smoothly even without this extra step, so chances are you will never even need to do this.
In conclusion
Even though this situation is extremely rare, and stems from pre-existing data conditions rather than anything introduced by V7, we still want every customer to have a smooth and stress-free upgrade experience.
If you encounter this message and the steps above don’t resolve it, our support team is always happy to help. Just open a ticket, include your upgrade logs, and we’ll guide you through it.
Upgrading mission-critical systems can be stressful, we get that. And we want you to know that Syncplify is fully committed to making your transition to V7 as seamless and reliable as possible.