Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Commit

Permalink
Add migration detail for Besu users and support language (#68)
Browse files Browse the repository at this point in the history
  • Loading branch information
Vijay Michalik authored Jun 2, 2021
1 parent 0a59bdc commit 4cc71d4
Showing 1 changed file with 15 additions and 4 deletions.
19 changes: 15 additions & 4 deletions docs/Tutorials/Migrating-from-Orion-to-Tessera.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,21 @@ description: Migrate your Orion configuration and data to Tessera.

## Migration Process

We recommend use of Tessera as a drop-in replacement private transaction manager in place of Orion.
As Tessera supports the same endpoints and functionality, nothing needs to be changed in your Besu deployment to migrate.
However, as Orion and Tessera can not communicate, you must stop all privacy-enabled Besu nodes in the network to perform the migration.
Besu nodes without an associated private transaction manager can remain live during this time.

A utility is included in Tessera which enables migration of an Orion configuration
file and database to a Tessera configuration file and database. No changes are required to the Besu configuration file to migrate.
file and database to a Tessera configuration file and database.

A full migration workflow would be as follows:

1. [Build](#build-migration-utility) or [download](#download-migration-utility) the migration utility.
1. Shut down the Orion and Hyperledger Besu nodes.
1. Shut down all privacy-enabled Besu nodes and Orion instances in the network (non-privacy-enabled nodes can remain active).
1. Perform [configuration and database migration](#migrate).
1. Start Tessera with the new configuration and database files.
1. Start Hyperledger Besu nodes.
1. Start Tessera instances with the new configuration and database files.
1. Restart all privacy-enabled Besu nodes in the network.

## Build Migration Utility

Expand Down Expand Up @@ -193,3 +198,9 @@ You must specify the following options in order to run the migration tool:
`password`= Target Tessera database password

`url`= Target Tessera database JDBC connection string

# Enterprise support

If you require support to undertake this process or any other use of ConsenSys Quorum software,
ConsenSys offers support subscriptions for Quorum to accelerate time to market and provide confidence in production networks.
Visit the following site to find out more: [ConsenSys Quorum Support](https://consensys.net/quorum/support/).

0 comments on commit 4cc71d4

Please sign in to comment.