RavenDB Upgrade

Question

I'm almost afraid to ask this question here because it seems like it should be readily available via google or on ravendb.net. However, I've been having a tough time finding out the proper way to upgrade my RavenDB to a new version. I'm currently running version 573 and want to upgrade to 616, simply for the ability to promote an index in Raven Studio.

What is the proper way to upgrade? Do I backup my DB, delete my entire Raven folder on the hard disk, then copy the new 616 version to that same folder area? Then restore the DB?

EDIT:

How I Upgraded RavenDB v573 to v960 (27-Nov-2012):

Note: Changing the MaxPageSize (step 7.b) is not recommended.

1. Run automated tests against local 960 to verify nothing breaks.
2. Back up 573 RavenDB
3. Install/unzip 960 to production server
4. Copy data folder from 573 to 960
5. Give user PrestoDatabaseUser full access to the data folder
6. Uninstall existing RavenDB service:
   a. sc delete RavenDB
   b. Rename old 573 folder to RavenDB-Build-573_deprecate
7. Set Raven.Server.exe.config (bring over any altered settings from the original config):
   a. <add key="Raven/AnonymousAccess" value="Get"/>
   b. <add key="Raven/MaxPageSize" value="2147483647"/>
   c. <add key="Raven/Authorization/Windows/RequiredUsers" value="domain\UserName"/>
8. Install as a service:
   a. C:\Software\RavenDb\RavenDB-Build-960\Server>Raven.Server.exe /install
9. Change RavenDB backup batch file to point to new 960 folder structure
   
10. If the services/apps aren't responding to the new RavenDB, restart them.

Answer 1

BobHorn,

The way I do it, on our production sites :-) 1) Stop the IIS site. 2) Replace the binaries 3) Start the IIS site.

If it is a big change, I also do a backup. But that is pretty much it.

Answer 2

In the past, I have installed RavenDB newer version as a IIS website completely separate from the old one. Then moved the data folder from old to new location. Then slowly phase the old one out (of course depending on your situation, you would change the appropriate IIS settings for the website as you keep phasing out old one)