The resulting database stores the transactions as though they were all sent to the primary node’s database.
The tool migrates both Tessera’s raw transactions and regular transactions.
We recommend backing up the primary database because the migration tool overwrites transactions with updated payloads and may not recover if errors occur during the migration. The secondary database is read only.
The tool takes both nodes’ (named
secondary) configuration files as input, which
contain the database credentials to connect; no other details in the configuration file is
To run the migration tool, run the following command:
./multitenancy-[version]/bin/multitenancy --primary <primary node configuration file> --secondary <secondary node configuration file>
After performing the migration, the primary node can be started with both nodes key pairs, and can decrypt the existing transactions using those keys.