Migrate an anvi'o database or config file to a newer version.
🔙 To the main page of anvi’o programs and artifacts.
contigs-db profile-db pan-db genes-db genomes-storage-db structure-db modules-db workflow-config
This program does not seem to provide any artifacts. Such programs usually print out some information for you to see or alter some anvi’o artifacts without producing any immediate outputs.
This is a multi-talented program that seamlessly updates any anvi’o database to the latest version.
You can provide one or more anvi’o databases as command line parameters to this program, and it will migrate each one. However, you must choose whether to migrate the databases safely, or quickly.
If you choose to migrate safely, anvi’o will first make a copy of each database and save it as a backup. In case something goes wrong during the migration, it let you know what happened and will restore your original database from the copy it made. Then you can go on your merry way. (The copy is deleted after the migration script is finished running.)
This is how you migrate safely:
anvi-migrate --migrate-dbs-safely *.db
Of course, we will always suggest that migrating safely is better, because fewer people get angry at us when we do that. In practice though, making those backup copies takes up extra time and it is unlikely that the migration will fail anyway, so if you have a lot of databases to migrate and are okay with a bit of risk, you have the option to migrate quickly instead. In this case, anvi’o will not copy your databases before starting the migration.
anvi-migrate --migrate-dbs-quickly *.db
Please remember that by living life in the fast lane, you forego your safety net. On the rare occasion that the migration does fail, this program will let you know what happened, leave you with a database that has a
.broken file extension, and sassily remind you that this all could have been avoided if you chose the other option. In this unlikely event, you can always reach out to us. We will probably be sassy to you, too, but we will still see if we can help you unbreak things. :)
If your database is a few versions behind the highest available version but for whatever reason you don’t want to migrate it all the way, you can specify which version to update your database to. Just use the
-t flag (note: migrating with this parameter only works on ONE database at a time):
anvi-migrate --migrate-dbs-safely -t 15 CONTIGS.db
Then anvi’o will update your database until it is whatever version you specified and stop. Of course, you cannot provide a version number that is higher than the highest available version. Nor can you provide a number that is lower than your database’s current version (ie, backwards migration is not possible).
Not sure what your database’s current version is? Try anvi-db-info.
Not sure what the highest available version is? Run any anvi’o command with the
-v option to see the version information for all database types (we recommend
anvi-interactive -v for no particular reason).
Edit this file to update this information.
Are you aware of resources that may help users better understand the utility of this program? Please feel free to edit this file on GitHub. If you are not sure how to do that, find the
__resources__ tag in this file to see an example.