Migration from PRBv2 to v3 - Archived
Last updated
Was this helpful?
Last updated
Was this helpful?
This guide will show you how to migrate a PRBv2 deployment to PRBv3 using Docker Compose.
First, you should create a clean PRBv3 deployment by referring to this page:
Make sure it's running and the wm
should be running and listening on port 3001 by default.
Check your .yml
file of PRBv2 and set the docker image of lifecycle
component to phalanetwork/prb:git-current-v2
to receive the bundled migration script.
In the lifecycle
, the componentβs docker-compose configuration file should be like:
Then run sudo docker compose pull
.
Your will see the lifecycle should pull a new image and restart.
In the docker-compose folder of PRBv2's lifecycle
component, run:
To stop the PRBv2 and to run the migration script.
There you should use the same endpoint of what you wrote in wm.yml to replace the `http://127.0.0.1:3001`.
Now the migration is done, just waiting for the worker's beginning to start.
Before Migration, you must ensure that there can be no duplicate items in the names of the pools and workers. Includes but is not limited to worker names being equal to pool names.
PRBv2 supports PID #0, but PRBv3 does not support it.
This makes the migration fail if you want to migrate PID #0 from PRBv2 to PRBv3.
If your PRBv3 is running and migration from PRBv2 is also necessary. Before your migration, check it to avoid the 2 limitations above.
If your PRBv3 is brand new but may have some test data or you failed to migrate before, the previous test data or half-imported dirty data will result in poor synchronization results. Therefore, you need to:
First, stop PRBv3 by sudo docker compose down
Delete the inv
and po
folders.
Start the normal synchronization process from the start of this article.