...
If the backup servers functionality is used, then backup servers should also be migrated at the same time.
The following notes provide more detailed guidance on the migration process.
This assumes you are migrating halfway through running some experiments, and want to continue where you left.
Steps for Old ecflow4 server:
shut-down
Code Block language bash title shutdown ecflow_client --shutdown
suspend all suites
Code Block language bash title suspend CL="ecflow_client --port 3142 --host machineX" for s in $($CL --suites); do $CL --suspend /$s; done
- wait for active/submitted tasks to complete
halt the server:
Code Block language bash title halt ecflow_client --halt
Use --migrate to dump state and structure to a file:
Code Block language bash title migrate ecflow_client --migrate > all_suites.def
- terminate server *or* leave the server running but start a new server on a different machine to avoid port number clash.
- remove checkpt and backup checkpt files, to prevent the new server from loading them
*Only* applicable if starting a new server on the same machine
Steps for New ecflow5 server:
module load the latest release
Code Block title Load latest ecflow > module load ecflow/5new > module load python3
start-server
Code Block ecflow_start.sh
load the migration file:
Code Block language bash title Load ecflow_client --load=all_suites.def
set server running:
Code Block language bash title restart ecflow_client --restart
resume suspended suites:
Code Block language bash title Resume CL="ecflow_client --port 3142 --host machineX" for s in $($CL --suites); do $CL --resume=/$s; done
However, the client/server/GUI between ecflow 4.x.x and ecflow 5.X.Y are not compatible.
Please see Switching between ecFlowUI version 4 and 5
The python api API remains backward compatible.
...