v2 migration questions

Support
1

A couple of questions…

  1. Will it matter if some machines are still on 1.x and others are on 2.x as I can’t upgrade all my systems at the same time?
  2. Will all my existing configurations migrate over w/o needing changes (particularly partially synced folders)
  3. After migrating to 2.x will there be any cleanup needed to get rid of left over stuff from 1.x, or is this automatically handled?

Thanks, ex-Gooserider

2
  1. Mixed deployments are fully supported
  2. So far we’re only migrating the database on the first start. Just make sure that your UI client is compatible if you’re using one
  3. Nope. That should be handled by the migration routine
3
  1. The backup of the old database is left behind for possible disaster recovery.
1 Like
4
  1. Also make sure your command line options all use the double -- variant (e.g. --home instead of -home). Otherwise, if using the single - syntax currently, Syncthing will fail to start after the ugprade.
5

Can you make the upgrade to V2 optional. Reason is, all my end points run Synctrayzor and an automatic upgrade to V2 will kill all of those instances. I’m sure I won’t be the only person that has unattended Synctrayzors. Equally, I want V1 to carry on updating until V2 is live.

Hopefully the trayzor project will come good soon.

6

Automatic upgrades to new major versions are not done.

There was a bug where it might upgrade to a new major version on startup (but not on periodic upgrade checks), but that was fixed in 1.29.4(-rc.1).

When 2.0 releases, you will have to press this button to upgrade:

Upgrade To v2.0.0

If you have release candidate upgrades enabled you have to press this button (release candidate is already out):

Upgrade To v2.0.0-rc.19

5 Likes
7

This is literally the reason it’s 2.0.

2 Likes
8

OK, thanks for the clarifications…

ex-Gooserider

9

Beware if you’re using docker and you’re pulling

syncthing/syncthing:latest

Docker may upgrade you automatically if a re-pull is required.

syncthing/syncthing:1 if you want to remain on 1.x.

2 Likes