Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2024-06-30 16:55:07 +02:00
Code Issues Projects Releases Wiki Activity
d0648efbb9
harbor/docs/migration_guide.md
Henry Zhang d0648efbb9 update migration guide
2017-01-23 21:17:06 +08:00

3.8 KiB
Raw Blame History

Harbor upgrade and database migration guide

When upgrading your existing Habor instance to a newer version, you may need to migrate the data in your database. Refer to change log to find out whether there is any change in the database. If there is, you should go through the database migration process. Since the migration may alter the database schema, you should always back up your data before any migration.

If your install Harbor for the first time, or the database version is the same as that of the lastest version, you do not need any database migration.

NOTE: You must backup your data before any data migration.

Upgrading Harbor and migrating data

  1. Log in to the host that Harbor runs on, stop and remove existing Harbor instance if it is still running:

    cd harbor
docker-compose down

  2. Back up Harbor's current files so that you can roll back to the current version when it is necessary.

    cd ..
mv harbor /tmp/harbor

  3. Get the lastest Harbor release package from Github: https://github.com/vmware/harbor/releases

  4. Before upgrading Harbor, perform database migration first. The migration tool is delivered as a docker image, so you should pull the image from docker hub:

    docker pull vmware/harbor-db-migrator

  5. Back up database to a directory such as /path/to/backup. You need to create the directory if it does not exist. Also, note that the username and password to access the db are provided via environment variable "DB_USR" and "DB_PWD"

    docker run -ti --rm -e DB_USR=root -e DB_PWD=xxxx -v /data/database:/var/lib/mysql -v /path/to/backup:/harbor-migration/backup vmware/harbor-db-migrator backup

  6. Upgrade database schema and migrate data:

    docker run -ti --rm -e DB_USR=root -e DB_PWD=xxxx -v /data/database:/var/lib/mysql vmware/harbor-db-migrator up head

  7. Unzip the new Harbor package and change to ./harbor as the working directory. Configure Harbor by modifying the file harbor.cfg, you may need to refer to the configuration files you've backed up during step 2. Refer to Installation & Configuration Guide for more info. Since the content and format of harbor.cfg may have been changed in the new release, DO NOT directly copy harbor.cfg from previous version of Harbor.

  8. Under the directory ./harbor, run the ./install.sh script to install new Harbor instance.

Roll back from an upgrade

For any reason, if you want to roll back to the previous version of Harbor, follow the below steps:

  1. Stop and remove the current Harbor service if it is still running.

    cd harbor
docker-compose down

  2. Restore database from backup file in /path/to/backup .

    docker run -ti --rm -e DB_USR=root -e DB_PWD=xxxx -v /data/database:/var/lib/mysql -v /path/to/backup:/harbor-migration/backup vmware/harbor-db-migrator restore

  3. Remove current Harbor instance.

    rm -rf harbor

  4. Restore the older version package of Harbor.

    mv /tmp/harbor harbor

  5. Restart Harbor service using the previous configuration.
    If previous version of Harbor was installed by a release build:

    cd harbor
./install.sh

    If your previous version of Harbor were installed from source code:

    cd harbor
docker-compose up --build -d

Migration tool reference

  • Use help command to show instructions of the migration tool:

    docker run --rm -e DB_USR=root -e DB_PWD=xxxx vmware/harbor-db-migrator help

  • Use test command to test mysql connection:

    docker run --rm -e DB_USR=root -e DB_PWD=xxxx -v /data/database:/var/lib/mysql vmware/harbor-db-migrator test