Hi Gregory,
The 1.6.x releases are quite old now and no longer supported, so you may or may not have some issues with the steps I’m about to describe.
I’m assuming you’re looking to move away from sqlite to something like MySQL while doing this. Under no circumstances should you ever use sqlite for production, as it’s not intended for access by more than one user at a time, its capabilities are limited, and it has very little protection against things like corruption and data constraints.
We have a couple management commands that may help for converting your database.
First, on the old server, run:
$ rb-site manage /path/to/site dumpdb > database.json
You will need to make sure nobody is writing to the database while you do this. I’d shut down the server temporarily.
On the second server, install exactly Review Board 1.6.11. You should not yet upgrade to 1.6.17. This is because you need both servers to match for the database conversion. You’ll then create a new site install using ‘rb-site install’, specifying MySQL or something as the database. It’ll ask you for information like an administrator account, etc., and then create the install.
After that’s done, run:
$ rb-site manage /path/to/new/site loaddb database.json
It should import into the database. You can then hook it up to Apache (especially for RB 1.6.x, I recommend this over lighttpd, as you will more than likely have new problems to deal with) and verify it’s working.
At that point, you can upgrade to any release of Review Board and it should work.
We can help more directly with getting you off an sqlite3 database on 1.6.x to something more modern (1.7.x or 2.0.x) if your company is interested in a support contract.
Christian