...
| Code Block |
|---|
bundle exec rake avalon:migrate:repo |
When you run the migration in the command line, you can see a broad view of how much progress has been made for each Class. Notice the last line is called the "second pass". I'll explain that more later. Below is a table of options and their default values:
Command Options
| Option | Explanation | Example Usage | Default Value |
|---|---|---|---|
| CONFIRM | Required in order to prevent accidental execution | CONFIRM=yes | |
| pids | A comma separated list of Avalon 5.x Fedora 3 pids to migrate | pids=avalon:1,avalon:2,avalon:3 | |
| pidfile | Path to a filename containing one Avalon 5.x Fedora 3 pid per line | pidfile=/path/to/pidfile |
|
| parallel_processes | Number of parallel processes the migration tool should use | parallel_processes=4 | number of processors - 2 |
| overwrite | Determines whether: existing Fedora 4 objects should be kept, cleaned out, and reused (overwrite=true); or new objects should be created even if matching migrated objects already exist (overwrite=false) | overwrite=true | false |
Rerunning the migration
Once the migration is running, it is best to let it fully finish before attempting to rerun failed objects. The migration should fail objects that are missing parent or child objects. Once the migration is finished running, a list of the failed object ids can be collected into a file by running this command:
...
| Code Block |
|---|
bundle exec rake avalon:migrate:repo pidfile=failed_objects |
...
Potential Problems
First read the Migration Report and Results to determine what objects failed migration and why.
...