Starting from NServiceBus Version 5.0 RavenDB is no longer the default persistence option in NServiceBus. A user has to explicitly select persistence. For more information, on the various available persistence options, read: Persistence in NServiceBus.
RavenDB-related code has been moved to a separate package NServiceBus.RavenDB and it is up to a user to install the RavenDB server from the official download page, following instructions on RavenDB website.
NServiceBus Version 4.x and 3.x used RavenDB for persistence by default. The NServiceBus license permits the use of RavenDB for the storage needs of the endpoint. This only includes NServiceBus-related data, such as sagas and subscriptions. If application-specific data is stored in RavenDB then the purchase of a separate license is required.
To use the default storage, ensure a RavenDB server is running to which the endpoint can connect. To set up and install RavenDB Download.
NServiceBus Versions 5.x: RavenDB is no longer auto-installed.
NServiceBus Versions 4.x: The
/ has been deprecated in Version 4.0 and above on NServiceBus.Host, and NServiceBus now expects RavenDB instance to be pre-installed and accessible to it. Use the powershell commandlets to install RavenDB on the needed servers. When the endpoints starts up, if the host is configured for RavenDB persistence and if the configured RavenDB persistence could not be contacted, then warnings will be logged.
NServiceBus Versions 3.x: RavenDB is included with the NServiceBus binaries (not ilmerged). When using the
/ switch on the NServiceBus.Host at install time, the infrastructure installer ensures that RavenDB is installed on the local machine. The install is only performed if the following is true:
- RavenDB persistence is configured for the endpoint
- A custom connection string is not specified by the user
- The current endpoint has no master node specified
- Port 8080 is available
- RavenDB is not already installed
When a master node is defined, NServiceBus understands that all data will be stored on that designated server instead. This means that the RavenDB server runs on that remote machine and not the local machine where the install is executed.
See also Administration of a RavenDB server.
To upgrade an existing RavenDB installation refer to the RavenDB upgrade process.
It is highly recommended to backup all databases before upgrading.
For a more detailed overview over the compatibility see RavenDB version compatibility.
NServiceBus.RavenDB greater or equal to Version 3.0.0 requires RavenDB Version 3.0 build 3660 or higher build number for Version 3.0.
NServiceBus.RavenDB smaller than Version 3.0.0 requires RavenDB Version 2.5 build 2908 or higher build number for Version 2.5.
Raven.executable on the machine and running it from the command line with
/. See Uninstalling RavenDB for full removal instructions. Note that the Version 2.5 download will be unlicensed, so a copy of the license.xml file needs to be taken from the Version 2.0 installation directory to the Version 2.5 installation directory. Contact Particular Software and request a Version 2.5 license file, or use a custom license file.
NServiceBus Version 4.0 is tested and compatible with RavenDB Version 2261 and RavenDB Version 2.
NServiceBus Version 3.X is tested and compatible with all RavenDB versions from Version 616 through version 992 and RavenDB version 1. It is strongly recommend using version 992 since it has better support for transaction recovery. Download version 992 here: RavenDB Server - 992.